3. Process Mapping and Value Stream Management

Introduction and Context

Lean management begins with a deceptively simple question: how does work actually flow from a customer need to a delivered product or service? Organizations often answer this question by describing departments, procedures, or information systems. Lean analysis asks a different question: what happens, in what sequence, at what time, and with what interruption, delay, movement, or rework?

Process mapping and value stream management provide the means to make that flow visible. They convert an abstract process into an observable system of activities, decisions, queues, movements, information exchanges, and outputs. Once the process is visible, managers and improvement teams can distinguish value-creating work from non-value-adding activity, identify constraints, and design a more effective future state.

A process map usually concentrates on the sequence and logic of activities. A spaghetti diagram emphasizes physical movement. A value stream map (VSM) extends the analysis across organizational boundaries by combining material flow, information flow, inventory, capacity, demand, and time. These tools are complementary rather than interchangeable. A process map may reveal repeated approvals; a spaghetti diagram may reveal excessive walking; and a value stream map may demonstrate that a product requiring only 30 minutes of processing spends 18 days in the system.

For postgraduate learners, the significance of these tools extends beyond drawing diagrams. Mapping is a form of operational inquiry. It requires a defined customer, reliable observations, careful measurement, cross-functional collaboration, and managerial judgement. Poorly designed maps can reinforce departmental assumptions, conceal variation, or encourage local optimization. Well-designed maps create a shared fact base for lean transformation.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain the purpose and scope of SIPOC diagrams, process maps, spaghetti diagrams, and value stream maps.

2. Define customer value, value-added activity, necessary but non-value-adding activity, lead time, cycle time, takt time, and process efficiency.

3. Construct and interpret a current-state value stream map using operational and time-based data.

4. Calculate lead time, processing time, and the value-added ratio.

5. Diagnose waste, bottlenecks, variation, information delays, and flow interruptions.

6. Design a future-state value stream using pull, flow, pacemaking, workload balancing, and appropriate control mechanisms.

7. Develop an improvement roadmap that connects process changes with governance, measurement, and sustained management practice.

8. Evaluate technological, ethical, and organizational issues associated with digital process mapping and analytics.

Seeing the Process as a System

A process is a linked set of activities that transforms defined inputs into outputs for an internal or external customer. The word “linked” is important. A collection of efficient departments does not necessarily constitute an efficient process. If work is transferred between departments through queues, batch schedules, unclear requirements, or repeated inspections, the total customer experience may remain poor.

Lean distinguishes between three broad categories of activity. Value-added activity changes the product or service in a way the customer is willing to pay for, is performed correctly the first time, and is necessary to deliver the specified outcome. Non-value-adding activity consumes resources without changing the product or service in a way valued by the customer. Waiting, unnecessary movement, excess processing, avoidable transport, inventory, defects, and overproduction are familiar examples. A third category is necessary but non-value-adding activity. Regulatory checks, legally required records, or essential safety controls may not transform the customer’s product, but eliminating them would create unacceptable risk. The correct response is usually to simplify, automate, or minimize them rather than remove them indiscriminately.

Mapping should begin with the process boundary. A map that is too narrow may optimize one workstation while worsening the total flow. A map that is too broad may become unmanageable and lose operational detail. A useful boundary often extends from the receipt of a customer order or service request to completion and delivery. The appropriate level depends on the improvement question.

SIPOC: Establishing the Boundary

SIPOC is a high-level scoping tool representing Suppliers, Inputs, Process, Outputs, and Customers. It is especially useful at the beginning of a project because it prevents premature attention to detailed activities before the team agrees on what process is being studied.

A SIPOC can be developed through the following sequence:

1. State the process name and define its start and end points.

2. Identify the principal outputs and their customers.

3. Identify the major process stages, normally at a high level rather than as individual tasks.

4. Determine the critical inputs required by those stages.

5. Identify suppliers of the inputs and clarify input requirements.

6. Validate the model with process participants and customers where possible.

For example, in a hospital outpatient laboratory, suppliers may include physicians, patients, and specimen collection units; inputs include test requests, specimens, and patient identification data; process stages include receipt, registration, testing, validation, and reporting; outputs are validated results; and customers include clinicians and patients. The SIPOC exposes the fact that data quality and specimen identification are process inputs, not merely administrative concerns.

SIPOC is not a substitute for a detailed process map. It defines the landscape and major relationships; it does not reveal every decision, handoff, or delay.

Process Mapping: Representing Logic and Responsibility

A process map presents activities in sequence and makes decisions, rework loops, handoffs, and responsibilities visible. Common symbols include rectangles for activities, diamonds for decisions, arrows for flow, and document or data symbols for information. Organizations may use different notation systems, including flowcharts, cross-functional swim-lane maps, Business Process Model and Notation (BPMN), or operational standard-work diagrams. Consistency and clarity matter more than artistic sophistication.

A reliable mapping exercise normally begins with the actual process rather than the documented procedure. The team should observe work, interview operators, examine records, and sample different shifts or demand conditions. The map should distinguish the ideal route from the route most work actually takes. Rework, escalation, missing information, and informal workarounds should be shown rather than treated as exceptions.

Swim lanes add responsibility by placing activities in lanes representing departments, roles, machines, or systems. They are valuable for identifying excessive handoffs and ambiguous ownership. However, they can also encourage a departmental view. The map should therefore be read horizontally as a customer-facing flow, not merely vertically as a sequence of departmental tasks.

Spaghetti Diagrams: Making Motion Visible

A spaghetti diagram traces the physical route followed by a person, material, document, or vehicle on a layout. The resulting line often resembles tangled spaghetti, hence the name. The diagram can reveal long travel distances, backtracking, crossings, inaccessible equipment, poorly located supplies, and unnecessary transport between offices or workstations.

To construct one, obtain an accurate layout, select a representative period or transaction, trace the route, record distance and frequency, and calculate the total movement. It is important to map more than one case when variation is substantial. A route that appears efficient during a quiet shift may become congested during peak demand.

The diagram does not prove that every movement is waste. Movement may be required for safety, technical sequencing, or customer interaction. Its purpose is to generate questions: why is the operator walking to obtain approval, why does a specimen return to registration, and why are frequently used tools stored outside the point of use?

Value Stream Mapping and the Current State

A value stream is the complete set of actions, both value-adding and non-value-adding, required to bring a product or service from request to delivery. Value Stream Mapping combines process steps with information and material flows. It is particularly useful for product families or service families that share similar processing routes.

A current-state map should describe what is happening now, not what procedures say should happen. It commonly includes:

• the customer and demand information;
• the supplier and major incoming flows;
• process boxes for significant activities;
• inventory or work-in-process between stages;
• information flows, schedules, and communication mechanisms;
• process data such as cycle time, uptime, changeover time, staffing, batch size, and available time;
• shipment or delivery frequency; and
• a time ladder distinguishing processing time from waiting or lead time.

Standard VSM icons are useful because they provide a shared visual language. Nevertheless, a map should not become so symbol-heavy that operators cannot read it. The map is a management instrument, not an end in itself.

Selecting the Product or Service Family

A value stream map should normally focus on a family rather than the entire organization. A product family consists of products or services that pass through similar downstream processes and use similar equipment or resources. A product-family matrix can compare products against process steps and help identify a representative family. If the routes differ substantially, separate maps may be required.

The improvement team should include people who understand demand, operations, quality, maintenance, logistics, information systems, and customer requirements. Mapping conducted solely by a central improvement office often produces technically neat but operationally weak results.

Collecting Current-State Data

Data collection should combine direct observation with validated records. Typical measures include:

• customer demand per day or week;
• available working time after breaks, meetings, planned maintenance, and other known losses;
• cycle time for each process step;
• number of operators and machines;
• uptime and first-pass yield;
• changeover or setup time;
• quantity of work-in-process or finished-goods inventory;
• batch sizes and scheduling frequency;
• queue time and transport time; and
• defect, rework, and cancellation rates.

A single average can be misleading. A process with a mean cycle time of five minutes may have a stable range of four to six minutes or a volatile range of one to twenty minutes. The managerial response differs greatly. Where possible, record distributions, causes of variation, and the conditions under which measurements were taken.

Time Analysis and the Value-Added Ratio

Lead time is the elapsed time from the beginning of the value stream to completion or delivery. It includes processing, inspection, movement, waiting, storage, rework, and information delays. In a simple inventory-based approximation, waiting time associated with an inventory quantity can be estimated as:

Inventory waiting time = Inventory quantity / Average daily demand.

If a stream contains 600 units of inventory and demand is 100 units per day, the inventory represents approximately six days of waiting, assuming demand and inventory flow are reasonably stable.

Cycle time is the time required to complete one unit or transaction at a process step. It must be distinguished from takt time, which represents the rate of customer demand:

Takt time = Net available production time / Customer demand.

If net available time is 420 minutes per day and demand is 105 units, takt time is four minutes per unit. A process cycle time greater than four minutes cannot consistently satisfy demand without additional capacity, reduced losses, or a different work design. Takt time is a demand signal, not a claim that every task should take exactly that long.

The value-added ratio or process cycle efficiency is commonly calculated as:

Value-added ratio = Value-added processing time / Total lead time × 100.

Suppose a service request spends 12 working days in the system, while activities that directly transform the service total 48 minutes. Assuming an eight-hour working day, total lead time is 5,760 minutes. The ratio is:

48 / 5,760 × 100 = 0.83%.

This does not mean that 99.17 percent of the organization’s work is useless in a moral or legal sense. It means that most elapsed time is not spent directly transforming the customer deliverable. The result directs attention toward queues, approvals, batching, rework, and handoffs.

Care is required when comparing ratios. The numerator must be defined consistently, and the denominator must use the same time basis. Calendar time, working time, and elapsed clock time should not be mixed casually. A high value-added ratio also does not automatically imply high quality or customer value; a process can be fast but produce the wrong outcome.

From Current State to Future State

A current-state map is diagnostic. A future-state map is a design hypothesis about how the value stream should operate. It should not be a picture of an ideal world without constraints. The design must respond to demand, available resources, quality requirements, regulatory obligations, technology, and organizational capability.

Designing Flow and Pull

The first design question is whether work can flow continuously or in smaller batches. Continuous flow is appropriate when demand, sequence, product characteristics, and process capability permit it. Where variability or technical constraints prevent continuous flow, a controlled supermarket or other pull mechanism may be appropriate. In a pull system, downstream consumption signals replenishment rather than upstream production based solely on forecasts.

A pacemaker process is the point at which production scheduling is controlled for the value stream. Scheduling multiple downstream processes independently often creates conflicting priorities and excess inventory. A pacemaker provides a clear rhythm, while upstream processes replenish according to a defined pull signal.

Future-state design commonly considers the following questions:

• What does the customer require, and at what rate?
• Where can continuous flow be established?
• Where are supermarkets or FIFO lanes needed because flow cannot be continuous?
• Which process should serve as the pacemaker?
• What quantity of work-in-process is necessary to protect the customer from predictable variation?
• How will quality be built into the process rather than inspected only at the end?
• How will abnormal conditions be signalled and managed?
• What information should be electronic, visual, standardized, or removed?

Balancing Work and Addressing Constraints

Work balancing compares process content with takt time and available capacity. If one operation requires 7 minutes when takt is 4 minutes, simply instructing the operator to work faster is not a lean solution. Options may include redistributing tasks, reducing changeover, improving equipment availability, simplifying the product, adding capacity, or redesigning the process.

The bottleneck or constraint deserves special attention because improving non-constraints may only increase inventory before the constraint. Constraint management therefore complements VSM. A future-state map should identify the constraint, protect it from avoidable interruptions, ensure that upstream work does not overwhelm it, and align improvement priorities with total throughput.

Improvement Roadmaps

A future-state map becomes useful when translated into a sequenced roadmap. A roadmap should identify the action, owner, expected effect, measure, required resources, dependencies, and review date. Early actions often establish basic stability: standard work, accurate demand data, workplace organization, preventive maintenance, quality-at-source practices, and removal of obvious information delays. Later actions may involve cellular redesign, changeover reduction, digital integration, supplier development, or advanced planning changes.

Roadmaps should avoid launching too many projects simultaneously. A practical sequence is to stabilize, create flow where feasible, establish pull and visual control, reduce remaining lead time, and then institutionalize daily management. The sequence is not universal; safety, compliance, customer risk, or a severe constraint may alter priorities.

An Illustrative Case: Reducing the Lead Time of a Medical-Device Order

Background

The following is a fictional illustrative case. MedEquip Components manufactures a family of standard diagnostic-device assemblies. Customers complain that quoted delivery time is 15 working days even though direct assembly and inspection time is less than one hour.

Situation and Problem

An improvement team selects the standard assembly family and observes the stream from order entry to dispatch. The company receives an average demand of 80 assemblies per day. Net available time is 400 minutes per day, giving a takt time of five minutes per assembly. The current stream contains four major stages: order review, material kitting, assembly, and final inspection/dispatch.

Observed data are as follows:

• Order review: 20 minutes of work, with an average queue of 240 orders.
• Material kitting: 15 minutes of work, with an average queue equivalent to 160 orders.
• Assembly: 18 minutes of work per order, with an average queue equivalent to 120 orders.
• Final inspection and dispatch: 10 minutes of work, with an average queue equivalent to 80 orders.

The total direct processing time is 63 minutes. Total work-in-process is 600 orders. At demand of 80 orders per day, the inventory-based waiting time is approximately 7.5 days. Additional waiting occurs in order release, batch scheduling, material shortages, and inspection holds. Observation shows that the actual average lead time is 15 working days. A spaghetti diagram also shows that assemblers walk approximately 1.2 kilometres per shift to obtain components and return completed paperwork.

Analysis

The value-added ratio, using direct processing time and the observed lead time, is:

63 / (15 × 400) × 100 = 1.05%.

The analysis identifies several problems. Each department schedules its own work, creating batches and competing priorities. Inspection is performed as a large end-of-line batch, so defects are discovered late. Kitting is physically distant from assembly, and paperwork travels between order review, production control, and dispatch. The assembly process itself is below takt only if its work is distributed appropriately; its 18-minute content may require several operators or a small balanced cell rather than one person working alone.

Future-State Approach

The team proposes a future state with order review and material availability checks completed through a standard electronic order form. A small assembly cell is created, with work elements balanced across four operators. A supermarket of pre-approved component kits is placed beside the cell. The cell becomes the pacemaker and is scheduled to a consistent mixed-model sequence close to customer demand. Quality checks are moved into the work, with error-proofing for component identification and immediate response to abnormalities. Final inspection is retained where required by the quality system but reduced to confirmation rather than discovery of routine defects.

A FIFO lane limits work between kitting and assembly. Replenishment of kits is triggered by actual consumption. The layout change reduces walking, while electronic status visibility removes several paper handoffs. The roadmap begins with data validation and standard work, followed by layout and kitting changes, then pull control and supplier replenishment improvements.

Outcome and Learning Points

In the illustrative scenario, the redesigned state reduces work-in-process, shortens order lead time, and makes abnormal conditions visible earlier. The numerical improvement is less important than the logic: the team does not begin by purchasing faster equipment. It first removes batching, clarifies the pacemaker, balances work to demand, locates materials at the point of use, and builds quality into the flow.

The case demonstrates five lessons. First, a process can have substantial capacity and still have long lead time. Second, inventory is often a symptom of disconnected scheduling rather than a solution to poor flow. Third, physical layout and information design are part of the same value stream. Fourth, future-state design must preserve required quality controls. Fifth, mapping must lead to daily management; otherwise the organization may return to departmental scheduling and accumulating queues.

Digital Mapping, Analytics, and Governance

Digital process-mining platforms can reconstruct process paths from event logs in enterprise resource planning, customer relationship management, laboratory, or workflow systems. They can identify variants, rework loops, waiting times, and conformance gaps at a scale difficult to achieve through observation alone. Dashboard tools can display lead time, queue age, first-pass yield, and adherence to a future-state design.

Technology does not remove the need for process understanding. Event logs may omit informal work, record timestamps inconsistently, or represent administrative completion rather than actual work. Automated maps can therefore produce false precision. A digitally detected “short process” may merely reflect missing events. Process mining should be combined with gemba observation, interviews, and validation by process owners.

Artificial intelligence may support anomaly detection, demand forecasting, document classification, and identification of likely bottlenecks. Its use requires governance concerning data quality, explainability, access rights, cybersecurity, and human accountability. A model that recommends prioritization may unintentionally disadvantage certain customers if historical data reflect biased service patterns. Automation should simplify work and improve control, not obscure responsibility.

Mapping also raises confidentiality and professional concerns. Patient, employee, supplier, and customer data should be minimized, protected, and used for legitimate purposes. Process transparency must not become individual surveillance without fair policy, clear purpose, and appropriate consultation. Metrics should evaluate the process and its conditions, not punish people for variation they cannot control.

Common Errors and Practical Safeguards

Several mistakes recur in mapping projects. Teams sometimes map the documented process rather than the real one, use averages that hide variation, exclude support functions, or begin with a preferred technology solution. Others treat every activity as either valuable or wasteful, ignoring necessary controls. A map may also become outdated when demand, product mix, staffing, or system rules change.

Practical safeguards include observing multiple cases, recording assumptions, separating fact from interpretation, validating data with operators, showing rework and exception paths, and defining the time basis of every calculation. The team should agree on the product or service family and map the complete customer-facing boundary. Future-state proposals should be tested through pilots or simulations before large-scale implementation.

Best practice is to treat VSM as a recurring management cycle rather than a one-time workshop: understand demand, observe the current state, identify the principal constraint and sources of delay, design a feasible future state, implement a focused experiment, measure results, and revise the map. The map should remain connected to standard work, visual management, daily accountability, and periodic review.

Chapter Summary

Process mapping makes work, responsibility, decisions, and rework visible. SIPOC establishes the scope and relationships among suppliers, inputs, process stages, outputs, and customers. Detailed process maps reveal sequence and ownership, while spaghetti diagrams expose unnecessary physical movement. Value stream mapping integrates process, information, material, inventory, capacity, and time across the customer-facing stream.

Current-state mapping depends on observation and reliable data. Lead time includes processing and all forms of waiting; cycle time describes a process step; takt time expresses the rate required by customer demand. The value-added ratio compares value-adding processing time with total lead time and helps reveal the scale of delay. Future-state mapping uses flow, pull, pacemaking, work balancing, quality at source, and constraint management to create a feasible improvement design. An improvement roadmap translates that design into owned, measured actions.

Digital process mining and analytics can strengthen mapping but cannot replace operational understanding. Ethical data governance, human judgement, privacy, and accountability remain essential. The most effective organizations use mapping as a continuous management discipline rather than as a one-time diagramming exercise.

Key Terms

SIPOC: A high-level view of Suppliers, Inputs, Process, Outputs, and Customers used to define process scope.

Process map: A visual representation of activities, decisions, sequence, handoffs, and outputs.

Swim-lane map: A process map that assigns activities to roles, departments, systems, or other responsibilities.

Spaghetti diagram: A layout-based trace of movement by people, materials, documents, or vehicles.

Value stream: The complete set of actions required to deliver a product or service from request to customer.

Value Stream Mapping (VSM): A visual method for analysing material flow, information flow, inventory, and time across a value stream.

Current-state map: A representation of how a process actually operates at present.

Future-state map: A designed representation of how the value stream should operate after improvement.

Value-added activity: Work that transforms the deliverable in a way the customer values and that is done correctly.

Necessary non-value-adding activity: Required work that does not directly transform the customer deliverable, such as certain compliance controls.

Lead time: Elapsed time from the beginning of a process or value stream to its completion.

Cycle time: Time required by a process step to complete one unit or transaction.

Takt time: Available operating time divided by customer demand.

Value-added ratio: Value-added processing time divided by total lead time, expressed as a percentage.

Work-in-process: Items or transactions that have entered a process but are not yet complete.

Pacemaker process: The process selected to receive the principal schedule and establish the operating rhythm.

Pull system: A system in which downstream consumption signals replenishment or production.

Supermarket: A controlled inventory point from which downstream users withdraw and which upstream processes replenish.

FIFO lane: A first-in, first-out controlled queue used to limit work and preserve sequence.

Process mining: The use of event-log data to discover, analyse, and monitor actual process paths.

Review Questions

Short Answer Questions

1. What is the principal purpose of a SIPOC diagram?

2. Distinguish between cycle time and takt time.

3. Why can a process map based only on written procedures be misleading?

4. What type of waste does a spaghetti diagram primarily help identify?

5. Define a pacemaker process in a future-state value stream.

Long Answer Questions

1. Explain how SIPOC, detailed process mapping, spaghetti diagrams, and value stream mapping complement one another.

2. Describe the steps involved in constructing and validating a current-state value stream map.

3. Explain lead time, processing time, cycle time, takt time, and value-added ratio, including their managerial significance.

4. Discuss the principles that should guide the design of a future-state value stream.

5. Evaluate the benefits and risks of using process-mining technology in lean improvement.

Analytical / Application Questions

1. A service process has a lead time of 10 working days, with 7.5 hours of direct value-adding work. If one working day contains 450 available minutes, calculate the value-added ratio and interpret the result.

2. Customer demand is 150 units per day and net available time is 420 minutes per day. Three sequential steps require 2.5, 3.2, and 4.8 minutes per unit. Identify the capacity concern and propose two improvement alternatives.

3. A current-state map shows large batches, three independent schedules, repeated quality inspection, and long movement between a warehouse and production. Design a prioritized improvement roadmap and explain the rationale for its sequence.

22. Multiple Choice Questions with Answers

Question 1

A team is beginning an improvement project but has not agreed on the process boundary or principal customers. Which tool is most appropriate initially?

A. Spaghetti diagram

B. SIPOC

C. Future-state VSM

D. Control chart

Correct Answer: B. SIPOC

Question 2

A process has 480 minutes of net available time and customer demand of 120 units per day. What is its takt time?

A. 2 minutes per unit

B. 3 minutes per unit

C. 4 minutes per unit

D. 5 minutes per unit

Correct Answer: C. 4 minutes per unit

Question 3

A transaction spends 2,400 minutes in a system, of which 30 minutes are value-adding. What is the value-added ratio?

A. 0.8%

B. 1.25%

C. 8%

D. 12.5%

Correct Answer: B. 1.25%

Question 4

Which observation most directly indicates that a value stream has been mapped from procedures rather than from actual work?

A. The map contains process data boxes

B. The map includes customer demand

C. The map excludes rework and informal workarounds observed by operators

D. The map identifies a pacemaker process

Correct Answer: C. The map excludes rework and informal workarounds observed by operators

Question 5

What is the principal purpose of a spaghetti diagram?

A. To calculate takt time

B. To display physical movement and possible excess travel

C. To identify suppliers and customers

D. To assign the production schedule

Correct Answer: B. To display physical movement and possible excess travel

Question 6

In a future-state design, downstream consumption signals replenishment from an upstream controlled inventory point. This is best described as:

A. A push system

B. A functional layout

C. A pull system using a supermarket

D. A batch inspection system

Correct Answer: C. A pull system using a supermarket

Question 7

A process step requires 7 minutes per unit while takt time is 4 minutes per unit. Which conclusion is most appropriate?

A. The process is automatically value-adding

B. The step may fail to meet demand unless capacity or work design changes

C. The customer demand should always be reduced

D. Inventory should be increased without further analysis

Correct Answer: B. The step may fail to meet demand unless capacity or work design changes

Question 8

Why is a pacemaker process used in value-stream design?

A. To schedule every process independently

B. To establish the operating rhythm and principal schedule for the stream

C. To eliminate all quality checks

D. To maximize batch size at the bottleneck

Correct Answer: B. To establish the operating rhythm and principal schedule for the stream

Question 9

Which is the strongest reason to combine digital process mining with direct observation?

A. Event logs always contain informal work accurately

B. Direct observation is unnecessary when timestamps exist

C. Event logs may omit work or record administrative events rather than actual activity

D. Digital tools cannot calculate waiting time

Correct Answer: C. Event logs may omit work or record administrative events rather than actual activity

Question 10

A team improves a fast, non-constraining workstation while inventory continues accumulating before a bottleneck. What lean principle has it most clearly overlooked?

A. The need to align improvement with the system constraint

B. The need to define a SIPOC

C. The need to increase departmental utilization everywhere

D. The need to remove all necessary controls

Correct Answer: A. The need to align improvement with the system constraint