Change Management and Stakeholder Adoption
This domain tests how to move a firm from a current workflow to a new one: who must be engaged, how resistance is handled, and how adoption is measured and sustained.
Core concepts
- Stakeholders: executive sponsor, process owner, users, IT, compliance, and clients. Assess impact by role.
- Case for change: problem, benefit, risk of not changing, and evidence.
- Frameworks: Kotter's eight steps; ADKAR (awareness, desire, knowledge, ability, reinforcement).
- Plan: communication, role-based training, pilot, champions, feedback loops, and support.
- Adoption metrics: usage, proficiency, workarounds, ticket volume, and cycle time.
- Reinforcement: governance, incentives, audits, and continuous improvement.
Worked example
A document management rollout stalls because partners keep emailing attachments. Reasoning: training alone does not change behavior. Address ability (Outlook and mobile integration), desire (client benefit and risk reduction), and reinforcement (the matter-close checklist requires documents in the system). A visible sponsor and pilot results support the change; attachment volume measures it.
Traps
Treating change as a training event; ignoring informal leaders; no sponsor; launching without a pilot; declaring success at go-live; no reinforcement.