The Factory That Almost Died — And the Leadership Secret That Saved It
Why 70% of improvement programs fail — and what the survivors do differently.
The Morning Everything Changed
Sarah Chen arrived at the plant on a Tuesday morning to find the third resignation letter on her desk that month.
She was the newly appointed Operations Director at a mid-sized manufacturing company — 400 employees, two shifts, and a reputation for producing decent products at painfully slow speeds. The board had hired her to "fix things." The previous director had tried lean tools, Six Sigma projects, even a fancy consulting engagement. None of it stuck.
The whiteboard in her office still had the faded remnants of the last initiative: a value stream map nobody followed, a 5S checklist nobody checked, and a mission statement nobody believed.
Sarah stared at the resignation letter. It was from Marcus, one of her best team leaders. His reason?
"I'm tired of being told to change without being told why — or how."
That single sentence would become the catalyst for the most dramatic transformation the company had ever seen.
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:
| Improvement Initiative Outcome | Percentage |
| Fail to sustain after 2 years | 70% |
| Achieve partial results only | 20% |
| Fully sustain and scale | 10% |
Sarah didn't know these numbers yet. But she was about to live them — and then defy them.
The Status Quo: A Company Running on Autopilot
Before we follow Sarah's journey, let's set the scene. Because her company looked a lot like yours might right now.
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 Inciting Incident: When the Mirror Cracks
Two weeks after Marcus quit, Sarah attended an industry conference. A speaker named David — a weathered veteran of organisational transformations — said something that rewired her thinking:
"You don't have a lean problem. You don't have a quality problem. You have a leadership problem wearing a process costume."
David introduced a concept he called LEANership — the deliberate integration of "people" skills with "process" skills to accelerate improvement. Not one or the other. Both. Simultaneously. Always.
He drew a simple framework on the whiteboard:
┌─────────────────┐
│ DIRECTION │
└────────┬────────┘
│
┌──────────────┼──────────────┐
│ │ │
┌─────────▼──────┐ ┌───▼────────┐ ┌──▼──────────────┐
│ SKILL │ │ ENABLING │ │ ENVIRONMENT │
│ ACQUISITION │ │ (Coaching) │ │ (Organisation) │
└────────────────┘ └────────────┘ └─────────────────┘
The idea was simple but radical: you cannot separate developing people from improving processes. The best time to develop your people is while you're improving the processes in your business. Not before. Not after. During.
Sarah flew home with a notebook full of scribbles and a plan forming in her mind.
The Five Success Factors Sarah Didn't Know She Needed
Before diving into what Sarah 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
| Factor | The Question It Answers |
| Purpose | Why are we changing, and where are we going? |
| People | Who needs to change, and what's in it for them? |
| Process | How will we get there, step by step? |
| Communication | How do we keep everyone informed and aligned? |
| External View | What can we learn from outside our own walls? |
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.
Sarah 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
Sarah'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, a man named Tom 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?"
Sarah 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.
Sarah spent the next two weeks having one-on-one conversations. Not presentations. Conversations. She asked each person two questions:
- What's the biggest frustration in your daily work?
- 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.
Phase Two: The Struggle — When Systems Thinking Meets Real Life
Everything Got Worse Before It Got Better
Six months in, Sarah 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. Sarah almost did.
But then she remembered something David 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)
| Law | What It Means In Practice |
| There are no right answers | Stop looking for the "one correct solution." Experiment. |
| You can't divide your elephant in half | Partial implementations create more problems than they solve. |
| Cause and effect are not close in time or space | The results of today's decisions won't show up for months. |
| You'll have your cake and eat it too — but not all at once | The benefits are real. They just don't arrive simultaneously. |
| The easiest way out will lead back in | Shortcuts and workarounds always return as bigger problems. |
| Behaviour will grow worse before it grows better | This is the one that matters most right now. |
That last one hit Sarah 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.
The Turning Point: When a Mechanic Named James Changed Everything
Three months into the dip, something happened that nobody planned.
James, 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, a junior operator named Priya 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 James 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. James 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 Framework Behind the Transformation
What Sarah had stumbled into (and what you can implement deliberately) was something organisational theorists Charles Kiefer and Peter Senge call a "Metanoic Organisation" — an organisation that operates with the conviction that it can create its own future.
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
Sarah'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. Sarah'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 Sarah's teams had crossed a threshold that researchers call "High Performance Team" status.
Characteristics of High-Performance Teams vs. Average Teams
| Characteristic | Average Team | High-Performance Team |
| Role clarity | "That's not my job" | Everyone understands every role |
| Skill diversity | Specialists working in silos | Complementary skills across members |
| Leadership | Positional authority | Rotating, situational leadership |
| Purpose | Vague or imposed | Deeply shared and personally meaningful |
| Results | Meet expectations occasionally | Consistently exceed expectations |
| Problem solving | Blame and escalate | Creative, collaborative solutions |
| Conflict | Avoided or destructive | Constructive debate is welcomed |
| Ego | Individual achievement first | Team needs ahead of individual needs |
That last row is the hardest to achieve and the most powerful when you get there.
James'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 Sarah 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:
| Era | Knowledge at Graduation vs. Career Needs |
| 50 years ago | A high school graduate left knowing 75% of what they'd need in their working life |
| Today | A high school graduate leaves knowing roughly 2% of what they'll need |
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 Sarah 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:
The Learning Architecture That Actually Works
| Timing | What to Teach | Why This Timing Matters |
| 6 months before someone manages people | Core leadership and coaching skills | They need these skills before they need them, not after they've already developed bad habits |
| At every level, different depth | Lean/CI/Quality fundamentals | An operator needs different depth than a director, but everyone needs the foundation |
| Day one and ongoing | "The way we work here" — culture orientation | People can't align to values they've never been taught |
| Continuously | Refresh, refresh, refresh | One training session creates awareness. Repetition creates capability |
The Second Case Study: When Openness Meets Chaos
Sarah'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 Raj, took a softer approach.
The Approach
Where Sarah faced strong resistance and met it with bold structural change, Raj encountered mild resistance and general openness. His team was willing to change. They just didn't know how.
Raj 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
| Outcome | Detail |
| Reorganised | Completely restructured around focus units |
| People departed | Many who couldn't adapt left the business |
| Management churn | Sustaining efforts through leadership changes was brutal |
| Control challenges | The pace of change outstripped the pace of learning |
The biggest lesson from Raj'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
| Factor | Sarah's Company | Raj's Company |
| Resistance level | High | Low |
| Approach | Bold structural change with heavy people investment | Rapid reorganisation with willing participants |
| Biggest risk | People refusing to move | People moving without being ready |
| Key lesson | Resistance is data, not an obstacle | Willingness is not the same as capability |
The Getting Buy-In Playbook
By year two, Sarah had developed an intuitive system for building support that she later codified into six principles:
1. WIIF Them (What's In It For Them)
Not "What's In It For The Company." For them. Personally. Specifically. Every role, every level, every individual has a different answer to this question. Find it.
2. Show Results, Not Promises
Nothing builds credibility like evidence. Sarah'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.
3. Communicate Successes Relentlessly
If a tree falls in the forest and nobody hears it, it didn't happen. The same is true for improvements. Sarah created a weekly "wins board" — a physical display updated every Friday showing what each team had accomplished.
4. 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.
5. Involve Them in the Discovery
The most powerful tool Sarah 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.
6. Accept That Some People Won't Get It (Yet)
Not everyone will be an early adopter. That's fine. Sarah 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
| Element | Do You Have It? | Warning Signs If Missing |
| Vision or Goals | A specific, measurable picture of the future | People can't describe where the company is heading |
| Conviction — Shared and Lived | Leaders who embody the change, not just announce it | "Do as I say, not as I do" behaviour from management |
| Plan | A structured roadmap with milestones | Activity without direction; lots of busyness, little progress |
| Skills — People and Process | Deliberate capability building at every level | People are expected to perform in roles they've never been trained for |
| Tracking and Adjustment | Regular review of progress with course correction | Plans are made but never revisited; same mistakes repeat |
| Lessons Learned | Systematic capture and application of experience | Every project starts from scratch; institutional memory is zero |
Be honest with yourself. How many of these does your organisation actually have — not in theory, but in practice?
The Transformation: 24 Months Later
Let's return to Sarah's plant.
Twenty-four months after that first resignation letter, here's what the numbers showed:
Before and After
| Metric | Before | After 24 Months | Change |
| Unplanned downtime (minutes/month) | 420 | 38 | -91% |
| Employee voluntary turnover | 18% annually | 6% annually | -67% |
| Time to double capacity | 3 weeks + overtime | Same day, no overtime | Transformational |
| Improvement suggestions per employee/year | 0.3 | 8.7 | +2,800% |
| Skills per team member (average) | 1.2 | 4.8 | +300% |
| Supervisor time spent coaching vs. directing | 10% coaching | 70% coaching | Complete reversal |
But the numbers don't tell the real story.
The real story was Tom — the supervisor who had stood up in that town hall and asked if his job mattered. Tom 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 James, 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 Marcus — the one who quit at the very beginning? He came back. Eighteen months later, he heard about what was happening, reached out to Sarah, and asked if there was still a place for him.
There was.
Your Takeaway: The Six Principles of LEANership
If Sarah's story resonates — if you see your own organisation in the frustrations, the resistance, the potential — here's what to carry forward:
1. 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.
2. 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.
3. Take Action
Every conversation is an opportunity to move toward the future state. And actions will always speak louder than strategy documents.
4. Give to Get
Share your knowledge openly. Share your mistakes openly. The organisations that hoard information decay. The ones that share it accelerate.
5. 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.
6. 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?
Sarah was unreasonable. James was unreasonable. Tom — 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.