Lesson 8 · Leadership
Leading change
Change efforts fail on adoption, not design. People resist loss, not change.
Most change efforts — a reorganization, a new process, a platform migration — fail on adoption rather than design. People do not resist change so much as loss: of competence, status or control. Start by answering the question they are really asking: what does this mean for me?
A workable sequence, after John Kotter: establish why now, with evidence; build a coalition of respected people beyond management; describe the end state clearly; remove obstacles; deliver a visible early win; then embed the change in tooling, onboarding and incentives. Skip steps and people comply without committing.
Adoption follows a curve. A few innovators and early adopters go first, then an early and a late majority, then the laggards. Do not spend your energy converting skeptics first: equip the enthusiasts, make their success visible, and the majority follows the evidence. Expect a dip in productivity before the gain, say so in advance, and communicate far more than feels necessary.
Picture it
A director mandates a new CI system by email. Three months later half the teams still use the old one “temporarily”. The second attempt starts differently: two respected teams migrate first and cut build times from 25 minutes to 8, then demo it at the engineering all-hands. A migration script and office hours remove the effort, and the old system gets a shutdown date. Within a quarter the stragglers are asking for help rather than exemptions.
Key formulas & frameworks
- Kotter, condensed
- Urgency → Coalition → Vision → Remove obstacles → Early win → Embed
- Adoption curve
- Innovators 2.5% · Early adopters 13.5% · Early majority 34% · Late majority 34% · Laggards 16%
- The J-curve
- Performance dips before it improves
- The real objection
- People resist loss, not change
Practice
Score: 0 / 5
Up nextCustomers & markets
Next lesson