MODULE 2.4: LEADING ORGANIZATIONAL CHANGE

FACULTY 2: ORGANIZATIONAL BEHAVIOR AND DESIGN

COURSE 2.4: LEADING ORGANIZATIONAL CHANGE

The test.

Think of a change initiative in your organization that failed. Not the one that was canceled. The one that was announced, implemented, and then slowly faded back to the old way. Answer three questions.

Question one. Who actually wanted the change? Not who announced it. Who would lose something if the change succeeded? Who would lose something if it failed? Answer honestly.

Question two. Was the change a one time event or a new way of working? Did the organization treat it as a project with an end date or a new operating system? Answer honestly.

Question three. What happened to the people who resisted? Were they convinced, overruled, ignored, or promoted? Answer honestly.

Now ask one person who has been through a failed change at your organization: Why did that change never stick? Listen to their answer. Do not defend. Do not explain.

That is your baseline. Actual data from actual change.

You think change fails because people resist. It does not. Change fails because the system is structured to revert.

Why this matters. What the research teaches.

John Kotter studied dozens of change efforts. His finding is consistent across industries. Seventy percent of change efforts fail. Not because the change was wrong. Because the approach was wrong.

Kotter's eight steps are not a checklist. They are a sequence. Skip one and the change collapses.

Step one: Create urgency. People must believe the status quo is dangerous. Not uncomfortable. Dangerous.

Step two: Build the guiding coalition. One leader cannot drive change. You need a coalition of influential people who share the goal.

Step three: Form a strategic vision. Not a plan. A picture of the future that is clear enough to guide decisions.

Step four: Communicate the vision. Not once. Every channel. Every meeting. Every week.

Step five: Empower broad action. Remove barriers. Enable people to act. Give them permission to try.

Step six: Generate short term wins. Not after the change is complete. Within six months. Visible. Unambiguous.

Step seven: Consolidate gains and produce more change. Do not declare victory too early.

Step eight: Anchor the change in culture. The change is not complete until it is how things are done here.

Failure mode. You treat Kotter's steps as a menu. You skip the ones that are hard. The most commonly skipped are Step One (urgency) and Step Eight (anchoring). The most common failure pattern is skipping urgency, then declaring victory at launch.

The trigger line. Change fails at the gaps between the steps. Most often between Step One and Step Two, and between Step Seven and Step Eight.

Lewin's three stages: Unfreeze, Change, Refreeze. "Make the old way harder" is unfreezing. "Anchor change in culture" is refreezing.

ADKAR: The individual change model. Awareness. Desire. Knowledge. Ability. Reinforcement. Most change efforts jump from Awareness to Knowledge. They skip Desire. People do not want to change. Build desire first.

How to spot missing Desire. Passive compliance. Slow adoption. People doing the minimum. They attend training. They do not apply it.

Boundary condition. The two most common ADKAR gaps are Desire (they do not want to) and Reinforcement (they are not sustained). Diagnose which gap you are dealing with before you design the intervention.

The trigger line. You can teach someone how to use a new system. You cannot make them want to use it.

Before you begin.

You can force compliance. You cannot force commitment. The goal is to make the old way harder than the new way.

The identity beneath the moves.

Amateurs announce change. Professionals design the conditions where change becomes inevitable.

The amateur asks "how do I convince them?" The professional asks "what incentives and constraints shape what people actually do?"

The four moves.

Move one: Diagnose the real resistance.

Principle. People do not resist change. They resist loss. Status. Control. Competence. Relationships. Identity. Find the loss.

Counter case. In a high trust organization, people resist because they have seen change fail before. The loss is not what the change would take. The loss is hope. They do not believe it will work.

Failure mode. You assume resistance is irrational. You argue with feelings. You make it worse.

Action. For every person who resists, ask: what do they lose if this change succeeds? That is the real resistance.

The trigger line. Resistance is a symptom. Find the loss.

Default rule. If you cannot name what someone loses, you do not understand their resistance.

Move two: Make the old way harder.

Principle. People choose the easiest path. You do not start by making the new way easier. You start by making the old way harder.

Counter case. In a crisis, the old way is already hard. The system is failing. People are desperate for a new way. Your job is not to push. Your job is to show them the path.

Failure mode. You add training and support. The old way remains easy. People stay there.

Action. Change one system that makes the old way comfortable. Approval processes. Metrics. Recognition.

The tradeoff. Making the old way harder has costs. Who will fight back when you remove their comfort? What happens when short term performance dips because people are learning? You will be blamed. Decide in advance what cost you are willing to bear. If you are not willing to bear it, do not start.

The trigger line. People do not choose the best way. They choose the easiest way. Make the old way harder. Then survive the backlash.

Default rule. If the old way is still comfortable, you have not done your job.

Move three: Generate short term wins within six months.

Principle. Change is abstract. Wins are concrete. People need to see success. Within six months.

Counter case. In a long term transformation, six month wins may be impossible. The change is too large. Then your wins are milestones. We reached this step. We cleared this barrier. We built this capability.

Failure mode. You declare victory at launch. The launch is not the win. The win is changed behavior.

Action. Identify one thing that can be better in six months. Make it visible. Make it measurable.

The trigger line. A launch is an event. A win is changed behavior.

Default rule. If you cannot point to something demonstrably better in six months, you are managing a project, not leading change.

Move four: Anchor change in culture, not process.

Principle. Process changes can be reversed. Culture changes persist. Reinforcement is culture made visible through rewards. Who gets promoted? Who gets celebrated?

Counter case. In a weak culture, you cannot anchor change in culture because there is no culture to anchor to. You have to build the culture first. See Course 2.2.

Failure mode. You write a new process. You train people on it. Six months later, everyone is back to the old way.

Action. Ask: what would someone new see in their first week that told them the new way is real?

Metrics as enforcement. What gets measured overrides what gets said. Dashboards beat speeches. If your metrics still reward the old way, nothing will change. Change your metrics first. Then change your process.

The trigger line. A process tells people what to do. A culture makes them want to do it. A metric forces them to choose.

Default rule. If the new way does not show up in who gets promoted and what gets measured, the change has not anchored.

The integration layer. Power, culture, and change as one system.

Course 2.2 taught you to read culture. What gets rewarded. What gets punished.

Course 2.3 taught you to map power. Who decides. Who can quietly kill.

Course 2.4 gives you change. You cannot lead change without reading culture and mapping power.

Informal veto players. They never say no directly. They delay. They request more data. They say "let's revisit." The meeting ends. The decision never returns. Find them first.

Use all three. Diagnose the reward signals. Map the coalitions. Then lead the change.

How to communicate change effectively.

Principle. Communication is not information. Communication is meaning. People fill gaps in information with stories. Those stories are worse than reality.

Failure mode. You send one email. You hold one town hall. You wonder why people are confused.

Action. Send the same message through email, town hall, small group, one on one, written, verbal, visual. Each repetition is reinforcement. The question is not how many times you said it. The question is how many times they heard it.

The change curve. People move through states. Denial. Anger. Bargaining. Depression. Acceptance. These are not personality flaws. They are states. Read them. Do not fix them.

Denial needs data. Anger needs listening. Bargaining needs boundaries. Depression needs support. Acceptance needs direction.

The trigger line. The person blocking your change may not be blocking it. They may be grieving it.

Sustaining change after implementation.

Principle. Change does not end at go live. Maintenance begins there. Without reinforcement, the system reverts.

Failure mode. You launch. You celebrate. You move to the next project. Six months later, the old way is back.

Action. Build reinforcement into the operating rhythm. Quarterly reviews. Annual audits. Recognition for the new way. Consequences for reversion.

The trigger line. Launch is a milestone. Maintenance is the work.

Default rule. If you do not have a plan for six months after launch, you have a launch plan, not a change plan.

Transformation vs incremental change.

Principle. Incremental change improves the existing system. Transformation replaces it. Know which you are leading.

Failure mode. You treat transformation as a series of incremental changes. The cumulative change never arrives.

Action. For incremental change, move fast. For transformation, expect three to five years.

The trigger line. Incremental change optimizes. Transformation rebuilds.

What this looks like when you get it wrong.

A company launched a new performance system. Trained everyone. Celebrated. Six months later, no one was using it.

One manager said: "I knew the software was better. But my bonus depended on getting reviews done on time. The old way was faster. I chose my bonus."

The old way was still easier. The new way had no reinforcement.

The clean story that matters.

A hospital needed to change how nurses handed off patients. The old way was inconsistent. Mistakes happened. Three mandates failed.

A new leader asked the nurses: "What makes the new protocol hard to use?"

The answers: the form took too long. The computer was on the other side of the room.

She moved the computer. She shortened the form.

Within three months, the new protocol was standard. Because the new way was easier than the old way.

She said: "I spent years thinking change was about convincing people. It is about making the right thing easier than the wrong thing."

The messy story that matters.

A manufacturing plant manager needed to reduce waste. The old way was inefficient but comfortable. Operators had built their routines over years. They knew exactly how to do their jobs with minimal effort.

The manager changed the metrics. He added a waste report. He posted results publicly. He made the old way visible.

The operators fought back. They slowed production. They blamed the new metrics. They went to the plant director. The director called the manager in. "Fix this or you are out."

The manager did not back down. He spent three months absorbing the criticism. He held one on one meetings with every operator. He listened. He did not argue. He said "I understand why you are angry. I am not going back. Let us figure out how to make this work."

Production dipped for six weeks. Then it recovered. Then it exceeded the old baseline. Waste dropped by forty percent.

The manager later said: "I almost lost my job. No one warned me that making the old way harder would make people want to make me fail. I would do it again. But I would have prepared differently."

That is the real arc. Not clean success. Success after paying a price.

How to lead change when you are not the top leader.

Principle. You do not need formal authority to lead change. You need four things: a clear diagnosis, a small coalition, a visible win, and the patience to outlast resistance.

Failure mode. You wait for permission. The change never starts.

Action. Find two people who share your frustration. Pick one small thing you can change without permission. Change it. Show the result. Expand.

The trigger line. Permission is not required. A coalition and a win are required.

Default rule. If you are waiting for someone above you to lead the change, you are not leading change.

When to use these checkpoints.

Use the full four moves when change is significant, resistance is strong, or previous changes have failed.

Boundary condition. If the change is from above and you have no influence, protect your team. See Course 2.3. If the organization has failed repeatedly, the problem is the system. See Course 2.2.

The four phase system.

Phase One: Diagnose the real resistance. For every key stakeholder, write down what they lose.

Warning sign. If you cannot name a specific loss, you have not diagnosed.

You now know what people are protecting. Next week you change what makes protecting it easy.

Phase Two: Make the old way harder. Change one system that supports the old way.

Warning sign. If the old way is still comfortable, nothing will change.

Mid course checkpoint. Return to the opening test. Improved even slightly? The system is working.

Phase Three: Generate short term wins. Identify one thing that can be better in six months.

Warning sign. If you cannot point to a concrete improvement, you are not generating wins.

Phase Four: Anchor change in culture. Ask who gets promoted under the new way. Ask what gets measured.

Warning sign. If the people who thrived under the old way are still thriving, the change has not anchored. If the metrics still reward the old way, the change has not anchored.

Failure reflection loop. Write down one time you assumed resistance was irrational. One time you made the new way easier instead of the old way harder. One time you declared victory too early. One time you forgot to build desire. One time you underestimated the backlash. That is your next adjustment.

The measure that matters. Watch what happens when you stop pushing. If people revert, you changed process. If they continue, you changed the system.

What you have already done.

You completed the test. You asked why a past change failed. You discovered at least one gap between announcement and reality. That is data you did not have before.

The loop.

Diagnose the real resistance. Make the old way harder. Generate short term wins. Anchor change in culture.

The final verdict.

You cannot force commitment. You can make the old way harder than the new way. Build desire before knowledge. Anchor in culture, not process. Change your metrics first. Survive the backlash. Then watch what happens when you stop pushing. If they continue, you changed the system. If they revert, you only changed the meeting. The meeting is not the work. The work is what happens when the meeting ends.