The Governance Gap: Why Digital Transformation Programmes Stall at 60%

Digital transformation programmes follow a remarkably consistent arc. Strong early progress — a well-received strategy, a promising pilot, visible leadership commitment. Then, somewhere around the 60% mark, the programme slows. Milestones are missed. Stakeholder alignment that seemed solid starts to fragment. The team is working hard but forward momentum has stalled.

This is not a technology problem. It is a governance problem. And it is one of the most consistent failure patterns in enterprise transformation.

What the stall actually looks like

The 60% stall has a recognizable signature. The initial transformation use cases — usually the highest-value, most visible ones — have been delivered. The business case has been proven in principle. But scaling from "this works in one business unit" to "this works across the enterprise" requires decisions that the original programme structure wasn't built to make.

Decisions about process standardization across business units that have historically operated independently. Decisions about data ownership and sharing across functions that don't trust each other's numbers. Decisions about technology consolidation that require retiring systems that specific departments have invested years in customizing. Decisions about organizational structure that affect people's roles, their teams and their career paths.

These decisions require executive authority, clear accountability and a governance structure that can resolve conflicts between business units. If that structure doesn't exist, decisions get escalated, delayed, escalated again, partially made and then re-opened. The programme accumulates dependencies on unresolved decisions and forward progress stops.

The governance structures that prevent the stall

Transformation programmes that maintain momentum through the scaling phase share a governance architecture with three components.

1. An accountable executive sponsor — not a steering committee

Steering committees are useful for visibility and stakeholder management. They are poor decision-making structures. Decisions by committee are slow, often lowest-common-denominator, and frequently reversed.

Transformation programmes need a single accountable executive sponsor with the authority and willingness to make decisions, resolve inter-business-unit conflicts, and protect the programme from organizational antibodies. This person needs to be senior enough that their decisions stick, engaged enough that they understand the real issues (not just the steering committee summary), and committed enough to stay involved for the duration of the programme.

The absence of a genuine executive sponsor — rather than a nominal one — is the most common single reason transformation programmes stall.

2. A defined decision authority framework

Not all transformation decisions require executive sponsor involvement. Most should be made at lower levels of the programme. But everyone involved in the programme — the programme team, the business units, the technology delivery teams — needs to know which decisions they can make, which require escalation, and to whom.

The absence of this clarity creates decision paralysis. Teams stop making decisions they should own because they aren't sure they have the authority. They escalate decisions that should be made quickly. Or they make decisions unilaterally in a way that creates conflict when affected stakeholders discover them.

A decision authority framework doesn't need to be complicated. A simple RACI (Responsible, Accountable, Consulted, Informed) for the major decision categories — process design, technology selection, resource allocation, scope changes — clarifies expectations and reduces the friction that accumulates when authority is ambiguous.

3. Outcome-based programme governance

Most transformation programmes are governed on activity: milestones completed, workstreams tracked, resources deployed. Activity-based governance is useful for project management. It is insufficient for transformation programmes.

Transformation programmes need outcome-based governance: regular measurement of business outcomes against the targets defined at the start of the programme. Not "Phase 2 deliverables are complete" but "decision cycle time in the affected business units has reduced from 18 days to 6 days, against a target of 5 days."

When governance is outcome-based, stalls become visible earlier. If milestone completion is on track but outcomes are not improving, the governance review surfaces this as a programme issue, not a delivery team failure. If outcomes are improving faster than expected, the governance review can accelerate the investment roadmap rather than holding to an outdated plan.

The change management component that most programmes underinvest in

Governance structures create the conditions for good decisions. They don't create the organizational will to implement them.

Digital transformation changes how people work. It changes the skills their roles require. In some cases, it changes whether their roles exist at all. People resist changes that threaten their competence, their status or their security — and they are often right to, because transformation programmes frequently underestimate the human and organizational impact of the changes they are driving.

The change management investment in most transformation programmes is insufficient and mis-timed. Training is delivered too late, when the system is live and people are under pressure. Communication is one-directional and top-down. Resistance is treated as a problem to be managed rather than information to be learned from.

Effective change management for transformation starts before the first delivery milestone. It involves genuine two-way engagement with the people whose work will change — understanding their concerns, addressing legitimate ones, and designing the transition so that people can develop the competence they need before they need it in production.

Organizations that underinvest in change management don't just stall at 60% — they often deliver technically complete programmes that revert to previous practices within 12 months of go-live, because the organizational conditions for sustained change were never created.

Why the stall is recoverable

The 60% stall is frustrating and expensive. But it is almost always recoverable — because the technical foundation has been built, the value case has been demonstrated, and the organization has learned what the scaling challenges actually are.

The intervention is governance-focused: clarifying the executive sponsor role and getting the right person genuinely engaged, establishing the decision authority framework that the scaling phase requires, shifting programme governance to outcome-based measurement, and resetting the change management programme for the harder organizational work of enterprise-wide adoption.

Programmes that have stalled sometimes need a reset — a deliberate pause to diagnose the governance gap, put the right structures in place, and re-launch the scaling phase with appropriate preparation. This feels like a setback. It is usually the precondition for finishing.

---

System Pixels Global Consulting designs and delivers digital transformation programmes — from strategy and operating model design through implementation, change management and programme governance.