Leading Organisational Change and Managing Resistance: The Learning Architecture That Actually Works

The Learning Architecture That Actually Works

The Second Case Study: When Openness Meets Chaos

the practitioner's story is one path. Let's look at another.

At a different company — a service organisation with about 600 people — the transformation followed a different trajectory. Their leader, a man we'll call the practitioner, took a softer approach.

The Approach

Where the practitioner faced strong resistance and met it with bold structural change, the practitioner encountered mild resistance and general openness. His team was willing to change. They just didn't know how.

the practitioner brought in an external review team. He created a multi-level steering committee. He established "Focus Units" with clear principles, big goals, and cascading sub-goals with action plans.

What Happened

The biggest lesson from the practitioner's experience? Openness to change does not equal readiness for change. His people were willing but unprepared. The organisation moved faster than its people could absorb, and the result was chaos disguised as progress.

The Critical Difference Between the Two Cases

The Getting Buy-In Playbook

By year two, the practitioner had developed an intuitive system for building support that she later codified into six principles:

. WIIF Them (What's In It For Them)

Not "the source organisation." For them. Personally. Specifically. Every role, every level, every individual has a different answer to this question. Find it.

. Show Results, Not Promises

Nothing builds credibility like evidence. the practitioner's early wins — even small ones — became her most powerful persuasion tools. A 20% reduction in changeover time on one line convinced more people than any presentation ever could.

. Communicate Successes Relentlessly

If a tree falls in the forest and nobody hears it, it didn't happen. The same is true for improvements. the practitioner created a weekly "wins board" — a physical display updated every Friday showing what each team had accomplished.

. Pilot and Expand

Don't try to change everything at once. Start with one team, one area, one process. Get it working. Let people see it. Then expand.

. Involve Them in the Discovery

The most powerful tool the practitioner used was Value Stream Mapping sessions — but not the way most companies do them. She made them multi-function, multi-level events. Operators sat next to directors. Mechanics worked alongside finance people. Everyone mapped the process together.

The magic wasn't in the map. It was in the conversation.

. Accept That Some People Won't Get It (Yet)

Not everyone will be an early adopter. That's fine. the practitioner stopped trying to convince the skeptics and instead focused on supporting the willing. When the results became undeniable, most skeptics came around on their own.

The ones who didn't? They self-selected out. And that was okay too.

The Paradigm Problem: Right Facts, Wrong Planet

One of the most insidious barriers to change is what you might call the "Right Facts, Wrong Planet" problem.

People in your organisation have facts. Real, accurate, verifiable facts. But those facts belong to the old reality — the way things used to work, the constraints that used to exist, the limitations that used to be true.

Examples you'll recognise:

"We tried that in 2015 and it didn't work." (Different team. Different context. Different tools. Different leadership.)

"Our customers won't accept that." (Have you asked them recently? Or are you assuming based on a complaint from three years ago?)

"The union will never agree." (The union agreed at two other plants. Did you involve them in the design, or just present them with a finished plan?)

Every one of these statements contains real facts. And every one of them is being applied to a planet that no longer exists.

Your job as a leader is to gently, persistently challenge which planet people are standing on.

What's Missing in Your Organisation Right Now?

After studying dozens of transformations, a pattern emerges. Most organisations that stall are missing the same things:

The Diagnostic Checklist

Be honest with yourself. How many of these does your organisation actually have — not in theory, but in practice?

Before and After

But the numbers don't tell the real story.

The real story was the practitioner — the supervisor who had stood up in that town hall and asked if his job mattered. the practitioner became the company's most effective coach. His team consistently outperformed every other team in the plant. When asked what changed, he said:

"I stopped telling people what to do. I started asking them what they thought. Turns out, they'd been thinking this whole time. I just never asked."

And the practitioner, the mechanic who caught the bearing failure? He became the company's first "Skills Ambassador" — a role that didn't exist before, where experienced team members spend 20% of their time teaching others.

And the practitioner — the one who quit at the very beginning? He came back. Eighteen months later, he heard about what was happening, reached out to the practitioner, and asked if there was still a place for him.

There was.

Your Takeaway: The Six Principles of LEANership

If the practitioner's story resonates — if you see your own organisation in the frustrations, the resistance, the potential — here's what to carry forward:

. Learn To See

The real art of discovery isn't finding new things. It's seeing what's already there with fresh eyes. Walk your own processes. Talk to your own people. The answers are closer than you think.

. Share Your Vision

Not a poster. Not a memo. A living, breathing picture of the future that you can articulate differently for every person — because every person needs to see themselves in it.

. Take Action

Every conversation is an opportunity to move toward the future state. And actions will always speak louder than strategy documents.

. Give to Get

Share your knowledge openly. Share your mistakes openly. The organisations that hoard information decay. The ones that share it accelerate.

. Develop Others

The best time to develop your people is while improving your processes — not before, not after, but during. Coaching and improving are the same activity.

. Synergise

High-performance teams put the needs of the team ahead of individual needs. This isn't natural. It must be designed, nurtured, and protected.

The Uncomfortable Question You Need to Answer Today

George Bernard Shaw once observed that reasonable people adapt to the world, while unreasonable people try to adapt the world to themselves — and therefore all progress depends on unreasonable people.

So here's the question:

Are you being reasonable?

Are you adapting to the dysfunction in your organisation — working around the broken processes, tolerating the disengagement, accepting the "that's just how it is" culture?

Or are you willing to be unreasonable enough to believe you can create something different?

the practitioner was unreasonable. the practitioner was unreasonable. the practitioner — eventually — was unreasonable.

The results were extraordinary.

What's Your Next Move?

You've read this far, which means something in this story resonated. So don't let it fade.

Pick one action from this list and do it this week:

• Have a one-on-one conversation with someone on your team and ask: "What's the biggest frustration in your daily work?"
• Identify one process where the people doing the work have never been asked for input — and ask them
• Look at your own calendar and calculate: what percentage of your time is spent directing versus coaching?
• Write down your organisation's vision in one sentence — if you can't, that's your first problem to solve
• Find one person outside your industry and ask them: "What would you change if you ran my operation for a week?"

The transformation doesn't start with a strategy document. It starts with a conversation.

Which conversation will you have today?

This post explores concepts from the LEANership™ framework developed by Practicon, integrating lean process improvement with leadership development to accelerate organisational change. The case studies are composites drawn from real transformation experiences across manufacturing and service industries.

If this resonated with you, share it with one leader who needs to read it. Not ten. Just one. The right one.

Context and scope

The uncomfortable truth: Your brilliant process improvement will fail—not because the logic is wrong, but because you forgot that humans aren't spreadsheets.

The Scene: A Transformation That Almost Wasn't

the practitioner had done everything right.

She'd mapped the processes. Identified the waste. Built the business case. The data was bulletproof—her lean transformation would save the hospital £2.3 million annually and reduce patient wait times by 40%.

Six months later, she sat in her car in the parking garage, forehead pressed against the steering wheel.

Nothing had changed.

The nursing staff still hoarded supplies "just in case." The consultants refused to attend huddles. The ward clerks had developed an impressive collection of workarounds that made her new system completely useless.

"They just don't get it," she told herself for the hundredth time.

But here's the thing the practitioner hadn't learned yet: People don't resist change. They resist being changed.

Level 1: "I Don't Understand" (The Easy One)

This is what most change leaders prepare for:

• Misinformation
• Missing data
• Confusion about trade-offs
• Conflicting information

You can fix this with facts. More training. Better documentation. Clearer communication.

But here's what trips people up: this is usually the smallest portion of your resistance.

Level 2: "I Don't Feel Safe" (The Hidden Iceberg)

Deeper than disagreement lies fear:

• Feeling undervalued or overlooked
• Distrust of leadership motives
• Fear of looking incompetent during the transition
• Loss of status or expertise
• Worry about job security
• Exhaustion from the last five "transformations"

You cannot fix this with a PowerPoint deck.

A project team at a major Australian logistics company discovered their executives scored high on technical competence but dramatically underperformed on emotional awareness of others. Their direct reports marked them 59% on understanding emotions—while the executives rated themselves at just 20%.

The gap between how leaders saw themselves and how their teams experienced them was a chasm.

Level 3: "I Don't Trust You" (The Deep Freeze)

Sometimes resistance runs deeper than any single change initiative:

• Historical animosity between departments
• Fundamental values conflicts
• Past betrayals that were never addressed
• Completely different goals

This requires relationship repair before any change can stick.

Direct the Rider: Make the Right Choice Obvious

Find the Bright Spots

Stop obsessing over what's broken. Start asking: Where is it already working?

In Vietnam, a nutrition researcher faced an impossible task: reduce childhood malnutrition with no budget and no authority. Instead of analysing the problem, he found families whose children were thriving despite identical poverty.

What were they doing differently? Small things—adding tiny shrimp and sweet potato greens to rice, feeding children multiple small meals instead of two large ones.

He didn't import solutions. He cloned what was already working.

In your organisation: Who's already doing this well? What ward, team, or individual has cracked it? Study them. Clone them. Scale them.

Script the Critical Moves

"Be more patient-centred" is useless.

"When a patient asks a question, stop what you're doing, make eye contact, and answer in plain English" is actionable.

The rider gets paralysed by abstract goals. Give specific behaviours instead.

A major retailer shifted their focus to just three critical moves for frontline managers. Not a 40-page playbook. Three things. Their staff engagement scores jumped 45%.

Point to the Destination

Not a vague vision statement. A destination postcard—a vivid picture of what the future looks like.

"In six months, every patient in this ward will receive their discharge summary in their hands before they leave the hospital. Not mailed later. Not emailed. In their hands, explained in words they understand, before they walk out the door."

That's a destination you can imagine reaching.

Motivate the Elephant: Make Them Feel Something

Find the Feeling

Here's what data-driven leaders get catastrophically wrong: Knowing isn't enough to cause change. People have to feel something.

A procurement manager wanted to consolidate the company's glove purchasing. Different factories were buying hundreds of different glove types at wildly different prices.

His PowerPoint got polite nods and no action.

So he collected a sample of every glove type the company purchased—all 424 of them. He piled them on the boardroom table. He tagged each one with its price.

Executives who had ignored the spreadsheet couldn't stop talking about the glove pile.

That's finding the feeling.

Consider a patient experience mapping exercise where every emotional touchpoint gets plotted. Not "Patient waits 47 minutes"—but "Patient feels forgotten, anxious that their name was missed, worried they're in the wrong place."

You're not mapping a process. You're mapping feelings.

Shrink the Change

The elephant gets spooked by big changes. Make the first step so small it feels almost ridiculous.

A car wash gave customers loyalty cards. Some started with 8 empty stamps (need 8 to get a free wash). Others started with 10 empty stamps plus 2 bonus stamps already filled in (need 10 to get a free wash).

Same number of stamps required. But the group with "progress" already made? 34% more likely to complete the card.

The elephant gets motivated by momentum. Show people they've already started.

Grow Your People

Behaviour change isn't just about actions. It's about identity.

"We're the kind of department that..." is more powerful than any policy document.

When nurses in a unit started calling themselves "The Falls Prevention Champions," their behaviour shifted before any new process was introduced. They'd already decided who they were.

Ask yourself: What identity does this change support? How can you help people see themselves as the kind of person who does this naturally?

Shape the Path: Make the Right Thing the Easy Thing

Tweak the Environment

Want doctors to wash their hands more? Put the sanitiser exactly where their hands naturally rest while waiting for the elevator.

Want staff to use the new form? Make it the default. Hide the old one.

Stop trying to change people. Change their surroundings.

An airline reduced costs by millions simply by making smaller garbage bags the default on flights. Crews used what was handed to them. No training required.

Build Habits

When behaviour is habitual, it's free. It doesn't drain the rider's energy or test the elephant's willpower.

Triggers build habits:

• "When I finish with a patient, I immediately log the notes"
• "When I arrive at my desk, I check the safety dashboard first"
• "When I see a colleague do something well, I say so out loud"

Checklists aren't about competence—they're about building habits that survive stress and fatigue.

Rally the Herd

Behaviour is contagious. Humans look to other humans for cues about how to act.

This cuts both ways.

If the dominant narrative is "This too shall pass, like every other initiative," that spreads. If respected peers visibly embrace the change, that spreads too.

You need to identify your informal influencers—not just the formal leaders—and get them on board first.

The Hidden Variable: Understanding Personality in Change

Not everyone resists for the same reasons or responds to the same appeals.

The Auditor (Analytical, Detail-Oriented, Introverted)

They need:

• Precise data
• Logical structure
• Time to analyse
• Detailed documentation

Don't: Rush them. Hit them with enthusiasm over evidence.

Do: Send materials in advance. Answer every question thoroughly. Show your working.

The Shaker (Decisive, Brief, Action-Oriented, Extroverted)

They need:

• One clear message
• Bold recommendations
• Quick decisions
• Bottom-line focus

Don't: Bury the lead. Give them 47 options. Over-explain.

Do: Start with the conclusion. Be direct. Keep it moving.

The Communicator (Big Picture, Energetic, Interactive)

They need:

• Stories and metaphors
• Involvement and participation
• Energy and passion
• Vision over detail

Don't: Drone through spreadsheets. Exclude them from the excitement.

Do: Paint the picture. Get them talking. Make them part of the narrative.

The Sharer (Empathic, Consensus-Seeking, People-Focused)

They need:

• Understanding of impact on people
• Consensus building
• Sensitivity to concerns
• Team involvement

Don't: Dismiss their people concerns as "soft." Rush past the relationship issues.

Do: Acknowledge feelings. Build in consultation. Show you've listened.

Here's the kicker: Your organisation probably isn't evenly balanced. If leadership is all Shakers and Auditors, you'll produce logical plans that nobody feels connected to. If it's all Communicators, you'll generate excitement that never converts to action.

The Return: What Changed for the practitioner

Six months after her parking garage breakdown, the practitioner tried again.

But this time, she started differently.

Before presenting any data, she spent two weeks shadowing—not to analyse processes, but to understand feelings. She asked nurses what made them proud. What frustrated them. What they worried about at 3 AM.

She found her bright spots: two nurses who had quietly developed workarounds that actually worked better than both the old system and her proposed new one.

She created an illustrative engineering practitioner through their department, including the moments of fear, confusion, relief, and gratitude.

She shrunk the change. Instead of a six-month transformation plan, she proposed one small experiment in one ward for three weeks.

She recruited the sceptics. The loudest critic became her co-designer, because she asked her: "What would make this work for you?"

The results:

• 22% improvement in total emotional intelligence scores
• 45% jump in interpersonal effectiveness ratings
• 33% increase in work output
• 25% improvement in quality measures
• 28% better planning and organisation
• Reduced absenteeism
• Lower dysfunctional team interactions

The transformation didn't just succeed. It spread. Other departments started asking: "What did you do differently?"

Engineering takeaway

Here's the uncomfortable truth you need to sit with:

Your best idea will fail if you only engage the logical mind while ignoring the emotional one.

Every resistance you encounter has a reason behind it. That reason might be cognitive (Level 1), emotional (Level 2), or deeply embedded (Level 3). Your response needs to match.

Before your next change initiative, ask yourself

Directing the Rider:

• Where are the bright spots we can clone?
• What are the three critical behaviours we need—and only those three?
• Can I describe the destination so vividly that people can see themselves there?

Motivating the Elephant:

• How will people feel this change, not just understand it?
• What's the smallest first step that creates momentum?
• What identity does this change support?

Shaping the Path:

• How can I make the right thing the easiest thing to do?
• What environmental cues will build habits?
• Who are my informal influencers, and are they visibly on board?

The Final Word

People will forget what you said.

People will probably forget what you did.

But people will never forget how you made them feel.

That's not soft. That's science. That's strategy. That's the difference between a transformation that changes everything and a project plan that gathers dust.

What's your biggest change challenge right now? Is the resistance you're facing about logic, emotion, or trust? Drop a comment below—I'd love to hear what you're navigating and what's working (or not).

Failure trigger and engineering context

It started with a late-night rabbit hole.

the practitioner was researching change management frameworks—again—when she stumbled across the practitioner's work on "Power and Love." Not the romantic kind of love, but something far more practical:

Power without Love is reckless and abusive. Love without Power is sentimental and anemic.

She watched his the source institution lecture three times. Something clicked.

The previous approach at the source manufacturing plant had been pure Power:

• Top-down mandates
• Penalties for non-compliance
• Vision dictated by leadership
• Resistance treated as a problem to solve

Meanwhile, scattered across the organization, small pockets of employees had been running their own grassroots improvements. One team had redesigned their workstation layout without permission. Another had created an informal knowledge-sharing system on their phones. A third had developed a customer feedback loop that management didn't even know existed.

These were acts of Love:

• Bottom-up innovation
• Passion and ideas driving change
• Empathy and shared values
• Support withdrawn when people didn't feel heard

Neither approach alone was working.

The mandated Lean program was technically sophisticated but emotionally bankrupt. The grassroots efforts were passionate but lacked resources and authority. Two rivers running parallel, never meeting.

the practitioner realized she didn't need better tools. She needed a completely different model.

Technical challenge

The next six months nearly broke her.

Week 2: the practitioner tried to merge the formal Lean program with the informal grassroots efforts. The operations managers saw it as "losing control." The floor workers saw it as "another management trick."

Trust was negative.

Week 6: She introduced the concept of "choice" into the improvement process. Instead of mandating participation in Kaizen events, she made them optional but meaningful. Attendance dropped 60% immediately.

Leadership panicked. "See? They don't want to improve."

But the practitioner noticed something else. The people who did show up were different. They weren't there because they had to be. They were there because they chose to be.

Month 3: The first cross-functional project launched—a collaboration between the quality team (who had formal Lean training) and the shipping department (who had the grassroots innovations).

It was a disaster.

The quality team wanted to "do it right" with proper documentation and sign-offs. The shipping team wanted to "just fix it" and move on. Meetings devolved into turf wars. Both sides accused the other of not understanding "real" improvement.

the practitioner almost gave up.

Month 4: She identified the missing ingredient—dedicated roles that bridged both worlds.

She didn't call them project managers. She called them Champions—people who believed in the vision but also had emotional capital with their peers.

She recruited Supporters—respected workers who would lend credibility without formal authority.

She secured an unwavering Sponsor—the CEO, who agreed to protect the experiment for one year, no matter what the quarterly numbers said.

And she brought in a Change Agent—an external consultant who didn't carry baggage from either camp.

This was the moment everything shifted.

Not because of the titles. But because each role served a different purpose:

Improvement method and result

Month 5: The first integrated improvement event happened in Assembly Line 3.

Here's what made it different from every previous Lean event:

Before:

• Management identified the problem
• the practitioner designed the solution
• Workers were told to implement
• Resistance was managed through compliance measures

After:

• A Champion identified the opportunity (a worker who'd been complaining for two years)
• Supporters validated it mattered to the team
• Cross-functional volunteers designed the solution together
• The Sponsor protected time and resources
• The Change Agent facilitated without controlling

The toolkit was the same: Value Stream Mapping, 5S principles, Kaizen methodology.

The conditions were completely different:

. Choice

No one was forced to participate. The twelve people in that room chose to be there. That choice created ownership no mandate ever could.

. Trust

The Sponsor had publicly committed to supporting the team's decisions, even if he disagreed. He kept that promise twice in the first month—once when the team rejected his preferred solution, once when they needed budget he hadn't allocated.

. Sacrifice

Management gave up control. Workers gave up cynicism. Both gave up the comfort of "that's not my job."

The result?

Assembly Line 3's cycle time dropped 34%. Not because of better mapping or cleaner workstations—those helped—but because twelve people who previously didn't talk to each other discovered they actually agreed on what needed to change.

The Methodology That Emerged: Four Quadrants of Change

By month eight, the practitioner had enough data to map what was actually happening. The organization was using three different change approaches—often unconsciously—and each had a place:

Quadrant 1: Change Management (Top-Down + Power)

Use when: You need to address formal, financial, or quality-driven outcomes. Strategic shifts. Compliance requirements. Major operational changes.

Characteristics:

• Initiated by leaders with clear vision and strategy
• Toolkit-driven approach
• Deals with resistance through structured engagement
• Begins with an agenda, objective, or problem

Risk: Becomes reckless when people feel like objects being moved on a chess board.

Quadrant 2: Grassroots Change (Bottom-Up + Love)

Use when: Innovation needs to bubble up. Continuous improvement culture. Employee-driven quality of life improvements.

Characteristics:

• Initiated by the people with passion and ideas
• Empathy and shared values drive momentum
• Toolkit is informal and emergent
• Deals with resistance by withdrawing support (the silent strike)
• Begins with a cause, struggle, or opportunity

Risk: Becomes anemic when it lacks authority to implement real change.

Quadrant 3: Change Advocacy (Bottom-Up + Social Cause)

Use when: Addressing workplace happiness, safety concerns, cultural shifts, or quality-of-life outcomes that management isn't prioritizing.

Characteristics:

• Grassroots energy around a specific cause
• Social outcomes matter as much as operational ones
• Often begins with frustration or passion, not data

Risk: Can feel threatening to leadership if not channeled productively.