Module 03 / Lesson 02
Map the Workflow and Find the Bottleneck
Draw the steps of a service and use timing to find where people actually wait.
Read the transcript
Introduction
A food pantry has a line at pickup. Let’s map what people do and see which step holds the line up.
- Draw the steps in order
Imagine watching a Wednesday pickup at a food pantry. A visitor gives their name at the front desk. A volunteer checks a list and marks the pickup as cleared. Then the visitor collects a bag from the next table. Put those actions on a line in the order they happen. Include the handoff. The visitor can only collect a bag after the front desk marks the pickup as cleared. Check your map against another pickup. If a visitor whose name is missing takes a different path, make a note of that. For now, we’ll follow the usual pickup so we can see where the line builds.
- Measure the wait
Time a few pickups. For this example, giving a name takes one minute, checking the list takes six, and handing over a bag takes one. Those numbers are a small sample, so keep watching at different times before you call it a pattern. In these pickups, most of the time is spent checking the list. When the list check falls behind, visitors arrive faster than that step can clear them. That step is the bottleneck. It limits how quickly everyone can get through. Look at where the queue builds while you time it. If the wait moves when another volunteer arrives, record that too. Conditions matter when you compare two days.
- Check where a change would help
It’s tempting to redesign the pickup table because that is where the bags are. But a faster handover saves little if visitors are still waiting for clearance. Talk to the front desk about what makes the list hard to check. Suppose names are buried across separate sheets. Try one sorted list for a small shift and see whether the wait actually changes. Measure the same steps again so you can tell when work has simply moved to another part of the line.
Recap
Put the steps in order and measure where the wait builds. Try the check, then we’ll look at the difference between what you saw and what you think caused it.
Listen to the audio onlyTry it yourself
Map the handoffs, time the steps, and improve the constraint you can observe.
Next, separate what you saw from your best guess about why it happened.
Next lesson