Key takeaways
- —The standard response to troubled transformation programs—more budget, tighter accountability, timeline extensions—has failed for decades
- —Three systemic breakdowns drive transformation failures: project managers buried in clerical work, governance signals that are delayed and fragmented, and communication that scatters across disconnected channels
- —Real solutions require automating administrative overhead, making governance data instant and objective, and creating a real-time record of truth for all decisions and risks
The old playbook doesn't work anymore
When a transformation program gets into trouble, the response is always the same: tighter accountability, more budget, a timeline extension. Organizations have been pulling these 3 levers for 50 years.
They don't work.
Across North America, governments and enterprises are accelerating ERP implementations, cloud migrations, and large-scale modernization programs all at once, faster than ever before. These aren't traditional IT projects anymore—they're the backbone of how organizations and society operate, compete, and survive. A failed ERP rollout disrupts supply chains, delays critical public services, and can take years to recover from. Some estimates put the failure rate at up to 99.9% when measured against the original program goals.
And yet, out comes the same old playbook.
Why the standard levers fail
More accountability doesn't cut it because oversight depends on information, and information depends on people capturing it correctly. At the scale and speed these programs now run, there's simply too much information moving too fast for any team to track manually. Bolting on another layer of people to a process already bottlenecked by people makes it even slower. More budget doesn't fix what you can't see. And longer timelines just make the wait longer for critical outcomes that are already overdue.
The root causes run deeper. There are 3 worth separating.
The three systemic breakdowns
Project management is how the work gets done: planning, resources, timelines, execution. Governance is what gets delivered and why: the right decisions, by the right people, properly documented. Communication is the connective tissue: how decisions, risks, and scope changes actually travel across teams.
Each one breaks in its own predictable way.
Project managers are drowning in clerical work
Project managers spend most of their time on administrative overhead: updating tools, reconciling data across systems, generating status reports. By the time that's done, there's little room left for strategic thinking. Project managers are too buried to flag issues early.
Governance runs on stale, manually assembled information
Governance is self-reported and slow. It runs on manually assembled artifacts: meeting minutes, risk logs, status decks. By the time those get compiled, the project has already moved on. Leadership is reading a snapshot from 3 weeks (or months) ago—which is usually when scope drift starts going unnoticed.
Communication fractures by default
Decisions scatter across email threads, chat messages, individual memory, and meeting notes that nobody consolidates. Critical context evaporates, and it becomes impossible for anyone to piece together what actually happened.
The compounding cost of invisible drift
When all 3 break at the same time—which they always do—the result is predictable: leadership sees the red flag months after the project started drifting.
In transformation programs, that delay is never free. Every week of invisible drift compounds in cost, in scope, and in the effort it takes to course-correct.
We've seen this pattern repeat across both public and private sector programs: organizations trying to govern fast-moving work with risk signals that are fragmented, delayed, inaccurate, and manually assembled.
That's the problem worth solving.
What fixing it actually looks like
1. Strip project management to its strategic core
Automate the administrative overhead: status tracking, reporting, cross-tool reconciliation. Let project managers spend their time on decisions and trade-offs—which is what they're actually good at.
2. Make governance instant and objective
Steering committees and escalation paths stay human. But the information feeding them shouldn't wait for someone to compile it. When governance data is generated automatically and continuously, decisions get made on what's happening now.
3. Turn communication into a real-time record of truth
Decisions, risks, scope changes: capture them at the source, in real time. A searchable record of what actually happened closes the gap between what truly occurred and what leadership understands.
The path to real delivery
The organizations that actually deliver the right outcomes—on time and on budget—fix the risk signals first. That means capturing decisions as they happen, catching risks before they compound, and being able to answer anything about the project accurately in seconds. The drift stops early, and they move faster because of it.
