← ArticlesLeading Organisational Change and Managing Resistance: Quadrant 4Engineering · ManufacturingLesson 25/32← PrevNext →
GuidePublished 14 Aug 20266 min readBy Kevin JoginManufacturingOperational ExcellenceThe Results: One Year Later

Engineering · Manufacturing · Operational Excellence

Leading Organisational Change and Managing Resistance: Quadrant 4

Engineering handbook for leading organisational change and managing resistance, covering quadrant 4: collaborative change (cross-functional + power and love),...

Executive summary

This handbook section converts the supplied engineering material into a practical, source-controlled reference. It concentrates on the following learning outcomes.

Quadrant 4: Collaborative Change (Cross-Functional + Power AND Love)
The Soft Tools Nobody Taught You in Business School
The Results: One Year Later
What This Means For You
The Framework: How to Apply This Tomorrow
Step 1: Map Your Current Approach

Quadrant 4: Collaborative Change (Cross-Functional + Power AND Love)

Use when: Complex challenges that require both authority and buy-in. Projects that cross departmental boundaries. Changes that need to stick.

Characteristics:

  • Can be initiated by leaders OR people
  • Vision meets passion
  • Puts ideas into action through defined implementation roles
  • Relies on conditions (choice, trust, sacrifice) rather than compliance
  • Uses both hard tools (Value Stream Mapping, 5S) and soft tools (facilitation, mentoring, mediation)

This is the quadrant where sustainable change lives.



The Soft Tools Nobody Taught You in Business School

Here's what surprised the practitioner most: the "soft" stuff was actually the hardest part.

The Lean framework gave her hard tools:

  • Value Stream Mapping (to see waste)
  • 5S Kaizen (to organize and standardize)

But she needed soft tools to make them work:

  • Facilitation (to keep cross-functional groups productive)
  • Mentoring (to develop internal change capability)
  • Mediation (to navigate the inevitable conflicts)

And underneath all of it, the "people stuff" that doesn't fit in frameworks:

  • Empathy (to understand why resistance exists before trying to solve it)
  • Respect (to value contributions regardless of title)
  • Leadership (not the positional kind—the courage to go first)

The dirty secret of Lean transformation?

You can teach someone Value Stream Mapping in an afternoon. Teaching empathy takes years. Building trust takes consistency over months.

Most organizations want the quick wins from the hard tools without investing in the soft infrastructure that makes those wins sustainable.

That's why most Lean transformations fail within three years.



The Results: One Year Later

By month twelve, the source manufacturing plant looked completely different:

Metric Before After
Employee turnover 47% 18%
Improvement suggestions (monthly) 3 47
Cross-functional projects 0 12 active
Average time to implement improvement 6 months 3 weeks
Employee engagement score 31 68

But here's what the numbers don't show:

The morning stand-ups where people actually talked to each other. The Champion in Quality who became the most requested facilitator in the company. The Sponsor who learned to ask "what do you need?" instead of "what's the status?" The floor worker who pitched an idea to the board—and got funded.

Change isn't something you implement. It's something you cultivate.



What This Means For You

If you're stuck in a change initiative that's stalling, ask yourself:

Are you over-indexed on Power?

  • Is your team compliant but disengaged?
  • Do improvements disappear when leadership stops watching?
  • Is "resistance" your most common diagnosis for what's wrong?

Are you over-indexed on Love?

  • Do you have lots of passionate ideas but nothing actually changes?
  • Are grassroots efforts happening underground, disconnected from strategy?
  • Does leadership seem threatened by bottom-up innovation?

The answer isn't choosing one or the other. It's building the conditions—choice, trust, sacrifice—that allow both to work together.



The Framework: How to Apply This Tomorrow


Step 1: Map Your Current Approach

Which quadrant are most of your change efforts sitting in? If everything is in Quadrant 1 (top-down power), you have a compliance problem. If everything is in Quadrant 2 (grassroots love), you have an authority problem.


Step 2: Identify Your Roles

Do you have:

  • ✅ An unwavering Sponsor with real authority to protect the work?
  • Dedicated Champions who carry emotional energy, not just project plans?
  • Committed Supporters who lend credibility with their peers?
  • ✅ A Change Agent (internal or external) who can facilitate without controlling?

Missing roles = missing capability. Fill the gaps.


Step 3: Establish the Conditions

Before your next improvement initiative, audit these three conditions:

Choice: Are people participating because they have to or because they want to? Make participation voluntary wherever possible. Watch who shows up.

Trust: Has leadership demonstrated willingness to be influenced by the team's decisions? If not, you're not ready for collaborative change. Build trust first.

Sacrifice: Is anyone giving something up? If management keeps full control and workers keep full cynicism, nothing has actually changed.


Step 4: Balance Your Toolkit

For every hard tool, identify a soft tool partner:

Hard Tool Soft Tool Partner
Value Stream Mapping Facilitation workshops
5S Kaizen Mentoring for sustainability
Implementation planning Mediation for conflict
Project meetings Active listening sessions

Step 5: Start Small, Cross-Functionally

Don't launch a company-wide transformation. Find one cross-functional problem where:

  • Leadership cares (power)
  • Workers care (love)
  • A Champion exists
  • Success can be visible in 90 days

Run one Collaborative Change project. Learn from it. Then scale what works.



The Question Nobody Asks

Most change management discussions focus on what to do: which framework, which tools, which methodology.

The question that actually matters is who you're becoming as you do it.

Are you becoming an organization that treats people as problems to be solved? Or one that treats them as partners in solving problems together?

Power AND Love. Tools AND people. Strategy AND empathy.

That's where real change happens.



Your Turn

I want to hear from you:

What's one change initiative you've seen fail because it was over-indexed on either Power OR Love? What would have been different if both were present?

Drop your story in the comments. The best learning comes from shared experience.


This framework is inspired by the practitioner's "Power and Love: A Theory and Practice of Social Change" and adapted for organizational Lean transformation. For deeper exploration, check out his book or his lecture at the source institution on YouTube.


About This Post

This article draws on principles from collaborative change methodology, integrating traditional Lean frameworks with human-centered approaches to organizational transformation. The fictional case study of "the source manufacturing plant" illustrates real patterns observed across multiple industries.

Want to go deeper? Share this with a colleague who's struggling with a stalled change initiative. Sometimes the breakthrough isn't a better tool—it's a different conversation.

Engineering use and verification

Choose and control a process from the required function, material, geometry, tolerance, surface condition, volume, safety and inspection plan. Confirm the process window with representative trials, identify the variables that move quality, and connect each critical characteristic to an observable control and reaction plan. Do not convert a successful source example into a universal limit; validate capability using the actual machine, tooling, material batch and operating conditions.

  • Confirm scope, assumptions, interfaces and required outcome.
  • Use one controlled unit system and show every conversion.
  • Identify current project, customer and regulatory requirements.
  • Separate source examples from mandatory acceptance criteria.
  • Check calculations, tables and selections by an independent method.
  • Verify safety, maintainability and credible failure modes.
  • Record evidence, revisions, approvals and unresolved limitations.
  • Validate the result under representative operating conditions.

Continue learning

Leading Organisational Change and Managing Resistance: The Learning Architecture That Actually WorksGuide · ManufacturingNEXT LESSON →Supply-Network Resilience and Total-Cost DecisionsGuide · ManufacturingLeading Organisational Change and Managing Resistance: The Myth That Kills Every Change InitiativeGuide · ManufacturingExperiential Training and Workforce CapabilityGuide · Manufacturing