What Is Value Stream Mapping — and How to Run One in 5 Steps

This is the practical, run-it-this-week walkthrough of Value Stream Mapping (VSM). If you want the deeper reference — the Lean theory, the full metrics, and the six-step methodology — read our companion guide on what Value Stream Mapping is and how to leverage it in 6 steps. Here, StrategyPeeps focuses on exactly how to facilitate a session and turn the map into change that sticks.

The problem with being inside the process

I was standing in a financial services office watching their accounts payable team work through invoices. Every person was busy. Everyone looked productive. But invoices were taking 14 days to process, and clients were calling daily asking about payment status.

The problem was obvious once we mapped it out — but when you are inside a process, handling your piece of it every day, you cannot see the whole picture. You cannot see the three-day wait between approval and data entry. You cannot see that invoices sit in email inboxes for two days before anyone touches them. This is exactly why Value Stream Mapping exists.

What Value Stream Mapping actually shows you

Value Stream Mapping is a Lean tool that draws out the entire flow of a process — from the moment a customer makes a request to the moment you deliver value back to them. It captures every step, every wait time, every handoff, and every approval. Most importantly, it makes waste visible that you cannot see when you are buried in the daily work.

In that financial services example, we discovered that out of 14 total days, only 4 hours were spent on actual work. The rest was waiting, searching for information, or sitting in someone’s inbox. When you map that visually, the waste jumps off the page — and people stop arguing about whether there is a problem.

The 5-step Value Stream Mapping process

Step 1: Define your product family

Pick one type of work that flows through your organisation. Do not try to map everything at once — you will get overwhelmed and quit. For our financial services client, we focused specifically on vendor invoice processing. Not expense reports. Not purchase orders. Just vendor invoices from receipt to payment.

Step 2: Map the current state

Walk the process from start to finish. Talk to every person who touches it. Time each step and count the wait times. Draw it out using simple boxes for process steps and triangles for waiting areas, and include the actual numbers — how long each step takes, how long things wait, how often mistakes happen.

We discovered their current state had 12 different handoffs, 3 approval layers, and invoices that got “lost” in email for days. The total lead time was 14 days, but the actual work time was 4 hours.

Step 3: Identify waste and root causes

Look for the classic wastes — waiting, overprocessing, defects, unnecessary motion, and overproduction — but go deeper than just spotting waste and figure out why it exists. In our example, invoices waited in email because people did not know they had arrived. Approvals took days because managers were travelling and checking email once daily. Data entry happened in batches once per week instead of continuously.

Step 4: Design the future state

This is where you redesign the flow to eliminate waste — not just reduce it, but eliminate it where possible. We redesigned their process to have automatic email notifications, approval limits that removed unnecessary sign-offs, and daily data entry instead of weekly batches. The new flow had 5 handoffs instead of 12.

Step 5: Build an implementation plan

Break the future state into specific, measurable changes you can implement in 30-60-90 day chunks. Assign owners. Set dates. We started with the email notifications and approval limits — changes that required no technology — then tackled the batching problem and finally the workflow redesign.

The results that matter

Six months later, that same financial services team was processing invoices in 3 days instead of 14. More importantly, they could see problems immediately instead of discovering them two weeks later. The accounts payable manager told me it was the first process improvement project that actually stuck. Previous consultants had given them recommendations that gathered dust — but because we mapped the current state together and they could see the waste for themselves, they owned the solution.

Value Stream Mapping works because it makes the invisible visible. Once people see how much time their work spends waiting around, they cannot unsee it, and they start asking better questions about why things work the way they do.

Where to start your first map

Pick a process that frustrates your customers or your team — something that takes too long or creates too many problems. Map it exactly as it works today, not how you think it works or how it is supposed to work. The truth about most processes is that they evolved accidentally over time. Someone left, so a step was added. A mistake happened once, so a verification step was added. These patches accumulate until the process is drowning in waste.

Frequently asked questions

How do you run a Value Stream Mapping session?

Define one product family, gather the people who do the work, and map the current state step by step with real timings. Then identify the waste and its root causes, design a future state that removes it, and turn that into a 30-60-90 day implementation plan with owners and dates.

How long does it take to create a value stream map?

A first useful current-state map can be drawn in a single facilitated session once the right people are in the room. Designing the future state and building the implementation plan typically follows over the next few weeks, with changes rolled out in 30-60-90 day chunks.

What do the symbols on a value stream map mean?

In a simple map, boxes represent process steps and triangles represent waiting areas or inventory between steps. Each box and triangle is labelled with real numbers — step time, wait time, and error rates — so the proportion of waiting to actual work is obvious at a glance.

What process should I map first?

Choose a process that frustrates your customers or your team — one that takes too long or creates too many problems. Map it exactly as it runs today rather than how it is supposed to run, because the accidental patches added over the years are usually where the waste hides.

Ready to see what is really happening in your processes?

If you are ready to see what is really happening in your critical processes, StrategyPeeps runs Value Stream Mapping sessions that get your team aligned on both the problems and the solutions. Book a free consultation.