Transformations stall because leaders hide their doubt

I sit in enough steering committees to know the moment a transformation turns.

Nobody announces it.

The updates stay upbeat, the slides stay on schedule, and then around month nine the room gets quiet in a way it wasn't before, and nobody says why out loud.

Every operator I know has felt that shift and called it strategy drift. It is rarely strategy.

It is the person running the room, unwilling to admit that they aren’t sure anymore.

The stall always starts with the leader

Here is what I watch happen, over and over, inside a value creation plan running past its first year. The plan was fine, and so was the sequencing.

What changes is the leader running it, and specifically what they stop admitting. Early on they will admit a target might be wrong. By month six, admitting that costs too much, so they stop.

The team reads the silence as confidence and matches it, which is worse than reading it as doubt. Everyone keeps executing a plan the person in charge privately no longer trusts, because saying so now would mean explaining why they did not say so sooner.

The plan does not fail on a spreadsheet.

It comes apart in the space between what the leader believes and what the leader still says, and nobody moves to close it until the transformation has already stalled.

The 30% success rate never moved in fifteen years

MIT Sloan followed one leadership team for four years, through more than 300 interviews and 760 hours sitting inside their meetings, embedded there the entire time. The transformation failed.

Every stage traced back to the same behavior: the executives who felt the plan slipping stopped admitting it, then found a convenient group to blame instead, then ran a communication campaign nobody believed. The pattern has a name now: defensive organizing.

The number has barely moved in fifteen years. McKinsey’s surveys of transformation outcomes consistently find that fewer than one in three transformations succeed at both improving performance and holding onto the gain.

That ceiling shows up elsewhere, too. A BCG survey of 825 senior executives found a nearly identical success rate.

The pressure on the people leading those transformations helps explain what happens inside the room. In a global DDI study of more than 10,000 leaders, 71% reported increased stress since taking on their current role.

You do not need a hold period or a value creation plan to recognize this.

Any leader running a stalled product launch, a reorg that will not finish, or a turnaround that missed its first two milestones is living the same sequence.

The plan is not the problem. The point where you stopped saying you were not sure is.

The blame lands on the one who doubted first

Here is what it actually costs the person running the room. Not the transformation's ROI.

It costs them their own credibility.

Every quarter they keep executing a plan they privately doubt, they draw down the one thing holding the team together: the belief that the leader is telling the truth.

When the numbers finally force the conversation, in month nine or month fourteen, the room does not remember the warning signs they saw and did not raise. It remembers the run of confident updates that turned out to be false.

The CEO eventually said they felt set up. But they had set it up themselves by repeatedly choosing not to say what they actually thought. The team that once believed them spent the next year treating every update as a negotiating position rather than a fact.

That is the real cost, not the missed target. It is how long it takes to be believed again after everyone in the room has learned that you will not say it when you are not sure.

Name the doubt before month six

The move is not a survey and not an offsite.

It is one direct question, asked by the operating partner or the board chair to the person running the plan, ideally before month six: what part of this are you no longer sure about, not what is on track, not what needs more resources, but what they privately doubt and have not said yet.

Three things separate this from becoming another status update:

• Ask it one on one, away from the steering committee, where admitting doubt does not cost the leader in front of their own team.

• Ask it on a fixed cadence, not only once the numbers already look wrong, or the leader will only ever answer when it is too late to matter.

• Write the answer down and revisit it next quarter, so a walked back doubt becomes a tracked correction instead of a memory nobody can check.

None of this needs new reporting.

It needs deciding that hearing what is actually true is worth more than hearing what is reassuring, and asking for it before the room stops believing either one.