Lesson 15 of 16 · Level 4: Expert
Leading Change in Your Organization
- ⏱ 13 min read
- ❓ 4 review questions
- ✍️ Exercise with solution
In this lesson
- Why change (the event) and transition (what people go through) need different leadership.
- John Kotter's eight steps for leading change, translated to team level.
- How to use the ADKAR model to find exactly where someone is stuck.
- A script for announcing a change and responses to the most common forms of resistance.
- How a Denver credit union branch got 37 of 40 employees using a new system in eight weeks.
Every team leader eventually has to lead a change they didn't choose: a new system, a reorganization, a new process, a merger. Most changes don't fail because the idea was bad; they fail because people weren't brought along. Leading change means creating a reason to move, a clear picture of where you're going, early proof that it works and plenty of support for the people who have to do things differently. This lesson combines three well-known models into a practical playbook.
Change is an event; transition is a process
Consultant William Bridges, in Managing Transitions (1991), made a distinction every leader should know. Change is external and situational: the new software goes live on March 3. Transition is the internal, psychological process people go through to accept it, and it doesn't follow your project plan. He described three phases:
Ending
People let go of the old way, and sometimes of the status or expertise that came with it.
Leader's job: acknowledge the loss openly. "You were the go-to person on the old system. That matters, and we'll need your knowledge."Neutral zone
The old way is gone and the new one doesn't feel natural yet. Productivity and morale often dip.
Leader's job: set short-term goals, communicate often and treat the dip as normal, not failure.New beginning
People build new habits, skills and identity around the change.
Leader's job: celebrate wins, reinforce new behaviors and retire the old tools for good.Kotter's eight steps
Harvard professor John Kotter studied why transformation efforts fail in a 1995 Harvard Business Review article and turned the lessons into eight steps in his 1996 book Leading Change. They were written for large organizations, but they work at team level too:
- Establish a sense of urgencyMake the "why now" concreteShare real data and customer stories: "We lost two accounts last quarter because our follow-up took a week."
- Create the guiding coalitionRecruit respected people earlyInvolve informal leaders, not just those with titles. Their support is worth more than any memo.
- Develop a vision and strategyDescribe the destination simplyIf you can't explain it in under a minute, it's not clear enough yet.
- Communicate the visionRepeat it more than feels necessaryHuddles, 1:1s, written updates and, above all, your own behavior.
- Empower broad-based actionRemove obstaclesFix the systems, rules and workloads that make the new way harder than the old one.
- Generate short-term winsPlan visible early successesA win within the first few weeks gives skeptics evidence and gives supporters energy.
- Consolidate gainsDon't declare victory too soonUse the credibility of early wins to tackle the harder parts.
- Anchor it in the cultureMake it "how we do things here"Update onboarding, metrics, recognition and job descriptions.
1. A manager announces a new scheduling process by email, and two weeks later almost nobody uses it. The team's most respected senior employee openly calls it "another corporate idea." Which Kotter step was most clearly skipped?
Involving informal leaders early (step 2) would likely have turned the senior employee into a supporter or surfaced real concerns before launch. The other steps come much later.
ADKAR: find where each person is stuck
Kotter's steps describe what the leader does for the organization. Prosci founder Jeff Hiatt's ADKAR model describes what each individual needs to change, in order. Change stalls at the first missing block:
| Block | The person needs… | Diagnostic question | What helps |
|---|---|---|---|
| Awareness | to understand why the change is needed | "Why do you think we're making this change?" | The business reason, in plain language |
| Desire | to want to support it | "What concerns you about it?" | Listening, addressing "what's in it for me," involvement |
| Knowledge | to know how to change | "What do you still need to learn?" | Training, job aids, examples |
| Ability | to do it in real work | "Where does it get hard in practice?" | Practice time, coaching, floor support |
| Reinforcement | reasons to keep it up | "What would make you go back to the old way?" | Recognition, metrics, removing old tools |
Announce it well
The first announcement sets the tone for everything after. Use this structure, live first and then in writing the same day:
1. What's changing, and when
2. Why (the problem it solves, with a fact or two)
3. What is NOT changing
4. What it means for you, specifically
5. What we know, and what we don't know yet
6. How we'll support you (training, time, help)
7. How you can give input, and when you'll hear more
Example: "Starting March 3, we'll move member follow-ups from spreadsheets into the new CRM. Why: last quarter, a third of our loan follow-ups happened more than a week late, and we can't see them across the branch. What's not changing: your members, your teams and your goals. For you, it means logging calls in one place instead of three. We don't yet know how reports will look; you'll hear by February 20. Everyone gets two hours of training and floor support the first two weeks. Tell me or any of our branch champions what worries you; we'll answer every question at Friday's huddle."
Responding to resistance
Resistance is information. It usually signals a missing ADKAR block, a real flaw in the plan or a loss nobody acknowledged.
| What you hear | What it may mean | What to say |
|---|---|---|
| "We tried this before and it failed." | Past changes weren't followed through. | "You're right to be skeptical. What went wrong last time? Let's make sure we don't repeat it." |
| "This will take more time." | Real workload concern. | "It probably will at first. What can we pause for the next month to make room?" |
| "The old way works fine." | Missing awareness, or loss of expertise. | "For you, it does, and you're great at it. Here's what we can't see with the old way…" |
| Silence and no adoption | Fear of looking incompetent. | "It's normal to feel slow on a new system. Want to sit with Jen for 30 minutes? She's been through it." |
2. A loan officer completed the CRM training, says she understands why it matters and wants it to work, but keeps freezing during busy member calls. Where is she stuck in ADKAR?
She has awareness, desire and knowledge (training). The gap is applying it under real conditions, so she needs practice and on-the-floor coaching, not another class.
Real case: a credit union branch in Denver
Elena Ruiz manages a 40-person credit union branch in Denver that moved member follow-ups to a new CRM. She followed Kotter's steps at branch scale: she shared the late-follow-up numbers (urgency), recruited five respected "champions" from different teams (coalition), set up floor support and paused one weekly report for the first month (removing obstacles) and celebrated the first loan closed entirely through the CRM in week two (short-term win). She tracked how many employees logged at least one member interaction in the CRM each week:
In week 3, Elena noticed the flattening and used ADKAR in her 1:1s. Most holdouts weren't against the change; they lacked ability under pressure. She added 20-minute practice sessions with the champions, and adoption picked up again.
3. Elena's goal was 90% adoption among 40 employees. How many people did that require, and by how many did week 8 exceed it?
90% × 40 = 36 people. In week 8, 37 used the CRM (92.5%), one more than the goal.
Your change plan checklist
Announcing by email and calling it "communicated."
Announce live, follow up in writing, and repeat it in 1:1s for weeks.
Treating every objection as resistance to crush.
Listen for real flaws. Some objections improve the plan.
Declaring victory at go-live.
Measure adoption until the new way is simply how work gets done.
4. In Bridges' model, what should a leader do in the "neutral zone"?
The neutral zone is uncomfortable but normal. Short-term goals and frequent communication help people through it; going back would restart the transition later.
Practice exercise
Priya's Seattle team is moving from its own deployment scripts to a company-wide platform. Three engineers react differently. Diagnose each one's ADKAR block and write what Priya should say. Then name the Kotter step she should prioritize this week.
- Ben: "Why are we doing this? Our scripts work."
- Carla: "I get why, and I'm in. I just haven't had time to learn the new pipeline syntax."
- Dev: "Honestly, I wrote those scripts. Now they're getting thrown away."
See solution
- Ben, Awareness. "Fair question. Our scripts work for us, but security patches take two weeks to roll out across teams because everyone deploys differently. The shared platform fixes that. Does that make sense?"
- Carla, Knowledge. "Thanks for being on board. Let's block four hours next week for the tutorial, and I'll pair you with someone who has already migrated."
- Dev, Desire (an Ending, in Bridges' terms). "Those scripts kept us running for three years, and that's thanks to you. I'd like you to lead our migration, because nobody knows our edge cases better."
Kotter step this week: communicate the vision (step 4), with special care for urgency (step 1) for people like Ben. Recruiting Dev to lead the migration also builds the guiding coalition (step 2).
Summary
- Change is the event; transition is the human process of ending, neutral zone and new beginning (Bridges).
- Kotter's eight steps: urgency, coalition, vision, communication, empowerment, short-term wins, consolidation, culture.
- ADKAR (Hiatt): awareness, desire, knowledge, ability, reinforcement. Fix the first missing block.
- Announce live and in writing: what, why, what's not changing, what it means for you, support and input.
- Treat resistance as information, track adoption weekly and retire the old way once the new one sticks.
Next lesson: From Individual Contributor to Manager: Your 90-Day Plan. You'll put the whole course together in a day-by-day plan for your first three months as a manager.
Create your account in 30 seconds, mark your lessons and download your certificate at the end.