Consider a job that takes three days of actual work but four weeks to get through your operation. The fabrication is done in a day and a half. The engineering drawings take half a day. Final inspection takes a few hours. Add it up and the real work occupies perhaps 20 hours across the whole job.
The other 17 working days? They are absorbed by queues. Materials waiting to be ordered. Jobs waiting for an engineer to become available. Work-in-progress sitting in front of a machine that is busy with a larger batch. Finished parts waiting for the weekly inspection run. The job is technically complete three weeks before it ships.
That gap — between how long a job takes and how long it occupies your operation — is where most of the profit in an engineering business is quietly lost. Value stream mapping is the tool that makes that gap visible, puts a number on every element of it, and gives you a structured method for closing it.
It is one of the most powerful diagnostic tools in Lean methodology — and it is one that most Australian engineering and manufacturing SMEs have never systematically applied to their own operations.
What value stream mapping actually is — a plain-English definition
Value stream mapping (VSM) is a Lean management tool for visualising the complete flow of materials and information required to bring a product or service from customer order to delivery. It maps every step in the process — not just the steps that add value, but everything: the approvals, the queues, the batching decisions, the handoffs, and the waits.
The output of a VSM exercise is two maps. The current state map shows how the value stream actually operates today — data collected by physically walking the process, not from management assumptions or procedure documents. The future state map shows how the value stream could operate with the identified waste removed and flow improved.
In most manufacturing and engineering operations, only 5 to 10 per cent of total lead time is value-adding. The rest is some form of waste. The job was never the problem. The flow was.
The four phases of a VSM exercise
Select — Choose the value stream
Identify the product family or service line to map. One flow, defined scope, clear customer endpoint.
Current State — Map how it works today
Walk the process floor-to-floor. Time every step. Measure queues. Record batch sizes and handoffs. Let the data reveal the waste.
Future State — Design how it should work
Apply Lean principles to the current state map. Remove queues, create flow, establish pull. Build a realistic, achievable target.
Implement — Close the gap
Translate the difference between current and future state into prioritised improvement projects with owners, timelines, and measurable targets.
Phase 1: Choose your value stream — the most important decision in the exercise
A value stream is the end-to-end sequence of activities required to deliver a specific product or service to a specific customer. Before you can map it, you need to define which one you are mapping.
Choose a value stream that is too broad — "everything we make" — and the resulting map will be so complex it is unusable. Choose one that is too narrow — a single rarely-produced custom job — and the insights will not justify the investment. The right choice for most engineering and manufacturing SMEs is the highest-volume product family, or the flow with the greatest commercial consequence, or the process causing the most operational pain.
Practical guidance: for a first VSM exercise, scope it to one product family from customer order acceptance to delivery, covering no more than 8 to 12 discrete process steps. Keep the scope tight enough that one person can walk the entire flow in two to three hours.
The most common VSM mistake is scoping too broadly. A map that covers everything maps nothing usefully. Pick one flow, go deep, and let the insights inform where you look next.
Phase 2: Map how the value stream actually works today
The current state map is the most important output of the entire VSM exercise — and it must be built by walking the process, not by reviewing procedure documents or interviewing managers. The data that matters is what is actually happening on the floor, not what the standard operating procedure says should be happening.
Walk the value stream from the delivery end back to the customer order — this counter-intuitive direction helps you follow the product through the system as the customer experiences it. At each step, record: cycle time, queue time, batch size, and number of operators involved. Do not estimate — measure. The number that reveals the most is almost always the queue time, not the process time.
The 8 wastes of Lean — use these as your current state analysis lens
Defects
Rework, scrap, failed inspections — output that doesn't meet spec the first time.
Overproduction
Making more than the customer needs, sooner than needed.
Waiting
Jobs in queues between steps, people waiting on approvals or materials.
Unused Talent
Operator knowledge and improvement ideas that are never engaged.
Transport
Unnecessary movement of materials or documents between steps.
Inventory
Excess raw materials or WIP piling between steps, tying up cash.
Motion
Operators reaching, walking, or searching for tools and materials.
Over-Processing
Doing more work than the customer specification requires.
When the current state map is complete, calculate two numbers: total lead time and total value-adding time. The ratio between these two — almost always somewhere between 5% and 15% for engineering SMEs that have never done VSM — is the number that makes the case for improvement better than any argument.
The current state map does not create waste — it reveals waste that already exists. The discomfort of seeing the numbers clearly is the first step toward doing something about them.
Current state vs. future state — an example
Engineering fabrication SME, single product family:
| Process Step | Current State | Future State (Target) |
|---|---|---|
| Customer order | No standard intake. Queue: 2 days | Standard order form, auto-acknowledged |
| Design / engineering | Drawn when available. Queue: 4 days | Template-driven. Same day for 80% of work |
| Materials procurement | Ordered after design. Lead time: 5 days | Kanban trigger on order acceptance |
| Fabrication | Batched. Queue: 3 days. Process: 1.5 days | FIFO flow. Queue: 4 hrs. Process: 1.5 days |
| Inspection / QC | Separate dept, 2 day queue. Rework: 15% | Inline checks. Queue eliminated. Rework: 3% |
| Dispatch / delivery | Weekly batches. Avg wait: 3 days | Ship-when-ready. Avg wait: 0.5 days |
| Total lead time | 18–22 working days | 5–7 working days (target) |
| Value-adding time | ~2.5 days (12% of lead time) | ~2.5 days (40–50% of lead time) |
Value-adding time is essentially unchanged between current and future state — the actual work takes the same amount of time. What changes dramatically is the queue time at every stage. The improvement target is not to make the work faster. It is to stop the work waiting.
Phase 3: Design how the value stream should work
The future state map is a redesign of the value stream based on Lean principles — not a wish list, but a realistic, achievable target implementable within 6 to 12 months. Five Lean design principles guide it:
- Create continuous flow. Eliminate queues between connected process steps so work moves directly from one step to the next.
- Introduce pull. Produce what the next step needs, when it needs it — not what a schedule pushes in advance.
- Reduce batch sizes. Smaller batches mean shorter lead times and faster defect detection.
- Establish takt time alignment. Align production rate to the rate the customer actually requires.
- Simplify information flows. Redesign approval, drawing, and schedule-update delays alongside physical process steps.
The future state map should be built collaboratively — with the people who work in the process, not just the managers who oversee it. A future state designed without them will not be implemented by them.
The future state does not need to be perfect — it needs to be better, achievable, and measurable. A realistic 50% reduction in lead time, achieved and sustained, beats an ambitious 90% reduction that stalls in implementation.
Phase 4: Translate the maps into improvement projects
The gap between the current state map and the future state map is your improvement backlog. A VSM exercise that produces two maps and nothing else is the most common reason VSM fails to deliver value.
The implementation plan works in improvement loops — groups of connected changes implemented together, typically covering two to four weeks of focused work. Each project within a loop has a specific target, a named owner, a deadline, and a measurement method.
Prioritise by impact (largest reduction in lead time or waste cost) and effort (achievable quickly without major capital investment). The high-impact, low-effort improvements become your first loop — building momentum and demonstrating results.
Improvements from VSM need to be documented in updated SOPs to hold the gain permanently — without documentation, process improvements frequently revert within weeks. Every improvement project should include an SOP update as a standard deliverable.
VSM without implementation is just wallpaper. The map reveals the waste — the implementation plan is what eliminates it. One is diagnostic; the other is the work. You need both.
What VSM reveals that other process tools miss
Process maps, swimlane diagrams, and flowcharts describe what should happen at each step. VSM reveals what actually happens between steps — and the between is where most of the waste lives.
- The value-adding ratio. Rarely surfaced by any other tool — it makes the business case for Lean improvement concrete and undeniable.
- The information flow. VSM maps how orders, schedules, engineering changes, and quality data move through the operation — often the largest single waste category in engineering businesses.
- System-level waste. Most tools optimise individual steps. VSM reveals that the majority of waste exists between steps — in queues, handoffs, and batching decisions.
Does VSM work for a small engineering or manufacturing business?
VSM is associated with Toyota and large-scale production environments — leading many SME owners to assume it doesn't scale down. It does, and in many ways it is more valuable at the SME scale, because the waste is proportionally more damaging and the business has less margin to absorb it.
VSM works for any operation with a repeatable flow — including most engineering fabrication, precision machining, assembly, and service delivery businesses.
A typical first VSM exercise:
- Floor walk (2–3 hrs): Record actual cycle and queue times at each step.
- Current state mapping session (2–3 hrs): Build the map, calculate the value-adding ratio, identify highest-impact wastes.
- Future state design workshop (2–3 hrs): Design the future state, identify improvement loops, draft the implementation plan.
Total investment: six to eight hours of focused work, producing a current state map, a future state map, and a prioritised improvement backlog. For most businesses, the lead time reduction made visible in the current state map alone — before a single change is implemented — justifies the investment many times over.
Your first VSM starts with a walk.
You don't need a Lean expert to take the first walk — just a clipboard, a stopwatch, and two hours of honest observation. If you want a structured partner to facilitate your current state map and future state workshop, Innovengg's Lean process improvement team has done this for engineering and manufacturing SMEs across Australia.
Book Your Free VSM Consultation →