Overview
This guide introduces value stream mapping (VSM) for pathology and diagnostic laboratory teams. It walks you through using Gemba-VSM v6.3 to capture data in your laboratory, build professional current and future state maps of diagnostic pathways, and export your work for printing, AI coaching, and further analysis.
Value stream mapping makes visible what patients and clinicians experience but laboratory staff rarely see as a whole — the delays between receipt and result, the batching that turns a 20-minute stain into a 2-day turnaround, the handoffs between sections, the waits for equipment, reagents, and authorisation that stretch a diagnostic pathway far beyond its touch time.
Who is this guide for?
Biomedical scientists, medical laboratory assistants, pathologists, laboratory managers, and anyone involved in improving pathology and diagnostic laboratory processes. No prior lean experience is required.
What you will learn
- How to map a diagnostic pathway from specimen receipt to report authorisation
- How to identify the 8 wastes in the laboratory using DOWNTIME
- How to walk the laboratory and collect accurate process 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 such as IHC staining or send-away referrals
- How to measure cycle time variation across staff and shifts
- How to record WIP range data showing specimen 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
When you first open the tool, it loads an example value stream (Brew & Go Tea Shop) so you can explore the features before mapping your own laboratory process.
Value Stream Mapping for Pathology & Diagnostics
What is a value stream in pathology?
A value stream is the complete sequence of steps a specimen follows from the point of receipt in the laboratory to the point where an authorised report reaches the requesting clinician. Every processing step, every stain, every quality check, every wait for a pathologist, every batch hold is part of the value stream.
In pathology, the customer is the clinician (and ultimately the patient) who needs an accurate, timely diagnostic result. Value is any activity that directly contributes to producing that result. Everything else is waste.
Why VSM matters in the laboratory
Laboratory processes are deceptive. They appear orderly and scientific, but when you map them you discover that the actual hands-on work — the cutting, the staining, the microscopy, the reporting — accounts for a tiny fraction of the total turnaround time. The rest is waiting: waiting for batches to fill, waiting in queues, waiting for equipment, waiting for reagents, waiting for pathologist availability.
A value stream map makes this visible. It shows you the ratio of touch time to total time, and that ratio is usually shocking. Process efficiencies of 1–5% are common in histopathology. This is not a criticism of laboratory staff — it is a property of the system they work within. The map reveals the system, and the system is what needs to change.
Key VSM Concepts
Cycle Time (C/T) — The time it takes to complete one unit of work at a process step. In the laboratory, this means timing one specimen or one slide through the step — not the batch. Measured by direct observation at the bench, not from LIMS timestamps.
Lead Time — The total elapsed time from when a specimen arrives at a step (enters the queue) to when it leaves. Lead time = cycle time + all waiting. In a batch processor like a tissue processor, lead time includes the queue time before the batch starts.
Takt Time — The rate at which you need to complete specimens to meet demand. Calculated as: Available working time per day ÷ Specimen demand per day.
Batch Size — The number of specimens processed together. Large batches create delays downstream. A tissue processor running 100 cassettes overnight creates a 100-specimen batch that must queue through embedding and microtomy the next morning.
Process Efficiency — The ratio of value-added (touch) time to total lead time. In histopathology, this is typically 1–5%. The gap between touch time and lead time is where improvement lives.
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 SOP says should happen, or what the quality manual describes. It is what you see when you walk the laboratory 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?
The future state map is a blueprint for improvement, not a wish list. Every change should be implemented through PDCA cycles and tested before being standardised.
Going to the Gemba
Gemba (現場) is a Japanese word meaning “the actual place” — where the work happens. In pathology, the gemba is the bench, the cut-up room, the staining area, the microscope. Value stream mapping must be based on direct observation, not on LIMS data or turnaround time reports. Walk the specimen journey yourself.
- Keep your value stream map high level — don’t get lost in sub-steps within embedding or microtomy
- Focus on the main pathway — what happens to a routine specimen 80% of the time
- Collect true and accurate information by walking through the laboratory yourself
The 8 Wastes in the Laboratory — DOWNTIME
Waste (muda) is any activity that does not add value from the customer’s perspective. The acronym DOWNTIME captures all eight wastes. Here is how they appear in the pathology laboratory:
| Waste | Laboratory Example | |
|---|---|---|
| D | Defects | Labelling errors, section quality issues requiring re-cuts, discrepant results requiring repeat testing |
| O | Overproduction | Cutting more levels than requested, running panels not indicated, producing reports before they can be reviewed |
| W | Waiting | Specimens queuing for processing, slides waiting for staining, cases waiting for pathologist availability |
| N | Non-utilized Talent | Qualified scientists performing tasks that could be done by support staff, pathologists doing clerical work |
| T | Transportation | Specimens moved between reception, processing, cut-up, microtomy, staining, and reporting areas |
| I | Inventory | Cassettes accumulating before the processor, slides banking before staining, cases building in the reporting queue |
| M | Motion | Scientists walking to distant printers, searching for reagents, retrieving blocks from remote storage |
| E | Extra Processing | Unnecessary quality checks duplicating earlier checks, re-entering data already in the LIMS, manual workarounds for system limitations |
When walking the laboratory, actively look for each of these 8 wastes at every process step. Gemba-VSM lets you tick the DOWNTIME wastes you observe directly in the data capture form.
How to Map a Laboratory Process
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. A typical histopathology scope runs from specimen receipt (supplier) to authorised report reaching the clinician (customer). Define the specimen type: all specimens, or a specific family such as GI biopsies or skin excisions? Agree the scope with the team before you start walking.
Step 2: Walk the Specimen Journey
Go to the laboratory and walk the entire process from reception to report authorisation. Follow the specimen, not the person. Observe what actually happens at each bench and workstation. Do not rely on SOPs, LIMS data, or what people tell you in the office. 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: reception, grossing/cut-up, processing, embedding, microtomy, staining, coverslipping, quality check, distribution, reporting, authorisation. For each step, enter the data into Gemba-VSM v6.3: cycle time (timed by direct observation at the bench), batch size, defect rate, uptime, 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 and measure the delay time. Count the cassettes waiting for the processor, the blocks waiting for microtomy, the slides accumulating before staining, the cases in the reporting queue. 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. This is where most of the turnaround time hides.
Capture the variation you observe. If WIP fluctuates through the day (e.g. 5 blocks at 8am, 80 at 2pm after the processor run), record the range and peak timing. If cycle time differs between operators, log multiple observations.
Step 5: Map Information Flows
Document how information moves through the laboratory. Which LIMS screens drive each step? Are there paper request forms alongside electronic orders? Are results communicated by LIMS, by phone, by email? Select the flow types for each step in Gemba-VSM v6.3, and the tool renders them on the map. Information flow problems — missing clinical details, unclear requests, delayed authorisations — are a major source of waste.
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 specimen pathway at one step and returns later. In histopathology, the most common parallel paths are immunohistochemistry (IHC), special stains, molecular testing, and send-away referrals. Each of these has its own lead time and often determines when the final report can be authorised. 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 time, adds up all the delays to give you the total non-value-added time, and calculates process efficiency. In histopathology, expect the result to be low — this is the improvement opportunity, not a problem to defend.
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.
Always map the current state first. Resist the temptation to jump straight to solutions before you truly understand what is happening today.
Developing Your Gemba Skills
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 laboratory 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 LIMS extract, or on a dashboard. It tells you what the system recorded. Facts are what you see when you stand at the bench and watch the work happen with your own eyes.
The two are not always the same. Your LIMS may record that a specimen was “in processing” for 14 hours. But when you stand in the laboratory and watch, you see that the tissue processor ran for 12 hours overnight, the cassettes sat in the processor for 90 minutes after the run finished because no one was available to unload, and the specimens then waited another 40 minutes in a tray before embedding started. The LIMS says 14 hours. The facts say 12 hours of processing and 2 hours of waste with specific, observable causes.
This is why going to the gemba is non-negotiable. You cannot map a laboratory value stream from a LIMS 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 scientist using a workaround — perhaps handwriting case numbers on slides because the printer is unreliable, or batching cases in a way that differs from the SOP — it is natural to think “that’s wrong.” Resist that impulse. Instead, ask yourself: why does this workaround exist? What is the person compensating for?
Workarounds are intelligent responses to broken systems. They tell you where the standard process has failed the person doing the work. Record them as facts, not as problems with individuals.
What to Observe
Beyond the cycle times and batch sizes, look for these things at each bench and workstation:
- Workarounds — any place where people have developed their own method because the standard process does not work. Handwritten labels, unofficial tracking sheets, verbal agreements about case priority.
- Equipment and materials — is everything needed for the step available, in the right place, at the right time? Watch for searching for reagents, waiting for instruments to become free, using backup equipment because the primary is down.
- Layout and motion — how far do scientists walk between the microtome and the water bath, between cut-up and the specimen fridge, between the microscope and the nearest printer? Draw a spaghetti diagram if the motion is significant.
- Information flow — how does the scientist know what to do next? Is the LIMS worklist clear? Are request forms complete? Watch for phone calls chasing missing clinical details, manual lookups to find previous results, and delays caused by unclear or incomplete requests.
- Interruptions — how often is the person pulled away from the task? Urgent add-ons, phone queries, equipment alarms. Interruptions destroy flow and increase error risk.
- Variation between people — observe the same step performed by different scientists. Do they embed in the same orientation? Do they cut at the same speed? The differences tell you whether a standard exists and whether it is followed.
A Worked Example: Breast Core Biopsy with IHC
Consider mapping the pathway for a breast core biopsy. The main value stream runs from specimen receipt through grossing, processing, embedding, microtomy, H&E staining, and initial reporting. But if the pathologist identifies invasive carcinoma on the H&E, the case needs immunohistochemistry for oestrogen receptor (ER), progesterone receptor (PR), and HER2 status before the report can be finalised and the case discussed at the breast MDT.
This IHC work is a parallel path. It departs the main stream at the point where the pathologist requests additional stains (typically after initial microscopy) and returns when the IHC slides are ready for the pathologist to review alongside the H&E. The main stream waits — the report cannot be authorised without the receptor status. In Gemba-VSM, you would record this as a parallel path with the departure step at “Initial Reporting / Microscopy” and the return step at “Final Reporting.”
If the IHC process is complex enough to warrant its own map — with its own cut-up for controls, section cutting, antigen retrieval, staining runs, and quality assessment — create it as a full VSM child project. If you simply want to record that IHC takes two working days, use a quick label with the lead time entered manually. Either way, the parallel path is now visible on the map and its lead time is reflected in the timeline.
When you walk this pathway at the gemba, you will discover the facts that no LIMS report contains: whether the IHC request is raised electronically or verbally, how long the cut sections wait before staining begins, whether the staining run is batched with other cases or run on demand, how the results are communicated back to the reporting pathologist, and where the real delays hide within what the system records as a single “IHC” step.
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 scientists feel they are being assessed, 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 team to correct you when you have misunderstood something, because you will.
The best value stream maps are created with the laboratory team, not about them. When the people who do the work contribute to the map, they see the waste for themselves. They understand why turnaround times are what they are. They generate the improvement ideas. This is the foundation of sustainable change — the people who own the process own the improvement.
Your first gemba walk is never your last. Expect to return multiple times, at different times of day, with different workloads, observing different staff. A single observation is a snapshot. The truth emerges over repeated visits.
If you are unsure whether to record something, record it. You can always discard an observation later. You cannot go back and re-observe a moment that has passed.
Installing Gemba-VSM on Your Device
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.
Install on Android
- Open Chrome. Navigate to the Gemba-VSM URL in Chrome on your Android phone.
- Install the app. You will see an install banner at the bottom. Tap Install. If no banner appears, tap the three-dot menu (⋮) and select “Install app” or “Add to Home screen”.
- Launch. The Gemba-VSM icon will appear on your home screen. It opens full-screen with no browser chrome.
Install on iPhone / iPad
- Open Safari. This only works in Safari, not Chrome on iOS. Navigate to the Gemba-VSM URL.
- Add to Home Screen. Tap the Share button (square with arrow), scroll down and tap “Add to Home Screen”, then tap Add.
- Launch. The app icon appears on your home screen and launches full-screen.
| OFFLINE USE |
|---|
| After installing, the app works offline. Load it once with internet access to cache the files, then use it at the gemba even without signal. Always export your data as JSON after a gemba walk — browser storage can be cleared if the phone runs low on space. |
Using Gemba-VSM to Map Your Laboratory Process
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 laboratory process.
Gemba Capture Tab
This is where you enter all your data. It has two sections:
Value Stream Information
Fill this in once for each map. Enter the name of the value stream (e.g. “Histopathology Biopsy Pathway”), the specimen type, who mapped it, the date, supplier (specimen source), customer (requesting clinician/MDT), specimen demand per day, and available working time per day in seconds.
IT Systems Registry
Register the IT systems used across your laboratory (e.g. LIMS, EPR, Order Comms, PACS, digital pathology platform). Quick-add buttons are provided for common healthcare systems. Registered systems appear as checkboxes when you select “Electronic” information flow for a step.
Add Process Step
For each step in the specimen pathway, capture the data using the fields described in the data table below. Key fields include process step name, cycle time (timed at the bench), batch size, defect/error rate, WIP/inventory count, delay before step, information flow type, DOWNTIME wastes observed, and gemba notes and photos.
After entering each step, click “+ Add Step”. The form clears ready for the next step. The stats bar at the bottom updates automatically as you add steps.
Process Steps Tab
This tab shows all your current state process steps in a list. You can drag and drop to reorder steps, edit any step using the pencil button, or delete a step. Each step displays its cycle time, batch size, defect rate, WIP, delay, waste badges, information flow badges, IT system badges, kaizen burst flags, and variation badges.
Current State Map Tab
This tab renders your data as a professional SVG value stream map showing process boxes, data boxes, inventory triangles, push/pull/FIFO connectors, information flow rails, kaizen bursts, parallel path boxes below the timeline, and the sawtooth timeline with summary metrics.
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 modify the future state to reflect improvements.
Compare Tab
This tab shows current and future state maps side by side for comparison.
Parallel Paths — Mapping Concurrent Processes
In many value streams, work does not follow a single linear path. At certain steps, an item 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.
In the pathology laboratory, parallel paths are extremely common:
- Immunohistochemistry (IHC) — additional stains requested after initial H&E reporting, results needed before final authorisation
- Special stains — PAS, reticulin, or other histochemical stains requested to support diagnosis
- Molecular testing — specimens sent for FISH, PCR, or NGS with results returning days or weeks later
- Send-away referrals — cases referred to specialist centres for expert opinion
- Decalcification — bone specimens requiring acid treatment before processing can continue
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
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.
Full VSM (Child Project) — a new, linked VSM project is created automatically. You map the parallel path as a complete value stream in its own right. Use this when the parallel process is complex enough to warrant its own map, such as a full IHC workflow.
Creating a Parallel Path
Click the “Add Parallel Path” button in the map toolbar. A modal opens where you enter the label, select departure and return steps, indicate whether the main stream waits, and choose quick label or full VSM.
How Parallel Paths Appear on the Map
Each parallel path renders as a labelled box below the timeline, positioned between the departure and return steps, connected by dashed arrows. Multiple parallel paths stack vertically.
Wait Time and Its Effect on Metrics
If the main stream waits for the parallel path, its lead time is added to the delay between departure and return steps, affecting total lead time and process efficiency calculations.
Navigating Between Parent and Child Projects
From the parent, click the parallel path box to navigate to the child project. From the child, a back-link in the project bar returns you to the parent.
Start with a quick label to capture the parallel path’s existence and estimated lead time during your gemba walk. You can always upgrade it to a full VSM child project later when you are ready to map the parallel process in detail.
Variation Capture — Cycle Time Observations & WIP Range
A single cycle time number is a snapshot. What you actually see at the gemba is a distribution — one scientist embeds in 2 minutes, another takes 5, the same person takes 3 minutes with simple cassettes and 8 minutes with complex specimens. The gap between those numbers is where the coaching conversation lives.
Cycle Time Observation Log
Below the cycle time field, a collapsible “Add observations” panel lets you record multiple timed observations, each with context (who, what time, what conditions). The app calculates min, max, mean, and range automatically.
Manual Range Fallback
If you did not capture individual observations but know the approximate range, expand “Or enter range manually” to enter min, typical, and max values with a note.
WIP Range
Below the WIP/Inventory field, record the minimum and maximum WIP observed with peak timing. “5 blocks at 8am, 80 at 2pm after the processor run” is dramatically more useful than “WIP: 40 (average).”
Where Variation Data Appears
- Step list — variation badges alongside each step
- SVG data box — C/T variation range in parentheses
- AI coaching export — individual observations for coaching
- CSV/Excel export — additional columns
- JSON export — full observation data preserved
You do not have to capture variation data — the panels start collapsed and add zero extra taps for a single value. But when you do capture variation, the coaching conversations become significantly richer.
AI Lean Sensei Coaching Export
Gemba-VSM can generate a structured coaching prompt from your data. Copy it into a free AI assistant (Microsoft Copilot, Claude, or Google Gemini) for guided gemba reality validation.
How It Works
Click the “AI Coach” button in the header. Choose a coaching tier (Sensei Prep for experienced coaches, Facilitator Coaching for team leaders), select your AI platform, optionally describe your work area context and attach a photo, then preview and copy the prompt.
The AI is instructed to coach, not solve. It will never suggest solutions — those must come from the people who do the work. It will never critique individuals — problems belong to the process, not people.
Saving, Exporting & Importing
Project Management
The dark project bar below the header lets you manage multiple value stream maps. Each project stores its own metadata, steps, and parallel paths independently. Data auto-saves as you work.
Browser storage can be cleared by your phone if storage runs low. Always export JSON after completing a gemba walk. The JSON file is your permanent backup.
JSON Export
Click “JSON” to download a complete backup containing all metadata, steps, variation data, parallel paths, and photos. Re-import on any device.
When to export: After every gemba walk. Before switching devices. Before clearing your browser. Before deleting any project.
CSV / Excel Export
Click “Excel” for a CSV file including metadata, summary statistics, full data table with variation columns, and parallel paths section.
SVG Export
Download the map as a scalable vector graphic for documents, presentations, or printing at any size.
Printing
Click “Print Map”. Set orientation to landscape and choose “fit to page”.
Importing
Click “Import” to load a JSON file. Creates a new project automatically — never overwrites existing data.
References & Further Reading
Further Reading
NHS Improvement Diagnostic Team. “Bringing Lean to Life — Making Processes Flow in Healthcare.” The VSM symbols and methodology used in Gemba-VSM are based on this resource.
Rother, M. & Shook, J. “Learning to See.” The definitive guide to value stream mapping from the Lean Enterprise Institute.
Womack, J. & Jones, D. “Lean Thinking.” The foundational text on lean principles.
Liker, J. “The Toyota Way.” Comprehensive overview of the Toyota Production System.
Clark, D. “Quality Improvement in Basic Histotechnology: The Lean Approach.” Virchows Archiv, 2015. Peer-reviewed paper documenting lean transformation in a histopathology laboratory: 45% reduction in turnaround time, 98% reduction in labelling errors.
Online Resources
Lean Enterprise Institute (LEI) — www.lean.org
Lean Enterprise Academy — www.leanuk.org
| Go See · Ask Why · Respect People Gemba-VSM was created to make value stream mapping accessible to teams at the gemba. The best map is one created by the people who do the work, based on what they observe with their own eyes. |
|---|
© 2024–2026 David Clark. Licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). These tools and guides are free for all healthcare improvement purposes. The NonCommercial restriction targets commercial resale, proprietary repackaging, and use as part of paid consultancy services. Full terms: gembasuite.org/licence
The map is a tool. The real work happens at the gemba, with the people who do the work.