Organisational Change Management (SFIA Level 4)
What this domain tests
Domain 2 moves from controlling a change to leading people through it, at SFIA level 4. The exam tests whether you can select and apply organisational change approaches, assess readiness, plan stakeholder engagement and communication, manage resistance, build capability and sustain adoption. The unit of success is not 'go-live' but measurable adoption and benefit.
Models as diagnostic tools
- Lewin: unfreeze, change, refreeze; force-field analysis compares driving and restraining forces - useful for choosing whether to strengthen drivers or remove barriers.
- Kotter's eight steps: urgency, coalition, vision, communication, empowerment, short-term wins, consolidation, anchoring. Use it as a sequence, not a checklist.
- ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement. It diagnoses where an individual or group is stuck; the weakest element determines the intervention.
- Bridges transition: endings, neutral zone, new beginnings - explains why people resist even a 'good' change.
- McKinsey 7S / congruence: strategy, structure, systems, style, staff, skills, shared values must align.
Readiness, stakeholders and resistance
Readiness assessment covers leadership alignment, capacity, capability, culture and history of change. Map stakeholders by influence and interest, then segment engagement: sponsor, managers, impacted users, technical teams, unions, customers. Prosci's research consistently finds active, visible sponsorship and manager involvement among the strongest contributors to success. Resistance is information: identify whether it is about awareness, capability, loss of status/control or fairness, and address the cause. Communication needs key messages, audience, channel, timing and a feedback loop - not a single town hall.
Worked example
An ERP rollout across three regions shows 40% adoption after go-live. Rather than more training, diagnose with ADKAR: awareness is high, desire is low in one region because managers still keep shadow spreadsheets, knowledge is partial, ability is low at month-end, reinforcement is absent. Interventions: sponsor-led message on why shadow systems stop; manager coaching; floor-walking at month-end; super-user network; adoption dashboards and consequences. The reasoning is diagnostic-first: identify the barrier before choosing the intervention.
Traps
- Reducing OCM to communications and training.
- Measuring deliverables (training completed) instead of outcomes (adoption, proficiency, benefit).
- Treating resistance as irrational or disloyal.
- Ignoring middle managers and supervisors, who translate change locally.
- Applying one model mechanically; models are lenses, not recipes.
- Forgetting reinforcement, so old behaviours return.