Learning objective
By the end of this lesson, you can build a current-state evidence spine that separates touch time, waiting time and information signals.
Why it matters
A procedure tells you what should happen. A value stream map must show what happened to real work. Without observation, teams automate the documented route while queues, rework and informal approvals remain invisible.
Core concept: follow one unit of demand
Choose one coherent demand family and trace a recent item from request to completed customer outcome. For every significant step, capture:
- who or what performs it;
- the system and information signal;
- touch time;
- waiting time;
- quality, rework and exception evidence.
Lead time is the elapsed customer journey through the flow. Touch time is only the time spent actively transforming the work. The gap is often more important than the longest task.
Visual explanation
Text alternative: three short processing steps are separated by much longer waits. Information signals and rules control when each step begins.
Worked example
An invoice team assumes data entry is the problem because it requires seven minutes. The map shows eighteen hours of waiting before matching and thirty-one hours before owner review. Thirty per cent of cases arrive at review without sufficient evidence.
The strongest first move is to improve input completeness and release rules around review, then test extraction on a bounded standard route. Making data entry faster alone may only enlarge the next queue.
Common mistake
Mistake: combining all demand types into one average map.
Standard invoices, international invoices and disputed invoices may follow different controls. Mixed averages hide the route that creates delay and risk.
Quick check
An automation saves five minutes at intake, but customer lead time remains three days. What should the team inspect next?
A. Model response length.
B. The active queue, hand-off and release rule in the end-to-end flow.
C. The colour palette of the map.
D. Only intake productivity.
Answer: B. System evidence, not a local saving, shows where the next improvement should occur.
Practical prompt
Select one recently completed case. Write its start, end, steps, touch time, wait time, information signal and any loop. Mark each entry as observed, system-derived, estimated or unknown.
Summary
- Map a real demand family, not the official procedure.
- Show work and information flows together.
- Separate customer lead time from touch time.
- Treat AI suggestions as hypotheses until verified.
- Improve the full flow before scaling local automation.
Next lesson
Apply the method in Map the Claims Intake Before Automating It, where fast extraction competes with a hidden validation queue.