Value Stream Mapping: Making the Path of an Order Visible

Why nobody knows the whole path of an order

In small companies, everyone knows what they themselves do with an order. Sales takes the inquiry, engineering checks it, costing calculates, production builds, accounting issues the invoice. How long the order is underway in total and where it sits between the steps, on the other hand, hardly anyone knows. Everyone sees their own section, nobody sees the stream.

Value stream mapping was developed to make exactly this stream visible. This leads to the guiding question of this article: what does value stream mapping offer a small company, and where does it lead astray? To answer it, we first clarify the terms, present the timeline as a thinking model, put the findings from case studies into context, weigh two readings, and finally describe how a first analysis can be done in half a day.

An order is rarely processed too slowly, but almost always left lying too long.

What is value stream mapping? Terms

The value stream comprises all the steps an order passes through from receipt to delivery, including the information that steers it. Value stream mapping records this stream. It became known through the workbook Learning to See by Mike Rother and John Shook (1998), who derived the representation from practice at Toyota. It belongs to the tools of lean thinking, which the article on lean in the office puts into context.

Three time terms carry the method. Processing time is the time during which an order is actually worked on. Waiting time is the time it waits between two steps: in an inbox, for an approval, for a piece of information. Lead time is the sum of both, from receipt to completion. From this follows the flow ratio, also called process cycle efficiency: the share of processing time in lead time.

Two maps are distinguished. The current-state map shows how the order actually runs today. The future-state map shows how it should run after targeted changes. Between the two lies the improvement. This sequence corresponds to the four-step loop from the article on process optimization step by step: current-state analysis, bottleneck analysis, target process, measurement of success.

The thinking model: the timeline beneath the map

What distinguishes value stream mapping from other process drawings is a simple line beneath the map. On it, waiting time is entered above and processing time below for each step. At the end there are two totals: the total lead time and the total processing time. This timeline is the actual thinking model. It shifts attention from the question of who could work faster to the question of why the order waits so long.

In the example, about 21 working days of lead time contain 25 hours of work, roughly three working days. The flow ratio is therefore around 15 percent. In pure office processes it is often even smaller. The article on lean in the office shows a quote with 96 hours of lead time on which 5 hours of work were done, just over 5 percent. An everyday analogy is a doctor's appointment: the treatment takes ten minutes, the visit two hours, and nobody would ask the doctor to treat faster.

What case studies show about value stream mapping

The findings on value stream mapping come almost exclusively from case studies. Three recent studies concern processes that resemble office and project work more than an assembly line. Pangestu and Mulyana (2025) examined project reporting in an Indonesian mining company. The analysis revealed duplicate approvals, errors in manual data entry, and a lack of standard templates. After switching to a digital reporting system with validation rules, the duration of a reporting cycle fell from 10.8 to 5.25 days, and according to the authors, the flow ratio rose from 44.1 to 90.5 percent.

Fajri and Isradi (2026) analyzed the coordination of design documents in a toll road project. They found four types of waste: waiting, transportation, defects, and overprocessing. After introducing a common data environment, waiting time fell from 72 to 25 days and total lead time from 255 to 134 days. The flow ratio, by contrast, only rose from 27.45 to 31.34 percent. The authors themselves point out that their results are based on a single project.

Goettems, Correa, Schaefer, Peres, and Baierle (2025) applied the method to product development in the engineering department of a Brazilian metal-mechanical company, explicitly beyond classic production. They observed the process directly, drew the current-state map, and designed a future-state map. Lead time fell by 39.13 percent, cycle time, meaning the processing time per step, by 15.6 percent. As limitations, the authors name the reference to a single industry and that some of the improvements still need to be verified over the long term.

The road construction case is noteworthy. There, lead time fell by almost half, but the flow ratio barely rose. This shows that the ratio alone can be misleading. Whoever shortens waiting time and processing time at the same time improves the process without the ratio showing it. What matters to the customer is lead time.

Measuring instrument or way of seeing? Two readings

There are two readings of value stream mapping. The first sees it as a measuring instrument: times are recorded precisely, ratios are calculated, and the future-state map becomes a binding plan. In its favor: the case studies work with such numbers and can document improvements. Against it: orders in small companies are rarely alike. A custom product runs differently from a spare parts delivery, and a map showing an average describes neither of them accurately.

The second sees it as a way of seeing: the team jointly traces a real order, estimates times where exact values are missing, and in doing so recognizes where the order waits. The title of the workbook that made the method known speaks for this. It is called Learning to See, not Learning to Measure.

For small companies I consider the second reading the fitting one. The case studies show impressive numbers, but they are individual cases without a comparison group, and failed analyses are rarely published. The most reliable benefit of the method is that a team sees the whole path for the first time. Whoever wants to measure afterwards measures one number, lead time, and does so over several weeks.

A first value stream map in half a day

The following guide is intended for a single process and takes about four hours with everyone who handles an order along its path.

1. Set the process and its boundaries

   Choose a process with a clear beginning and end, such as inquiry to delivery for a typical order type. Define what counts as receipt and what counts as the end.

2. Select a real order

   Take a completed order from the last few weeks, not an ideal one. Collect emails, documents, and dates that show when it was where.

3. Draw the steps on the wall

   One note per step, in order, with the person responsible. Loops and queries are drawn as arrows going back.

4. Add the timeline

   Beneath each step go processing time and waiting time. Where exact values are missing, estimate and mark them.

5. Name the longest waiting time

   At the biggest number on the upper line, ask: what is the order waiting for here? Usually it is an approval, a piece of information, or a person who is only available on certain days.

6. Set one change and measure

   Choose a single change at this point, with a responsible person and start date. Then measure the lead time of the next orders for four weeks.

The longest waiting time is often, but not always, the bottleneck in the sense of the theory of constraints. How to tell the two apart and why improvements elsewhere hardly have an effect is described in the article on Goldratt's theory of constraints. Whoever wants to show what the waiting time costs will find a simple calculation in the article on what a process costs. And whoever wants to trace the path of the order not just at the table but on site will find the right walk-through in the article on going and seeing.

Where value stream mapping reaches its limits

The method shows a process at one point in time. If order types or volumes change considerably, the map is quickly outdated. It also shows the flow of one order, not the interaction of many orders competing for the same people. For that, capacity planning and a limit on parallel work are the better tools.

The evidence is limited as well. The case studies cited come from mining, road construction, and metalworking in Indonesia and Brazil, and each is based on a single case. They show where improvements can start, not how large they will be in your own company.

Conclusion: what does value stream mapping offer small companies?

The question was
value stream mapping brings a small company and where it leads astray. Its value lies in the timeline. It shows that an order spends most of its time waiting and shifts attention from the people who work to the handoffs where nothing happens. One process, one real order, and half a day are enough for this.

As shown, the case studies document markedly shorter lead times, but as individual cases, and the road construction case shows that individual ratios can be misleading. The method leads astray when it becomes the precise measurement of an average order that does not exist in that form. As a way of seeing, it is one of the most effective tools a small company can know.

How to get started

1. Choose a process whose duration customers or colleagues complain about.
2. Pick a completed order from the last few weeks and collect all documents with dates.
3. Draw the steps with those involved and enter processing time and waiting time.
4. Name the longest waiting time and its cause.
5. Set one change and measure the lead time of the next orders for four weeks.