Change management treated as a delivery workstream — started after the operating model is designed, the technology selected and the programme plan baselined. Average entry point: month 4 of a 12-month programme.
CN change practitioners are embedded in the design team from day one. Not as a parallel workstream — as a design input. The people who will have to change are understood before the design is finished because their capability, resistance patterns and informal influence structure should shape what gets designed and how it gets sequenced.
Programmes with integrated change management from discovery produce operating models that are designed for how people actually work — not how the consultant assumes they work. Redesign rates drop significantly. Adoption at go-live is higher because the design was tested against real resistance before it was finalised.
CN programmes with change management integrated from week one: 82% achieved ≥70% adoption at go-live. CN programmes where change management joined after design: 51%.
Stakeholder map produced listing senior leaders by seniority and function. Engagement planned around formal hierarchy. Communications sent through management chain. Town halls and all-staff emails as primary channels.
CN builds a corridor map in discovery — a working document that identifies by name the informal leaders whose opinion shapes what their colleagues think, plots their current position on the change, and maps the influence relationships between them. The engagement strategy is designed from this map. The formal stakeholder map governs governance engagement. The corridor map governs the work that matters.
Programmes that engage informal leaders specifically — before communications go out — see the uncertain majority move earlier and more durably. The informal leader who converts brings their followers. The informal leader who hardens creates organised resistance. CN's approach ensures the programme knows which is happening, when, and why.
CN programmes with explicit corridor mapping: 76% of identified informal resisters moved to neutral or supportive by month 3. Without corridor mapping: 31%.
Managers receive a briefing session — typically 60–90 minutes — that tells them what is changing. They leave with a slide deck and a FAQ document. The assumption is that informed managers will have effective conversations with their teams.
CN designs manager enablement programmes, not briefings. The distinction: a briefing tells managers what is changing. An enablement programme equips them to handle the specific conversations their direct reports will have — before those conversations happen. Scenarios are built from discovery intelligence. Role play is mandatory. The session is not complete until each manager has committed to a specific conversation within five working days.
Managers who have practised the difficult conversation before it happens in the corridor are significantly more effective than managers who have been told what to say. The direct report who gets a credible, confident, specific answer from their manager decides differently than the one who is told to check the intranet.
CN programmes with full manager enablement programmes vs briefing-only: adoption at month 3 was 67% vs 41%. Manager-reported confidence in corridor conversations: 84% vs 29%.
Programme resources peak at go-live. Governance stands down. Change champions are thanked. Budget is reallocated. The organisation is told the change has been delivered. Post-go-live monitoring, if it exists at all, is light-touch and short-duration.
CN writes the month 12 review into every SoW before the programme starts. Embedding resource is planned and budgeted for a minimum of 12 weeks post go-live. The adoption tracking framework distinguishes go-live adoption from month 3, month 6 and month 12 adoption — because the only number that matters is the last one. Go-live is a milestone. Month 12 is the finish line.
Programmes that maintain active embedding resource through the reversion window retain significantly more of their go-live adoption. The difference between a programme that resources embedding and one that doesn't is not marginal — it is the difference between 71% adoption at go-live becoming 38% at month 12, or becoming 74%.
CN programmes with structured embedding programmes: average adoption at month 12 was 94% of go-live adoption. Programmes without: 54%. Source: CN Performance Index, 2024.
Benefits case approved at programme start. First benefits measurement taken at go-live or at programme close. No baseline established before programme activity changes the thing being measured. Month 12 verification either does not happen or cannot be meaningful without a pre-programme reference point.
CN establishes the benefits baseline in the first two weeks of every engagement — before any programme activity changes the thing being measured. Every benefit in the business case is connected to a specific operating model change with a credible mechanism. The month 12 review is written into the SoW before delivery begins. CN returns, measures against baseline, and delivers an honest close-out report.
Programmes with a pre-programme baseline and a committed month 12 review change the incentive structure of the entire engagement. The delivery team knows from day one that it will return and verify. The client knows from day one that the engagement does not close at go-live. Both parties make better decisions throughout.
100% of CN engagements include a benefits baseline established in weeks 1–2. 100% include a month 12 review written into the SoW. These are contractual requirements, not aspirational practices.
Business case approved with change management investment. Costs escalate — usually in technology, always somewhere. Budget pressure arrives. The people workstream is reduced because it feels softer, its deliverables are less tangible, and the programme director believes the organisation can absorb the gap.
CN makes the cost of cutting the people workstream visible before the decision is made — not after. When budget pressure arrives, CN presents the historical evidence: what happens to programmes that make this cut, what the remediation cost typically is, and what the minimum viable change investment looks like if the budget genuinely cannot be protected in full. The conversation is financial, not defensive.
Organisations that understand the remediation multiplier make different decisions under budget pressure. Some still cut — but they do so with explicit recognition that they are taking on a deferred liability, not making a saving. That change in framing changes the accountability structure.
CN has never had a programme close with change management budget below the minimum viable threshold agreed at scoping. In cases where budget pressure has arisen, CN has redesigned the scope to protect the critical path rather than accept a reduction that would compromise outcomes.
Programme timeline pressures discovery into one or two weeks. Interviews limited to senior stakeholders who support the programme. Findings confirm the direction of travel. Programme design begins on the formal version of the organisation.
CN will not reduce discovery below what is needed to build a credible corridor map and a genuine current-state assessment. When timeline pressure arrives, CN presents the trade-off explicitly: a compressed discovery produces a programme designed around assumptions. The assumptions will be tested at go-live — at a cost significantly higher than the time saved. CN has walked away from engagements where the discovery timeline was non-negotiable at a level that would compromise the diagnostic.
A programme designed on a genuine understanding of the informal organisation — who the influential resisters are, what the real objections are, where the burning platform is not felt as real — is a programme that does not have to be redesigned in month six when it meets the organisation as it actually is.
CN discoveries of four weeks or more: 89% produced at least one finding that materially changed the programme design. CN discoveries of two weeks or less: 41%. The uncomfortable finding is the value.
A group of internal staff trained to cascade the change programme to their colleagues. Presented as building internal capability and reducing external cost. Trainers selected for availability. Materials handed over. Programme team stands down when the cascade is delivered.
CN distinguishes between train-the-trainer as a genuine capability-building model — where trainer selection is based on influence, involvement in design is genuine, and the cascade is actively managed — and train-the-trainer as an exit mechanism. Where the former is appropriate, CN designs and manages it. Where the latter is what is being proposed, CN names it directly and presents the evidence for what it produces.
Organisations that build genuine internal capability to own change work — as in the defence TOM engagement — exit the external dependency entirely. Organisations that use train-the-trainer as a budget mechanism get month 12 adoption of 34%. CN is designed to produce the former.
CN capability transfer engagements (where building internal methodology ownership is the explicit goal): 100% of internal teams able to run methodology independently at engagement close. The defence TOM engagement is the model.
If you are dealing with any of these failure modes — in a programme that has started, or one you are planning — we should talk.