The leader running a transformation changes the plan and leaves their own habits outside it
A corporate transformation begins with a presentation. The new structure is drawn, the new meeting rhythm is explained, the new measures are shared, and the leader tells the room: this is how we will work from now on. The plan is usually sound. The trouble sits outside it, in what the plan does not cover: the leader's own calendar, the questions asked before approving something, the place where attention still goes.
The person running the change tends to cast themselves as the owner of the programme. The team will change, the structure will change, the process will change. The leader is the subject of the change and not its object. That framing is natural and mostly unconscious. What the team sees, though, is not the content of the programme. It is what the person who presented it does the following week.
A team learns the new structure from a document and decides how seriously to take it by watching the leader. If the leader sets up the new forum and then keeps making decisions in the old room, the team works out very quickly which of the two is real. In a transformation the team reads the consistency of the person presenting the plan, and the plan itself comes second.
What gets read as resistance
Executives often reach for the word resistance and mean slowness or reluctance in the team. What we see in the field is usually a plainer reading: the team has noticed the gap between what the leader says and what the leader does, and has become careful. Caution looks like resistance, but it is a risk calculation. Someone who sees the old way still being rewarded will, at most, try the new one.
The leader's own change shows in three places: the calendar, the first exception and the story of the old way
Whether a change is real is settled between meetings, not in them. There are three places to look, and all three are in the leader's own hands.
The first is the calendar. A calendar is the one document that shows what a leader cares about without saying it. In the first three months of a transformation, the hours given to the new work and the hours still given to the old work sit side by side. When the old work holds more of them, the team follows the calendar and not the presentation, and it does so because it has read the calendar correctly.
The second is the first exception. Every new arrangement is tested once: an urgent client, a month-end that has to close, a trusted manager asking for just this once. If the leader grants the first exception, the team learns that the arrangement has exceptions, and nobody needs to wait for a second. The exception does not have to be a bad decision. The damage is that it replaces the written rule, and from then on nobody knows which of the two applies.
The third is the least noticed: how the leader describes the old way of working. "We used to be faster" is an innocent memory, but said in the middle of a transformation it announces that the new way is a loss. A leader can speak about the old way with affection. It only helps to know which door the story leaves open.
The team does not read the plan. It reads the person presenting it.
Letting go of the old role feels like a loss, so it is often put off
The leader's inconsistency rarely comes from bad faith. The old role was the mastery that brought this person to the seat. They knew which meeting to ask what, which figure was misleading, which call to take and when. A transformation makes part of that mastery unnecessary, and the leader becomes a beginner again in a field where they were the expert the day before.
The loss of mastery
For a senior person, being a beginner is quietly uncomfortable. The discomfort does not get spoken. Reasonable sentences take its place, such as "let us run the two systems in parallel for a while." Running in parallel can be necessary for a handover, but parallel running with no end date is letting go postponed.
How the delay shows
The postponement usually turns visible in three behaviours:
- The leader asks for the new report and keeps requesting the old one.
- A decision is taken in the new forum and sent back through the old channel for approval.
- A responsibility is handed over, and the leader goes on asking how the work is done.
None of these is a bad behaviour. Each marks a letting-go that has not finished, and the team sees it before the leader does. An old role that is not released stays inside the new one as a weight the team feels and cannot name.
The method is small: write down three things to release, and tell the team
Managing this pattern needs no new programme. A small, written and testable promise on the leader's own side of the change is enough.
Three sentences
Before the transformation starts, the leader writes three sentences: what they will stop doing, what they will ask differently, and which decision they will leave in someone else's hands. Each sentence is tied to a concrete behaviour. Not "I will trust more" but "I will not attend the weekly sales meeting." The logic runs opposite to Growing Means Holding Control at Three Points, where three things are chosen to hold. Here three things are chosen to release.
Telling the team
Three sentences kept by the leader remain an intention. Said to the team, they become a commitment, and the team has a concrete measure, for the first time, for pointing out an inconsistency. That can feel uncomfortable. Often the first inconsistency named is one the leader already knew about.
Sixty days later the leader asks the team two questions: which sentence did I keep, and which did I not. The answers stay short and are not debated. The aim is to make the invisible visible, not to give a grade. The stages in A Founder's Role Changes Three Times, Not Once can be read the same way: a role changes by being said aloud and tested again.
From the field
The subject usually enters the room as a complaint about the team: "they are resisting the transformation." The complaint is real, but the first place looked at is usually the wrong one.
What we do in the first session
In the first session we ask the leader to bring the calendar for the last two weeks. Together we count the hours given to the transformation and the hours that went to the old work. Often the leader stops talking when the number appears, because the gap between what the team was told and what the calendar says needs nobody to point it out.
Running a transformation means being able to say, before changing the team, which part of your own role will change. How we work begins with that count. The result often fits on a short sheet: three sentences and a date sixty days away.
The sheet does not complete the transformation, but it shows the leader in advance what the team will read, and what follows holds fewer surprises.