The crossing an organization has to make, from a model built for stability to one built for continuous change, is real, and it has been done at scale. But organizations rarely stall there for lack of a better strategy. They stall because the person leading it has not made the crossing themselves.
That is the leader’s dilemma: why the leader who can see the horizon still will not step off the edge and take flight. I raised it at the close of the first piece because it is the question that matters most, and the one most of the transformation literature is quietest about. Why an organization won’t let go has very little to do with the organization. It has everything to do with its leaders.
This is what makes the transformation harder than a reorganization or a transition. It asks the leader to develop capabilities they don’t yet have, and to do it visibly, in front of the people they are asking to follow them.
Navigating without a map
The truth is, there is no map or crystal ball that tells you exactly what to do. That is not a rhetorical flourish. It is the structural condition. A map describes territory that holds still. But leading a built-for-air organization means letting go of the mental map the leader has been operating under and learning to navigate by compass in an ever-changing, very complex environment.
This is where the work gets personal, because the need for change usually gets triggered by something outside the leader. The business trajectory isn’t sustainable long-term. The initiative isn’t building. The coalition isn’t holding. Something visible is breaking down. That external pressure produces an internal pressure: the leader needs to know their next move will work, because too much depends on getting it right.
This kind of metamorphosis doesn’t permit certainty. The leader is being asked to do something they have not done before, in an environment they have not operated in before, with no proven playbook. So the need for certainty meets a situation that cannot supply it. And what fills that gap, almost without exception, is fear.
The fear usually doesn’t announce itself as fear. It announces itself as a need to be more careful. More precise. More controlled. The leader starts working longer hours. Reviewing more details personally. Asking for more data before deciding. Trying to be perfect, because perfection feels like the only protection against being wrong about something that matters this much.
But perfection isn’t available either. There are too many variables outside the leader’s control: stakeholders they can’t command, market forces they can’t predict, political dynamics they can’t manage. The pursuit of perfection runs into the wall of reality, and what surfaces next is the most painful: the nagging thought that they are not enough and the whole thing is going to fall apart. That whatever success they have had until now has been luck, and this just might be the moment their luck runs out.
Those thoughts are the load-bearing fear underneath most stalled transformations. It is the fear that has the leader doubling down on what got them where they are. Because what got them here is the only evidence they have that they are not, in fact, an imposter. To let go of the way they have always done things would be to risk discovering that what they do is the only thing holding them up.
And here is the part that explains why intelligent, capable leaders cannot think their way out: when a person operates from that fear, they perceive every tension as a threat. Every challenging conversation. Every piece of negative feedback. Every difficult stakeholder. The threat response narrows their attention to immediate self-protection, and it shuts down the capacity to generate possibilities they haven’t already tried. The cognitive flexibility transformation requires has been compromised by the very situation transformation is supposed to address.
This is why the leader cannot see what their team is telling them. They are not refusing the input. They are no longer able to process it. The same brain that needs to imagine a different organization is the brain operating in survival mode. Inside that mode, doubling down on what’s familiar feels like the most rational possible response.
This is the structural reason most transformations require someone outside the system. Not just a strategist who hands the leader a better plan, but someone who can hold the larger picture while the leader does the work of letting go, someone who isn’t inside the political dynamics, the past success, or the personal stakes that produced the mental map in the first place.
Modeling the crossing
Because the hardest truth in all of this is the simplest: an organization cannot become something its leadership is unwilling to become. A leader who needs certainty cannot lead an organization into a form built for continuous change. The crossing has to be modeled before it can be led. The leader goes first: visibly, uncomfortably, without guarantee.
I watched this at VIA Metropolitan Transit. Before anything could change across a forty-year-old culture, the work had to happen at the executive table first. The silos and the self-protection there had to be resolved before anything could move outward. The CEO went first. Not by announcing a transformation, but by being willing to be changed inside it, in front of his own team. Only then could it move to the rest of the organization.
What the leaders who cross actually do
I’ve worked with leaders who make this crossing, and they share a small number of disciplines that distinguish them from leaders who don’t. None of these disciplines are dramatic. They are, mostly, refusals.
They refuse to build a new model built for stability. When the next transformation-to-a-fixed-state is proposed, and it will be, with a roadmap and a future-state diagram, they ask the only question that matters: are we building a living ecosystem that lets us keep adapting without losing who we are?
They refuse to call an upgrade a becoming. They do not mistake a reorganization, a new initiative, a sharper strategy, or a cleaner reporting structure for true evolution. Those are structural renovations: valuable, often necessary, but they leave the legacy DNA of the organization completely intact. Naming the difference protects these leaders from promising a workplace fit for human creativity and adaptability while delivering yet another compliance manual.
They refuse to start downstream. When trust between departments or partners is broken, no policy or MOU will fix it. When a leadership team is operating from self-protection, no strategic plan will be executed honestly. When the people you serve no longer believe the organization means what it says, no communications strategy will repair the bond. The discipline is to address the upstream problem first, even when the downstream solution is what stakeholders are demanding.
The last one is the hardest to talk about: they refuse to lead the crossing without being changed by it themselves. The people you serve cannot trust an organization whose leaders are still relating to them from old patterns. The leader has to go first, in ways that are uncomfortable and not always rewarded, before the rest can follow.
That is what the crossing actually requires. There is no version of the work that skips the leader’s own becoming.