The real reason transformation drifts
Why most programmes lose direction and how to prevent it
Digital transformation programmes rarely fail because of technology. They drift because governance becomes ceremonial, decisions accumulate without resolution, and accountability fragments across too many stakeholders. Understanding this pattern is the first step to preventing it.
The drift begins with governance theatre
Most transformation programmes establish impressive governance structures: steering committees, design authorities, change boards. Yet these often become forums for status updates rather than decision-making. When a committee meets monthly but decisions need to be made weekly, the real choices happen elsewhere, often without proper oversight or documentation.
The result is a growing gap between what the governance structure believes is happening and what is actually being delivered. By the time this gap becomes visible, months of work may need to be revisited.
Decision debt compounds silently
Every transformation involves thousands of decisions, some strategic, most tactical. When decision-making authority is unclear, or when leaders are unavailable, teams make assumptions. These assumptions become embedded in designs, configurations, and integrations.
We call this "decision debt." Like technical debt, it accumulates interest. A single unvalidated assumption about data migration can cascade into weeks of rework when discovered during testing. Multiply this across hundreds of decisions, and you understand why programmes drift.
"When everyone is responsible for success, no one owns specific outcomes."
The accountability paradox
Large programmes often have too many accountable parties and therefore none. When everyone is responsible for success, no one owns specific outcomes. This is particularly acute at the boundaries: where the ERP meets legacy systems, where the integrator hands off to internal teams, where business process design meets technical implementation.
These boundaries are where drift accelerates. Without clear ownership, problems are identified but not resolved. They are escalated but not decided. They are documented but not fixed.
Preventing drift requires different oversight
The solution is not more governance. It is different governance. Effective oversight for transformation requires:
• Weekly decision forums with authority to decide, not just discuss • Clear escalation paths with defined resolution timeframes • Explicit ownership of boundary conditions and integration points • Regular reconciliation between governance understanding and delivery reality
This is the work we do. Not adding another layer of oversight, but ensuring the oversight that exists actually prevents drift.
Want to discuss how these insights apply to your programme?
Start a conversation
