change-management

# Change Management ## Core Frame Change initiatives fail predictably. Common patterns: too fast for people to integrate; too slow to maintain momentum; communicated through email cascades that nobody reads; rolled out without manager preparation; measured by hours of training rather than behavior change. The discipline is treating change as a system: communication architecture + sequencing + manager enablement + measurement. ## Frameworks (with Skepticism) ### Kotter's 8 Steps (Brief) John Kotter's framework, with appropriate skepticism about prescriptive use: 1. Create urgency 2. Form a coalition 3. Create vision 4. Communicate vision 5. Empower action 6. Generate short-term wins 7. Sustain acceleration 8. Institute change Useful as a checklist, not a script. Most companies skip steps 5–7 (empowerment, wins, sustaining) and wonder why change doesn't stick. ### ADKAR Awareness / Desire / Knowledge / Ability / Reinforcement. A simple individual-level frame for what each employee needs to actually change behavior. Most change initiatives skip "Desire" (why should I care?) and "Reinforcement" (how is the new behavior sustained?). ## Communication Architecture ### Sequence 1. **Pre-announce** to senior leaders and managers (so they're not surprised) 2. **Announce** broadly (all-hands, written memo) 3. **Detailed Q&A** in town halls and team meetings 4. **Manager-led conversations** (most important; this is where change lands) 5. **Ongoing reinforcement** in 1:1s, all-hands, recognition Skipping #1 or #4 is the most common failure. ### Channel Mix - **Written**: detailed memo, FAQ — for those who want depth - **Verbal**: all-hands, town halls — for narrative and energy - **1:1**: team meetings, manager-employee — for personal application - **Q&A**: explicit channel for questions; visible answers ## Manager Enablement The single biggest leverage point. Managers translate change for their teams. For any consequential change: - Brief managers 1+ week before announcement - Provide talking points (not scripts; talking points) - Manager training on the change (especially for performance, comp, structural changes) - Q&A with managers before they have to deliver to teams - Coaching for managers who'll have hard conversations ## Sequencing Common Changes ### New Performance System - Q1: design with leadership input - Q2: pilot with one function - Q3: manager training company-wide - Q4: roll out to all + first calibrated cycle Total: typically 9–12 months. Faster usually fails. ### Comp Philosophy or Bands Refresh - Month 1: leadership alignment - Month 2–3: bands set; pay equity audit (under privilege) - Month 4: communicate philosophy to all employees - Month 5: compensation cycle uses new bands ### Reorg (Restructure) - Pre-day: leadership alignment; manager pre-brief - Day 0: announcement (all-hands; written memo) - Day 0+1 hour: individual conversations for affected employees - Day 0+1: team meetings - Week 1: Q&A; FAQ; settling - Week 2–4: 30-day check-ins - Quarter 1: measure success; iterate ### Layoff / RIF - See `offboarding-architect` ## Stages of Adoption Predictable stages: 1. **Awareness**: people know about it 2. **Skepticism**: "this won't last" / "we tried this before" 3. **Tactical compliance**: people do it because they have to 4. **Behavior change**: people do it because it's now how things work 5. **Internalization**: it's how we do things Don't expect to skip from #1 to #4 in a quarter. Most change requires 12–18 months to internalize. ## Resistance Resistance is information. Common sources: - Real concerns about implementation - Past failed initiatives (skepticism) - Self-interest (people who lose under the new system) - Identity or values conflict - Lack of capacity (can't take on more change) Address each differently: - Real concerns: listen, adjust where reasonable - Past failures: explicitly acknowledge; explain what's different this time - Self-interest: name openly; don't pretend it's not real - Identity: deeper conversation; sometimes role change appropriate - Capacity: re-sequence or de-prioritize something else Pretending resistance doesn't exist makes it worse. ## Measurement Measure not just adoption but outcomes: - **Adoption**: are people doing the new behavior? - **Quality**: are they doing it well? - **Outcomes**: are the outcomes the change was supposed to produce showing up? - **Reversion**: at 6 / 12 / 24 months, has it stuck? Most companies stop measuring at adoption. The real question is whether outcomes shifted. ## Common Failures - Email cascade as the entire communication strategy - No manager pre-brief - Manager talking points not provided - Change rolled out faster than people can integrate - Multiple changes simultaneously (capacity overload) - No measurement of behavior change - Reversion to old patterns without notice - Senior leaders modeling old behavior while announcing new - "We've completed the change initiative" said too early ## Cross-References - `manager-enablement-coach` agent - `culture-architect` agent - `executive-coach` agent - `people-orchestrator` agent ## Key References - Kotter, J. P. (2012). *Leading Change*. - Hiatt, J. M. (2006). *ADKAR*. - Heath, C., & Heath, D. (2010). *Switch: How to Change Things When Change Is Hard*. - Pascale, R. T., Sternin, J., & Sternin, M. (2010). *The Power of Positive Deviance*.