Full guide in Portal →
Methodology Guides/Change Management
🔄
Core Methodology — Delivery Stream

Change Management.

The human programme that makes transformation hold. Designed for the corridor as well as the boardroom. From discovery through to month 12 verification.

Manager effectiveness is the single strongest predictor of employee adoption — stronger than comms quality or training design
Prosci Best Practices in Change Management (2023)
This is why CN designs enablement programmes, not briefings. The corridor conversation is the mechanism. Full evidence →
Full practitioner methodology in the CN Portal Log in →
The key principles

How CN approaches this work.

01
Design for the corridor, not just the boardroom
The formal programme reaches people through communications, workshops and training. The real decision about whether to adopt the change is made in the corridor, the 1:1, the team meeting before the meeting. Both must be designed for explicitly.
02
Resistance is information, not a problem to manage
People resist change for entirely understandable reasons — career uncertainty, loss of status, genuine disagreement with the direction. Treating resistance as a communications problem to be overcome misses the point. Understanding what people are being asked to give up is the diagnostic that informs the programme.
03
Manager enablement, not manager briefing
Managers are the single most important lever in any change programme. But briefing them on what is changing is not the same as equipping them to handle the specific conversations their teams will have. The difference between a briefing and an enablement programme is the difference between change that is announced and change that holds.
04
Go-live is a milestone, not the finish line
The programme is most vulnerable in the weeks immediately after go-live. The formal structures have demobbed. The change champions have been thanked. The organisation has been told the change has been delivered. And the drift begins. The finish line is month 12.
05
Baseline before you start
If you have not measured the current state before the programme begins, you cannot demonstrate at month 12 that anything changed. Baselining is the first act of a serious change programme.
What good looks like
  • Change programme designed in parallel with operating model, not after
  • Informal network mapped and influential individuals identified by name
  • Manager enablement programme distinct from manager briefing
  • Resistance diagnostic completed before communications go out
  • Go-live readiness assessed against defined criteria, not assumed
  • Embedding period planned and resourced before go-live
  • Benefits baseline established in week one
Warning signs
  • Change management commissioned after the operating model is designed
  • Comms plan treated as the change programme
  • Managers briefed but not equipped for corridor conversations
  • Resistance managed rather than understood
  • Programme demobs at go-live
  • Month 12 review not planned before the programme starts
  • Benefits case not baselined — making verification impossible
Diagnostic questions

Use these in client conversations or team reviews to quickly surface where the real issues are.

QHave you mapped the informal leaders whose view shapes what their teams think — and do you know where they stand?
QAre your managers equipped to handle the specific question "will my job actually change?" from a direct report at 4pm on a Friday?
QWhat is your go-live readiness criteria — and who has authority to delay if it is not met?
Full Practitioner Guide

The complete methodology is in the CN Portal.

The full guide covers: stakeholder landscape mapping methodology, informal network analysis, resistance diagnostic framework, manager enablement programme design, corridor moment preparation, go-live readiness assessment, embedding programme design, and the month 12 verification process.

Access Portal Join the network