Change Management
You've decided the company must do something different — scale, pivot, reorganize, adopt a new tool. The decision was the easy part. Getting a hundred people to actually change what they do every day is the work that breaks most leaders.
🎯 By the end you'll understand
Why most change efforts stall, the real psychology of resistance, Kotter's eight-step model done correctly, why urgency and a guiding coalition matter more than the perfect plan, and how to drive change without breeding malicious compliance.
KEY INSIGHTThe one idea to take away
You don't change an organization by announcing a new direction. You change it by changing what people feel safe and motivated to do on a Tuesday morning — and that is a campaign, not a memo.
A commonly cited but disputed figure says roughly 70% of organizational change efforts fail to deliver what they promised. Treat the exact number with caution — it's commonly cited rather than rigorously measured, and the original basis for it has been challenged — but the direction is real and the reason is consistent: leaders treat change as a decision (a strategy, a reorg chart, an all-hands) when it is actually a transition that every individual has to make in their own head. The strategy can be flawless and the change still dies, because nobody addressed why a real human being would willingly give up the way they currently work.
Change fails for human reasons far more than strategic ones. The plan is rarely the problem. The problem is resistance you didn't anticipate, urgency you didn't create, and loss you didn't acknowledge. Master those and the same strategy that would have failed now sticks.
DEFINITIONWhat it actually is
A working definition: change management is the discipline of moving an organization — and the people in it — from a current state to a desired future state while preserving performance and minimizing destructive resistance. Note the two halves. There's the technical change (the new structure, system, process, strategy) and there's the human transition (people adjusting their habits, identities, and relationships). The technical change can be designed in a room. The transition can only be led, person by person, over time.
Change management — the structured approach to helping individuals, teams, and the organization adopt a new way of working, so that a change actually delivers its intended results rather than being formally launched and quietly ignored.
The distinction matters because most leaders are excellent at the technical change and blind to the transition. They ship the reorg, send the announcement, update the wiki — and then are genuinely surprised six months later when behavior hasn't moved. The org chart changed. The org didn't.
CORE CONCEPTWhy people resist change
Resistance is not stupidity or stubbornness, and treating it that way guarantees you lose. Resistance is information: it tells you something about what the change costs the people being asked to make it. From a person's seat, almost every change carries a threat. The common drivers:
- Loss and fear. Change is experienced as loss — of competence (I was good at the old way), status, relationships, certainty, or even identity. People don't resist change so much as they resist loss. (This is the emotional core; we'll come back to it.)
- Uncertainty. The brain treats ambiguity as a threat. "Things will be different" with no detail is more frightening than bad news clearly stated. Vagueness breeds the worst-case story.
- Comfort and habit. The current way works well enough and is automatic. New ways are effortful and feel like a downgrade until mastered. Inertia isn't laziness; it's the cost of relearning.
- Lack of trust in leadership. If the last three initiatives were abandoned, or if leaders aren't trusted, people rationally wait it out. "This too shall pass" is learned, not innate.
- Change fatigue. Too many initiatives, too fast, leaves people exhausted and cynical. The eleventh "transformation" lands on numb ears.
- No WIIFM. If a person can't answer "What's in it for me?", they have no reason to spend effort. Benefits to the company are not automatically benefits to the individual asked to change.
- Not-invented-here. People resist change imposed on them that they had no hand in shaping — the same status-and-ownership dynamic you met in 2.12. A decent idea handed down can lose to a worse idea people helped build.
Each form of resistance points to a specific remedy: uncertainty → clarity and detail; no WIIFM → make the personal benefit explicit; low trust → small visible commitments kept; not-invented-here → involve people in shaping it. If you can name the kind of resistance, you can usually dissolve it.
FRAMEWORKKotter's eight steps
John Kotter's eight-step model (from Leading Change) is the most-cited change framework, and for good reason: it sequences the human work, not just the technical work. Use it as a checklist of forces to create, not a rigid waterfall — the steps overlap and loop in reality.
Create a sense of urgency
Make the case for why change must happen now. Without felt urgency, inertia wins and the effort never gets real energy.
Build a guiding coalition
Assemble a group with enough power, credibility, and relationship-reach to lead the change — not just senior titles, but the trusted connectors people actually listen to.
Form a strategic vision
A clear, vivid picture of the future and the strategy to get there — simple enough to explain in a minute.
Communicate the vision
Over-communicate, relentlessly, through many channels — and crucially, walk it. People believe behavior, not slides.
Empower action / remove barriers
Strip out the structures, processes, and incentives that fight the new way. Give people authority and resources to act.
Generate short-term wins
Engineer early, visible victories that prove the change is working and reward the people driving it. Momentum is manufactured, not hoped for.
Sustain acceleration
Don't declare victory too soon. Use early credibility to tackle bigger barriers and keep pressing until it's done.
Anchor in the culture
Make the new way "how we do things here" — embed it in norms, hiring, promotion, and incentives, so it survives the people who started it.
Kotter's 8 steps — a sequence for leading organizational change: urgency, guiding coalition, vision, communication, empowering action, short-term wins, sustaining momentum, and anchoring the change in culture. Strongest as a reminder of which human forces must be present; weakest when run as a top-down checklist with no real buy-in.
SEE ITWhy this change stalled
Imagine you're rolling out a major new way of working. Four ingredients tend to decide whether it sticks. Toggle them on and off and watch what happens — a change effort missing any one of them tends to die in a predictable way.
Notice it isn't additive — there's no "75% of a change." Missing a single critical ingredient is usually enough to kill the whole effort, because each gap opens a specific failure mode that the others can't compensate for. A perfectly communicated vision with no urgency still rots; quick wins with no coalition stay isolated.
CORE CONCEPTThe emotional side: change is felt as loss
This is the part technical leaders skip, and it's the part that decides everything. People do not process change rationally; they process it emotionally, as a loss to be grieved. The familiar change curve — adapted from Kübler-Ross's stages of grief — captures the arc most people move through:
The dip is not a sign of failure — it's the normal cost of transition, the valley people pass through before they climb out the other side. The mistake is interpreting the resistance phase as proof the change was wrong, and reversing course right when people were about to turn the corner. Your job as a leader is to shorten and support the dip, not pretend it won't happen.
Change curve — the emotional arc people typically move through during change (shock → denial → resistance → exploration → commitment), adapted from Kübler-Ross. Performance dips before it recovers; the dip is expected, not a defect.
What actually shortens the dip: naming the loss out loud. "I know this means the team you built is being split up, and that's a real loss" does more than any incentive. It's the same principle as loss aversion (2.5) — people feel what they're losing far more sharply than what they might gain, so acknowledging the loss is what unlocks the room to see the gain.
CORE CONCEPTYou can't out-announce the culture
Here is the hard ceiling on change management: you cannot change behavior while the incentives and norms still reward the old behavior. Tell people to "collaborate more" while you promote the lone heroes and pay bonuses on individual numbers, and the announcement loses to the incentive every single time. People are rational; they read what's actually rewarded, not what's on the poster.
This is why anchoring in culture (Kotter's step 8) isn't a soft afterthought — it's the only thing that makes change permanent. If the new way isn't wired into hiring, promotion, recognition, and what gets measured, it reverts the moment the founder's attention moves on. Culture eats your change plan for breakfast unless the change plan rewrites the incentives. (This is the deep version of the lesson in 4.9 on incentives.)
For a founder scaling or pivoting, this is the practical crux. Over-communicate the vision and the why — relentlessly, the way you learned in 1.11 and 3.7 — but back every word by changing what you measure, reward, and personally model. Recruit the connectors and influencers from your influence network (4.10) into the guiding coalition, because change spreads through trusted relationships, not through the org chart. And involve people in shaping the change: co-creation produces ownership, and ownership is the antidote to the not-invented-here resistance from 2.12. People defend what they helped build.
WEAKNESSWhere change management goes wrong
A leader declares the new direction at an all-hands and assumes the announcement is the change. With no felt urgency, people see no reason to move now; with no guiding coalition, there's nobody trusted carrying it into the trenches. The memo lands, nods are nodded, and nothing actually changes.
Treating change as a purely logical sell — "here's why this is better for the business" — while ignoring what people are losing. The resistance you then get looks irrational, so you push harder, which deepens the loss, which hardens the resistance. You can't reason someone out of a grief they were never allowed to feel.
Force change down with no buy-in and people comply — to the letter, and no further. They do exactly what's mandated, no initiative, no discretionary effort, quietly hoping it fails. Malicious compliance looks like adoption on the dashboard and is actually sabotage. Beware too: change-management frameworks can become checkbox theater (ran the steps, held the workshop, nothing changed), and not all change is good — change for change's sake plus too many initiatives breeds the change fatigue that kills the next, genuinely important effort.
KEY INSIGHTWhere this connects in your course
- Buy-in & co-creation (2.12) — involving people so they own the change instead of resisting an imposed one; the cure for not-invented-here.
- Loss aversion (2.5) — why change is felt as loss, and why naming the loss is what unlocks acceptance.
- Communicating vision (3.7) — over-communicating the why, the skill that carries the change message through the organization.
- Culture (4.9) — the norms and incentives that quietly veto any change they still oppose; anchoring is where change becomes permanent.
- Influence networks (4.10) — recruit the trusted connectors into your guiding coalition; change spreads through relationships, not titles.
- Systems thinking (1.6) — change as moving a system from one stable state to another, fighting its inertia and feedback loops, not just flipping a switch.
Next we look at why even good ideas fail to spread — the diffusion problem underneath every stalled change.
GLOSSARYKey terms introduced
- Change management
- The discipline of moving an organization and its people from a current state to a desired future state while preserving performance and minimizing destructive resistance.
- Kotter's 8 steps
- A model for leading change: urgency, guiding coalition, vision, communication, empowering action, short-term wins, sustaining momentum, anchoring in culture.
- Guiding coalition
- A group with enough power, credibility, and relationship-reach to lead a change — including the trusted connectors people actually listen to, not just senior titles.
- Sense of urgency
- A felt, shared belief that change must happen now; without it, inertia wins and the effort never gains real energy.
- Change curve
- The emotional arc people move through during change (shock, denial, resistance, exploration, commitment), adapted from Kübler-Ross; performance dips before it recovers.
- Malicious compliance
- Doing exactly what a mandate requires and no more — technically compliant, withholding all discretionary effort, often hoping the change fails. The product of change forced without buy-in.
- WIIFM
- "What's in it for me?" — the personal benefit an individual needs to see before spending effort on a change; company benefit is not automatically personal benefit.
ACTIVE RECALLCheck your understanding
Answer in your own words first, then reveal.
1Why do roughly 70% of change efforts reportedly fail, and is it usually the strategy's fault?›
Rarely the strategy. Change is treated as a decision (announce a new direction) when it's actually a transition each person must make in their own head. It fails for human reasons — unanticipated resistance, no felt urgency, unacknowledged loss — not analytical ones. (Treat the exact "70%" figure as commonly cited rather than proven.)
2Name three drivers of resistance and the specific remedy each points to.›
For example: uncertainty → give clarity and detail; no WIIFM → make the personal benefit explicit; not-invented-here → involve people in shaping the change so they own it; low trust → make small visible commitments and keep them. Resistance is a map to the fix, not just an obstacle.
3What is the change curve telling you, and what's the leadership mistake it warns against?›
That morale and performance dip through denial and resistance before recovering — the dip is the normal cost of transition, not a sign the change is wrong. The mistake is reading the resistance phase as failure and reversing course right when people were about to turn the corner. Shorten and support the dip; don't abandon it.
4Why does top-down change without buy-in often produce malicious compliance, and how do you avoid it?›
Forced change with no ownership gives people no reason to invest discretionary effort, so they do exactly what's mandated and no more — sometimes quietly hoping it fails. The dashboard shows adoption; reality shows sabotage. Avoid it by co-creating the change (ownership), recruiting trusted connectors into the coalition, naming the loss, and aligning incentives so the new behavior is actually rewarded.