A transformation can be presented convincingly and still lose momentum within weeks of launch. The problem often lies less in the ambition than in the execution system: late decisions, unclear responsibilities, overlooked dependencies, and adoption left to chance.
Symptoms often hide a decision-making problem
Repeated delays, a growing number of meetings, or conflicting priorities are sometimes treated as motivation problems. Before drawing that conclusion, examine pending decisions, capacity conflicts, incompatible objectives, and dependencies between teams. A team cannot execute a priority while waiting for a decision that no one is authorised to make.
Map the blockers and distinguish governance, process, skills, tooling, and adoption issues. This helps avoid generic responses—such as adding a meeting or launching another communication campaign—when the root cause lies elsewhere.
Appoint a sponsor and operational owners
The sponsor must resolve priority trade-offs and remove obstacles beyond a team’s remit. Operational leads need to know what they can decide themselves, when to escalate, and what outcomes they must deliver. Shared responsibility without a clearly accountable owner often creates delays.
Document key decisions, their owners, required contributors and deadlines. Governance should be proportionate to risk: structured enough to prevent ambiguity, but light enough not to slow execution.
Break change into verifiable stages
A programme that is too broad can be difficult to manage. Break it into stages that produce visible outcomes and enable learning. For each stage, define deliverables, dependencies, acceptance criteria, and the conditions for moving to the next stage.
The first delivery should test the riskiest assumptions, not merely produce a document. If team adoption is essential, measure actual usage, difficulties encountered, and outcome quality—not just the number of training sessions delivered.
Treat adoption as part of the work
Change affects habits, responsibilities, and sometimes performance measures. Teams need to understand why the change is happening, what it means for their work, and how they can get support. User feedback should be collected and acted upon, with visibility into the decisions made as a result.
Provide support suited to each group: communication, training, documentation, management support and process adjustments. A one-off training session cannot compensate for an inconsistent process or a difficult-to-use tool.
Measure impact and reallocate resources
Track both execution metrics and outcome metrics. The former show whether milestones are progressing; the latter indicate whether the transformation is having the intended effect. Define a baseline, observation period, and limits on attribution. A simultaneous improvement alone does not prove that the transformation caused it.
At each review, decide whether to continue, adjust, accelerate or stop a workstream. Discipline also means releasing resources when assumptions are no longer valid.
Sources and further reading
These public resources complement the analysis. Recommendations should be adapted to each organisation’s sector, country and circumstances.
This publication is a general strategic-thinking resource. It is not legal, tax, accounting, or regulatory advice, nor a guarantee of results. Assumptions and decisions should be validated against the company’s actual circumstances.