A founder essay. Across sixteen years of leading change inside operations, HR, and organisational development at Saudi enterprises, I have learned a lot of things. If I could go back and tell my younger self only one of them, this is what it would be.

I started leading change inside Saudi enterprises in 2009. Retail, F&B, startups, construction. I was, by most measures, competent. I had read the literature, I knew the frameworks, and I could deliver projects on plan. The change programmes I led delivered, mostly, what they were supposed to deliver.

What I did not know, at the time, is how much energy I was burning to deliver them. The change was happening, but the cost of producing it, in my own time, attention, and personal capacity, was significantly higher than it needed to be. I was treating every transformation programme like a problem to be solved through individual force. I was the change leader. The work was on my desk. The harder it got, the harder I worked.

If I could go back to 2009 and tell my younger self one thing, it would be this: the change you are trying to lead will not be delivered by you. It will be delivered by the system you build to deliver it.

This sounds like a slogan. It is not. It is the lesson that took me a decade to learn, and that transformed how I approach every senior engagement now.

What I used to do

When I was given a change mandate, my first instinct was to understand it deeply, build the plan, and start executing. I treated the plan as the thing. The plan was rigorous. It had milestones, dependencies, risks, mitigations. I would brief stakeholders. I would communicate. I would manage upward. I would absorb resistance. I would push.

This worked. The change happened. What I did not see was that I was the only person whose effort was indispensable. If I had stepped away for a month, the programme would have stalled. The system that was supposed to deliver the change was, in practice, me applying personal force to a structure that depended on me to keep moving.

For some changes, this was fine. For most of the changes I was being asked to lead, it was the wrong design.

What I would do differently

The shift, when it eventually came, was structural rather than personal. I stopped asking "how do I deliver this change" and started asking "what system needs to exist for this change to deliver itself."

The questions are not equivalent. The first one assumes the change leader is the engine. The second one assumes the change leader is the architect of an engine that runs without them.

In the second framing, the work looks different from the start.

Sponsorship is not a relationship to manage. It is a structure to build, with named owners, formal cadence, and explicit decision rights. When the change needs a decision, there is a body whose job is to make it. The change leader does not need to convene that body each time. The body exists.

Communication is not something the change leader produces. It is a capability the organisation has been given, with trained people, repeatable formats, and a feedback loop. The change leader oversees it. They do not personally write every memo.

Resistance is not a problem to be addressed in real time by the change leader. It is a predictable phenomenon that the system has been designed to surface, route, and resolve, often before the change leader hears about it.

Reinforcement is not an event at the end. It is a function inside the organisation that has been built into how performance is measured, how managers are coached, and how feedback is given.

In other words, the change leader stops being the person doing the change. They become the person who designed the conditions under which the organisation can do the change to itself.

What this changed

Two things changed when I started operating this way.

The change happened more reliably. Not because I worked harder, but because the system did not depend on any one person's effort to keep moving. People got sick. People left. Priorities shifted. The system absorbed all of it.

The cost to me dropped dramatically. I stopped being the human bottleneck of the programmes I was leading. The hours did not necessarily decrease, but the kind of hours changed. I was doing strategic and design work, not heroic operational work. I was sustainable in roles that previously would have burned me out by month nine.

This is the lesson I now coach senior leaders through, in different forms, almost every week.

Why this is hard for senior leaders

Senior leaders, by the time they reach the role of leading transformation, have usually been promoted because they were the person who could carry hard things alone. The pattern is rewarded for fifteen years. Then the role changes, and the pattern that got them there starts costing them.

Letting go of personal force as the primary delivery mechanism is uncomfortable. It feels like abdication. It is not. It is the senior version of leadership, where the leader's job is to build the conditions for delivery rather than to deliver.

The senior leaders I coach often resist this initially. They say it sounds slow. They say their people are not ready. They say the change cannot wait for the system to be built. Sometimes they are right. More often they are protecting the comfort of being the person whose effort is indispensable.

The shift, when it lands, takes pressure off the leader and produces better outcomes for the organisation. It is the most reliable senior development move I have personally seen.

The bottom line

I would not change the projects I worked on between 2009 and 2018. I learned what I needed to learn. I would tell my younger self, if I could, that the work was not to push harder. The work was to build the engine that would push without me.

For senior leaders evaluating their own current change mandate, the honest question is: if I stepped away for a month, would this still be moving? If the answer is no, the design needs to change before the leader does.

This is what most of my senior coaching engagements end up being about.

---

Begin a confidential conversation. Schedule a discovery session

FAQ

What is the most common mistake change leaders make? Treating themselves as the engine of the change rather than the architect of the system that delivers it. This pattern delivers change at high personal cost and produces brittle outcomes that depend on the change leader's continued presence.

How does a senior leader build a self-sustaining change system? Through structured sponsorship bodies with named decision rights, distributed communication capability rather than personal communication, designed-in resistance management, and reinforcement built into measurement and management practices. The leader oversees the system rather than running it personally.

Why do senior leaders resist this shift? Because the pattern of personal force has typically been rewarded for fifteen or more years before the leader reaches transformation roles. Letting go of personal force as the primary mechanism feels initially like abdication, even though it usually produces better outcomes.