LEAN SUPPLY CHAIN
Most Warehouses Have Run a LEAN Program.
Few Have Built a LEAN Operation.
There’s a difference between deploying the tools and building the discipline that makes them hold. We’ve walked enough distribution centers to know which one most operations have — and where the real work starts.
What We Actually See
Walk into most distribution centers that have run a LEAN initiative, and you’ll find the same scene: 5S boards on the walls, standard work documents in a binder somewhere, maybe a laminated Kaizen summary from a few years back. The bones of a program are there. What’s usually missing is the management discipline underneath — the daily huddles, the escalation paths, the accountability to standard work that makes improvements self-sustaining rather than dependent on whoever championed the initiative.
You’d be surprised how many operations we walk into where the LEAN tools are technically in place but nobody can tell you what the top three process wastes in the building are, who owns them, or what’s being done about them this week. That’s not a LEAN operation. That’s a LEAN installation.
The other thing we see consistently: teams that try to run the full program at once. VSM, 5S, standard work, slotting, Kaizen events, daily management — all launched together, all underfunded in terms of time and attention, all producing modest results that fade within six months. LEAN done that way looks like a lot of activity and feels like it isn’t working.
Our approach is different. We start with what we can observe on the floor — not what the system reports say — find the improvements with real impact, capture those early, and build the management infrastructure as the program matures. The tools follow the discipline, not the other way around.
We Don’t Start With a Program. We Start With a Floor Walk.
Almost every LEAN engagement we take on starts the same way: someone walks the facility with a stopwatch and maps what’s actually happening, not what the WMS says is happening. The two are often meaningfully different.
WMS timestamps tell you when tasks were completed. They don’t tell you that the pallet sat at the receiving dock for 22 minutes waiting for a putaway task to generate, that your best picker double-scans every carton because she stopped trusting the location data three months ago, or that a supervisor is clearing 40 location conflicts a day — each one taking 90 seconds — that shows up nowhere in a productivity report. None of that is visible in the system. All of it is visible on the floor. And in our experience, that’s where the majority of the recoverable time lives.
The floor walk almost always surfaces quick wins — improvements that can be implemented within a week and produce measurable results within 30 days. Usually it’s a slotting issue: your top-velocity SKUs aren’t where they should be, and the pick path reflects decisions made when the product mix looked different. Sometimes it’s a system configuration that’s creating artificial queue time.
These aren’t LEAN ‘events.’ They’re just fixes, grounded in what was actually observed. Capturing them early matters — not just for the operational improvement, but because it builds the organizational confidence that the program is real and that it works. That confidence is what funds the harder, slower work of building the management system underneath.
The Five Elements — In the Order They Get Built
There’s a reason the sequence matters. Each element depends on the previous one being reasonably solid before it can hold. Teams that try to run all five simultaneously usually end up with none of them working.
01 — Value Stream Mapping: See It Before You Fix It
VSM is the right place to start — not 5S, not a Kaizen event, and definitely not a new visual management board. You map the current state first, because everything else in the program is prioritized based on what the map reveals.
The critical discipline is doing the mapping from direct observation, not from system data. In most DCs, a properly executed floor-based VSM shows that 50–70% of the time product is in the building, nothing useful is being done to it. It’s queued, waiting, or being re-handled because something upstream didn’t go right. That ratio — the real one, not the system one — is where you find the high-impact work.
02 — 5S and Standard Work: The Foundation, Not the Destination
5S is the most visible part of LEAN and the part most operations have at least partially done. What separates operations that sustain it from those that don’t is whether standard work sits underneath it.
One thing worth saying plainly: standard work has to be in place before you automate. We’ve seen companies invest heavily in automation and get ROI that significantly underperformed projections — not because the technology failed, but because the process it was built on wasn’t stable.
03 — Slotting and Layout: The Highest-ROI Move in the Building
Velocity-based slotting consistently produces 15–25% reductions in pick labor within 60 days when done correctly. That’s not a transformation initiative — that’s an analysis, a re-slot, and a reconfiguration. It’s one of the fastest ways to produce measurable results in a warehouse.
The problem is that most operations treat slotting as a project rather than a discipline. Product velocity changes constantly. The fix is building the quarterly slotting review into the management calendar as a standing discipline — not something that gets scheduled when someone has time.
04 — The Daily Management System: What Most LEAN Programs Are Missing
This is the one. If you asked us to name the single thing that separates LEAN programs that hold from ones that don’t, it’s the daily management system. The infrastructure is: daily tier 1 huddles at zone level, tier 2 review at DC level, a clear escalation path, and a structured problem-solving process that actually closes issues.
Without it, LEAN is something the team does when there’s time. Which means it happens inconsistently. Which means the improvements erode. And then someone says the LEAN program didn’t work — when what actually happened is the program worked fine and the management system wasn’t there to sustain it.
05 — Continuous Improvement Cadence: When the Organization Does It Itself
Kaizen events and improvement sprints only produce durable results when elements 01 through 04 are reasonably solid. Running a Kaizen in an operation without standard work or a daily management system produces gains that typically erode within 90 days.
The goal of a sustained CI cadence is to build a team that identifies and closes waste systematically — without waiting for an outside intervention to drive it. When that capability is embedded, the operation improves continuously on its own. That’s the Run phase of LEAN.
If your LEAN program isn’t holding, the tools probably aren’t the problem.
We’ve walked a lot of distribution centers. It usually takes one honest floor walk to identify both the quick wins and the management gaps. If you want that read on your operation, it’s a straightforward conversation.
On Technology: Process First. Always.
The most expensive LEAN mistake isn’t a failed Kaizen or a slotting project that didn’t hold. It’s automating before the process is stable.
The scenario plays out the same way more than it should. A company invests in goods-to-person, AMRs, or AI-driven sortation. The pilot numbers look strong. Then they go live in a facility where the slotting logic hasn’t been touched in two years, inventory accuracy is hovering around 94%, and nobody has defined standard work for the pick process. The technology performs exactly as it was designed. The operation doesn’t improve the way the business case projected.
Companies that stabilize their LEAN operations before making automation investments consistently realize higher ROI on the same technology. Not because the technology is different — it isn’t. Because the foundation it’s running on is.
This is the operational expression of how we work across every engagement. People and process first. Technology that supports what you’ve built — not technology that’s supposed to fix what you haven’t.
→ The operating philosophy behind this: People + Process + Partners for Technology
Five Numbers Worth Watching
LEAN without measurement is just activity. These are the five metrics we track with clients — and the ones that tell you, without ambiguity, whether a program is producing real results.
Lines Picked Per Direct Labor Hour
Your primary productivity measure. General merchandise benchmark for manual pick is 80–120 lines/hour — but your own baseline matters far more than the external number. Establish it before you start anything, then track the trend. A monthly management report is too slow to catch drift before it becomes a service issue; this belongs in the daily tier 2 review.
Pick Accuracy Rate
Best-in-class operations hold 99.8%+. Anything below 99% is a process problem, not a people problem. If your team is attributing miss-picks to associate error, start with the process — the scan workflow, the label, the location accuracy — before you look at performance management.
Inventory Record Accuracy
98% is the practical floor for a WMS-directed operation. Below that, your team stops trusting the system and builds workarounds. Once workarounds become standard practice, you’ve lost the management system — and you’ll spend more time managing exceptions than running the operation.
Dock-to-Stock Cycle Time
How long from goods receipt to available inventory in the system. The WMS-reported number and the floor-observed number are frequently different — because the system doesn’t count queue time. Walk the receiving process before you trust the report.
Labor Cost Per Order Shipped
The number that connects operational performance to financial outcomes. It integrates productivity and wage rate in one figure your CFO can read — and it’s how you build and defend the business case for the LEAN program at the leadership level. Establish baselines before you start. Without them, you can’t tell the difference between real improvement and normal variation.
