Most Leaders Ignore the Harder Half of Transformation

 

By Nadir Ahmad, CEO at Dowling Street

Every transformation announcement follows the same arc. There is a compelling rationale, a strategic framework, and a call to action. Leaders communicate the vision. Managers cascade the message. And then, quietly, the organization does what it has learned to do: it waits.

Not out of laziness. Not out of resistance. Out of experience.

Because most people in most organizations have lived through enough transformations to know the pattern: the announcement, the initial energy, the gradual fade, and the quiet return to old ways, just with new language layered on top. They have learned, rationally and correctly, not to fully commit until they see whether this one is real.

This is not a cynicism problem. It is a debt problem.

The Debt Leaders Don’t See on the Balance Sheet

In software, technical debt refers to the accumulated cost of shortcuts taken during development. The code works, but it is fragile, harder to build on, and increasingly expensive to maintain. The longer you ignore it, the more it constrains what you can do next.

Organizations carry an equivalent burden that rarely appears in any report: change debt.

Change debt is the accumulated cost of transitions that were announced but never completed: transformations that deployed new systems or structures without ever guiding people through the psychological journey those changes required. Every initiative that launched without landing leaves residue. Every restructuring that reorganized the org chart without rebuilding trust adds to the balance. Every technology rollout that measured adoption in logins rather than genuine shifts in how people work compounds the problem.

The residue looks like cynicism. It sounds like “here we go again.” It shows up as the workforce that technically complies but does not actually change. Over time, it hardens into a cultural immune system: an organization that has learned to metabolize transformation announcements without meaningfully transforming.

Most leaders launching their next initiative are building on top of this debt without knowing it is there. The question worth asking, before the next all-hands or strategy cascade, is: what do we still owe people from the last time?

Change Versus Transition: The Distinction That Changes Everything

Organizational psychologist William Bridges spent decades studying why so many change initiatives fail despite being logically sound and well-resourced. His central insight was deceptively simple: organizations confuse change with transition, and they are not the same thing.

Change is the external event: the new structure, the new platform, the new strategy. It has a launch date. It can be project-managed, communicated, and measured.

Transition is the internal psychological journey that people must make for the change to actually take hold. It does not start at the launch date. It starts when people begin to let go of the old way. And it does not end when the system goes live. It ends when people have genuinely internalized the new way of working, when it feels normal rather than imposed.

Bridges mapped this as a three-phase arc: an ending (letting go of what was), a neutral zone (the uncomfortable in-between), and a new beginning (genuine adoption of the new). Most organizations manage the ending badly, skip the neutral zone entirely, and then wonder why the new beginning never really arrives.

Here is the painful irony. Leaders are trained to manage change. They learn project management, communication planning, stakeholder alignment, and milestone tracking. What almost no one teaches them is how to manage transition: how to help people genuinely move through the psychological arc that makes change sustainable rather than cosmetic.

So, they default to what they know. More communication. Better messaging. Clearer rationale. These are not useless. But they are tools for managing change, not transition. And when the organization does not move the way leaders expect, the diagnosis is almost always wrong: it is not a communication problem, a commitment problem, or a talent problem. It is an unmanaged transition problem built on top of unresolved change debt.

What Transition Architecture Actually Looks Like

At Dowling Street, we work with leadership teams navigating exactly this challenge: organizations that have the strategy right but cannot get the people to move. What we have found, consistently, is that the bottleneck is not motivation or capability. It is the absence of deliberate transition architecture: the intentional design of the human journey alongside the structural change.

Transition architecture is not a feelings exercise. It is a leadership discipline. It means building into the transformation plan explicit attention to the three phases Bridges identified, and giving leaders the tools to guide people through each one.

Phase 1: Name the ending honestly. Every change requires people to give something up, and leaders who skip this leave people stranded in unacknowledged grief.

  • Identify specifically what this change asks people to let go of: a process, a role identity, a working relationship, a sense of competence.

  • Acknowledge the loss publicly and with specificity. "We know change is hard" is not enough. Name what is actually ending.

  • Resist the pull toward premature positivity. Honoring the ending is what allows people to move past it.

Phase 2: Design for the neutral zone. The space between the old way and the new is the most dangerous and the most neglected phase of any transformation.

  • Acknowledge the neutral zone explicitly. Name it as real and temporary so people do not interpret their disorientation as failure.

  • Provide enough structure to feel safe, enough flexibility to allow genuine figuring-out. Over-controlling this phase produces compliance theater.

  • Watch for informal leaders filling the vacuum with their own narratives. Get ahead of the story before others write it for you.

  • Model tolerance for ambiguity at the top. If leaders signal that confusion is unacceptable, people will perform certainty they do not have.

Phase 3: Create genuine new beginnings. New beginnings do not arrive on the project go-live date. They arrive when people have had enough successful experiences with the new way to start trusting it.

  • Engineer early wins that are authentic, not manufactured. People can tell the difference, and manufactured wins deepen cynicism.

  • Celebrate specific behaviors that reflect the new reality, not just outcomes. Behavior change is the evidence that transition is happening.

  • Continuously connect daily work to the larger purpose the transformation serves. Internalization, not compliance, is the goal.

Paying Down the Debt Before You Add to It

None of this is possible if leaders are launching a new transformation on top of significant unresolved change debt. Before deploying the next strategy, it is worth conducting an honest audit of what previous transitions left behind.

A few useful questions: Which of our recent changes do people comply with but do not believe in? Where have we retrained people on new systems but never addressed the loss of the old ones? What do our people not say in meetings that they almost certainly say after them? Where did we declare success on a transformation that the organization never actually completed?

The answers reveal where the debt lives. And addressing it directly, even retroactively, does something powerful: it signals that leadership can be trusted to see the human reality of change, not just the operational scorecard. That signal, more than any communication plan, is what unlocks genuine movement.

This work is not glamorous. It does not show up on a project timeline. It is not the kind of thing that gets celebrated in a board presentation. But it is the work that determines whether the next transformation lands or simply adds another layer to the debt.

The Question Before the Next Launch

The organizations that will navigate the current era of transformation most successfully will not be the ones that move fastest. I have written about this before in the context of AI adoption, and the data bears it out: velocity without human readiness is expensive theater.

But I want to be precise about something. The answer is not to slow down the change. The answer is to speed up the transition work that makes change real.

That means treating the human journey as a design problem, not an afterthought. It means naming what is being asked of people with honesty and specificity. It means holding space for the disorienting in-between rather than pretending it does not exist. And it means taking seriously the accumulated weight of every previous transformation that asked something of people and never fully delivered on what was promised in return.

Before you launch the next transformation, ask one question that rarely appears in any project charter: What do we still owe our people from the last one?

The answer will tell you more about your organization’s readiness than any readiness assessment. And addressing it honestly, even partially, will do more to unlock the next transformation than any communication plan you could build.


Sources: