Value Stream Mapping
with Gemba-VSM

This guide introduces value stream mapping (VSM) and walks you through using Gemba-VSM v6.3 to capture data at the gemba, build professional current and future state maps, and export your work for printing, AI coaching, and further analysis.

Value stream mapping is one of the most powerful tools in lean management. It provides a visual representation of all the actions required to deliver a product or service, making it possible to see where waste occurs and where improvement opportunities exist.

Who is this guide for?

Anyone involved in process improvement — whether in healthcare, manufacturing, service industries or administration. No prior lean experience is required. The guide covers the theory behind VSM, the observation skills needed to capture reality at the gemba, and then provides practical, step-by-step instructions for using Gemba-VSM v6.3.

What you will learn

• What a value stream map is and why it matters
• How to identify the 8 wastes (DOWNTIME) in your process
• How to walk the gemba and collect accurate data
• How to develop the observation skills that make a good map possible
• How to build current state and future state maps
• How to map parallel paths — concurrent processes that depart from and return to the main value stream
• How to capture cycle time variation through multiple observations
• How to record WIP range data showing flow patterns through the day
• How to use the AI Lean Sensei Coaching Export for guided reflection
• How to install and use Gemba-VSM on your phone or computer
• How to save, export and share your value stream maps

What is a value stream?

A value stream is all the specific actions (process steps) within an end-to-end pathway that bring a product or service to the customer. This includes both value-adding activities and non-value-adding activities (waste).

What is value?

Value can only be defined by the end customer. It is any activity that directly contributes to satisfying the needs of the customer — any activity the customer would be willing to pay for. Everything else is waste.

What is a value stream map?

A value stream map (VSM) is a visual representation of all the actions currently required to deliver a product or service. It documents the flow of materials and information across the entire pathway from origin to final point of delivery. The map shows:

• Each process step and how long it takes (cycle time)
• How work moves between steps (push or pull)
• Where work accumulates between steps (inventory / WIP)
• The delays and waiting times between steps
• Batch sizes at each step
• Defect rates and quality issues
• How information flows (paper, electronic, verbal)
• The trigger that starts each process step
• Parallel paths where work leaves the main stream and returns later

The Five Principles of Lean

Value stream mapping sits within the broader framework of lean thinking. Womack and Jones identified five key principles that underpin all lean activity:

• Specify Value from the perspective of the customer. What does the customer actually need?
• Identify the Value Stream and map all the steps. This is where VSM comes in.
• Make Value Flow without interruption, waiting, detours or defects requiring rework.
• Respond to Pull — only produce what the customer demands, when they demand it.
• Pursue Perfection by continually removing successive layers of waste.

Key VSM Concepts

Cycle Time (C/T) — The time it takes to complete one unit of work at a process step. Measured by direct observation at the gemba, not from a desk. In Gemba-VSM, you can capture multiple cycle time observations to record the variation you see between operators and conditions.

Lead Time — The total end-to-end time from when work enters the value stream to when it exits. Lead time = value-added time + all delays and waiting. In most processes, lead time is dramatically longer than the actual value-added (touch) time.

Takt Time — The rate at which you need to complete work to meet customer demand. Calculated as: Available working time per day ÷ Customer demand per day.

Batch Size — The number of items processed together before being passed to the next step. Large batches create delays and inventory. Reducing batch size towards single-piece flow is a key lean strategy.

Process Efficiency — The ratio of value-added time to total lead time, expressed as a percentage. In many service and healthcare processes, this can be shockingly low — often well under 5%. This is normal and shows the scale of the improvement opportunity.

Current State vs Future State

You always start by mapping the current state — what actually happens today, based on direct observation. This is not what the procedure says should happen, or what managers think happens. It is what you see when you walk the process yourself.

Once you understand the current state, you design the future state — what the process should look like with waste removed. Use the ECSS technique:

• Eliminate — can any steps be removed entirely?
• Combine — can steps be merged together?
• Simplify — can remaining steps be made simpler?
• Sequence — is the order of steps optimal for flow?

Going to the Gemba

Gemba (現場) is a Japanese word meaning "the actual place" — where the work happens. Value stream mapping must be based on direct observation at the gemba, not on assumptions, reports or interviews. Walk the process yourself. Watch what actually happens. Time it. Count the inventory. Talk to the people who do the work. Capture photos.

This is the principle of "Go See, Ask Why, Respect People" — the foundation of all authentic lean practice.

• Keep your value stream map high level — don't get lost in the detail
• Focus on the main pathway — what happens 80% of the time
• Collect true and accurate information by walking through the pathway yourself

Waste (muda) is any activity that does not add value from the customer's perspective. Originally Taiichi Ohno identified 7 wastes as part of the Toyota Production System. An eighth waste, "Non-utilized Talent", was later added. The acronym DOWNTIME captures all eight.

Letter	Waste	Description
D	Defects	Producing defective products or services that require rework or replacement
O	Overproduction	Producing more than the customer needs or before it is needed
W	Waiting	Idle time when people, information, or materials are not moving
N	Non-utilized Talent	Failing to leverage the full capabilities and creativity of your people
T	Transportation	Unnecessary movement of products or materials between processes
I	Inventory	Excess storage of raw materials, work-in-progress, or finished goods
M	Motion	Unnecessary movement of people or equipment that does not add value
E	Extra Processing	Performing unnecessary steps or using inappropriate methods

This section describes the methodology. Section 7 shows how to do each step using Gemba-VSM v6.3.

Step 1: Define the Scope

Establish the start and stop points of the value stream you are mapping. Who is the supplier (where does the work come from)? Who is the customer (where does the finished product or service go)? What is the customer demand rate? Agree the scope with the team before you start walking.

Step 2: Walk the Process

Go to the gemba and walk the entire process from end to end. Observe what actually happens. Do not rely on procedures, manuals, or what people tell you in a meeting room. Take your phone with Gemba-VSM v6.3 installed — it is your data collection tool, your stopwatch, and your camera in one. You enter the facts you observe, and the tool draws the map and calculates the metrics for you.

Step 3: Document the Process Steps

Record each major process step in sequence. For each step, enter the data into Gemba-VSM v6.3: cycle time (timed by direct observation), changeover time, batch size, defect/error rate, uptime/availability, number of operators, and the trigger that starts the step. The tool stores each step and builds the process box and data box on the map automatically.

Step 4: Record Inventory, Delays and Variation

Between each process step, count the work-in-progress (WIP) and measure or estimate the delay time. This is where most of the lead time hides. Enter the WIP count and delay for each step in Gemba-VSM v6.3 — the tool renders inventory triangles and delay segments on the timeline for you.

Capture the variation you observe. If WIP fluctuates through the day (e.g. 3 at 8am, 25 at 2pm), record the range and peak timing. If cycle time differs between operators or conditions, log multiple observations. The gap between your fastest and slowest observation is where the coaching conversation begins.

Step 5: Map Information Flows

Document how information moves through the process. Is it paper-based, electronic, or verbal? Which IT systems are involved at each step? Information flow problems are a major source of waste. Select the flow types for each step in Gemba-VSM v6.3, and the tool renders them on the map: paper flows as solid lines, electronic flows as dashed lines, and verbal flows as dotted lines with a speech bubble symbol.

Step 6: Identify Waste

At each step, identify the DOWNTIME wastes you observe. Tick the wastes you see in Gemba-VSM v6.3's data capture form and flag improvement opportunities — the tool marks them as kaizen bursts on the map.

Step 7: Identify Parallel Paths

Look for work that leaves the main value stream at one step and returns at a later step. These parallel processes — such as samples sent to an external laboratory, equipment sent for calibration, or referrals awaiting specialist input — have their own lead time and often determine how long the main stream waits. Add these as parallel paths in Gemba-VSM v6.3 and the tool renders them below the timeline on your map (see Section 8).

Step 8: Review the Timeline

Gemba-VSM v6.3 calculates the timeline automatically from the data you have entered. It adds up all the cycle times to give you the total value-added (touch) time, adds up all the delays to give you the total non-value-added time, and calculates process efficiency: value-added time ÷ total lead time. The sawtooth timeline at the bottom of the map shows this visually. The gap between touch time and lead time is your improvement opportunity.

Step 9: Design the Future State

Using ECSS (Eliminate, Combine, Simplify, Sequence), design a future state map with waste removed. Copy your current state to future state in Gemba-VSM v6.3, then edit the steps to reflect improvements. The tool recalculates the projected metrics so you can see the impact of your proposed changes. Create an action plan of PDCA cycles to implement them.

Value stream mapping is a skill, and like any skill it develops through practice. Your first map will be incomplete. Your second will be better. Your tenth will reveal things you could not have seen on your first visit. This is normal and expected — developing the ability to observe a process clearly, without preconception or judgement, takes time and deliberate effort.

Facts, Not Just Data

Taiichi Ohno drew a sharp distinction between data and facts. Data is what arrives on a report, in a spreadsheet, or on a dashboard. It tells you what the system recorded. Facts are what you see when you stand at the gemba and watch the work happen with your own eyes.

The two are not always the same. A system may record that a task takes 15 minutes. But when you stand and watch, you see that the operator finishes the hands-on work in 4 minutes, then spends 11 minutes searching for a missing piece of equipment, walking to a printer in another room, and waiting for a colleague to unlock a cupboard. The data says 15 minutes. The facts say 4 minutes of value and 11 minutes of waste — and the waste has specific, observable causes.

This is why going to the gemba is non-negotiable. You cannot map a value stream from a desk. You cannot identify waste from a report. You have to go and see.

Learning to Observe Without Judgement

The hardest skill in gemba observation is seeing what is actually happening without immediately judging it. When you see a workaround, it is natural to think "that's wrong" or "they should be doing it differently." Resist that impulse. Instead, ask yourself: why does this workaround exist? What is the person compensating for? Workarounds are intelligent responses to broken systems, not evidence of carelessness or rule-breaking.

Record what you see, not what you think should be happening. The unavailable equipment, the layout that forces unnecessary motion, the information that arrives on paper because the electronic system is too slow, the verbal handoff that happens because the formal process does not match the reality of the work — all of these are facts. They all need to be observed and recorded.

What to Observe

Beyond the cycle times and batch sizes, look for these things at each process step:

• Workarounds — any place where people have developed their own method because the standard process does not work. Ask what problem the workaround solves.
• Equipment and materials — is everything needed for the step available, in the right place, at the right time? Watch for searching, fetching, and waiting for equipment.
• Layout and motion — how far do people walk? How many times do they move between workstations, printers, stores, or other areas? Draw a spaghetti diagram if the motion is significant.
• Information flow — how does the person know what to do next? Is the information clear, timely, and complete? Watch for phone calls to chase missing information, handwritten notes that supplement electronic records, and delays caused by unclear instructions.
• Interruptions — how often is the person pulled away from the task? What causes the interruption? Interruptions destroy flow and increase error risk.
• Variation between people — observe the same step performed by different operators. The differences in method, speed, and sequence tell you whether a standard exists and whether it is followed.

Building Trust

The people doing the work need to trust you. They need to understand that your intention is to help them and empower them, not to judge or blame them. If people feel they are being assessed or monitored, they will perform the work differently — often more carefully and slowly than normal — and you will record a process that does not exist outside of your observation.

Be transparent about what you are doing and why. Explain that you are mapping the process, not measuring individuals. Make clear that the purpose is to find problems in the system so they can be fixed — problems belong to the process, not to people. Share what you are recording. Invite the people doing the work to correct you when you have misunderstood something, because you will.

The best value stream maps are created with the team, not about them. When the people who do the work contribute to the map, they see the waste for themselves. They understand why things take so long. They generate the improvement ideas. This is the foundation of sustainable change — the people who own the process own the improvement.

Gemba-VSM is a Progressive Web App (PWA). It runs in your browser and can be installed on your phone or tablet for full-screen, offline use at the gemba. No app store required.

What you need to get started: A phone or computer with a modern browser and internet access. Open https://gembasuite.org/vsm in your browser.

Gemba-VSM has six main tabs: Gemba Capture, Process Steps, Current State Map, Future Steps, Future State Map, and Compare. Work through them in order.

Example Data

When you first open Gemba-VSM, it loads an example value stream — the Brew & Go Tea Shop — with five current state steps and four future state steps already populated. This lets you explore the mapping, comparison, and export features before creating your own project. Create a new blank project when you are ready to map your own process.

Gemba Capture Tab

This is where you enter all your data. It has three areas:

Value Stream Information

Fill this in once for each map. Enter the name of the value stream, the product/service family, who mapped it, the date, supplier (start point), customer (end point), customer demand per day, and available working time per day in seconds. This information appears on the printed map header and is used to calculate takt time.

IT Systems Registry

Register the IT systems used across your value stream (e.g. LIMS, EPR, Order Comms, PACS). Quick-add buttons are provided for common healthcare systems. Registered systems appear as checkboxes when you select "Electronic" information flow for a step, letting you record exactly which systems connect to each process step.

Add Process Step

For each step in the value stream, capture the following data:

Field	What to capture
Process Step Name	The name of the activity, e.g. "Specimen Reception"
Process Type	Process Step, Inspection, Transportation, Delay, or Storage
Trigger / Flow Type	Push, Pull, or FIFO — what starts this step
Cycle Time (C/T)	Time to process one unit — observed directly at the gemba
C/T Unit	Seconds, Minutes, or Hours
C/T Observations	Multiple timed observations with context — see Section 9
Changeover Time (C/O)	Time to switch between different types of work
Batch Size	Number of items processed together before passing downstream
Defects / Errors (%)	Error rate at this step
Uptime / Availability (%)	Percentage of time the step is available to process work
Operators	Number of people working at this step
WIP / Inventory	Count of items waiting before this step
WIP Range	Min and max WIP with peak timing notes — see Section 9
Inventory Type	Standard triangle or Supermarket symbol
Delay Before Step	Waiting time before this step begins (with unit)
Information Flow	Paper, Electronic, Verbal — multi-select
IT Systems	Which registered systems connect to this step (if Electronic)
DOWNTIME Wastes	Tick each waste type observed at this step
Kaizen Opportunity	Flag improvement ideas with a note
Notes	Gemba observations, workarounds, problems, waste seen
Photos	Take photos directly from the gemba using your phone camera (max 2 per step, auto-compressed)

Process Steps Tab

This tab shows all your current state process steps in a list. You can drag and drop to reorder steps using the handle on the left, edit any step using the pencil button (opens a modal with all fields including variation capture), or delete a step using the bin button.

Each step displays its cycle time, batch size, defect rate, WIP (with range if captured), delay, waste badges (coloured tags showing which DOWNTIME wastes were observed), information flow badges, IT system badges, kaizen burst flags, data gap warnings, photo thumbnails, and variation badges showing observation count.

Current State Map Tab

This tab renders your data as a professional SVG value stream map in the traditional format:

• Supplier box on the left, customer box on the right with demand rate
• Process boxes with data boxes underneath showing C/T (with variation range if captured), C/O, Batch, Defects, Uptime
• Yellow inventory triangles (or supermarket symbols) with WIP counts between steps
• Push arrows, pull circles, and FIFO lanes connecting process steps
• Information flow bus/rail architecture — IT systems shown as horizontal rails with drop-down taps to connected steps, paper flows as solid lines, electronic flows as dashed lines
• SVG speech bubble symbols for verbal information flow
• Kaizen burst stars on flagged steps
• Parallel path boxes below the timeline showing concurrent processes (see Section 8)
• Sawtooth timeline at the bottom — delays above (red), cycle times below (green)
• Summary line: Value-Added Time, Total Lead Time, Process Efficiency, Takt Time

The toolbar provides buttons to Print the map, download as SVG, and add parallel paths.

Future State Map Tab

Click "Copy Current → Future" to duplicate your current state data, including any parallel paths. Then use the Future Steps tab to modify the future state: eliminate steps, reduce batch sizes, remove delays, combine activities, change push to pull, add supermarket inventory. You can also add entirely new steps to the future state. The future state map renders with the same professional format and can be printed or exported independently.

Compare Tab

This tab shows current and future state maps side by side, making it easy to see the improvement at a glance. Use the Print button to produce a comparison sheet.

In many value streams, work does not follow a single linear path. At certain steps, an item or request leaves the main process flow, undergoes a separate process in parallel, and returns at a later step. The main stream may wait for this parallel process to complete, or it may continue independently.

These parallel paths are common in healthcare, manufacturing, and service processes. Examples include:

• A specimen sent for specialist staining while the main workflow continues to the next case
• A referral to an external laboratory or specialist, with the result returning days later
• Equipment sent for calibration or repair, returning to the line when ready
• A document sent for approval or sign-off while other work proceeds

Without parallel paths on the map, these concurrent processes are invisible. The delay they introduce appears as an unexplained gap on the timeline. Making them visible is the first step to managing them.

Two Ways to Record a Parallel Path

Gemba-VSM offers two options when you create a parallel path:

Quick Label — a named box on the map with a manually entered lead time. Use this when you know the parallel process exists and roughly how long it takes, but you do not need to map it in detail. The box appears below the timeline between the departure and return steps.

Full VSM (Child Project) — a new, linked VSM project is created automatically for the parallel process. You map the parallel path as a complete value stream in its own right, with its own process steps, data boxes, and timeline. The child project links back to the parent, and you can navigate between them. Use this when the parallel process is complex enough to warrant its own map.

Creating a Parallel Path

Click the "Add Parallel Path" button in the map toolbar. A modal opens with the following fields:

Field	What to enter
Label	A name for the parallel process (e.g. "IHC Staining", "External Review")
Departure Step	The step where work leaves the main stream
Return Step	The step where the result re-enters the main stream (must be after the departure step)
Main Stream Waits	Toggle: does the main stream wait for this path to complete?
Type	Quick Label (enter a lead time) or Full VSM (creates a child project)

How Parallel Paths Appear on the Map

Each parallel path renders as a labelled box below the timeline, positioned horizontally between the departure and return steps. Dashed arrows connect the departure step down to the parallel path box and the return step back up from it. If a child project is linked, clicking the box navigates to that project.

Multiple parallel paths stack vertically beneath the timeline. Each additional path extends the map height.

Wait Time and Its Effect on Metrics

If you have indicated that the main stream waits for the parallel path, the parallel path's lead time is added to the delay between the departure and return steps on the timeline. This affects the total lead time and process efficiency calculations for the main value stream.

If the main stream does not wait, the parallel path appears visually on the map but does not alter the main stream's timeline calculations. The lead time used for the wait calculation comes from the manually entered value (for quick labels) or the calculated total lead time of the child project (for full VSM paths). A manual override is always available.

Navigating Between Parent and Child Projects

When you are viewing a child project, a back-link appears in the project bar showing the parent project name and the parallel path label. Click it to return to the parent. From the parent, click the parallel path box on the SVG to navigate to the child project. Both parent and child appear in the normal project list and can also be opened directly from there.

A single cycle time number is a snapshot. What you actually see at the gemba is a distribution — operator A takes 4 minutes, operator B takes 11 minutes, the same operator takes 6 minutes before the morning backlog and 14 minutes during the afternoon rush. The gap between those numbers is where the coaching conversation lives.

Cycle Time Observation Log

Below the cycle time field in both the Gemba Capture form and the Edit modal, you will find a collapsible "Add observations" panel. Each observation records:

• Value — the timed cycle time (with unit)
• Context — who was performing the work, what time of day, what conditions (e.g. "Operator A, morning, no queue")
• Timestamp — automatically recorded when the observation is added

As you add observations, the app automatically calculates and displays the minimum, maximum, mean, and range. The typical cycle time field auto-updates to the mean but can be manually overridden — for example, if the mean is 9.9 minutes but you consider 7 minutes to be the typical value because one operator was in training.

Manual Range Fallback

If you did not capture individual observations but know the approximate range from memory or a previous visit, expand "Or enter range manually" to enter min, typical, and max values with a note explaining the source.

WIP Range

Below the WIP/Inventory field, a collapsible "WIP range" panel lets you record the minimum and maximum WIP observed, along with a peak timing note.

"WIP was 3 at 8am and 25 at 2pm" is dramatically more useful than "WIP: 14 (average)." It tells you something about flow, about where batching happens, about capacity mismatches across the day. This is exactly the kind of gemba observation that makes a coaching conversation come alive.

Where Variation Data Appears

• Step list — variation badges (observation count or range indicator) appear alongside each step
• SVG data box — the C/T line shows the variation range in parentheses when observations or range data exist
• AI coaching export — individual observations are listed for facilitator coaching; summary statistics are included for sensei prep
• CSV/Excel export — additional columns for CT Observations, CT Range, and WIP Range
• JSON export — full observation data with timestamps and context preserved for data portability

Gemba-VSM can generate a structured coaching prompt from your value stream mapping data. You copy this prompt into a free AI assistant (Microsoft Copilot, Claude, or Google Gemini) for guided gemba reality validation — helping you see whether you have captured what actually happens and identify gaps in your observation.

How It Works

Click the "AI Coach" button in the header. A modal opens with the following options:

Coaching Tier

Tier	Who and how
Sensei Prep	You are an experienced lean coach preparing to guide a team. Peer-level, lean terminology used freely, concise single-shot data quality briefing.
Facilitator Coaching	You are a team leader with some lean knowledge running improvement projects. Guided reflection with concepts explained. Socratic questioning style.

AI Assistant

• Microsoft Copilot — available on NHS M365 desktops, no signup required. Shorter prompts for Copilot's context window.
• Claude — strong at following structured coaching instructions. Free account at claude.ai.
• Google Gemini — conversational style. Free account at gemini.google.com.

Additional Options

• Work area context — describe your specific setting so the AI can frame its coaching appropriately
• Mapping status — "Still mapping" or "Finished gemba walk" — changes the coaching approach
• Step selection — choose which steps to include. For Copilot, steps are auto-prioritised and capped at 6 to fit context limits
• Photo attachment — optionally select one gemba photo to paste alongside the prompt (with IG consent warning)

Preview and Copy

The full prompt is shown in a preview panel so you can read through your data before copying. Click "Copy to Clipboard" to copy the prompt, or "Download .txt" to save it as a file. Then paste it into your chosen AI assistant and begin the coaching conversation.

Core Principles Embedded in Every Prompt

• Respect for people — workarounds are intelligent responses to broken systems, not rule-breaking
• Observe multiple operators — one person's method is not the process
• Observe across conditions — different times, workloads, shifts
• First gemba walk is never the last — incomplete data is normal
• Good enough to start team dialogue — a map that sits unshared is inventory waste
• No measure, no do — challenge anything that cannot be measured

Project Management

The dark project bar below the header lets you manage multiple value stream maps:

• Project dropdown — switch between saved value streams
• Save — saves the current workspace (also auto-saves as you work with a 1.5-second debounce)
• + New VSM — saves current work, clears the workspace, prompts for a name
• Rename — change the current project name
• Delete — permanently remove a project (export JSON first as backup)

Each project stores its own metadata, current state steps (including variation data), future state steps, and parallel paths independently. Data auto-saves to your browser's local storage as you work. Child projects created from parallel paths appear in the same project list.

JSON Export — Back Up Your Data

Click "JSON" in the header to download a complete backup of your value stream map. The JSON file contains all metadata, current state steps (with all data fields, waste flags, kaizen notes, photos, cycle time observations, cycle time range, WIP range), future state steps, and parallel paths. This file can be re-imported to restore your work on any device.

When to export: After every gemba walk session. Before switching devices. Before clearing your browser. Before deleting any project. Keep your JSON files in a folder on your computer or cloud drive — they are small and contain everything.

CSV / Excel Export

Click "Excel" to download a CSV file that opens directly in Excel, Google Sheets or Numbers. The file includes a metadata header, summary statistics (total steps, value-added time, lead time, process efficiency), a full data table with every field for each process step including variation data columns (CT Observations, CT Range, WIP Range), and a separate section listing all parallel paths.

SVG Export

On the Current State or Future State Map tab, click "SVG" to download the map as a scalable vector graphic. This produces a print-quality file that can be opened in a web browser, imported into documents or presentations, or printed at any size without losing quality. Parallel path boxes are included in the SVG.

Printing

Click "Print Map" to open the map in a new window formatted for your printer. For best results, set the orientation to landscape and choose "fit to page" in your print settings.

Importing

Click "Import" to load a previously exported JSON file. The imported data creates a new project automatically — it will not overwrite your current work. The import supports files from all previous versions of the tool and automatically handles backward compatibility for variation data fields and parallel paths.

Further Reading

• NHS Improvement Diagnostic Team. "Bringing Lean to Life — Making Processes Flow in Healthcare." A practical booklet covering A3 thinking, value stream mapping, standard work, visual management, waste identification, flow, pull, takt time, 5S, PDCA and continuous improvement. The VSM symbols and methodology used in Gemba-VSM are based on this resource.
• Rother, M. & Shook, J. "Learning to See: Value Stream Mapping to Create Value and Eliminate Muda." The definitive guide to value stream mapping from the Lean Enterprise Institute (LEI). Essential reading for anyone serious about VSM.
• Womack, J. & Jones, D. "Lean Thinking: Banish Waste and Create Wealth in Your Corporation." The foundational text on lean principles — the source of the five lean principles covered in this guide.
• Liker, J. "The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer." Comprehensive overview of the Toyota Production System and the management philosophy behind it.
• Clark, D. "Quality Improvement in Basic Histotechnology: The Lean Approach." Virchows Archiv, 2015. Peer-reviewed paper documenting the application of lean transformation including VSM in a histopathology laboratory, with measurable results: 45% reduction in laboratory turnaround time, 98% reduction in labelling errors, with no increase in staffing.

Online Resources

• Lean Enterprise Institute (LEI) — www.lean.org — Primary resource for lean thinking and practice.
• Lean Enterprise Academy — www.leanuk.org — UK affiliate of the Lean Global Network.