Supply Chain · Map
Bottleneck Walk
Walk the flow with the people who run it and mark every queue, wait and double-handling you see.
- Time30 min
- FormatTeam
- StageMap
Bottleneck Walk: what it is and why it works
A bottleneck walk is a short, structured gemba walk along one product flow with the people who run it. Instead of reading reports, the team physically follows the material from the first operation to the last, counting what is queued in front of and behind each resource, noting double handling and searches for parts, and timing one real order as it moves. The largest queue found on the walk is treated as the working constraint until data proves otherwise, and it becomes the starting point for constraint management.
The walk beats spreadsheet analysis when reported data and floor experience disagree. Utilization figures can make the wrong machine look like the bottleneck because the busiest resource is not always the one that limits flow; a machine can run constantly on work nobody downstream needs yet. Queues, on the other hand, are hard to hide: material piles up in front of the resource that cannot keep pace. Involving operators brings in knowledge of workarounds, informal buffers and recurring searches that no system records. The findings feed directly into Theory of Constraints work, a value stream map for the same flow, and WIP control to keep the queue from rebuilding.
What you need
- One product flow selected, with its routing from first operation to shipping
- Two to five people who work in the flow, plus a supervisor or planner
- A simple tally sheet or tablet for counts, a timer, and a floor layout sketch
- Site safety briefing and PPE for walking production areas
What you get
- Queue counts in front of and behind each resource, recorded at one point in time
- A list of double handling, extra moves and material searches with their locations
- The actual elapsed time for one unannounced order through the flow
- A named working constraint and a short list of questions to confirm it
When to use it
When the data says the flow is fine but experience says otherwise.
How to do it, step by step
- Pick one product flow and walk it physically, upstream to downstream.
- At each step, count what waits in front of the resource and what waits behind.
- Record every double handling and every search for material.
- Time one order through the flow without announcing it in advance.
- Mark the single biggest queue — that is your constraint until proven otherwise.
Worked example: Finding the real constraint in a machining cell
Illustrative scenario — figures are realistic but not from a real company.
A contract machine shop making aerospace brackets was convinced its five-axis mill was the bottleneck because it ran at over 90% utilization. Management had requested quotes for a second mill costing about $650,000, yet lead times had not improved after adding overtime on the mill.
- The cell lead, two machinists and the scheduler walked the flow from saw cutting through milling, deburring, inspection and packing.
- In front of the mill they counted 11 jobs. In front of the coordinate measuring machine (CMM) in inspection they counted 34 jobs, many already milled days earlier.
- Machinists described walking parts to a second building for a surface-finish check and searching for inspection paperwork, which they had never logged as delays.
- They tagged one order at the saw without announcing it. It spent 40 minutes on the mill and three and a half days waiting for inspection.
Result. The working constraint was the single CMM, which was staffed on one shift only. Adding a second inspection shift and moving the surface-finish gauge into the cell cut average lead time from 12 to 7 working days, and the mill purchase was deferred. The team kept a weekly queue count to check whether the constraint moved.
Common pitfalls and how to avoid them
- Announcing the walk in advance so areas are tidied and queues cleared before the team arrives.Walk at a normal time without warning, and track one real order rather than a staged one.
- Walking only with managers and engineers.Include operators and material handlers; they know where parts wait and where people search.
- Equating the busiest machine with the bottleneck.Count queues in front of each resource; the largest persistent queue signals the constraint better than utilization does.
- Declaring the constraint after one walk and acting immediately on capital spending.Repeat counts over several days or shifts to confirm the pattern before investing.
Frequently asked questions
How do you identify a bottleneck in production?
Look for the resource with the largest and most persistent queue in front of it and starved stations after it. Confirm with data: compare required load against available capacity over several weeks, and check whether extra output at that resource raises total shipments. High utilization alone is not proof, because non-bottlenecks can also stay busy by building inventory.
What is a gemba walk?
Gemba is a Japanese term for the place where the work happens. A gemba walk means going to the shop floor, warehouse or office to observe the process directly, ask questions and understand problems in context, rather than relying on reports. A bottleneck walk is a focused form of gemba walk aimed at finding queues and flow interruptions along one product flow.
How often should you do a bottleneck walk?
Do a first walk whenever lead times or output disappoint without an obvious cause. After improvements, a short repeat walk every week or two for a month or so shows whether the constraint has moved. Many plants then fold queue checks into regular gemba routines so a shifting bottleneck is noticed early.
Origin
Gemba walking applied to constraints — Ohno/Lean tradition.
Used in these playbooks
Lead time halving week 1 week
One week to find where time hides: map the flow, walk it, compress queues and lots — measure before and after.
Related methods
- Theory of ConstraintsFind the one constraint that sets the pace, exploit it fully, subordinate everything else, then elevate it.
- Value Stream MappingMap every step of a product family from supplier to customer, with timelines, to expose waste and lead time.
- WIP ControlCap work-in-progress with a fixed number of job cards; new work only enters when finished work leaves.
More in “Map”
See the whole chain end to end before touching any part of it.