You’ve been here before. The programme has good people. The budget is there. Leadership is visibly committed. And yet progress has slowed to a crawl, escalations are multiplying, and the usual fixes — more governance, better communication, another restructure — aren’t moving the needle.

The instinct is to look for an execution problem. Poor prioritisation. Weak ownership. Cultural resistance. So more energy goes in: tighter reporting, more frequent check-ins, a new framework layered on top of the last one.

And it still doesn’t shift.

This is the pattern I’ve been diagnosing for over thirty years, across banking, government, technology and professional services. The frustrating truth: most stalled transformations aren’t failing because of execution. They’re failing because of misdiagnosis. The wrong intervention is being applied to a misread condition — and in many cases, the intervention is actively making things worse.

“Diagnosis without treatment is a more articulate autopsy. Treatment without diagnosis is malpractice.”

---

The Diagnostic Error at the Heart of Most Failures

Here’s what makes transformation recovery genuinely difficult: identical symptoms can indicate opposite conditions requiring different interventions.

A team that isn’t delivering could be overwhelmed by volume — too much work in progress, no room to finish anything. Or it could be paralysed by competing mandates from leadership. Or navigating a genuinely complex system where nobody fully understands how the parts interact. Or operating in a trust deficit so severe that problems hide until they become crises.

Each of those looks similar from the outside. Each requires a completely different response. Apply the wrong one and you don’t just waste time — you reinforce the condition you’re trying to resolve.

The reason standard transformation playbooks underperform isn’t that they’re bad frameworks. It’s that frameworks carry their conditions of origin. SAFe was built to solve coordination problems in large software programmes. Team Topologies was built to reduce cognitive load. OKRs were built to align distributed teams around outcomes. All effective — in the conditions they were designed for. Imported wholesale into a different condition, they create friction while the underlying problem compounds.

---

Five Conditions That Stall Transformations

After 200+ diagnostic interventions, the conditions that cause transformations to stall cluster into five recognisable patterns — CIRCA: Complex, Insecure, Rapid, Contradictory, Anxious.

---

Why the Same Symptom Requires Different Responses

Consider one of the most common presenting symptoms: teams not finishing work.

Under Rapid conditions, it’s a flow problem. Too much WIP, not enough capacity to complete anything. Constrain the intake.

Under Contradictory conditions, it’s a priority problem. Teams can’t finish because they keep being pulled toward whichever stakeholder shouted loudest this week. Make the trade-off explicit.

Under Complex conditions, it’s a knowledge problem. Teams can’t finish because they don’t yet know enough to make confident decisions. Build structured learning.

Under Insecure conditions, it’s a safety problem. Teams know what needs to happen but won’t surface it because previous candour was punished. Rebuild trust first.

Apply the Rapid response to an Insecure condition — WIP limits to a team paralysed by fear — and you add constraint to an already fragile environment. Misdiagnosis doesn’t just waste time. It compounds the original condition while adding the side-effects of the wrong intervention.

---

What Accurate Diagnosis Actually Changes

A financial services transformation I worked on had been stalled for eighteen months. Forty-seven active initiatives. A major consultancy providing an orchestration framework. Extensive governance infrastructure. The programme was working harder than ever and finishing almost nothing.

The diagnosis: Contradictory condition. Three stakeholder groups pulling in incompatible directions, with no explicit hierarchy and no decision authority assigned. The programme wasn’t failing because of poor execution — execution was structurally impossible.

Intervention: a 90-minute forced ranking session, a documented priority hierarchy, a decision rights protocol. ThroughFlow improved from 62% to 78% within six weeks. The execution capacity had always been there. It was blocked by an unresolved diagnostic problem nobody had named.

---

The Signals Worth Watching

Most transformation metrics are lagging indicators. Revenue holds. Velocity looks acceptable. KPIs stay green — until they suddenly don’t. By the time traditional metrics signal a problem, the condition has been compounding for months.

Two leading indicators provide earlier warning. ThroughFlow measures the proportion of work completing cleanly versus being reworked — it detects quality deterioration and capacity fragmentation two to four weeks before it shows in delivery metrics. Human Pulse measures team sustainability, clarity, and psychological safety — it catches the human dimensions of turbulence before they manifest as attrition or performance decline.

Together they function as a paired signal. ThroughFlow improving while Human Pulse declines means an intervention that’s improving throughput at the cost of people’s sustainability. That’s not recovery — it’s deferred collapse.

---

Where to Start

If your transformation has stalled and the usual fixes aren’t working, the first question isn’t “what should we do differently?” It’s “which condition are we actually in?”

That diagnostic takes two to three days. It uses observable evidence — specific events, behaviours, data points — not surveys or stakeholder opinions. And it produces a starting point calibrated to your actual situation rather than borrowed from someone else’s.

---

Find out which condition you’re in

Five questions. About a minute. If the result resonates, it’s worth a conversation.