Value Stream Mapping for Business Processes: See Where Time Goes

Ask how long it takes to hire someone, pay an invoice or onboard a new client, and you'll usually get a confident answer. Ask how much of that time anyone is actually working on it, and the room goes quiet. In many business processes, most of the elapsed time is spent waiting: in inboxes, approval queues and batches that run once a week.

Value stream mapping is a lean technique for making that visible. The Lean Enterprise Institute (LEI) defines it as diagramming every step in the material and information flows needed to bring a product from order to delivery. It began in manufacturing, but LEI notes that managers in any industry can get value from it, and the same thinking applies to office, service and administrative work.

This guide explains what a value stream is, how to map one for a business process, what to measure, and how to turn the map into real improvement.

Where Value Stream Mapping Comes From

According to LEI, Toyota developed the tool, calling it a material and information flow diagram, as part of the Toyota Production System. It reached a wide audience through Learning to See, a workbook by Mike Rother and John Shook published by LEI, which received a Shingo Research Prize in 1999.

Later authors adapted the method for non-manufacturing settings. Karen Martin and Mike Osterling's book Value Stream Mapping, for example, is described on the authors' firm's website as written for people in service and office environments, in settings that include financial services, government, healthcare and retail.

Value Streams and What Counts as Value

LEI defines a value stream as all the actions, both value-creating and non-value-creating, required to bring a product from concept to launch or from order to delivery. That includes the actions that process information from the customer, not just the physical work.

For a business team, a value stream might be:

• Hiring: from approved job requisition to the new hire's first productive day.
• Procure to pay: from a purchase request to the supplier being paid.
• Client onboarding: from signed contract to the client's first successful use of the service.

LEI distinguishes value stream mapping from ordinary process mapping. A value-stream perspective means working on the big picture rather than individual processes, improving the whole rather than optimizing the parts. A value stream map also shows information flow, such as how each step learns what to do next, alongside the work itself.

What counts as value? LEI offers a simple test for whether a task is value-creating: ask whether the customer would judge the product less valuable if the task were left out. Its glossary notes that rework and queue time are unlikely to be judged as having any value by customers.

In office work, the "customer" may be internal. For the hiring stream, the customers are the hiring manager and the candidate. Interviewing creates value for both. Re-keying the same candidate data into three systems does not, though it may be necessary until the systems are connected.

Before You Map: Scope and People

LEI suggests a few starting rules: select a product family, have one person personally lead the mapping effort, begin at the "door-to-door" level to capture the complete flow, and consider both material and information flow.

In business terms, a "product family" is a group of requests that follow broadly the same steps, such as standard purchase orders under a set threshold, rather than every purchase the company makes.

LEI also describes a broader method it calls value-stream improvement. Leadership defines the need and scope; stakeholders build current-state and future-state maps in a workshop, which usually lasts three days; then an improvement phase, typically 60 to 120 days, runs experiments and checks results. Smaller teams can scale this down, but the sequence of scope, map, then experiment still holds.

Invite people who actually do each step. A value stream crosses departments, so no single person sees all of it.

Drawing the Current-State Map

Map the process as it really works today, not as the procedure manual says. LEI describes the current-state map as capturing the actual condition of the value stream. For office work, that means following real requests through email, systems and approvals.

For each step, LEI's data boxes include measures such as cycle time, lead time and percent complete and accurate (%C/A), the share of work that is completed with perfect quality in a process step. For business processes, useful data usually includes:

• Process time: hands-on working time for one item.
• Wait time: how long items sit before or after the step.
• %C/A: how often the next step can use the output without correction or clarification.
• Batching: whether work is held and released in groups, such as approvals done on Fridays.

Then draw a timeline under the map that separates working time from waiting time. Imagine a hypothetical purchase request that takes 12 working days from submission to approved order, but involves only about three hours of actual work. The map doesn't need to be precise to show that the problem is in the waiting.

LEI's guidance includes a useful reminder: having a perfectly drawn current-state map is not the point. The goal is a shared understanding of how work flows.

Designing the Future State

LEI's guidelines for a lean value stream were written for production, but several translate well:

• Match the pace to demand. LEI defines takt time as available production time divided by customer demand, and gives a non-factory example: if customers want two new products per month, takt time is two weeks.
• Create flow where possible. Move items through steps one at a time instead of in large batches. LEI defines batch-and-queue as processing large lots and moving them on whether or not they're needed, where they wait in a line.
• Use pull where flow isn't possible. Let downstream steps signal when they're ready for more, rather than pushing work at them.
• Simplify information flow. Fewer handoffs, approvals and status chases.

For the hypothetical purchase request, a future state might remove one approval layer for low-value orders, replace a weekly approval batch with daily review, and fix the form so requests arrive complete.

From Map to Action

A future-state map is a plan, not a result. Break it into specific changes, assign owners, and test each one. LEI describes value-stream improvement as based on the plan-do-check-act cycle and uses the word "countermeasures" rather than "solutions," to signal that any change can itself be improved later. Revisit the map after a few months to see whether lead time actually fell. Our guide to continuous improvement and kaizen covers running small experiments.

Common Mistakes

• Mapping the ideal process instead of the real one.
• Drawing every tiny step until the map is unreadable.
• Mapping without the people who do the work.
• Blaming individuals for delays the system creates.
• Producing a beautiful map and never acting on it.

Key takeaways

• A value stream includes every step, value-creating or not, from request to delivery, plus the information that drives it.
• Map the real current state with the people who do the work, then separate working time from waiting time.
• Use LEI's simple test for value: would the customer miss this step if it were gone?
• Design a future state that reduces batching, handoffs and waiting, and pulls work instead of pushing it.
• Treat the future state as a set of experiments to run and check, not a finished answer.

Sources

• Lean Enterprise Institute, Value Stream Mapping Overview
• Lean Enterprise Institute, Value Stream
• Lean Enterprise Institute, Value
• Lean Enterprise Institute, Value-Stream Improvement
• Lean Enterprise Institute, Takt Time
• Lean Enterprise Institute, Batch-and-Queue
• Lean Enterprise Institute, Learning to See (book page)
• Karen Martin and Mike Osterling, Value Stream Mapping (book page)