Value stream mapping (VSM) is a lean technique for drawing every step a piece of work goes through, from the customer's request to delivery, together with the information that triggers each step and the time the work spends waiting between them. Its purpose is to show where the time goes. In most processes, the work itself takes minutes or hours and the waiting takes days.
This guide is for operations, finance, IT and quality leads who want to shorten a process that takes too long and need numbers to argue for the change. It explains what a value stream map is and where it comes from, the current-state and future-state maps, the symbols and the metrics, and a seven-step method. A worked example follows a supplier invoice from arrival to payment. Then come value stream mapping in offices, IT and services, the common mistakes, and how VSM fits with process mapping and continuous improvement.
What Is Value Stream Mapping?
A value stream is every action, value-creating or not, needed to take a product or service from order to delivery. The Lean Enterprise Institute's lexicon defines it as all the actions needed to bring a product from order to delivery (the operational value stream) or from concept to launch (the development value stream): see its entries for value stream and value-stream mapping. Value stream mapping is the technique of drawing that stream on one page: the steps, the flow of information that tells each step what to do next, and a timeline that separates the time spent working from the time spent waiting.
Three things make a value stream map different from an ordinary flowchart:
- It follows one product or service family end to end, across every team that touches it, rather than one department's part of it.
- It maps information as well as work. How does each step know what to do next? An order, an email, a schedule, a ticket queue? Much of the delay in a process sits in this information flow.
- It has numbers. Each step carries data such as process time, waiting time and error rate, and a timeline along the bottom adds them up into the total lead time and the share of it that adds value.
Where value stream mapping came from
Toyota developed the technique and called it a “material and information flow” diagram, according to the Lean Enterprise Institute's Lean Lexicon. Mike Rother and John Shook, who had both studied Toyota's methods, recast it as value stream mapping in Learning to See, a workbook published by the Lean Enterprise Institute that won a Shingo Research Prize in 1999. In their foreword to the book, James Womack and Daniel Jones describe the map as the tool for the step of lean thinking that most companies had overlooked: mapping the whole value stream for each product family.
The ideas behind it
Value stream mapping is the working tool of lean thinking. Womack and Jones set out its five principles in Lean Thinking in 1996, as summarised in the Lean Lexicon: specify value from the end customer's point of view; identify every step in the value stream for each product family; make the value-creating steps flow in tight sequence; let customers pull value from the next step upstream; and pursue perfection until value is created with no waste. The map is how you do the second principle, and it sets up the next three: once the stream is on the wall, you can see where work stops flowing, where it is pushed into a queue rather than pulled by the next step, and what to improve first.
Lean sorts activity into three kinds, and a value stream map makes them visible. The labels below follow NHS Improvement's guide:
- Value-adding: work the customer would pay for if they could see it, done right first time. Checking an invoice against the purchase order is arguably not; paying the supplier is.
- Necessary but not value-adding: work you cannot drop today, such as a legal approval or an audit record, but should make as small as possible.
- Waste: waiting, rework, unnecessary hand-offs, duplicate data entry, searching for information.
Current-State and Future-State Maps
Value stream mapping always produces at least two maps, and the second one is the point of the exercise.
| Map | What it shows | How it is made |
|---|---|---|
| Current state | How the process actually runs today, with real times and error rates | Walking the process and collecting data from real cases, not from the procedure manual |
| Future state | How the process should run by a date you set, once the changes in the plan are made | Designed by the team from the current state, by removing waits, rework and hand-offs |
| Ideal state (optional) | The long-term direction, with no constraints assumed | A team exercise that keeps the future state ambitious |
The Lean Lexicon describes the current-state map as a picture of the actual condition, and the future-state map as a target image of how material and information should flow. Learning to See is blunt about which matters: “A current state without a future state is not much use.” The Lean Enterprise Institute's workbook Seeing the Whole adds an ideal state beyond one or more future states, as the long-term direction. The future state is only useful if it comes with an implementation plan: who changes what, by when, and how you will measure the result. Once the future state is real, it becomes the new current state and the cycle starts again.
Value Stream Mapping Symbols
The standard symbol set comes from Learning to See, and most diagramming tools include it (see Lucidchart's reference list, for example). You do not need all of them. For an office or service process, the first eight below carry almost every map.
| Symbol | How it is drawn | What it means |
|---|---|---|
| Customer or supplier | A box with a saw-tooth roof (a factory outline) | The start and end of the stream: who sends the work in, and who receives the result |
| Process box | A rectangle with a title bar | One step where the work flows continuously, such as "Approve invoice". The stream is broken into a new box wherever the work stops and waits |
| Data box | A box of rows under a process box | The step's numbers: process time, cycle time, people, error rate, availability, batch size |
| Inventory or queue | A triangle with an "I" inside | Work waiting between steps, with the quantity or the waiting time written beneath. In an office this is an inbox, a ticket queue or a pile of forms |
| Push arrow | A striped (hatched) arrow | Work sent to the next step whether it is ready or not |
| Manual information flow | A straight thin arrow | Paper, a conversation, a phone call |
| Electronic information flow | A thin zig-zag (lightning) arrow | Email, a system message, an ERP or ticketing update |
| Timeline | A stepped line along the bottom of the map | Waiting time on the upper steps and process time on the lower steps, totalled at the right-hand end |
| Kaizen burst | A spiky starburst outline | An improvement opportunity, usually added while designing the future state |
| Supermarket | A shelf shape open on one side | A small controlled stock from which the next step pulls what it needs |
| Pull arrow | A curved arrow | The next step taking work when it is ready, rather than having it pushed |
| FIFO lane | Two parallel lines labelled with a maximum quantity | A first-in, first-out queue with a limit, so work is taken in order and cannot pile up |
| Kanban signal | A card or a triangular flag | The signal that authorises a step to produce or move more work |
| Shipment | A truck | Delivery to the customer or from a supplier, with its frequency |
| Go and see | A pair of glasses | Scheduling or decisions based on someone checking in person, rather than on a signal |
| Operator | A circle with a head and shoulders | A person working at a step; the number of operators is written beside it |
Draw the symbols by hand. Stencils and diagram templates are convenient once the map is settled, but a pencil and a large sheet of paper are faster while the team is still arguing about what happens, and nobody minds rubbing a pencil line out.
Value Stream Mapping Metrics
The numbers are what turn a value stream map from a picture into an argument. Collect them from real cases, measured, not estimated in a meeting.
| Metric | What it measures |
|---|---|
| Lead time | The elapsed time for one item to move through the whole stream, from start to finish, waiting included. The Lean Lexicon calls it production lead time or throughput time; office teams also say turnaround time. |
| Process time | The hands-on time someone actually spends working on one item at a step. The Karen Martin Group lists touch time and work time as other names for it. |
| Cycle time | In the Lean Lexicon, the time to complete a process as timed by actual measurement: in a factory, how often a finished item leaves the step. Office teams often use it to mean process time, so say which you mean on the map. |
| Value-added time | The part of the process time spent on work that transforms the item in a way the customer is willing to pay for. The Lexicon notes that value-creating time is usually less than cycle time, which is in turn less than lead time. |
| Takt time | Available working time divided by customer demand: the pace the stream must keep. The Lexicon's example is 480 minutes a day ÷ 240 units a day = one unit every 2 minutes. |
| Percent complete and accurate (%C&A) | The share of work a step receives that it can use as it is, without correcting, adding missing information or asking for clarification. Karen Martin and Mike Osterling made it a standard metric for office and service streams in Value Stream Mapping (McGraw-Hill Education, 2014). |
Process cycle efficiency
The headline figure on most maps divides the time that adds value by the total lead time:
Process cycle efficiency = value-added time ÷ total lead time
iSixSigma gives the formula as value-added time ÷ total elapsed time, and quotes Michael George's Lean Six Sigma for the rule of thumb that a lean process reaches 25% or more. Transactional processes usually score far lower, because most of their lead time is waiting: a worked example on iSixSigma comes out at about 5.7%, which its author calls typical. Martin and Osterling call the same ratio the activity ratio.
Rolled percent complete and accurate
Multiply the %C&A of every step to get the share of work that passes through the whole stream without being sent back, corrected or chased. Four steps that are each 90% right first time give 0.9 × 0.9 × 0.9 × 0.9, about 66%: one item in three needs rework somewhere. In the example in the first chapter of Martin and Osterling's book, the current state has a rolled %C&A of 30% and the future state 89%.
Which time to use
Use the clock your customer feels. For a factory that is usually calendar time; for an office process, working days are fairer, as long as you say so on the map and use them throughout. Mixing hours, working days and calendar days on one timeline is the quickest way to an efficiency figure nobody believes.
How to Create a Value Stream Map in 7 Steps
Learning to See sets out the core sequence: choose a product family, draw the current state, draw the future state, then write and carry out a plan (Part I). The versions published by ASQ and NHS Improvement add a sponsor and team at the start and measurement at the end. The seven steps below follow that pattern.
Choose one value stream and the problem to solve
Pick one product or service family that follows broadly the same steps, such as "supplier invoices from receipt to payment" or "new-starter IT set-up". Not "finance" and not "IT". Write down, in one sentence, why you are mapping it and what better looks like: "Suppliers wait nearly two weeks to be paid and chase us by email." The problem decides the level of detail and which numbers you need.
Name a sponsor and a small team
A value stream crosses departments, so it needs one person who owns the whole flow and can make changes across team boundaries. Learning to See calls this person the value-stream manager, someone who walks and checks the flow, and warns against splitting the mapping between area managers. Add one person from every team the work passes through: the people who do the work, not only their managers. Keep the group small; ASQ suggests a team of about ten.
Set the boundaries
Agree the trigger that starts the stream, the point where it ends, and what is out of scope. Map at the level where work stops and waits, which usually means a handful of process boxes. Rother's advice is to stay at a 50-foot altitude on the first walks. If a box needs its own detailed map, mark it and map it later with an ordinary process map.
Walk the process and collect the data
Go to where the work happens and follow real items through it. ASQ's guidance is to go to the gemba, the place where the work is done, and walk the flow and interview those who perform the task. For software and IT work, DORA's guide notes that you generally need low precision in the data: rough times from real cases beat precise guesses. At each step, record the process time, how long work waits before it, how much is waiting now, how often the work is wrong or incomplete when it arrives, and how the step knows what to do next. Use system timestamps, ticket histories and audit trails wherever they exist: they are more honest than anyone's memory.
Draw the current-state map
Start with the customer in the top right and the supplier in the top left, then draw the process boxes left to right across the middle, the queues between them, and the information flows across the top. Add a data box under each step and the timeline beneath the whole stream. Total the lead time and the process time, and calculate the process cycle efficiency and the rolled %C&A. Then check the map with the people who do the work: they will spot what the walk missed.
Design the future state
Mark the biggest waits and the steps with the worst %C&A with kaizen bursts. Then ask, for each one, how the work could flow without stopping. Mike Rother suggests that more than about six kaizen bursts on one future-state map means you are getting ahead of yourself: make the few changes that remove most of the waiting first. Draw the future-state map with its own timeline, so the expected lead time is a number you can test.
Write the plan, make the changes and measure
Turn each kaizen burst into an action with an owner, a date and a measure. Make the changes in loops, so each one is tested before the next. Review the stream monthly against the future-state timeline. When the future state is reached, map the stream again: the new current state will show the next set of problems.
Value Stream Map Example: Supplier Invoice to Payment
Here is a worked example of the method on a common office process. The company is a services firm of about 250 people. Its problem: suppliers complain about late payment, and the finance team spends hours a week answering "where is my invoice?" emails. The figures below are illustrative, chosen to show the method; they are not a benchmark for your own process. Times are in working days of 7.5 hours.
The current state
The team followed 20 recent invoices through the process, using the timestamps in the shared inbox, the ERP and the approval emails.
| Step | Wait before the step | Process time | %C&A | What the team saw |
|---|---|---|---|---|
| 1. Log the invoice from the shared inbox | 0.5 days | 4 min | 95% | Logged in one batch each afternoon |
| 2. Match to the purchase order and goods receipt | 1.5 days | 10 min | 80% | One invoice in five has no PO number and is emailed back to the supplier |
| 3. Budget holder approves by email | 4 days | 3 min | 85% | Approval emails are buried; some come back with the wrong cost code |
| 4. Post to the ledger | 1 day | 6 min | 95% | Re-keyed from the approval email into the ERP |
| 5. Pay in the weekly payment run | 2.5 days | 2 min | 100% | One run each Thursday, so an approved invoice waits half a week on average |
| Total | 9.5 days | 25 min | Rolled 61% |
The lead time is about 9.6 working days (4,275 minutes of waiting plus 25 minutes of work), so the process cycle efficiency is 25 ÷ 4,300, about 0.6%. The rolled %C&A is 0.95 × 0.80 × 0.85 × 0.95 × 1.00, about 61%: four invoices in ten need chasing or correcting at least once. That is the number behind the "where is my invoice?" emails.
What the map showed that nobody had said out loud: none of the five steps is slow. The longest takes ten minutes. All the time is in the four queues and in the rework loops back to suppliers and budget holders.
The future state
The team set a target lead time of under four working days within three months and made four changes, each marked as a kaizen burst on the map:
- No PO, no invoice. Suppliers are told the PO number is required, and invoices without one are returned the same day with a standard reply. %C&A at matching is expected to rise from 80% to about 97%.
- Log and match in one step, every morning, by whoever is on the rota, instead of two batches on different days.
- Approval as an assigned task, not an email. Each invoice becomes a task for the budget holder with a due date of one working day, a reminder when it is overdue, and a drop-down of valid cost codes so the wrong one cannot be typed.
- Two payment runs a week instead of one, which halves the average wait for payment.
| Current state | Future state (target) | |
|---|---|---|
| Process boxes | 5 | 4 |
| Total waiting | 9.5 days | 3.25 days |
| Process time | 25 min | 21 min |
| Lead time | about 9.6 days | about 3.3 days |
| Process cycle efficiency | about 0.6% | about 1.4% |
| Rolled %C&A | about 61% | about 89% |
Why the efficiency figure is still low
A process cycle efficiency of 1.4% sounds poor, but it is the lead time that matters to the supplier, and that falls by two thirds. Office processes have tiny process times, so the percentage stays small even when the flow is good. Track the lead time and the rolled %C&A month by month; quote the efficiency figure only to show how much of the lead time is waiting.
Value Stream Mapping for Office, IT and Service Processes
Value stream mapping was developed for factories, but nothing in the method needs a production line. Martin and Osterling wrote their book for office, service, creative and knowledge work, where the “product” is an invoice, an application, a change request or a case. What changes is what you are looking at:
| On a factory map | On an office, IT or service map |
|---|---|
| Inventory of parts between machines | Items in an inbox, a ticket queue, an approval list or a shared folder |
| Machine changeover time | Switching between tasks, systems or clients |
| Scrap and defects | Forms sent back, missing information, wrong codes, reopened tickets: measured as %C&A |
| Uptime of a machine | Availability of a person: the approver who is in meetings all week |
| Production schedule | Batch rules such as "payments run on Thursdays" or "the change board meets fortnightly" |
Three differences matter most in practice. Office work is invisible, so the queues have to be found in systems rather than seen on the floor. Most of the waiting is caused by information: approvals, missing data and questions, so the information-flow half of the map deserves more attention than it gets in a factory. And the same person often works in several steps and several streams, so availability, not capacity, is usually the constraint.
IT and software delivery
DORA, the DevOps Research and Assessment programme, publishes a guide to value stream mapping for software delivery. It starts by agreeing the outcome you want, then maps the steps from idea to production, captures wait times and hand-offs, and measures flow. It also suggests mapping the “happy path” and the recovery path from a failure as separate streams. In IT operations the same method works for service requests, new-starter set-up and change requests. A common finding is that most of the lead time sits in approvals and in waiting for another team, not in the technical work. For change requests, our IT change management checklist shows one way to make the approval steps explicit.
Healthcare and public services
NHS Improvement's overview of value stream mapping (2011) applies the method to patient pathways in eight steps: a sponsor, a team, the choice of process, data collection and the current state, a critique, the future state, an action plan, and measuring the benefits. It sorts every activity into value-adding, non-value-adding but necessary, and waste, the same three groups as above. ASQ also lists healthcare among its value stream mapping case studies.
Common Value Stream Mapping Mistakes
Mike Rother's “Avoiding Common Pitfalls of VSM” and the “common failings” in the first chapter of Martin and Osterling's book cover most of the ways value stream mapping goes wrong.
Mistake 1: Mapping the organisation instead of one value stream. A map of "operations" has no single flow to follow and no customer to measure from. Pick one product or service family, map it end to end, improve it, then move on to the next.
Mistake 2: Drawing the map in a meeting room. A map drawn from memory around a meeting table shows how people think the process works. Walk the process instead. One Lean Enterprise Institute coach describes taking a team out of the conference room to map at the gemba with pencil and paper, and Seeing the Whole warns that the beauty and precision of maps is generally inversely proportional to their usefulness.
Mistake 3: Mapping the process as designed. The procedure manual describes the process someone intended. The workarounds, the second approvals and the "I always check with Sam first" steps are where the waiting is. Follow real items and ask what happened to them.
Mistake 4: Guessing the times. People remember how long they work on something, not how long it waited for them. Use timestamps from your systems for waiting time, and time a handful of real cases for process time.
Mistake 5: Too much detail. Martin and Osterling warn about wall-length maps with 30, 50 or more steps: that is a process flowchart in disguise. Keep to the level where work stops and waits; if a box hides a complicated procedure, give it its own process map.
Mistake 6: Stopping at the current state. A current-state map with no future state and no plan changes nothing. Martin and Osterling list creating maps but taking no action among the most common failings. Always finish with a future-state map and an implementation plan with owners and dates.
Mistake 7: No owner for the whole stream. Each team improves its own step, the hand-offs between them stay the same, and the lead time barely moves. Someone has to own the flow across departments.
Mistake 8: Treating the map as the result. The map is a means of seeing. The result is a shorter lead time, measured. Put the map on the wall, review it against reality every month and redraw it when the process changes.
How VSM Relates to Process Mapping and Continuous Improvement
Value stream mapping vs process mapping
The Lean Enterprise Institute puts the difference simply: value stream mapping is about improving the whole stream, not just the parts, while process mapping improves one specific process (Understanding the Fundamentals of Value Stream Mapping). In practice, a value stream map is built for one question: why does this take so long? An ordinary business process map answers a different one: how exactly does this work, and who does each step?
| Value stream map | Process map, flowchart or swimlane | |
|---|---|---|
| Question it answers | Where does the time go, and where is the waste? | What are the steps, decisions and roles? |
| Scope | One product or service family, end to end, across departments | Any process, at any level of detail |
| Level of detail | High level: a handful of process boxes, one per point where work waits | As detailed as needed, including every decision |
| Decisions and branches | Usually left out | Central: the diamonds are often the point |
| Information flow | Drawn explicitly | Usually implied |
| Data | Times, queues, error rates and a timeline | Optional |
| Typical output | A future-state map and an improvement plan | A documented process, a procedure or a to-be design |
The two work well together. Martin and Osterling describe value stream maps as strategic and process maps as tactical, and warn that a map with dozens of steps, laid out in swimlanes or missing its information flow, is no longer a value stream map. Use a value stream map to find the step or hand-off that holds everything up, then a detailed process map or process flowchart to redesign that step.
Value stream mapping and continuous improvement
Value stream mapping is a tool for continuous improvement, not a one-off project. It fits the Plan-Do-Check-Act cycle closely: the current and future-state maps are the Plan, the implementation plan is the Do, the monthly review against the future-state timeline is the Check, and redrawing the map once the future state is reached is the Act. Kaizen events usually come straight from the kaizen bursts on a future-state map; Martin and Osterling note that value stream mapping typically comes before them, not during them. Rother recommends rapid PDCA cycles towards a target condition rather than one big change. For the wider lean background, see our guide to lean manufacturing principles.
Value stream mapping and business process reengineering
Business process reengineering starts from a blank sheet and asks how the process would be designed if it did not exist. Value stream mapping starts from the process as it is and removes the waste step by step. A current-state value stream map is still a useful input to a reengineering project, because it shows exactly how much of the lead time the redesign has to remove.
From Future-State Map to Running Process
The weak point of most value stream mapping is the gap between the future-state map on the wall and what people do on Monday morning. The new process lives in a slide deck, the old habits return, and six months later nobody can say whether the lead time fell.
CheckFlow does not draw value stream maps. It runs the process you designed, which closes that gap:
- Build the future state as a template. Each process box becomes a phase or a task, assigned to a person or a group, in the order you drew it. Approvals can be steps that only the approver can complete, with later tasks held until they do. See workflow software for how hand-offs and approvals work.
- Remove the rework at the source. Required form fields, drop-downs and conditional logic stop work moving on with information missing, which is what raises %C&A.
- Make the queues visible. Every task has an assignee and a due date, overdue tasks send alerts to their assignees, and the Reports Grid shows every running checklist and where it is waiting.
- Measure the new current state. The activity feed records who did each step and when. Analytics reports the average cycle time per template and ranks the bottleneck tasks most often late or overdue, so the next round of improvement starts from data rather than a fresh workshop.
For a whole portfolio of processes, our business process management software page explains how mapping, running and improving fit together.
Templates to Start From
These templates are ready-made processes you can adapt as the target for a future-state map, or use to run the improvement work itself.
Sources and Further Reading
- Lean Enterprise Institute, Lean Lexicon: “Value-stream mapping”
- Lean Enterprise Institute, Lean Lexicon: “Value stream”
- Lean Enterprise Institute, Lean Lexicon: “Cycle time” (with production lead time and value-creating time)
- Lean Enterprise Institute, Lean Lexicon: “Takt time”
- Lean Enterprise Institute, Lean Lexicon: “Lean thinking and practice” (the five principles)
- Mike Rother and John Shook, Learning to See, Lean Enterprise Institute
- Learning to See, Part I (Lean Enterprise Institute excerpt)
- James P. Womack and Daniel T. Jones, foreword to Learning to See
- Lean Enterprise Institute, Seeing the Whole, Part I (excerpt)
- Mike Rother, “Avoiding Common Pitfalls of VSM”, Lean Enterprise Institute, 2009
- Lean Enterprise Institute, “Keep It Simple: Value Stream Map at the Gemba”, 2022
- Lean Enterprise Institute, “Understanding the Fundamentals of Value Stream Mapping”
- Karen Martin and Mike Osterling, Value Stream Mapping, McGraw-Hill Education, 2014: chapter 1
- The Karen Martin Group, value stream mapping overview
- ASQ, “What Is Value Stream Mapping (VSM)?”
- Nari Kannan, “Improving Help Desk Functions Using Lean Six Sigma”, iSixSigma
- Alastair Muir, “Calculating Process Efficiency in Transactional Projects”, iSixSigma
- Andrew Davis and Rob Edwards, “How to use value stream mapping to improve software delivery”, DORA, 2024
- NHS Improvement, “An Overview of Value Stream Mapping”, 2011
- Lucidchart, “Value stream mapping symbols”
Frequently Asked Questions
What is value stream mapping?
Value stream mapping is a lean technique for drawing every step a product or service goes through from request to delivery, together with the information flow that triggers each step and a timeline of working time against waiting time. Toyota developed it as a material and information flow diagram; Mike Rother and John Shook popularised it as value stream mapping in Learning to See. Its purpose is to show where the lead time goes, so you can remove the waiting and rework.
What are the steps of value stream mapping?
Choose one value stream and the problem to solve; name a sponsor and a small cross-team group; set the boundaries; walk the process and collect real data; draw the current-state map with its timeline; design the future-state map; then write an implementation plan with owners and dates, make the changes and measure the result against the future-state timeline.
What is the difference between a current-state and a future-state map?
A current-state map shows how the process actually runs today, with measured times, queues and error rates. A future-state map is the target: how the work should flow once the waiting, rework and unnecessary hand-offs are removed, with its own timeline. A current-state map is not much use without a future state and a plan to reach it.
What is the difference between value stream mapping and process mapping?
A value stream map follows one product or service family end to end across departments at a high level, and adds the information flow and a timeline of process time against waiting time. It answers "where does the time go?" A process map, flowchart or swimlane shows the detailed steps, decisions and roles of one process and answers "how does this work?" Use the value stream map to find the problem and a process map to redesign the step that causes it.
How do you calculate process cycle efficiency?
Divide the value-added time by the total lead time. For example, 25 minutes of work in a process that takes 4,300 working minutes from start to finish gives 25 ÷ 4,300, about 0.6%. Use the same unit of time, such as working minutes, throughout. A lean process is often said to reach 25% or more, but transactional processes usually score much lower because most of their lead time is waiting.
What does %C&A mean in value stream mapping?
%C&A, percent complete and accurate, is the share of work a step receives that it can use as it is, without correcting it, adding missing information or asking for clarification. Multiply the %C&A of every step to get the rolled %C&A: the share of items that pass through the whole stream with no rework. It is the main quality measure on office and service value stream maps.
Can value stream mapping be used outside manufacturing?
Yes. The method works for any repeatable flow of work: invoices, purchase requests, new-starter set-up, IT change requests, software delivery, patient pathways and client onboarding. The queues are inboxes, ticket lists and approval queues rather than stock on the floor, and most of the delay usually sits in the information flow: approvals, missing data and hand-offs between teams.
What are the main value stream mapping symbols?
For most maps you need the customer or supplier icon, the process box with its data box, the inventory triangle for work waiting in a queue, push and pull arrows, manual and electronic information flow arrows, the kaizen burst for an improvement opportunity, and the timeline along the bottom. Factory maps add supermarkets, FIFO lanes, kanban signals and shipment trucks.
