Change programmes fail for many reasons, but the most common failure point is the design phase, specifically the things that were not decided before implementation began. Governance left ambiguous. Milestones set without agreement on what they actually measure. No agreed criteria for stopping. This article covers five design principles that address the most common gaps.
1. Governance Must Be Explicit, Not Assumed ¶
Who has the authority to make decisions about the programme? Who has the authority to pause it? Who is accountable for each workstream? These questions need written answers before the programme launches. In most organisations, governance is assumed rather than designed, and the assumptions held by different people are different. The first governance meeting of a new programme is often the first time these assumptions are tested. That is too late.
2. Milestones Should Measure Outcomes, Not Activities ¶
A milestone that reads 'training delivered to all staff by week eight' measures an activity. A milestone that reads 'eighty percent of operational staff able to demonstrate the new process without prompting by week ten' measures an outcome. The distinction matters because activity milestones can be met while the programme is failing. Outcome milestones make the failure visible earlier, when there is still time to respond.
3. Communication Architecture Is Not a Comms Plan ¶
A comms plan describes what messages will be sent and when. A communication architecture describes how information will flow through the organisation during the programme: who needs to know what, at what point, and through which channel. It also describes how feedback from the organisation will reach the programme team. Most change programmes have a comms plan. Very few have a communication architecture.
4. Design the Off-Ramp ¶
Before the programme launches, the leadership team should agree in writing the conditions under which the programme will be paused or stopped. This is not pessimism. It is discipline. Programmes without an agreed off-ramp continue past the point where the evidence suggests they should be reviewed, because stopping feels like failure and nobody has been given the authority to call it. Designing the off-ramp in advance makes stopping a legitimate option rather than an admission of defeat.
5. Build in a Review Point at the Midpoint ¶
A structured review at the midpoint of the programme, conducted by someone outside the programme team, is one of the most cost-effective investments a change programme can make. It surfaces problems while there is still time to address them. It also provides the leadership team with an independent assessment of progress that is not filtered through the programme team's own reporting. This review should be scoped and commissioned before the programme begins, not after a problem has become visible.
A change programme that has been designed carefully is not a guarantee of success. It is a structure within which success becomes possible and failure becomes visible early enough to respond to.