The Long Game: Why Most Digital Transformations Stall — and How to Make Yours Last
Most digital transformations fail not from flawed strategy but from accumulated short-term compromises—individually reasonable decisions that collectively erode the initiative's integrity over time. Protecting the long game means holding the transformation roadmap against sustained quarterly pressure.
You’ve read the frameworks. You’ve aligned the leadership team. You’ve launched the transformation. Twelve months later, the energy has faded, the old habits are back, and the dashboards show the same numbers as before. This is not failure. It is physics.
I have seen this pattern repeat across industries and geographies — in fast-growing tech companies and in legacy enterprises trying to modernize. The transformation launches with genuine momentum. There are workshops, new tools, a fresh narrative. Then slowly, almost imperceptibly, the pull of the familiar reasserts itself. People revert. Progress stalls. Leaders blame execution. But the real culprit is something deeper, and understanding it is the first step to building a transformation that actually lasts.
The H Force Always Wins
In the Unified Theory of Existence and Emergence, I described how every organization operates between two fundamental forces: Existence (H) — the drive toward stability, optimization, and the repetition of what already works — and Emergence (T) — the drive toward exploration, experimentation, and the creation of what is becoming. Most leaders intuitively understand this duality when they read it. What they underestimate is how powerful H actually is.
H is not the enemy. It is the immune system of the organization, built and reinforced over years of operational discipline. Every process, every reporting line, every meeting cadence that exists today was at some point a deliberate choice that produced results. The organization’s memory is encoded in those structures. When transformation pressure (T) arrives, H does not panic — it waits. It has survived every previous initiative. It knows that urgency fades, sponsors move on, and eventually the system returns to equilibrium.
Most leaders treat this as resistance to be overcome. The wiser ones design for it. Instead of trying to eliminate H, they ask: how do we gradually reprogram what the organization considers “normal”? The goal is not to destroy stability — it is to shift the center of gravity so that the new behaviors become the default, not the exception.
The 18-Month Dip
McKinsey, Kotter, and Prosci have each independently documented the same uncomfortable truth: transformation fatigue hits hardest between months nine and eighteen. The initial energy — the launch events, the executive sponsorship, the early adopters — has dissipated. But the new way of working has not yet become habit. The organization is in the most vulnerable window of the entire journey: it has left the old shore but has not yet reached the new one.
This is exactly where most initiatives die. And the mistake most leaders make at this point is to push harder — more communication, more accountability, more pressure. That is the wrong instinct. Pushing harder at the dip increases cognitive load on people who are already fatigued. It signals that leadership is anxious, which amplifies uncertainty across the organization.
The right move is counter-intuitive: remove friction and celebrate small wins loudly. Identify the three things that are making the new behaviors harder than the old ones and eliminate them. Find the teams that are genuinely practicing the new way of working — even imperfectly — and make them visible. Recognition at this stage is not a nice-to-have. It is the fuel that carries the transformation across the dip into the territory where habits begin to form.
Embedding Emergence into Operations
In The Executive Shift, I outlined the 4 Strategic E’s — Ecosystem Design, Ethical Governance, Empathy and Insight, and Experimentation — as the new competencies of the AI-era leader. But frameworks only survive if they become rituals. A framework that lives in a slide deck is decoration. A framework that shows up in weekly routines is infrastructure.
Here is what embedding looks like in practice. Create a weekly twenty-minute “emergence review” — a standing slot where one team shares what they experimented with that week, what they learned, and what they are trying next. It does not have to be a success story. The point is to normalize the act of experimentation itself, to make T-activity visible and rewarded rather than hidden and penalized.
Make experimentation explicit in OKRs. If innovation is not measured, it will not be prioritized. One of the most effective signals a leadership team can send is to include a “learning metric” alongside performance metrics — something that captures how many new approaches the team tested this quarter, not just what they delivered.
And consider protecting at least one “Chief Emergence” role — a person whose formal mandate is to disrupt, not to deliver. This is not a Chief Innovation Officer who manages an innovation lab at arm’s length from the core business. This is someone embedded in operations whose job is to surface the assumptions the organization is no longer questioning. Their success metric is discomfort, not output. In my experience, organizations that have this role — even informally — sustain transformation energy far longer than those that do not.
The Leader’s Role in the Long Game
The biggest single risk to any transformation is the leader who drives it intensely for six months and then moves on to the next initiative. I have been that leader. Most of us have. The urgency of the new thing pulls our attention away before the old thing has taken root. Transformation becomes a chapter in our leadership story rather than a permanent shift in how the organization operates.
The mindset shift required is profound: transformation is not a project with an end date. It is a permanent operating mode for organizations that intend to survive the next decade. The leader’s role is not to be the most passionate advocate at launch — it is to be the most patient steward over time. That means staying curious about the friction points long after the launch energy has faded. It means protecting the people who are doing the hard work of changing, even when short-term metrics create pressure to revert. It means being willing to say, eighteen months in, that we are still in the middle of this — and meaning it.
- High energy, 6-month push
- Moves to next initiative when excitement fades
- Celebrates launch, not adoption
- Treats transformation as a project
- Creates the 18-month dip
- Steady presence through the dip
- Stays the course when excitement fades
- Celebrates behavior change, not announcements
- Treats transformation as a permanent operating mode
- Gets through the dip to the new normal
The organizations that will thrive are not the ones that launch the most initiatives. They are the ones that build the discipline to see them through — the ones that understand the physics well enough to work with it rather than against it, and that develop leaders willing to play the long game.
← The Executive Shift: AI and Digital Leadership · The Unified Theory of Existence and Emergence
