Why Most Transformations Fail — And What Agile Leadership Actually Looks Like

Here is a scenario that plays out in organizations every single day.

Leadership spends months crafting a transformation strategy. They present it to the business. There is alignment at the top, energy in the room, and a clear roadmap on a slide. Everyone nods. The initiative is officially launched.

Six months later, the teams doing the actual work are confused about priorities, buried in competing demands, and quietly wondering if anything has really changed at all.

This is not a strategy problem. The strategy was probably fine. It is a leadership gap — specifically, the distance between what leaders decide and what employees actually experience day-to-day. BCG calls this “change distance.” And in most transformation programmes, it is precisely where things fall apart.

So what does actually work? PMI’s Manifesto for Enterprise Agility offers a practical framework — not a methodology to implement, but four leadership values to practice. Here is what each one means and why it matters for organizations navigating transformation in 2026.

Table of Contents

• What Is Enterprise Agility? (And Why It Matters Now)
• Value 1: Clear Purpose Over Perfect Plans
• Value 2: Shared Enterprise Outcomes Over Departmental Wins
• Value 3: Continuous Reinvention Over Protecting the Status Quo
• Value 4: Human Centricity Amidst Change
• How These Values Show Up in Project Delivery

1. What Is Enterprise Agility?

Enterprise agility is not the same as Agile project management — though the two are related. Agile (with a capital A) is a project delivery approach. Enterprise agility is a leadership capability: the organizational ability to sense change, respond deliberately, and deliver value continuously — not just once a transformation programme concludes.

The distinction matters because most transformation efforts treat agility as something the delivery teams need to adopt. Enterprise agility says the leadership layer needs to change first. Teams cannot move fast, adapt well, or sustain change if the leaders above them are operating on outdated assumptions, misaligned incentives, or annual planning cycles that are already obsolete by Q2.

Here is a question worth sitting with: when your team’s plan changes — and it will — do people understand why, or do they just receive a new set of instructions?

That distinction matters more than most leaders realize. Plans are necessary, but they have a short shelf life. Markets shift. Technologies evolve. The assumptions that were reasonable in January can look shaky by March. When leaders over-invest in a plan and under-invest in the purpose behind it, teams have no anchor when the plan inevitably needs to change.

Purpose is that anchor. When people genuinely understand why the organization is making a change — not just what the change is — they can navigate adjustments without losing direction. They can make judgment calls in the moment rather than waiting for updated instructions from above.

What this requires from leaders

• Be explicit about trade-offs — what the organisation will do, what it will stop, and what will wait. Ambiguity here wastes months of effort heading in slightly wrong directions.
• When plans change, explain the reasoning — not just the new direction. ‘What changed and why’ is the difference between learning and whiplash.
• Define success criteria early, so teams can make sensible trade-offs independently without guessing what leadership would want.

The payoff is measurable. Leaders who clearly define and cascade purpose achieve transformation success rates more than twice as high as those who do not. For delivery teams, it shows up as fewer last-minute pivots, clearer priorities, and significantly less rework when direction shifts.

 Once purpose is clear, the next challenge is alignment — getting different parts of the organisation pulling toward the same destination, rather than each function optimising for its own performance metrics.

This is harder than it sounds. Most organisations have built their incentive systems around departmental KPIs. Sales has its targets. IT has its KPIs. Finance has its dashboards. Everyone is working hard. But the enterprise transformation outcome — the actual thing the whole change was meant to achieve — sits in the background, acknowledged in strategy documents but not embedded in anyone’s performance review.

The result is predictable fragmentation. Cross-functional dependencies stall in committees. Decisions get escalated because no one has authority across functions. Teams do locally sensible things that add up to enterprise-level confusion.

What this requires from leaders

• Define outcomes that genuinely cut across silos — not departmental milestones dressed up as enterprise goals.
• Align incentives and decision rights to match. If people are still being measured on local metrics, shared enterprise outcomes will always lose when there is a conflict.
• Fund outcomes, not legacy projects. Portfolio overload is where transformation investment quietly disappears.
• Establish clear escalation paths so delivery does not stall when cross-functional disagreements arise.

For the teams doing delivery work, shared enterprise outcomes show up in a very practical way: fewer conflicting asks, faster decisions, and dependencies that get resolved rather than parked indefinitely.

‘Continuous reinvention’ can sound exhausting — especially to teams already navigating significant change. But the version of reinvention that actually works is not constant disruption. It is the deliberate habit of questioning your own assumptions before the market does it for you.

Think of it less as a burning platform and more as a regular maintenance routine. Organisations that test what is working — and retire what is not — avoid the all-or-nothing transformation crises that drain people, budgets, and morale. They change in smaller, more manageable increments, consistently.

There is strong evidence for this approach. An analysis of 1,700 transformations found that organisations which had previously completed a successful transformation were 11 percentage points more likely to succeed in their next one. That is not luck. It is the compound benefit of treating transformation as a repeatable organisational capability rather than a one-time event.

What this requires from leaders

• Pace change deliberately. Give teams clear start and stop points so they can absorb, stabilise, and learn — not just keep absorbing.
• Create a genuine path from experimentation to scale. Test new ways of working in bounded, safe spaces. Then embed what works into actual business operations — do not leave valuable improvements trapped in pilot mode forever.
• Balance autonomy with coherence. Give teams room to innovate while keeping shared outcomes and guardrails clear enough that innovation compounds rather than fragments.

For delivery teams, this looks like something valuable: permission. Permission to retire broken processes, adopt better tools, and improve how they work — without being handed yet another organisational mandate on top of existing delivery commitments.

The first three values create the strategic and structural conditions for transformation. This fourth one determines whether any of it actually sticks.

Even the most well-designed transformation will stall if it exhausts the people expected to execute it. And this is not a soft, peripheral concern — it is the most practical risk in any change initiative, and the one most consistently underestimated.

Large-scale transformation reliably triggers human fears that leaders tend to overlook: fears about identity (does my expertise still matter in the new world?), safety (will there still be a role for me?), and confidence (do I actually have the skills this new environment requires?). When these questions go unanswered, people disengage — not necessarily loudly, but in the ways that matter most: discretionary effort, risk-taking, and honest feedback.

What this requires from leaders

• Name the human reality directly. Identity disruption, confidence gaps, and uncertainty are normal in transformation. Pretending otherwise isolates people. Create day-to-day clarity about what is changing, what good looks like, and how decisions will be made.
• Deliver enablement before expectation. Training, coaching, and practical tools should arrive before new ways of working are required — not after people are already struggling to catch up.
• Acknowledge progress out loud. Mark wins. Recognise the effort teams are putting in. Make appreciation a consistent part of how change is sustained — not a one-off announcement at the end of a programme.

For delivery teams, this means new expectations come with real support attached. Leaders protect time for learning. Uncertainty gets actively reduced. And the organisation has genuinely invested in the conditions that make execution possible — not just announced that change is happening and expected performance to follow.

5. How These Values Show Up in Real Project Delivery

These four values are not abstract leadership philosophy. They have direct consequences for the people managing and delivering projects day-to-day.

PMI’s own Project Success research reinforces this connection: projects with a clearly defined vision perform significantly better than those without one, because teams are not forced to improvise priorities and trade-offs midstream. The four values of enterprise agility are, at their core, leadership choices that either create or remove that clarity for the people doing the work.

The Bottom Line

Transformation is no longer a project with a defined end date. In 2026, it is a permanent operating condition for most organisations.

The organisations that handle this well are not the ones with the most sophisticated transformation methodologies. They are the ones whose leaders have built the habit of going deliberately slow on the things that matter most — clarity of purpose, shared outcomes, paced reinvention, and genuine investment in the human conditions for execution — so the organisation can move fast where it counts.

Enterprise agility is not a framework you roll out. It is a leadership posture you practice, repeatedly, until it becomes the default way your organisation responds to change.

Keep advancing in your PMP journey — explore our other in-depth guides

• 2026 PMP Exam Changes: The “Practicum” Revolution & Why 4 Hours Changes Everything
• The 2026 PMP Exam Shift: How to Master the “Business Environment” Surge (8% to 26%)
• The 5 Scrum Events Explained: Purpose, Attendees, and Effective Execution
• Why PMP Aspirants Fail? – And How to Avoid Them
• Why You Should Track Your Errors — and How to Do It Right

Your first project is calling—will you answer? Join the ShriLearning Community Connect with fellow PMP aspirants and expert instructors. Crete your study plan for free from ShriLearning study-plan-generator.

Sign Up for PMP Training