The Brutal Truth About "Lean"
Here's what nobody tells you when you start your lean journey:
You can implement every lean tool perfectly and still fail completely.
Why? Because most companies treat lean manufacturing like a recipe. Add value stream maps. Sprinkle in some kaizen events. Fold in a pull system. Bake for 18 months.
But the people-centred production system—the original source of everything we now call "lean"—was never about tools. It was about something far more difficult to copy.
It was about developing people.
the practitioner, a founding member of the Association for Manufacturing Excellence and decades-long observer of the originating manufacturer's methods, puts it bluntly: the biggest differences between TPS and lean relate to "how TPS, much more than lean, emphasizes developing people to solve basic process problems."
This isn't a subtle distinction. It's the difference between transformation that lasts and improvement theater that fades.
Two Maps, Two Destinations
Let's break down how most lean implementations work versus how the originating manufacturer actually operates.
The Typical Lean Approach
You've probably seen it—or lived it:
- Create value stream maps. Document the "as-is" state of your processes, then design a "to-be" future state.
- Identify big targets. Find obvious waste and attack it with kaizen event teams.
- Set dashboard metrics. Track progress toward your vision with key process indicators.
- Deploy pull systems. Connect operations, usually starting at final assembly and working backward.
- Declare victory. Once most workflows use pull systems, plant leaders often announce success.
This approach isn't wrong, exactly. It can produce real improvements. But notice something critical: management and staff lead the conversion, and workers participate.
Workers are given training. They join kaizen teams. They learn techniques.
But they don't own the transformation.
The the originating operating philosophy: True North
the originating manufacturer approaches the same challenge from an entirely different starting point.
Rather than mapping the current process and designing a better future state, the originating manufacturer points everyone toward something they call True North—the ultimate ideal for every process and sub-process.
What does True North look like?
- Zero defects. Not Six Sigma. Zero—as in, not even one customer receives a defect.
- 100% value add. No waste whatsoever.
- Lot sizes of one, in sequence, on demand.
"True North is what we should do, not what we can do," as the originating manufacturer's training materials explain.
Sound impossible? That's exactly the point.
Why "Impossible" Standards Actually Work
Here's the counterintuitive genius of True North: you're not supposed to reach it.
You're supposed to pursue it—relentlessly, every day, forever.
Most companies set achievable goals. Hit 95% quality. Reduce lead time by 40%. Cut costs by 15%. When they hit those targets, they celebrate. The pressure comes off. Processes drift. Within a year or two, they're setting new goals to re-capture the performance they already achieved.
the originating manufacturer's approach prevents this decay entirely.
If you're aiming for zero defects, and you're currently at one defect per million, you still have a problem to work on. There's no finish line. No moment when the work is "done." No complacency.
As one the originating manufacturer trainer explained: "As long as the originating manufacturer is south of True North, they have problems to work on somewhere."
This isn't perfectionism. It's perpetual motion.
The People Paradox
But here's where things get really interesting—and where most lean implementations go completely off the rails.
To pursue True North, every person in the organization needs to be able to see problems and solve them. Not just managers. Not just improvement specialists. Everyone.
That means the entire system has to be designed for visibility. When something goes wrong, it should be immediately obvious. When waste exists, it should be impossible to ignore.
This is why the originating manufacturer obsesses over what they call "standardized work."
Standardized Work: The Missing Piece
Most lean implementations either skip standardized work entirely or treat it as documentation—a necessary bureaucratic step to record what good work looks like.
the originating manufacturer sees it completely differently.
Standardized work isn't documentation. It's an improvement process.
It covers layout. Work sequence. Work methods. And crucially, it emphasizes human motion—teaching workers to develop efficient workflows that meet takt time while considering safety, quality, quantity, and cost.
The goal isn't to document what workers do. The goal is to coach workers until they can generate their own standard work.
This usually takes the longest time in a the originating manufacturer transformation. But the originating manufacturer considers it essential. Without mature standardized work, improvements don't stick.
They have a simple diagram to illustrate this:
Improvement without standards = no sustainment.
Imagine a ball rolling uphill toward your improvement goal. Without standardized work, every time you let go, the ball rolls back down. With standardized work in place, you put a wedge under the ball each time you make progress. It can only ever go up.
the practitioner's Transformation
Let's go back to the practitioner's factory—and meet the practitioner, a second-shift assembly line worker who'd been with the company for seven years.
Before the "lean transformation," the practitioner did her job. She hit her numbers. She didn't make waves. When problems arose, she flagged her supervisor and waited for instructions.
After the consultants left and the kaizen events ended, nothing had really changed for the practitioner. She used some new terminology. She had a different layout at her station. But her fundamental relationship to her work remained identical.
She was still waiting for someone else to solve the problems.
Six months later, the practitioner brought in an illustrative engineering practitioner who'd spent twenty years in the originating manufacturer plants before launching his own consulting practice.
the practitioner didn't start with value stream maps. He didn't schedule kaizen events. Instead, he did something strange.
He spent his first week just watching.
He watched the practitioner work. He watched her colleagues. He asked questions—not about processes or metrics, but about what frustrated them. What problems they noticed. What they would change if they could.
Then he did something that shocked everyone.
He handed the practitioner a dry-erase marker and walked her to the whiteboard near her station.
"You see that issue with the component feeding?" he said. "You're the one who noticed it. You're the one who's going to fix it."
the practitioner looked at him like he was crazy. "That's not my job."
"It is now."
The Five Whys and the Deming Circle
Over the next three months, the practitioner didn't teach lean tools. He taught thinking.
He taught the practitioner and her colleagues the Five Whys—a simple but powerful technique for drilling down to root causes:
Problem: Component feeds jam every hour.
- Why? The feeder mechanism sticks.
- Why? Debris accumulates in the feed channel.
- Why? The component packaging sheds particles when opened.
- Why? We're using a lower-cost supplier whose packaging isn't as clean.
- Why? We selected them based on unit price without considering this downstream impact.
Root cause identified. Solution: change supplier qualification criteria.
He taught them the Deming Circle (Plan-Do-Check-Act)—how to propose a change, test it, measure the results, and either adopt it or try something else.
Most importantly, he gave them permission to act.
Not permission from management. Permission from themselves.
The Real Metrics That Matter
the practitioner initially resisted the practitioner's approach.
"Where are the dashboards?" he kept asking. "How do we track progress?"
the practitioner's answer surprised him.
In the originating manufacturer plants, he explained, the shop floor rarely sees unit cost measurements. The key metrics are quality and lead times. The logic is elegant:
If muda (waste) is disappearing, costs will come down. It's that simple.
And plant efficiency isn't measured in traditional output terms. It's defined as the ability to meet exact customer requirements with minimum resources: people, lead time, and space.
"Stop obsessing over your dashboard," the practitioner told the practitioner. "Start obsessing over whether your people can see problems and solve them."
Six Months Later
By month four, something remarkable had happened.
the practitioner—who six months earlier had waited for permission to do anything beyond her basic tasks—had become a relentless problem-solver.
She'd identified and fixed seventeen process issues. Some were tiny. Some saved thousands of dollars annually. All of them came from her own observations, her own analysis, her own initiative.
And her improvements stuck.
Because she understood why each change mattered. Because she had developed the standard work herself. Because she was personally invested in making her process move toward True North.
More importantly, the practitioner had started teaching her colleagues.
Not formally. Not in training sessions. Just by example. By showing them what was possible when you stopped waiting for someone else to fix things.
By month six, the practitioner's defect rate had dropped 62%. Lead times had shrunk by 41%. Employee engagement scores were the highest they'd been in a decade.
And the practitioner finally understood what Sandra had seen in that photograph years ago.
What This Means for You
Let's bring this home. Because whether you run a factory, lead a team, or just want to improve how you work, the True North philosophy applies.
Stop Chasing "Best Practices"
Tools and techniques matter. But they're not the transformation. They're just things you use during the transformation.
If you implement lean tools without developing the people who use them, you'll get temporary improvements that fade. Every time.
Define Your True North
What does perfection look like in your context? Not "realistic" improvement. Not "achievable" targets. Absolute perfection.
- Zero customer complaints. (Not 98% satisfaction.)
- Zero missed deadlines. (Not 95% on-time delivery.)
- Zero waste in your process. (Not "acceptable" inefficiency.)
You won't reach these goals. That's okay. You're not supposed to. You're supposed to pursue them—forever.
Invest in Visibility
Build systems that make problems impossible to hide. When something goes wrong, it should be obvious immediately—not hidden in a monthly report.
This might mean:
- Real-time dashboards showing quality issues as they happen
- Physical systems (like the originating manufacturer's andon cords) that let anyone flag a problem
- Regular process walks where leaders actually see work being done
The purpose isn't control. It's capability. If people can't see problems, they can't solve them.
Develop Problem-Solvers, Not Problem-Reporters
This is the hardest part—and the most important.
Every person in your organization should have the skills to:
- Observe a process and identify waste
- Analyze root causes (Five Whys)
- Propose and test solutions (Plan-Do-Check-Act)
- Document improvements as new standards
- Teach others what they've learned
This doesn't happen overnight. the originating manufacturer takes years to develop this capability. But every step in that direction pays dividends.
Accept That Standardized Work Takes Time
You can't skip this step. If you don't invest in helping people develop standardized work—if you just document processes and hand them off—your improvements won't stick.
Standardized work is slow. It's frustrating. It requires patience that most organizations don't have.
It's also the only way to sustain progress over time.
The Choice You Face
the practitioner stands at a crossroads that every leader eventually reaches.
Path One: Keep chasing quick wins. Run kaizen events. Build dashboards. Check the lean boxes. Watch improvements come... and watch them go.
Path Two: Commit to True North. Invest in people. Accept that real transformation takes years, not months. Build something that lasts.
the originating manufacturer chose Path Two over sixty years ago. They've never looked back.
What will you choose?
Your Next Step
Here's a challenge for this week:
Find one person on your team who has noticed a problem that nobody else has addressed.
Don't solve it for them. Don't add it to a project list. Don't wait for the next kaizen event.
Instead, give them what the practitioner gave the practitioner:
"You're the one who noticed it. You're the one who's going to fix it."
Then get out of their way.
That single act—multiplied across your organization, repeated every week, sustained over years—is what separates companies that achieve excellence from companies that just talk about it.
True North isn't a destination. It's a direction.
Start walking.
What's one problem in your work that you've been waiting for someone else to fix? Drop a comment below—I read every single one.
Context and scope
Meet the practitioner, a manufacturing director who thought she had it all figured out—until a single question from a the originating manufacturer veteran shattered everything she believed about operational excellence.
The Comfortable Illusion
the practitioner stood at the front of the conference room, laser pointer in hand, presenting slides filled with impressive charts. Her plant had achieved what most would call a textbook lean transformation.
The numbers looked great:
- Value Stream Maps covering every process
- 47 kaizen events completed in 18 months
- Pull systems connecting operations door-to-door
- A dashboard tracking 23 key performance indicators
- Formal lean training for 100% of employees
She had done everything the consultants recommended. The books she'd read. The conferences she'd attended. Her plant had officially "gone lean."
Then the practitioner walked in.
the practitioner was a retired the originating manufacturer production veteran, brought in by her CEO for a simple plant tour. Just a courtesy visit, she thought. Maybe he'd validate their progress. Maybe she'd learn a small trick or two.
What happened next changed everything.
The Question That Changed Everything
After a 90-minute walk through the practitioner's facility, the practitioner stopped at a workstation where an operator was assembling components. He watched for several minutes in silence.
Then he asked the practitioner one question:
"Can this worker generate her own standardized work?"
the practitioner hesitated. "Well, we have standardized work documents. They're posted right there on the wall. Our industrial engineers created them during our kaizen events."
the practitioner nodded slowly, the way someone nods when they've just confirmed a suspicion.
"In the originating manufacturer," he said quietly, "we don't implement the system. We create people who create the system."
the practitioner felt the floor shift beneath her.
Difference #1: Where You Start Determines Where You End Up
The Lean Approach: Top-Down Mapping
If you've been through a typical lean implementation, this probably sounds familiar:
- Create an "as-is" Value Stream Map showing current state
- Design a "to-be" map representing your future vision
- Identify the gaps
- Generate a list of kaizen targets
- Track progress on a dashboard
- Declare victory when the map looks better
Management leads. Staff directs. Workers participate—sometimes.
This approach isn't wrong. It helps leaders visualize the journey, anticipate business issues like capacity and cash flow, and prioritize efforts. Many companies have achieved real results this way.
But it's fundamentally different from how the originating manufacturer does it.
The the originating manufacturer Approach: True North
the originating manufacturer doesn't start with Value Stream Maps. Those come later—much later—to connect processes that have already been improved.
Instead, the originating manufacturer starts with True North.
True North isn't a vision statement created in a conference room. It's the absolute ideal:
- Zero defects. Not Six Sigma (3.4 defects per million). Zero.
- 100% value-add. No waste of any kind.
- Lot size of one, in sequence, on demand. Perfect flow.
"True North is what we should do," as the originating manufacturer describes it, "not what we can do."
The difference isn't just philosophical. It's practical.
When you aim for True North, you never get comfortable. You never declare victory. If one customer in a million receives a defect, you're not there yet. If one second is wasted in a process, there's still work to do.
When you aim for an improved Value Stream Map, you can hit your targets, update your dashboard, and move on—even though enormous waste remains hidden in your operations.
Difference #2: What You're Really Building
This is where most lean implementations miss the mark entirely.
Lean Often Builds: A Better System (Operated by the Same People)
In a typical lean conversion:
- Consultants and staff design the improved processes
- Kaizen teams execute the changes
- Workers receive training on the new methods
- Standard work documents get posted on the wall
- The process gets "turned over to production"
The system improves. The people? They learn to operate the new system. That's not the same as learning to improve it.
the originating manufacturer Builds: Better People (Who Create Better Systems)
Look at this excerpt from the originating manufacturer's own framework:
Human Development (weighted equally with process improvement):
- Physical and mental safety
- Security
- Professional challenge
That last item—professional challenge—means something specific. It means developing every person to solve problems and improve processes through direct experience, not just formal training.
Here's the critical insight:
"If someone else does it, then 'turns the process over to production,' workers are ill-prepared to continue kaizen on their own. To become professional workers in this sense, they should experience how and why their process was developed."
This is why the originating manufacturer keeps foremen and team leaders, converting them into coaches and backups—while many lean organizations try to stretch the worker-to-supervisor ratio.
The question isn't: "Have we trained people on lean tools?"
The real question is: "Can our workers—with their team leaders—generate their own standardized work?"
If the answer is no, you have a lean-looking system operated by people who can't sustain or improve it.
Difference #3: The Role of Standardized Work
This is the single biggest gap between TPS and lean—and it explains why so many lean implementations eventually stall.
What Most Organizations Mean by "Standardized Work"
Documentation. Procedures. Visual instructions posted at workstations.
Staff creates these documents during kaizen events. Workers follow them. Supervisors audit compliance.
Done.
What the originating manufacturer Means by "Standardized Work"
Standardized work at the originating manufacturer isn't just documentation. It's an improvement process that includes:
- Layout optimization
- Work sequence refinement
- Human motion analysis
- Takt time pacing
- Safety, quality, quantity, and cost integration
And critically: workers with their team leaders generate their own standardized work.
This takes enormous time to develop. Some the originating manufacturer plants are much better at this than others, even within the originating manufacturer's own network.
Here's how you can tell the difference when you visit a facility:
Signs of mature standardized work:
- Near work areas, you see evidence of worker problem-solving—real things in real time, like hand-drawn flip charts, not sanitized computer graphics
- Work details at each station are crisp; 5S is detailed enough that you can identify more than just main material flows
- Workers aren't moving at breakneck pace, but they're so concentrated on value-added activity that they have less time to banter or even smile at visitors
Signs of immature standardized work:
- Beautiful documentation that looks great in presentations
- Workers who follow procedures but can't explain why
- Improvement that happens during events, not continuously
The Wedge That Keeps It Together
the originating manufacturer uses a powerful visual to explain why standardized work matters so much:
Imagine a ball rolling uphill toward True North.
Without standardized work, every time you make an improvement, the ball is free to roll back down. You improve. It slides back. You improve again. It slides again.
With standardized work, you insert a wedge behind the ball after each improvement. The wedge holds the gain. The next improvement builds on the previous one.
This is why the originating manufacturer states unequivocally:
"Improvement without standards = no sustainment."
Most lean implementations focus heavily on improvement. They run kaizen events. They achieve breakthroughs. But without the discipline of mature standardized work, those gains don't compound.
The ball keeps rolling back down the hill.
The Real Sequence the originating manufacturer Follows
If you want to replicate what actually works, here's the progression the originating manufacturer uses:
Phase 1: Stabilization
Before you can improve, you need predictability. This means converting people from firefighting to deliberate problem-solving.
Focus on:
- Creating visibility in current processes
- Teaching the Five Whys and PDCA (the Deming Circle)
- Coaching people to carefully observe and document what they're doing now
- Making processes predictable enough that continuous flow won't choke
You're not eliminating all waste yet. You're creating the foundation.
Phase 2: Continuous Flow
Now increase visibility dramatically by setting up local flows that produce only what's needed when it's needed.
Focus on:
- Condensing cells and layouts
- Cutting setup times
- Minimizing lot sizes
- Moving toward one-piece flow where possible
- Teaching multi-functional work and group problem-solving
This phase continues until the workforce does it routinely—not just during events.
Phase 3: Standardized Work
Here's where the originating manufacturer invests far more time than most lean implementations.
Focus on:
- Human motion efficiency
- Introducing takt times
- Coaching workers to develop efficient work flow considering safety, quality, quantity, and cost
- Continuing until workers and team leaders can generate their own standardized work
This usually takes the longest time of any phase.
Phase 4: Getting It All Together
Only now does the originating manufacturer implement detailed pull systems connecting everything to a plant-wide takt time.
Focus on:
- Heijunka (load leveling)
- Standard inventory at designated points
- Gradually decreasing inventories to stress the system just enough for workers—now capable of standardized work—to press toward True North as a unified team
The visibility now shines light on every pebble in the path. Every process improver in every corner of the operation has something to think about and work on.
What This Means for Your Journey
the practitioner's plant didn't scrap their lean implementation. They didn't have to.
But she made three fundamental shifts:
Shift #1: From Dashboard Goals to True North
She stopped celebrating when targets were hit and started asking: "Why isn't this at zero? Why isn't this perfect?"
The goals didn't change. The mindset did.
Shift #2: From Staff-Led Kaizen to Worker-Developed Solutions
She slowed down the event pace and invested more time in coaching workers through problem-solving rather than having staff solve problems for them.
Improvements took longer to implement. But they stuck—and compounded.
Shift #3: From Documented Standards to Living Standardized Work
She stopped measuring how many standardized work documents existed and started measuring whether workers could create, modify, and improve their own work standards.
The flip charts got messier. The computer graphics got less impressive. And the results got better.
The Question You Need to Answer
Close your eyes and picture your best-performing work area.
Now ask yourself honestly:
Can the workers in that area—with their team leaders—generate and improve their own standardized work?
If yes, you're on the path the originating manufacturer actually travels.
If no, you may have implemented lean. But you haven't created the people-centred production system.
And that difference is why your gains aren't compounding the way you expected.
Your Next Step
Here's what I want you to do this week:
Pick one work area. Walk out to the floor. Don't bring any staff or engineers.
Find a worker who seems engaged. Ask them this question:
"If you wanted to change how you do this task tomorrow—to make it safer, faster, or higher quality—what would that process look like?"
Listen carefully to their answer.
If they describe a clear process they've used before, you're building capability.
If they look at you blankly or say "I'd ask my supervisor" or "I'd put in a suggestion," you've discovered your real opportunity.
The gap between those answers is the gap between lean and the people-centred production system.
What did you discover when you asked the question? Share your experience in the comments below—your insight might help someone else on their journey.
About the Source Material:
This article draws on the research and insights of Robert W. Hall, Editor-in-Chief of Target Magazine and a founding member of AME (Association for Manufacturing Excellence). Hall's analysis comparing the people-centred production system with lean manufacturing was originally published in Target Magazine and draws on TSSC (the originating manufacturer Subsidiary) workshops given to AME audiences.
Context and scope
The one thing every company copies wrong (and the fix that changes everything)
The Midnight Revelation at a Japanese Factory
the practitioner had seen it all.
Twenty-three years in manufacturing. Six Sigma certifications. Lean training. He'd toured plants across three continents.
But standing in that the originating manufacturer facility at 2 AM, watching a line worker stop an entire production line over a slightly misaligned bracket, he felt something shift.
"Why aren't the supervisors angry?" he asked his guide.
The translator smiled. "Why would they be angry? He found a problem."
the practitioner stared at the worker—now surrounded by three colleagues, all examining the bracket like surgeons over a patient.
"But... the cost. The downtime. The—"
"The cost," his guide interrupted gently, "of not stopping is always higher."
the source organisation Makes
Here's what the practitioner discovered that night—and what Alcoa, one of the world's largest aluminum companies, learned the hard way over a decade:
You can't copy a finished product.
When Alcoa executives visited the originating manufacturer in the mid-1990s, they saw something beautiful. Machines humming in perfect rhythm. Workers moving with surgical precision. Zero waste. Zero accidents. Best quality, lowest cost, shortest lead time.
They wanted that.
So they did what any ambitious company would do: they copied it.
They adopted the tools. The terminology. The visual boards. The Japanese words like "Kaizen" and "Jidoka."
And for years, it didn't work.
Where It All Went Wrong
Picture this scenario. You probably recognize it:
The Conference Room Implementation
A team of executives returns from a benchmarking trip, fired up. They mandate new processes. They hire consultants. They roll out training.
Six months later?
The visual boards are dusty. The daily stand-up meetings became weekly, then monthly, then "whenever we can fit it in." The suggestion box sits empty.
Sound familiar?
Alcoa's leadership discovered something crucial buried in their failures:
They had been looking at the roof when they should have been examining the foundation.
The Stability Model: Building From The Ground Up
Here's what the originating manufacturer couldn't explain—because to them, it was invisible. Like asking a fish to describe water.
the originating manufacturer's success wasn't built on fancy systems. It was built on people.
Not people following systems.
People becoming the system.
The breakthrough came when Alcoa stopped asking "What tools does the originating manufacturer use?" and started asking "How did the originating manufacturer create people who want to use these tools?"
The answer became their Stability Model—seven interconnected practices that transform disengaged workers into invested problem-solvers:
The Seven Stability Tools:
- TPM (Total Productive Maintenance) — Workers own their equipment
- Kaizen — Small improvements, made constantly, by everyone
- Problem Solving — Structured thinking, not finger-pointing
- Daily Management — Real-time visibility into what's working
- Communications — Information flows in all directions
- Suggestions — Every idea gets heard and tracked
- Reward and Recognition — Success gets celebrated publicly
But here's what makes these different from every other corporate initiative:
They're not programs. They're opportunities.
Seven opportunities for getting employees to want to work with leadership—and for leadership to recognize success when it happens.