There is a purchase order that takes eleven minutes of actual work and four days to get approved. Nobody planned it that way. The request sits in someone's inbox for a day, gets forwarded to the wrong person, comes back, waits for a signature, gets re-keyed into the accounting file and then someone checks it against the budget in a spreadsheet. Eleven minutes of work. Four days of waiting, re-keying and chasing.
A process map would show you the steps. A value stream map shows you the time between the steps. That is where the waste actually lives in most office and admin processes, and it is almost always bigger than people expect.
What value stream mapping is, in plain English
Value stream mapping started on factory floors. Toyota used it to see every step between raw material arriving and a finished car leaving, then worked out which steps added value and which were just waiting, moving or fixing mistakes. The technique spread to healthcare, logistics and eventually office work.
A value stream map is a diagram of how work actually flows from start to finish, with two numbers on every step: the time spent doing the work (process time) and the time spent waiting before the next step starts (lead time). When you draw both, you get a ratio, and in most office processes that ratio is startling. The total process time might be thirty minutes. The total lead time might be eight days.
The map also shows where information moves between systems or people, where batches build up (for example, invoices waiting for a Thursday approval run) and where the same data gets entered more than once. It is a picture of how things really work, not how the procedure says they should.
How it differs from a process map or swimlane diagram
A process map or swimlane diagram shows who does what, in what order. It is good for documenting a process, training new staff and spotting handoff points. But it treats every step as equal. A two-minute data entry step and a three-day approval wait look the same on a swimlane.
A value stream map adds time. It draws a timeline across the bottom that separates process time from wait time, so you can see at a glance that the actual work is a small fraction of the elapsed time. It also typically shows inventory or work-in-progress at each stage: how many invoices are sitting in the approval queue, how many purchase orders are waiting to be entered, how many timesheets are waiting to be checked.
There is also a difference in scope. A process map often covers one department's steps. A value stream map follows the work across departments and systems, from the moment a customer need or an internal request appears to the moment it is fulfilled. That cross-department view is where the biggest delays usually hide, because nobody owns the gap between one team finishing and the next team starting.
You do not need both for every process. A process map is enough when you are documenting steps for training or compliance. A value stream map earns its keep when the process takes far longer than the actual work, and you want to know why.
A worked example: purchase to pay
Here is what a value stream map looks like for a typical purchase-to-pay process in an Australian business with about 40 staff, an accounting file in Xero or MYOB, and a separate job or stock system. This is a composite, not a real client, but the numbers are typical of what we see.
The current state
Step 1 — Request. Someone on site or in the warehouse needs something. They send an email or fill in a paper form. Process time: 5 minutes. Wait time before anyone acts on it: about 1 day.
Step 2 — Approval. The request goes to a manager by email. If the manager is on site or travelling, it waits. Process time: 2 minutes to read and approve. Wait time: 1 to 3 days. If the amount is above a threshold, it goes to a second approver and waits again.
Step 3 — Purchase order. The accounts person creates a PO in the accounting file or the job system. If it is a job, the cost code is looked up in a separate spreadsheet. Process time: 5 minutes. Wait time: usually same day once the approval lands.
Step 4 — Goods receipt. The goods arrive. Someone on site or in the warehouse checks them and signs a delivery docket. That docket might sit on a desk or in a tray until someone takes it to the office. Process time: 3 minutes. Wait time: 1 to 5 days for the paperwork to reach accounts.
Step 5 — Invoice matching. The supplier invoice arrives, usually by email. The accounts person matches it to the PO and the delivery docket. If the docket is missing, they chase it. If the quantities do not match, they chase the supplier or the site. Process time: 5 minutes when everything lines up. Wait time: 1 to 7 days chasing paperwork. The three-way matching post covers why these three documents rarely agree on the first try.
Step 6 — Payment. The invoice goes into a payment batch. Most businesses run payments weekly or fortnightly. Process time: 1 minute per invoice. Wait time: up to 14 days in the batch.
Totals. Process time across all steps: about 21 minutes. Elapsed time from request to payment: 10 to 30 days. The process time is less than one per cent of the elapsed time.
The waste is not in the steps. It is in the gaps: waiting for approval emails, chasing dockets, re-keying from one system to another, and batching.
The future state
A value stream map of the improved process might look like this:
- The request is entered in a system (even a simple form) that routes it to the right approver with a notification, not an email. Wait time for approval drops from days to hours.
- The PO is created from the approved request, with the cost code already attached. No re-keying.
- The goods receipt is recorded on a phone at the point of delivery and linked to the PO. No paper docket waiting on a desk.
- The supplier invoice arrives electronically (or is read by AI from a PDF) and matched to the PO and receipt automatically. Mismatches are flagged, not chased. There is a practical look at how AI handles this in AI for Dockets, Orders and Supplier Invoices.
- Payment terms are applied automatically. No manual batching.
For example, if your accounts team ran this process under the improved flow, the process time would likely drop to single figures and the elapsed time might come down from weeks to days. The accounts person spends less time chasing and more time on work that matters.
There is a full step-by-step walk through the purchase-to-pay process in The Purchase to Pay Process.
Where the waste hides in office processes
Factory value stream maps look for seven types of waste (Toyota's original list). In an office, the same ideas apply with different names.
Waiting. The biggest one. Approvals, sign-offs, someone being out of the office, emails sitting unread. In most admin processes, more than half the elapsed time is waiting.
Re-keying. The same information typed into two or more systems. A timesheet entered on site, then entered again into payroll, then entered again into the client invoice. Each re-entry takes time and creates a chance for error. We call this double data entry and it is one of the most common problems we see.
Batching. Work piled up and processed in a batch, usually because it is not worth doing one at a time the way things are set up. Weekly payment runs, monthly reconciliations and fortnightly payroll are all batches. Some batching is sensible. But when invoices wait ten days for a weekly approval run, that is not efficiency. It is a queue.
Corrections and rework. Mistakes found downstream that send work back upstream. A wrong cost code on an invoice, a missing ABN on a supplier record, a timesheet with the wrong award classification. The fix takes longer than doing it right the first time, and it interrupts someone else's work.
Handoffs. Every time work moves from one person or team to another, context is lost. The person receiving it has to work out what happened before them, often by reading an email chain. The more handoffs, the slower the process and the more likely something falls through the gap.
How to run a value stream mapping exercise for an office process
You do not need special software. A whiteboard, sticky notes and a stopwatch (or a rough estimate from the people who do the work) are enough. Here is a practical approach.
Pick one process that is slow and crosses departments. Quote to cash, purchase to pay, timesheet to payroll to client invoice, or month-end close are all good candidates. Follow one real piece of work from start to finish. Not the procedure manual version — the actual path it took, including the detours. The process mapping guide has a good starting method.
For each step, write down who does it, what system they use, how long the actual work takes (process time) and how long the work waits before the next step (lead time). Ask the people who do it. They know.
Draw the steps left to right. Draw a timeline along the bottom with process time below the line and wait time above. Add the totals at the end.
Then look at the gaps. Where is work waiting longest? Where is information being re-keyed? Where do corrections happen most often? Those are your starting points.
You can run this in half a day for a single process. A process mapping session covers one or two processes in depth and produces a map the business can act on. If you want a broader look across several processes, the $5,000 Process and Systems Audit maps how data flows through the business and where it gets stuck.
Frequently asked questions
What is value stream mapping in simple terms?
Value stream mapping is drawing out every step in a process, from start to finish, with the time each step takes and the time spent waiting between steps. It shows you where the real delays are, not just what the steps are. In most office processes, the waiting time is many times larger than the working time.
What is the difference between value stream mapping and process mapping?
A process map shows who does what, in what order. A value stream map adds how long each step takes and how long work waits between steps, across the whole process from end to end. A process map is good for documenting and training. A value stream map is good for finding where time is being lost. For more on process maps and templates, see Swimlane Process Mapping Template.
Can I use value stream mapping for office work, not just manufacturing?
Yes. Value stream mapping started in manufacturing but works well for any process where work flows through several steps and people. Office processes like purchase-to-pay, quote-to-cash, hiring, onboarding and month-end close all benefit from it, especially when the elapsed time is much longer than the actual working time.
Do I need a consultant to run a value stream mapping exercise?
Not necessarily. If you have a whiteboard, sticky notes and the people who do the work in the room, you can map a process in half a day. A consultant helps when the process crosses several departments or systems, when you want an outside perspective on where the waste is, or when you want help designing the future state. Get in touch for a free initial chat if you are not sure whether it is worth bringing someone in.
What should I do with the value stream map once I have it?
Start with the biggest wait or the most obvious re-keying. Fix one thing, measure the improvement and then move to the next. A value stream map is a diagnostic tool, not a project plan, but it tells you where the biggest gains are. If the waste sits between systems — approvals, data re-entry, chasing paperwork — that is where integration or automation starts to make sense.