Value Stream Mapping vs Process Mapping: Which One Do You Need?

A lab products manufacturer brought me in with a backlog that kept growing and orders taking more than 30 days to ship. They had already done what most growing companies try first. They hired more people, and everybody worked a little harder. The backlog kept growing anyway.

If you’ve spent any time around lean, you’d probably expect the first thing I drew was a value stream map. It wasn’t. It was a rough process map of the whole business. The value stream map came next.

Neither tool is better than the other. They answer different questions, and the most common mapping mistake I see is reaching for one when you’re actually asking the other one’s question.

Two maps, two questions

A process map shows the steps. Every touch point, and who owns it. Most process maps use swim lanes, one lane per department or work center, so you can follow an order as it crosses from one to the next: in from the customer, into order entry, over to quoting, through purchasing, and onto the floor. Every handoff is visible because the work physically jumps from one lane to another.

The process map is the tool I reach for most, because it flexes. You can draw it at the department level and see the whole business on one page, then draw a second one zoomed in on a single process, down to each step and task. I often end up with both, a high-level map of the business and a detailed one of wherever the trouble is. (If you’ve never built one, I walk through the steps in how to create a process map.)

A value stream map works at a higher altitude. It follows the flow of material and information for one value stream, meaning one product line or one service, from the customer’s order through to delivery. It doesn’t care much about each individual touch. It cares about what happens between them: how work gets released and how much of it is sitting in front of each step. It also uses standard symbols that mean the same thing to anyone trained in lean (a FIFO lane, for example, is a lane where work waits and leaves in the order it arrived), so it’s not the place to improvise your own notation.

The short version: a process map answers “how does work move through here, and who touches it?” A value stream map answers “where is the time going?”

Value stream map vs process map at a glance

	Process map	Value stream map
The question it answers	How does work move through here, and who touches it?	Where is the time going?
Scope	Anything from the whole business down to a single task	One value stream (a product line or service), order to delivery
What it shows best	Steps, owners, handoffs between departments	Work waiting between steps, how work is released, material and information flow
Layout	Swim lanes, one per department or work center	Left-to-right flow with standard lean symbols
When I use it	Learning a business, finding handoff problems, documenting how work gets done	Throughput, lead time, and cycle time problems, supplier and material flow
Speed	Fast to rough out	Takes more data (WIP counts, times) to be useful

Neither one needs software to start. Paper and sticky notes work fine, and if you do want a tool, I’ve compared a few in business mapping tools.

Why the process map came first

When I walk into a company, I’m an outsider. Before I can fix anything, I need to know how work actually moves through the business and where it changes hands. A high-level process map gets me there faster than anything else, and it gives me more of that detail than a high-level value stream map would.

That first map wasn’t the fix. It was how we picked what to fix. Once we could see the whole business, we prioritized, and the first initiative was clear: increase throughput for manufacturing.

That’s a “where is the time going” question. So the very next map was a value stream map covering both of their product lines, end to end across the company.

I don’t follow a rule that says process map first. When I’m learning a business, I want the process map. When we’re going after a flow problem like throughput or lead time, I want the value stream map. The problem picks the map.

What the value stream map showed

Two things the process map couldn’t.

The first was work-in-process (WIP), the jobs that have been started and not finished, and exactly where it was piling up. Instead of mapping every touch at each work center, we zoomed out and counted what was sitting in front of each critical step. That gave us a WIP profile of the current state. From there we designed a future state with a reset WIP profile and changed how orders were released to the floor so it would hold.

The second was where full kit belonged. Full kit is a simple discipline: you don’t start a job unless you have everything you need to finish it. They weren’t doing it. Labeling, for example, happened whenever it could. Sometimes the vials got labeled on the front end. Sometimes the labels weren’t ready, so the team made and filled the product and came back to label it when they had a gap.

None of that looked critical on its own. What it created was a lot of starts and stops.

So we put the full kit check at labeling. Every vial labeled and all of the material on hand before a job was released into production.

Within about six months, throughput was up 200% and lead times were cut in half, with the same people and equipment they already had.

The cost of starting what you can’t finish

This goes well beyond one lab.

Starting work you can’t finish is one of the things that slows manufacturing down the most, and most leaders don’t realize how much time it eats. A job gets started, stalls because a component or a label or an answer isn’t there yet, and gets set aside. Somebody starts something else. Later, someone has to find the first job, figure out where it stopped, and get going on it again. Every one of those restarts pulls attention away from the work that would actually ship.

Lean counts waiting as one of the 8 wastes, and it’s the one that hides best. A process map won’t show you much of it, because every step is still there and still in the right order. A value stream map shows it as work sitting between steps. Your customers see it as a lead time nobody inside the building can explain.

Then the constraint moved

Once the floor was flowing, the bottleneck moved upstream. Manufacturing had capacity it didn’t have before, and not enough orders to fill it.

For that problem I went back to a process map. The value stream map already covered the front of the business at a high level. What we needed now was detail: every touch it takes to get from a first inquiry to an order entered.

That map turned it into a demand problem. Nobody up front was writing orders before they had the information they needed, so there was no full kit fix waiting to be found. The plant had fixed its throughput and lead times, and now the business had to go back to the market and ask for more work. That meant more effective outreach and turning more of those conversations into orders.

Before you draw anything

Write down the question you’re trying to answer.

If it’s “how does work actually move through here?” draw a high-level process map this week. One lane per department, one box per touch, from inquiry to shipped, on a single page. Once you can see it, you’ll know where to zoom in.

If it’s “why are we late?” pick one recent order and trace it end to end. Time everything in between, then add up the time the order spent waiting and compare it to the time somebody was actually working on it. Then walk the floor and count the jobs sitting in front of each step. That count is the start of a value stream map, and it will tell you more about your lead time than another 50 boxes on a process map.

Final Thoughts

Over one engagement, that manufacturer needed three different maps: a process map to learn the business, a value stream map to find where the time was going, and another process map once the problem moved to the front office. Nobody picked a favorite tool. Each time, the question came first.

That’s it for today.

See you all again next week!

Dave