The Crisis
Six months after implementing Kanban, the manufacturing facility's CEO walked onto the factory floor.
She wasn't here for a routine inspection.
She was here because a customer was leaving. Not just any customer. Their biggest customer. The one responsible for 30% of annual revenue. The one they were about to lose.
"After 8 years of partnership, we're forced to end our contract with your company. Your 15-day processing time is destroying our business. Our competitors deliver in 3 days. We've tried to work with your team, but nothing changes.
Last week we had an urgent order. We waited 2 days just for someone to open the email.
You're not just slow. You're unreliable. We're moving to your competitor next month. Consider this your final notice."
The CEO felt her stomach drop. $10 million in annual revenue. Gone. And this wasn't the first complaint. Three other customers had threatened to leave that quarter.
She called an emergency meeting.
The Confrontation
The operations team sat in stunned silence as the CEO read the letter aloud.
The Emergency Meeting
"We implemented Kanban six months ago," the operations director said defensively. "We can SEE everything now. Work is visible. We know exactly what's happening."
"You can see the problem," the CEO said, her voice cold. "But you haven't fixed it. You've been watching orders get stuck for six months and doing nothing."
The silence was deafening.
"How many customers have we lost this quarter?"
"Three," someone whispered.
The CEO stood up. "I want to know exactly what's happening with that order. Walk me through the entire process. Not the ideal process. The actual process. Every step. Every delay. Everything."
The Walk-Through
They followed the path of one customer order through the facility. It was worse than anyone had admitted.
Wait
2 Days
Customer Order Arrives
Emails processed in batches on Thursdays only. Today is Tuesday—customer waits 2 days for acknowledgement.
Wait
1 Day
Initial Review
Manager approval required. Actual decision: 5 minutes. Actual wait: 1 full day. He's too busy with all the other approvals.
Wait
3 Days
Batching
Orders accumulate until Friday when they're processed in bulk. "More efficient to process together." For who?
Work
2 Days
Production
The only stage where actual value is created. 2 days of work out of 15 total. The only thing customers actually pay for.
Rework
2 Days
Quality Check
First-time failure rate: 28%. Cause: rushing due to queue backlog. Queue exists because of batching. The system creates the failure.
Wait
1 Day
Shipping
Batch shipments only. Order sits complete and finished—but waits for others to accumulate before it can leave.
"So out of 15 days, how much time actually adds value?"
The operations director looked at the timeline. "Maybe 2 days of actual work."
"Which means 13 days of waste."
"Yes."
"And that's why we're losing customers."
The Numbers Are Devastating
15
Days average order time
2
Days of value-added work
13
Days of pure waste
86%
Of every order: waste
They were wasting more than three-quarters of every customer's time. And they'd been watching it happen with Kanban for six months.
The Kanban board made the work visible. But visibility without fixing was just making the disaster more obvious. They could SEE customers getting angry. They could SEE orders getting stuck. They could SEE the waste. But they couldn't fix it—because they had no framework for understanding WHY it was broken.
The Consultant Arrives
By Monday morning, a process improvement consultant was walking the floor.
"You have a Kanban system?" she asked.
"Yes. Six months in."
"And your processes are still broken?"
"We can see the problems. We just can't fix them."
"Because you're treating symptoms instead of root causes," she said. "You need Lean thinking. Process mapping. Five Wastes elimination."
She pulled out a sheet of paper. "Your order takes 15 days. Walk me through the actual steps."
She started drawing the real process. Every wait. Every batch. Every rework. Every unnecessary approval.
"Look at this," she said. "13 days of waste. And I can tell you exactly what's causing it."
The Five Wastes Revealed
Every single inefficiency in their process fell into one of five categories. Once you understand the type, you can fix it.
Waste 01
Waiting
7 days of pure waiting out of 15 total. Waiting for email batches. Waiting for approval. Waiting for production batches. Waiting for shipping.
- 2 days: email batch processing (Thursdays only)
- 1 day: manager approval queue
- 3 days: production batch accumulation
- 1 day: batch shipment delay
Root cause: optimized for batching instead of for customers.
Waste 02
Overproduction
Multiple approval steps for routine orders. Collecting information nobody uses. Quality checks for things that should never fail.
- Senior approval on every order regardless of complexity
- Data collected that never influences decisions
- Processes designed for edge cases, not normal work
Waste 03
Defects
28% of orders failed quality check. Not because the team was incompetent—because the system forced it.
- Rushing due to queue pressure → quality suffers
- Queue exists because of batching policy
- Batching exists to be "efficient"—but creates slowness
Fix quality upstream, not catch it downstream.
Waste 04
Motion & Complexity
Customer data flowing through three different systems. Manual production scheduling. Manual quality reports. Workarounds everywhere.
- Triple data entry across disconnected systems
- Unofficial processes because official ones don't work
- Manual scheduling creating bottleneck delays
Waste 05
Underutilized Talent
Senior manager approving every routine order. 5 minutes per decision. 200+ approvals per month—over 1,000 minutes of senior management time. Monthly. For 5-minute decisions.
- Junior staff could handle 95% of approvals independently
- No empowerment structure existed
- Decision-making centralized by default, not by design
The Quick Wins
"If you're systematic, the quick wins alone will cut your processing time in half within two weeks," the consultant said. "Show me."
01
Stop batching emails
Process customer requests daily, not weekly. Customer emails responded to within hours, not days.
What changed: inbox opened every morning instead of Thursday batch
02
Empower approval
Junior staff approved routine orders. Only complex orders required senior review. 30-minute turnaround instead of 1 day.
What changed: decision criteria made explicit, authority delegated
03
Individual processing
Process orders individually, not in batches of 10. Production starts immediately—no customer waiting for others to accumulate.
What changed: one-piece flow replacing batch production
04
Automate scheduling
Automated scheduling replaced manual coordination. Orders move from intake to production floor automatically.
What changed: eliminated scheduler bottleneck entirely
05
Quality upstream, not downstream
Better training and statistical process control. Fix the cause, not the symptom. Rework dropped from 28% to 5%.
What changed: inspection moved to source, not output
06
Direct shipping
Ship orders immediately when complete. Customers receive orders as soon as they're done—not when the batch accumulates.
What changed: completion triggers shipment, not schedule
The Results: 30 Days Later
The operations director stood in front of the transformed Kanban board. Then picked up the phone and called their biggest customer.
The Call
"Your last order? We processed it in 3 days. We're implementing new systems today to make it even faster. We'd like to keep your business."
Long pause on the other end.
"You're serious?"
"We've completely redesigned how we work. We mapped our processes, found the waste, and eliminated it. We're not going back."
"I'll believe it when I see it."
"You will. Your next order ships in 2 days. We're going to earn your trust back."
The Transformation: 90 Days Later
Before
15 days
processing time
After
4 days
processing time
Before
42%
customer satisfaction
After
87%
customer satisfaction
Biggest customer renewed—and increased order volume by 40%
Three customers who threatened to leave came back
Rework dropped from 28% to 5%
Team morale transformed—desperation and blame disappeared
"Kanban said: look at this disaster. Lean said: here's why it's happening and how to fix it. Together? They transformed our organization."—The CEO, 90 days later
The Parallel to Your HR Function
This is happening in your HR right now.
You implemented Kanban. Beautiful—you can finally see your HR bottlenecks. But what you're seeing isn't pretty:
Waiting
- Requests sitting in inboxes
- Waiting for approvals
- Batching delays (process on Fridays)
Result: leave approvals take 10 days (should be 1)
Overproduction
- Multiple approvals for routine requests
- Collecting unnecessary information
- Forms designed for edge cases
Result: 80% of effort spent on 20% of requests
Defects
- Incomplete requests (employee doesn't know what's needed)
- Policy confusion creating back-and-forth
- High first-time failure rates
Result: constant rework and frustrated employees
Complexity
- Multiple disconnected systems (leave, payroll, HRIS)
- Manual data entry across platforms
- Convoluted approval chains
Result: unnecessary steps and wasted motion
Talent Waste
- Senior HR staff processing routine paperwork
- No empowerment for junior staff
- Decision-making centralized by default
Result: bottleneck at every senior touchpoint
The Timeline for Change
The transformation doesn't have to take months. The manufacturing facility saw dramatic improvements in weeks.
Week 1–2
Map processes and identify waste
Walk through every HR request end-to-end. Draw the actual process, not the ideal one. Categorize every delay into the Five Wastes.
Week 3–4
Implement quick wins
Stop batching. Delegate routine approvals. Eliminate the obvious waits. These changes cost nothing and deliver immediately.
Week 5–6
Measure results and celebrate
Quantify processing time reduction. Share results with the business. Build momentum for deeper changes.
Week 7+
Tackle strategic improvements
Address deeper system integration, training gaps, and structural issues. The quick wins have proven the approach—now build on it.
The Critical Insight
Kanban shows you the problem. Lean fixes it. But only if you act.
Only if you're willing to map your processes. Find the waste. Eliminate it. Only if you're willing to change how you work.
The manufacturing facility made that choice when they were desperate. But they didn't have to wait until desperation.
And neither do you.
Connecting the Series
This is Part 5 of our HR Transformation Framework—the Lean layer that sits on top of Kanban execution to drive continuous, systematic improvement.
Part 1 — Assessment
Why HR Transformations Fail—and where to start instead
Part 2 — Objectives
The Objective Problem: Why Busy HR Teams Still Go Nowhere
Part 3 — Initiatives
The Archer's Problem: Why Initiatives Matter More Than You Think
Part 4 — Execution
The Restaurant That Lost Control: Why Kanban is the Answer
Part 5 — Process Optimization (You Are Here)
The Factory on the Brink: One Crisis Revealed Everything
Part 6 — Key Results
The Problem With Winning: Why Key Results Expose the Truth
The question for you
Are you going to wait until your organization is in crisis
before you fix your HR processes?
Kanban has shown you what's happening.
Lean will tell you why.
The only question left is: Will you do something about it?