Leading Organisational Change and Managing Resistance: The Myth That Kills Every Change Initiative

Context and scope

Leadership & Change Management

The Myth That Kills Every Change Initiative

Here's what nobody tells you in business school:

Change is fast. Transition is slow.

These are not the same thing, and confusing them is the single biggest reason transformations fail.

Change is situational. It's the new software, the restructured team, the updated process. It happens on a specific date, with a specific announcement. Done.

Transition is psychological. It's the slow, messy, deeply human process where people gradually accept the new reality — and grieve what they've lost.

Yes, grieve. That word isn't too strong.

the practitioner, the godfather of transition management, mapped out exactly what this looks like. Every transition moves through three phases — and skipping any of them is like removing a load-bearing wall from a building.

Phase 1: The Ending (Where Everything Actually Begins)

This is the part that breaks most leaders.

Every transition — even a positive one — starts with a loss. Before anyone can embrace what's new, they have to let go of what was. And what they're letting go of isn't just a process or a title. It's their identity. Their competence. Their sense of "I know how things work here."

What People Actually Feel During Endings

Think about the last time your role fundamentally changed. You probably experienced some version of this emotional cascade:

Denial → "This won't really affect me." ↓ Shock → "Wait, they're serious?" ↓ Anger → "Nobody asked ME about this." ↓ Frustration/Stress → "I can't do my job AND learn all this new stuff." ↓ Ambivalence → "Maybe it'll work. Maybe it won't. I don't care anymore."

Here's the critical insight most leaders miss: these reactions aren't resistance. They're a completely human response to loss.

The Story of the practitioner's "Resistance"

Back at the practitioner's factory, the practitioner had been the shift lead for seven years. She knew every quirk of the production line. When a machine sounded slightly off at 2 AM, she could diagnose the problem by ear alone.

The Lean Implementation meant standardized work instructions, visual management boards, and cross-training rotations. On paper? A massive improvement. For the practitioner? It meant the expertise she'd spent seven years building was suddenly... irrelevant.

She wasn't "resistant to change." She was mourning the loss of what made her her at work.

If you're leading a change right now, stop and ask yourself: Who on your team is losing something they deeply value — even if you can't see it?

The 5 Rules for Handling Endings (Without Destroying Trust)

Rule 1: Describe the Change in Brutal Detail

Vagueness is the enemy. When people don't have information, they invent it — and what they invent is always worse than reality.

Say what you know. Say what you don't know. And commit to a specific time when you'll give them more.

That last part is crucial. "We'll keep you updated" means nothing. "I'll share the next update at our Thursday 9 AM meeting" means everything.

Rule 2: Identify the Ripple Effects

Every change creates secondary losses that leaders rarely anticipate:

• The team lunch routine that disappears when desks are rearranged
• The informal mentorship that evaporates when reporting lines shift
• The sense of mastery that dissolves when tools and processes change
• The social status that erodes when titles or responsibilities are reassigned

Map these out. Write them down. If you don't, they'll ambush you later.

Rule 3: Acknowledge Losses — Even the Ones You Think Are Silly

This is where most leaders fail spectacularly.

When someone tells you they're upset about losing their corner desk, your instinct is to say, "Come on, it's just a desk." Don't.

Loss is subjective. Your point of view on whether their loss is "rational" is completely irrelevant. If you dismiss what people feel, you don't just lose the argument — you lose the dialogue entirely. They'll stop telling you what's wrong, and you'll lose your ability to lead them through it.

Be aware of the "Psychological Contract" — the unwritten agreement between people and their organization about how things should work. Break it without acknowledgment, and trust shatters.

Rule 4: Never Ridicule the Past

This one cost the practitioner dearly.

In a team meeting, trying to build excitement for the new Lean metrics, he said: "Honestly, productivity as we measured it before was a pretty garbage metric."

What he meant: "We have better tools now."

What the team heard: "Everything you've worked toward for the last decade was worthless."

Position the past as a positive legacy that made the new possible. The old way wasn't wrong — it was the foundation. Frame it that way, and people can move forward without feeling erased.

Rule 5: Let People Take Something With Them

When you renovate a house, you keep the family photos. When you transform an organization, you need to find the equivalent.

Maybe it's preserving a team tradition. Maybe it's carrying forward a metric that still matters. Maybe it's simply saying, "This part of how we did things? That was excellent, and it stays."

Give people something to hold onto while everything else shifts.

Phase 2: The Neutral Zone (The Dangerous Middle)

If the Ending is where trust breaks, the Neutral Zone is where initiatives go to die.

This is the messy, uncomfortable gap between the old way and the new way. People have let go of what was, but they haven't yet grabbed onto what will be. They're floating.

What the Neutral Zone Looks and Feels Like

The Neutral Zone is where old weaknesses re-emerge. At the practitioner's factory, the team had just spent months moving from batch production to continuous flow. Three weeks into the Neutral Zone, without anyone deciding to do it, the line started batching again. The old habit crept back like water finding a crack.

How to Survive (and Leverage) the Neutral Zone

Here's the counterintuitive truth: the Neutral Zone isn't just a danger — it's an opportunity. It's the most creative period in any transition, because the old rules don't fully apply and the new ones aren't locked in yet.

But you have to manage it deliberately:

→ Set the bar low and celebrate small wins. During the Neutral Zone, your team's capacity is genuinely reduced. Don't pretend otherwise. Set achievable short-term goals so people can feel progress even when everything feels uncertain.

→ Don't overpromise output. If you're implementing new processes, build buffer into your timelines. Have some slack in your pocket. Nothing kills morale faster than failing to hit targets during a period when people are already doubting themselves.

→ Provide training on teamwork and problem-solving. Not as a one-time event ("sheep dipping," as practitioners call it — where you dunk people in training and then wonder why nothing sticks). Continuous, practical, applied training. If people understand, they can accept. If they practice, they can master.

→ Watch for unrelated changes. People can handle understandable change when it's part of the bigger picture. But unrelated, unexpected changes during a transition? That's the straw that breaks the camel's back. Postpone anything non-essential.

→ Develop temporary roles and structures. Reassure people explicitly: their jobs are secure. Create transitional responsibilities that bridge old skills to new ones. This isn't just kind — it's practical. A panicked workforce doesn't innovate.

Phase 3: The New Beginning (Not the Same as a "Start")

Here's a distinction that separates great leaders from mediocre ones:

Starts involve new situations. Beginnings involve new understandings.

You can start a new process on Monday. But the beginning — the moment when people genuinely internalize why it matters, how it works, and where they fit — that takes intentional effort.

The 4 P's That Launch Real Beginnings

the practitioner eventually learned these the hard way. You don't have to.

That last P — Part — is the one that changed everything for the practitioner.

When he stopped treating his team as recipients of change and started treating them as co-designers of it, something shifted. The Kaizen teams he formed didn't just fix processes; they gave people ownership. And ownership is the antidote to helplessness.

Change by me — OK. Change to me — NOT OK.

This is one of the most powerful principles in change management. The moment you invite people to solve the problems themselves, resistance evaporates — not because the change got easier, but because the change became theirs.

The Do's and Don'ts Cheat Sheet

After watching dozens of transformations succeed and fail, here's the distilled wisdom:

✅ DO

• Link improvement efforts to the organizational plan and develop KPIs so progress is visible and trackable
• Implement temporary systems during the transition — don't force a cold cutover
• Benchmark firsthand — take people to see what "good" looks like at other organizations
• Offer comprehensive, ongoing training — not one-off workshops that lead to disinterest
• Use pilot areas to stimulate interest and enable peer-to-peer knowledge sharing
• Develop a dedicated change/transition manager role — someone whose job is the human side
• Hold regular team meetings even before the change begins, building the habit of dialogue
• Talk openly about the transition and normalize the emotional journey

❌ DON'T

• Explain change through a memo or org chart — people can't process transformation through a document
• Turn the entire change over to a single expert and ask them to build the plan alone — this isn't one person's job
• Make threats — fear doesn't create commitment; it creates compliance at best and sabotage at worst
• Rely on trickle-down communication — supervisors are in transition themselves and can't be your only channel
• Rationalize not communicating — the grapevine already has the news, and silence fills the void with fear

The Organizational Life Cycle: the source organisation Sit?

Every organization follows a predictable arc. Understanding where you are determines how you should approach change.

                    ┌─────────────┐
                    │  Make It Big │
                   ╱               ╲
          ┌───────┐                 ┌────────────────┐
          │  Get  │                 │Institutionalize│
          │Organized                │                │
         ╱                                            ╲
┌───────┐                                     ┌────────┐
│Launch │                                     │Close In│
│Venture│                                     │        │

╱ ╲ ┌─────┐ ┌─────┐ │Dream│ │ Die │ └─────┘ └─────┘

Four Laws of Organizational Development

1. The Comfort Trap: The people most comfortable in one phase experience the most setbacks in the next. Your star performers today may be your biggest resistors tomorrow — not because they're bad, but because they have the most to lose.
2. The Success Paradox: The things that made one phase successful are usually the things that must be released in the next. The scrappy startup mentality that built the company will strangle it at scale.
3. The Pain Signal: When you see pain in an organization, people are probably going through a transition. Don't diagnose it as a performance problem. Diagnose it as a human one.
4. The Commitment Rule: Don't go halfway. A half-implemented change is worse than no change at all. It creates all of the disruption with none of the benefit.

Organization Renewal: The Infinite Game

Here's the mindset shift that separates organizations that thrive from those that merely survive:

Every status quo is just a temporary way until a better way has been discovered.

The goal isn't to complete one transformation and then rest. It's to build an organization that treats change as its natural operating mode.

How to Stay Ahead of Non-Stop Change

The organizations that get this right don't just survive change — they capitalize on it. While competitors are still processing what happened, transition-ready companies are already three moves ahead.

the practitioner's Ending (And New Beginning)

Six months after his disastrous memo, the practitioner tried again. But this time, everything was different.

He started by sitting with the practitioner and her team — not to present, but to listen. He asked them what problems they saw on the production line. He asked what frustrated them. He asked what they'd fix if they could fix anything.

Then he gave them the tools and authority to fix it.

The Lean transformation that had failed as a top-down mandate succeeded as a bottom-up movement. Not because the methodology changed, but because the approach to people changed.

the practitioner didn't submit a transfer request. She became the champion of continuous improvement on her shift — not because the practitioner convinced her, but because she convinced herself.

Your Move

If you're leading a change — or about to — here are three questions to sit with before you do anything else:

1. What are people losing? Not what you think they should feel. What are they actually losing — including the intangible things like identity, competence, and belonging?

2. Where are you in the transition? Are you still in the Ending phase, the Neutral Zone, or approaching the New Beginning? Each requires a fundamentally different leadership approach.

3. Have you given people a Part to play? Not just a role in the new structure — but a genuine voice in shaping how you get there?

The difference between a change that transforms and a change that traumatizes often comes down to one thing: whether you managed the situation or managed the transition.

They're not the same thing. And now you know the difference.

What's the biggest change you're navigating right now — and which phase of transition are you stuck in? Drop your thoughts below. Every response gets a reply.

References & Further Reading:

• Managing Transitions by the practitioner — the foundational text on the psychology of organizational change
• Bridges' Transition Model — Ending → Neutral Zone → New Beginning
• Lean Implementation change management frameworks

This post was adapted from change management principles presented in the the source organisation Lean Network series, November 2009, drawing on the practitioner' transition management methodology.

The Uncomfortable Truth Nobody Wants to Hear

Here's what most organisations get catastrophically wrong about improvement:

They treat it as a process problem when it's actually a people problem.

They buy the tools. They hire the consultants. They roll out the training. And then they wonder why, six months later, everything has reverted to the old way of doing things.

The data is brutal:

the practitioner didn't know these numbers yet. But she was about to live them — and then defy them.

What "Normal" Looked Like

The plant ran the way it had always run. Operators operated. Mechanics fixed things when they broke. Supervisors supervised — which mostly meant telling people what to do and writing reports about what went wrong.

There were three invisible walls that kept everything stuck:

Wall #1: Seniority ruled everything. Promotions, shift assignments, even who got to operate the new equipment — all based on how long you'd been there, not what you could do. A brilliant 25-year-old with three years of experience waited behind a disengaged 55-year-old with thirty years of showing up.

Wall #2: Information flowed one way — down. The people closest to the problems had the least authority to solve them. Every decision, no matter how small, needed approval from someone who hadn't touched the production floor in years.

Wall #3: Learning had stopped. The last formal training most employees remembered was their onboarding. Skills were passed down informally, inconsistently, and often incorrectly — like a decades-long game of telephone.

Sound familiar?

The Five Success Factors the practitioner Didn't Know She Needed

Before diving into what the practitioner did, you need to understand the framework she unknowingly followed. Every successful organisational change — every single one — addresses five critical factors:

The Change Success Framework

Miss even one, and the whole thing collapses. Most organisations nail Purpose (they write a great vision statement), half-attempt Process (they create a project plan), and completely ignore the other three.

the practitioner was about to learn this the hard way.

Phase One: The Bold Vision (And the Resistance It Created)

Setting a Purpose That Actually Meant Something

the practitioner's first move was to write a three-year vision. Not a corporate platitude. A specific, measurable, slightly terrifying picture of the future:

"In three years, every production team will be self-sufficient — capable of doubling output without overtime, managing their own scheduling, quality, and maintenance. Every team member will be a multi-skilled technician, not a single-task operator."

She printed it on large posters and hung them in every break room, every meeting space, every hallway.

The reaction was immediate. And it was not applause.

The Wall of Resistance

Her middle managers — the supervisors and shift leaders — were the first to push back. For years, their authority came from being the gatekeepers of information and decisions. Self-sufficient teams meant their traditional role was obsolete.

One supervisor, an illustrative engineering practitioner who'd been there for twenty-two years, stood up in a town hall meeting and said what everyone was thinking:

"So you're telling us our jobs don't matter?"

the practitioner paused. This was the moment that would define everything.

"No," she said. "I'm telling you your jobs are about to matter more than they ever have. But they're going to look completely different. You're not going to be controllers anymore. You're going to be coaches."

The room went silent.

This is the part most leaders skip. They announce the vision but never address the question every single person in the room is silently asking:

"What's In It For Me?"

This question — WIIFM — is not selfish. It's human. And if you can't answer it for every level of your organisation, your change initiative is already dead.

the practitioner spent the next two weeks having one-on-one conversations. Not presentations. Conversations. She asked each person two questions:

1. What's the biggest frustration in your daily work?
2. If you could change one thing about how this place runs, what would it be?

The answers were remarkably consistent:

"I'm bored."

"Nobody listens to my ideas."

"I've been doing the same thing for twelve years."

"I don't understand why we do half the things we do."

People didn't resist change. They resisted change that didn't include them.

Everything Got Worse Before It Got Better

Six months in, the practitioner was questioning everything.

She had reorganised the floor into self-directed teams. She had launched a skills-based qualification system to replace the old seniority model. She had created cross-functional steering committees. She had done everything "right."

And the numbers were going in the wrong direction.

Productivity dropped 15%. Scrap rates increased. Two more experienced employees quit. The finance director started making pointed comments about ROI in leadership meetings.

This is where most leaders panic and abandon ship. the practitioner almost did.

But then she remembered something the practitioner had said at that conference — a set of principles from systems thinker Peter Senge that she'd scribbled in her notebook:

Senge's Laws of Systems Thinking (The Ones That Save Your Sanity)

That last one hit the practitioner like a freight train.

The dip was not failure. It was the system reorganising itself.

Operators who had only ever pressed buttons were now learning mechanical changeovers. Mechanics who had always worked alone were now teaching others and learning coordination skills. Supervisors who had always given orders were now learning to ask questions instead.

Of course things got messier. Everyone was simultaneously incompetent at their new responsibilities while mourning the competence they'd had in their old ones.

an illustrative engineering practitioner Changed Everything

Three months into the dip, something happened that nobody planned.

the practitioner, a 15-year mechanic who had initially been one of the loudest critics of the new system, was working on his coordination skills. Part of his new role required him to facilitate a daily team huddle — something he'd never done and actively resented.

On a Thursday morning, during what should have been a routine 10-minute standup, an illustrative engineering practitioner mentioned a recurring vibration in one of the packaging lines. In the old system, she would have filed a maintenance request, waited 48 hours, and a mechanic would have eventually looked at it.

But the practitioner was standing right there. He asked her to show him. She did. He recognised the pattern immediately — a bearing that was three weeks from catastrophic failure. Together, they scheduled a replacement during the next planned downtime.

Estimated cost of the prevented failure: over 200,000 in the local currency unit of any manufacturing plant you've worked in.

But that's not the real story.

The real story is what happened next. the practitioner went back to the huddle and said:

"I've been doing maintenance here for fifteen years. I've fixed that exact bearing failure six times. Six times. And every single time, it was an emergency. Because nobody on the floor knew what to listen for. And nobody asked me to teach them."

He paused.

"This is the first time someone caught it before it broke. And it wasn't because of some new system or tool. It was because we were actually talking to each other."

That moment — not a training program, not a consultant's framework, not a leadership directive — was when the culture started to shift.

The Five Elements of Metanoic Organisations

┌────────────────────────────────────────────────────┐ │ │ │ 1. VISION │ │ A stretch goal that people believe is │ │ possible but don't yet know how to reach │ │ │ │ 2. ALIGNMENT │ │ Every individual rowing in the same direction │ │ │ │ 3. PERSONAL ABILITY & MASTERY │ │ Developing each person to their full potential │ │ │ │ 4. SYSTEMS DESIGN │ │ Consciously designing how the organisation │ │ works as an interconnected whole │ │ │ │ 5. REINTEGRATION OF INTUITION & RATIONALITY │ │ Trusting experienced judgment alongside data │ │ │ └────────────────────────────────────────────────────┘

Most organisations get stuck on Element 1. They write beautiful vision statements, laminate them, and hang them on the wall. Then they skip straight to Element 4 — reorganising, restructuring, implementing new systems.

They miss the human middle: alignment, mastery, and intuition.

This is exactly what makes LEANership different from plain "lean." Lean gives you the process tools. LEANership ensures the people wielding those tools are developed, motivated, and aligned enough to use them.

The Organisational Design Nobody Talks About

the practitioner's team used a model from organisational theorist Jay Galbraith that connects five interdependent elements:

The Galbraith Star Model

TASKS (What work needs doing?) │ ┌───────────┼───────────┐ │ │ │ STRUCTURE INFORMATION DECISION (How is work & METRICS MAKING organised?) (What do we (Who decides │ measure?) what?) │ │ │ └───────────┼───────────┘ │ ┌─────┴─────┐ │ │ PEOPLE REWARDS (Skills, (What gets values, recognised culture) & rewarded?)

The critical insight: if you change one element, you must adjust all the others. the practitioner's company changed the Tasks (operators now did maintenance, mechanics now coordinated) but initially failed to update:

• Rewards — the pay system still rewarded seniority, not skill
• Decision Making — supervisors still held approval authority
• Information — teams didn't have access to their own performance data

Once she aligned all five elements, the results started compounding.

What High-Performance Teams Actually Look Like

By month fourteen, something remarkable had happened. Three of the practitioner's teams had crossed a threshold that researchers call "High Performance Team" status.

Characteristics of High-Performance Teams vs. Average Teams

That last row is the hardest to achieve and the most powerful when you get there.

the practitioner's team was the first to hit it. The metric that proved it? They went from 420 minutes of unplanned downtime per month to 38 minutes. Not because they got better equipment. Because they were talking to each other, teaching each other, and catching problems before they became emergencies.

The Unlearning Problem: Why Smart People Get Stuck

Here's something the practitioner didn't anticipate: the most experienced people had the hardest time.

Not because they lacked intelligence. Because they had to unlearn before they could relearn.

American futurist Alvin Toffler captured this perfectly:

The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.

Consider this sobering data point from educational researcher Andrew Fuller:

The implication is staggering. If formal education now covers only 2% of what your people will need, then 98% of their capability must be developed on the job. And if your organisation doesn't have a deliberate system for that development, you're leaving 98% of your potential on the table.

This is why "just-in-time learning" matters. But the practitioner learned it comes with a critical caveat:

Just-in-time learning is powerful — but don't skip the fundamentals at key stages of development.

Her most successful approach looked like this: