The One Change Nobody Manages Is the Leader's Own

In a transformation, the one person whose change nobody manages is the executive leading it

Every transformation programme has a change plan. There is a training schedule for the teams, a communication sequence for the managers, cut-over dates for the processes. Each line of the plan has someone watching someone else change: managers watch their people, the programme office watches the managers, the board watches the programme. One link in that chain is left empty. Nobody manages the change of the executive who is managing the change.

This is not an oversight. The programme assumes the executive has already changed, because they asked for it, designed it and explained it. The difference between wanting something and living through it disappears inside that assumption. Having designed a change is not the same as having been through it. The executive is the architect of the new arrangement and also one of the people who will work inside it, a second role with neither preparation nor a timeline.

The architect's blind spot

An architect knows the plans of a building better than anyone. That knowledge says nothing about what it is like to live there. The executive leading a change is in the same position. They know the logic of the new structure, its rationale, the result it should produce. They do not know how an ordinary Tuesday will feel inside it. In the first months the gap stays hidden, because the executive spends most of their time explaining the programme, and explaining feels like a substitute for living it.

We have written about the leader who changes their own role first from the team's side: a team reads not the plan but the consistency of the person presenting it. This piece looks at the same subject from the inside. Before any inconsistency shows, something else happens within the executive, and it is rarely given a name.

The executive's change happens first not in behaviour but in the definition of a good day

Every executive carries a definition of a good day, usually never written down. It is what lets them say, on the way home, that today went well. For a head of operations, a good day is solving before lunch a problem nobody else could crack. For a sales leader, it is winning over a difficult client at the table. The definition forms over years, and it matches whatever carried the person into the seat they now hold.

The old source of satisfaction

A transformation quietly cancels that definition. In the new arrangement others solve the problems and others win the clients over; the executive's job is to build the conditions in which they can. The behaviour plan says so, correctly. What it leaves out is where the executive will now get a good day from. The old source of satisfaction has closed and the new one has not yet opened. The weeks in between look successful from outside and feel strangely empty from within.

That emptiness is usually lived as fatigue or impatience. The executive finds the team slow and the meetings long, and finds reasons to take back a piece of the old job. Changing the behaviour without changing the definition of a good day leaves every evening feeling as though something is missing. The feeling is not a sign of failure. It is a sign that the change has not yet reached the executive.

Noticing what has shifted

The new definition arrives slowly and usually begins with a sentence: today went well because the right decision was made in a meeting I was not in. The executive who says this for the first time feels it not as a loss but as a kind of pride. The time it takes to reach it has nothing to do with the programme's timeline, and is generally longer.

Under pressure, the executive goes looking for the old good day

Until the new definition takes hold, every pressure calls the executive back to the old one. A bad quarter, an angry client, a missed delivery date: each offers a chance to do the work they know best. When they do it, they have a genuinely good day. That is the problem.

Three shapes of the return

The return is rarely experienced as a decision. It usually takes one of these shapes:

• Stepping straight into the field during a crisis and solving the problem by hand.
• Taking back, "just this once", a decision that had been handed to the new forum.
• Offering their own solution halfway through the team's account of theirs.

All three look like competence from outside, and often they work. But each lets the executive relive the old good day, and the taste of it sets the new definition back by a step. A return made under pressure reminds the executive that the old identity is still the safest place to stand. The team sees it too, but what the team sees is the behaviour. It does not see the relief inside.

This is why treating the returns as a discipline problem seldom works. The executive sets stricter rules, keeps them for a while and drops them at the first serious pressure. The rule is aimed at behaviour; what produces the return is satisfaction.

The executive's own change needs a timeline and a witness too

Two things written for every other part of the programme can be written for the executive's own change: a timeline and a witness. The timeline says when the change is expected to be complete. The witness makes sure that someone other than the executive can see whether it is happening.

A separate timeline

The executive's timeline cannot be the programme's. The programme builds the new structure in six months; the definition of a good day takes longer to move and is often halfway there when the programme closes. Accepting this from the start narrows the gap between what the executive expects of themselves and what they live. At the closing meeting the transformation is declared complete, while the executive's own transition is still in the middle. Knowing that is a relief.

A witness

A witness is someone who can name the executive's returns without judging them. It cannot be someone from the team, because the team is both witness to the executive's change and its subject. It can be a board member, a long-standing peer or a coach. The witness's job is to ask one question regularly: which days were good this week, and why. The executive learns whether the change has reached them mostly from how the answer to that question drifts.

The answer moves over months. At first the good days are the ones spent inside a crisis. Then comes a mixed period. At some point, for the first time, the good day described is one on which the executive solved nothing. That sentence appears in none of the programme's indicators, yet it shows best whether the transformation will last.

From the field

Executives who bring this subject rarely come to talk about themselves. They talk about a slow team, a delayed programme, a manager who resists. As the conversation goes on, part of the problem turns out to live in the executive's own evenings: the work is on track, but the days no longer feel as good as they did.

The question we ask first

In the first conversation we talk not about the programme but about the last two weeks. We ask the executive to describe their three best days. Often all three are days when part of the old job got done again. Noticing this is not an accusation; it is an honest measurement that the change has not yet reached them. The executive's own change begins when the place a good day comes from begins to move.

The work from there is to write a new definition of a good day together and to test it over months. How we work begins with this question. The leader who tires of the message shows another side of the same transformation, and our other pieces sit on the Perspective page.