At nine on Monday morning, a customer places an order for a stocked product. The warehouse dispatches it six hours later. The people who verify, pick and pack it spend less than an hour handling it. Both statements can be true. The customer experiences the entire interval, including the time between people’s actions. The operations team usually sees the pieces it works on. A map of one order’s path brings those views together and shows where to look for evidence before changing the process.
NIST’s Manufacturing Extension Partnership describes value stream mapping as a way to see the work and the information that directs it. The same distinction is useful in a small order operation. The parcel has a physical path from shelf to carrier. Its instructions take a different path through records, approvals, queues and handoffs. Drawing the two together can explain how a shelf full of available stock and an open packing bench still produce a long delay.
Choose one order family and two clear boundaries
Start with a group of orders that follow broadly the same path. A small retailer might pick domestic orders for stocked goods that fit in one parcel. Preorders, custom goods and large shipments may wait for different reasons and require separate maps. If all order types are mixed into one diagram, a perfectly normal wait for a made-to-order item can look like a problem with the ordinary packing queue.
Write down the events that start and end the clock. For example, begin when the shop accepts an order and end when the carrier records possession of the parcel. If the business uses a different dispatch event, define it. Printing a label, leaving a parcel at the dispatch bench and handing it over can happen at three different times. A team reporting label time while the customer is promised carrier handover is answering a different question.
Agree on whether you are measuring elapsed clock time or working time. An order placed Friday evening and collected Monday morning has spent the weekend in the system from the customer’s perspective. The warehouse may need a separate measure that starts at its next staffed shift. Both measures have uses. Record which clock you are using and keep it consistent when comparing before and after.
Set aside a way to record exceptions without excluding them silently. An order with a missing address, a failed stock check or a damaged item can branch from the ordinary route. Note the branch and why it happened. A sample used to understand typical orders can be narrower than a report about all orders. The difference belongs in the label and the notes.
Build the current map from an order that actually moved
Follow one order from the customer event to the carrier event. Ask each person what they did and how they knew the order was ready for them. Look at a timestamped record where one exists. An event from the order system can tell you when the status changed. The picker can tell you whether that status change means work started or merely means the order became eligible to be picked. Both observations matter.
Use a short line for the progress of the work. For example, the order goes through verification, picking, packing and collection. Add queues between steps where it waits. On a separate line mark the signals that release it. Verification might send a status change to a shared screen. A supervisor might print a list at the top of the hour. A carrier might arrive at one fixed time. Write those triggers in plain language before choosing symbols.
The Lean Enterprise Institute’s overview of value stream mapping distinguishes work steps, information flow and measures such as lead time and cycle time. In an order review, call the interval from the agreed start to the agreed finish elapsed lead time. Keep a separate column for observed hands-on time. If you also record a station’s cycle time, state what repeated work you timed. A station’s recurring cycle and a single order’s time in the whole system answer different questions.
Mark the quality of each observation. A scan may give a precise time for a label to enter a system, but an interview may be your only evidence for when someone actually started packing. A note saying “between 11:00 and 11:10, estimated from the shift log” is better than a precise-looking minute chosen to fill a blank. Missing evidence is a reason to improve the observation or keep a range in the map.
Reconcile every interval on the timeline
Here is a hypothetical order with a six-hour path. The shop accepts it at 09:00. Verification starts at 09:35 and takes 10 minutes. The order is available to pick at 09:45. Picking starts at 11:15 and takes 20 minutes. Packing starts at 13:00 and takes 15 minutes. The carrier collects the parcel at 15:00. In this example, collection is the closing event rather than a separate timed work step.
The three hands-on steps add up to 45 minutes. There are four gaps. The order waits 35 minutes before verification, 90 minutes before picking, 85 minutes before packing and 105 minutes before collection. Together they account for 315 minutes. Add the 45 minutes of work and the result is 360 minutes, matching the six hours from receipt to handover.
That reconciliation keeps a discussion grounded. A proposal to cut the packing step from 15 minutes to 10 could free five minutes of bench time. It might have no effect on this customer’s dispatch if the parcel still leaves on the same truck at 15:00. The time saving can still matter if it increases capacity or lets a later order make the cutoff. The map helps the team state which outcome it expects before claiming that the customer’s order will move faster.
Some processes overlap. A colleague may print shipping paperwork while another person picks the goods. The two people’s labour minutes can add up to more than the elapsed minutes occupied by that part of the order. Keep those measures separate and mark the overlap explicitly. A timeline that forces simultaneous actions into consecutive boxes can invent waiting that did not occur.
Trace a wait to the rule that releases it
After you identify a long gap, ask what had to happen before the order could leave it. In the example, the 90-minute wait before picking could come from an hourly release rule, a backlog, a missing shelf location or a discrepancy between the online inventory and the goods on hand. The timestamp alone does not tell you which. Ask the person who works the queue to show you what the order looked like when it was ready and what made it appear on the work list.
Draw the information signal close to the wait it governs. If the verifier marks the order ready at 09:45 but the picker receives a printed batch at 11:15, find out who schedules the batch and why. It might save walking by grouping orders from the same aisle. It might once have helped staff check stock by hand. Or a report may simply have been left on an old schedule after a software change. Each explanation suggests a different experiment.
The Lean Enterprise Institute’s discussion of administrative mapping is useful when the signal lives in an office or a shared inbox. In a small operation, the parcel may wait because a screen and a shelf use different references for the same item. Mark the moment when staff learn that the references disagree. Then trace how the correction reaches the person waiting to pick. The map should make the work visible without treating the person who reports the problem as its cause.
Collect a small sample of comparable orders across different parts of the day. If early orders wait for a scheduled printout while late orders wait for an open packing bench, the largest delay in one order may not be the largest delay in another. Preserve outliers and note what happened. Before choosing a change, look at the pattern and check whether the delay belongs to a process rule, a capacity limit or an unusual case.
Test a change without sending the queue somewhere else
Suppose the sample suggests that verified orders sit until the next printed list, and that warehouse staff often have capacity to start sooner. A short pilot might release orders from one product family twice an hour while keeping the existing rule for other orders. Agree on who can trigger the release, what qualifies as ready and when the pilot begins and ends. Keep stock and address checks in place so a faster release does not create more wrong picks.
Measure the gap the pilot aims to shorten and at least one downstream outcome. For the sample order, that means ready-to-pick time, plus whether the order made the carrier cutoff. Track packing backlog and a simple quality measure such as orders that needed repacking or correcting. If the time to pick falls while the packing queue grows by the same amount, the delay has moved to a new place. If the carrier cutoff does not move, faster internal progress might help late orders without changing dispatch time for orders that were already ready early.
Write down conditions that would end or revise the pilot. An increase in mispicks, a growing backlog at packing or a loss of the batching benefit could each warrant a change. Compare similar days or report the volume difference so a quiet afternoon does not look like proof of success. The pilot can show that a particular rule is worth adjusting under observed conditions. It is too small to establish what will happen in every season or order mix.
Draw a proposed version next to the current map. Keep the differences visible. Change only the signal or process that the pilot actually tests, and annotate the points where you expect a wait to shrink. When observations return, compare the new timeline with the prediction. Keep any result that surprises the team. A longer queue elsewhere is evidence about the system, even if it complicates the plan.
Keep the map small enough to use again
A working map should let another colleague answer a few basic questions. Which orders does it describe? What starts and stops the clock? Where does the order sit when no one is working on it? Which event tells the next person to start? Put the date, the order family and the source of each timestamp on the page. Attach the sample and the pilot notes so the headline figures can be traced back to observations.
Agree on who will revisit the map after the experiment. A manager who owns only packing may have limited ability to change the release rule or the carrier schedule. Someone responsible for the whole order path can bring the people who control those decisions into one review. Use the map to discuss a concrete handoff or waiting interval instead of asking every team to work faster at once.
If you have little time, start with one order and a table with four columns. Record when an event happened, what changed, how you know and what triggered it. Read the entries in order with the people who did the work. Add a marker whenever the order was ready but could not move, and write down what it was waiting for. You can refine the diagram later. The first version needs a clear timeline and enough evidence to ask a better question.
The six-hour order contains 45 minutes of work and several waits with different causes. That split makes a practical difference. A faster packing step, a more frequent picking release and a different carrier handover each affect a different part of the timeline. Once the team can see where the order is held and what releases it, it can choose one change, measure its effect and see whether the customer gets the result any sooner.
For a related operations example, see how to review a potential supplier.
Sources consulted 4 November 2026. The order timeline and pilot are illustrative.