Seeing Past the Chaos
Clinical & Ward-Based Edition

This guide introduces value stream mapping (VSM) for clinical and ward-based teams. It walks you through using Gemba-VSM v6.3 to capture data on your ward or in your department, build professional current and future state maps of patient pathways, and export your work for printing, AI coaching, and further analysis.

Value stream mapping makes visible what patients experience but staff rarely see as a whole — the delays between steps, the handoffs between teams, the waits for beds, results, decisions, and transport that turn a 45-minute clinical interaction into a 6-hour stay.

Who is this guide for?

Nurses, ward managers, doctors, AHPs, healthcare assistants, and anyone involved in improving clinical pathways and ward-based processes. No prior lean experience is required.

What you will learn

• How to map a patient pathway from referral to discharge (or any clinical process)
• How to identify the 8 wastes on the ward using DOWNTIME
• How to walk the patient journey 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 diagnostic investigations running alongside clinical care
• How to measure cycle time variation across staff and shifts
• How to record patient flow patterns through the day
• How to use the AI Lean Sensei Coaching Export for guided reflection

What is a value stream in clinical work?

A value stream is the complete sequence of steps a patient experiences from the point of referral or arrival to the point of discharge or outcome. Every consultation, every test, every wait for a bed, every handoff between teams is part of the value stream.

In clinical work, the customer is the patient. Value is any activity that directly contributes to diagnosis, treatment, or recovery — any activity the patient would consider necessary and worthwhile. Everything else is waste.

Why VSM matters on the ward

Clinical pathways are deceptive. Individual interactions — the consultation, the procedure, the medication round — may each be efficient. But when you map the whole pathway from the patient’s perspective, you discover that the actual clinical contact time accounts for a small fraction of the total stay. The rest is waiting: waiting for a bed, waiting for results, waiting for a decision, waiting for transport, waiting for discharge paperwork.

A value stream map makes this visible. Process efficiencies of 5–15% are common in clinical pathways. This is not a criticism of clinical staff — it is a property of the system they work within.

Key VSM Concepts

Cycle Time (C/T) — The time it takes to complete one clinical interaction or task. Measured by direct observation, not from EPR timestamps.

Lead Time — The total elapsed time from when a patient enters the pathway to when they leave. Lead time = clinical contact time + all delays and waiting.

Takt Time — The rate at which patients need to be processed to meet demand. Available time per day ÷ patient arrivals per day.

Batch Size — The number of patients handled together. Ward rounds, medication rounds, and discharge batches all create delays.

Process Efficiency — The ratio of clinical contact time to total pathway time. The gap is the improvement opportunity.

Current State vs Future State

Always map the current state first — what actually happens today, based on walking the pathway yourself. Then design the future state with waste removed using ECSS: Eliminate, Combine, Simplify, Sequence.

Going to the Gemba

In clinical work, the gemba is the ward, the clinic, the department. Walk the patient journey yourself. Watch what actually happens between the clinical interactions. The waste lives in the transitions and the waits, not in the consultations.

Waste (muda) is any activity that does not add value from the patient’s perspective. The acronym DOWNTIME captures all eight wastes. Here is how they appear in clinical settings:

	Waste	Clinical Example
D	Defects	Drug errors requiring incident reports, incorrect patient identifiers, discharge summaries with missing information
O	Overproduction	Ordering investigations not clinically indicated, preparing discharge paperwork before the decision is made
W	Waiting	Patients waiting for beds, results, transport, decisions, reviews, medications, procedures
N	Non-utilized Talent	Registered nurses performing housekeeping tasks, doctors doing clerical work, HCAs not trained to perform observations they could do
T	Transportation	Patients moved between wards unnecessarily, specimens hand-carried to the laboratory, equipment borrowed from other areas
I	Inventory	Patients boarding in ED, patients medically fit for discharge still occupying beds, stockpiled supplies beyond par levels
M	Motion	Nurses walking to distant supply rooms, doctors searching for working computers, staff travelling between wards for handovers
E	Extra Processing	Duplicate documentation across systems, repeated patient identity checks beyond protocol, unnecessary escalation steps

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. A typical scope might run from patient arrival in ED to discharge from the assessment unit. Define the patient group: all patients, or a specific cohort such as medical admissions or elective surgical patients? Agree the scope with the team.

Step 2: Walk the Patient Journey

Go to the ward and walk the pathway from end to end. Follow the patient experience, not the staff. Observe what actually happens. Do not rely on policies, pathway documents, 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 step: triage, assessment, investigation, diagnosis, treatment, review, discharge planning, discharge. For each step, enter the data into Gemba-VSM v6.3: cycle time (timed by observation), number of staff involved, the trigger that starts each step. The tool stores each step and builds the process box and data box on the map automatically.

Step 4: Record Waits, Queues and Variation

Between each step, measure the waiting time. Count the patients queuing. Enter the patient count and delay for each step in Gemba-VSM v6.3 — the tool renders inventory triangles and delay segments on the timeline for you. If waits fluctuate through the day, record the range and peak timing.

Step 5: Map Information Flows

Document how clinical information moves. EPR entries, verbal handovers, paper forms, phone calls to chase results. Select the flow types for each step in Gemba-VSM v6.3, and the tool renders them on the map. Information flow problems are a major source of clinical delay.

Step 6: Identify Waste

At each step, identify the DOWNTIME wastes. 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 processes that run alongside the main patient pathway. Blood tests sent to the laboratory, imaging requested, specialist referrals awaited — each has its own lead time and may determine how long the patient 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 clinical contact times (value-added) and all delays (non-value-added) and calculates process efficiency. The sawtooth timeline at the bottom of the map shows this visually. The gap between contact time and lead time is your improvement opportunity.

Step 9: Design the Future State

Using ECSS (Eliminate, Combine, Simplify, Sequence), design a future state 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.

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 clinical 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 dashboard, in a report, or from the EPR. It tells you what the system recorded. Facts are what you see when you stand on the ward and watch the patient pathway unfold with your own eyes.

The two are not always the same. The EPR may record that a patient was “admitted at 09:15 and seen by the medical team at 10:30.” But when you stand on the ward and watch, you see that the patient arrived at 09:15, waited 20 minutes for a bed to be cleaned, spent 15 minutes having observations taken, then waited 40 minutes for the medical team because the registrar was called to another ward. The data says 75 minutes. The facts say 15 minutes of clinical activity and 60 minutes of waste with specific, observable causes.

This is why going to the gemba is non-negotiable. You cannot map a patient pathway from a performance dashboard. 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 nurse using a workaround — perhaps writing patient details on a piece of paper because the electronic system is too slow to access during a medication round, or phoning the laboratory to chase a result because the system does not alert when results are ready — it is natural to think “that’s wrong.” Resist that impulse.

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 waiting periods, look for these things at each step in the pathway:

• Workarounds — any place where staff have developed their own method because the standard process does not work. Handwritten lists, unofficial whiteboards, verbal agreements about priorities.
• Equipment and materials — is everything needed for the step available? Watch for searching for working equipment, waiting for monitors, fetching supplies from distant store rooms.
• Layout and motion — how far do staff walk during a shift? How many trips to the medication room, the supply cupboard, the nurses’ station? Draw a spaghetti diagram if the motion is significant.
• Information flow — how does the clinician know what to do next? Is the handover clear? Are results available when needed? Watch for phone calls chasing results, verbal handovers that lose critical details, and delays caused by incomplete or inaccessible information.
• Interruptions — how often is the clinician or nurse pulled away from the current task? Bleeps, phone calls, urgent requests from other patients. Interruptions destroy flow and increase error risk.
• Variation between shifts — observe the same pathway during day shift and night shift, during weekdays and weekends. The differences reveal where capacity, staffing, or support service availability creates variation in the patient experience.

A Worked Example: Medical Assessment with Diagnostic Investigations

Consider mapping the pathway for a medical patient admitted through the emergency department to a medical assessment unit (MAU). The main value stream runs from ED arrival through triage, clinical assessment, treatment initiation, senior review, and discharge or transfer decision. But at the point of clinical assessment, the doctor orders blood tests and a chest X-ray. Both of these are parallel paths.

The bloods are sent to the laboratory. The patient is moved to radiology for the X-ray. The main pathway — the medical decision about treatment and disposition — waits for both results to come back. In Gemba-VSM, you would record the bloods as a parallel path departing at “Clinical Assessment” and returning at “Senior Review,” and the imaging as a second parallel path with the same departure and return steps. Both have “main stream waits” enabled, because the senior review cannot happen without the results.

If you simply want to record that bloods take 90 minutes and imaging takes 2 hours, use quick labels. If the laboratory turnaround is complex enough to map in detail, create a full VSM child project for it. Either way, the parallel paths are now visible on the map and their lead times are reflected in the timeline, explaining why the patient waits 3 hours between assessment and review even though the clinical interactions take only minutes.

When you walk this pathway at the gemba, you will discover facts that no dashboard contains: whether the blood request is raised before or after the clinical assessment is complete, how long the porter takes to arrive for the radiology transfer, whether the results come back to the EPR automatically or require a phone call to chase, and where the real bottleneck lies in what the system records as “awaiting results.”

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 staff feel they are being assessed or monitored, they will behave differently, and you will record a pathway that does not reflect normal practice.

Be transparent about what you are doing and why. Explain that you are mapping the patient pathway, 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 clinical team, not about them. When the people who do the work contribute to the map, they see the waste for themselves. They generate the improvement ideas. This is the foundation of sustainable change.

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. 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

1. Open Chrome. Navigate to the Gemba-VSM URL in Chrome on your Android phone.
2. Install the app. You will see an install banner. Tap Install. If no banner appears, tap the three-dot menu (⋮) and select “Install app” or “Add to Home screen”.
3. Launch. The Gemba-VSM icon will appear on your home screen.

Install on iPhone / iPad

1. Open Safari. This only works in Safari, not Chrome on iOS.
2. Add to Home Screen. Tap the Share button, scroll down and tap “Add to Home Screen”, then tap Add.
3. 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, then use it on the ward even without signal. Always export your data as JSON — browser storage can be cleared if the phone runs low on space.

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. Create a new blank project when you are ready to map your own pathway.

Gemba Capture Tab

Enter your value stream information (pathway name, patient group, mapper, date, start/end points, demand). Register IT systems (EPR, PAS, etc.). Then add process steps with cycle times, delays, waste observations, and photos.

Process Steps Tab

View, reorder, edit, and delete steps. Each displays cycle time, delays, waste badges, variation data, and photos.

Current State Map Tab

Professional SVG map with process boxes, data boxes, inventory triangles, information flow rails, kaizen bursts, parallel path boxes below the timeline, and the sawtooth timeline with summary metrics. The toolbar provides Print, SVG download, and Add Parallel Path buttons.

Future State Map Tab

Copy Current → Future to duplicate your data, then modify to reflect improvements.

Compare Tab

Side-by-side current and future state maps.

In many patient pathways, processes run concurrently. At certain steps, a request or referral leaves the main pathway, undergoes a separate process, and the result returns later. The main pathway may wait for this.

In clinical settings, parallel paths are common:

• Blood tests sent to the laboratory with results returning hours later
• Imaging requests (X-ray, CT, MRI) with results awaited before clinical decisions
• Specialist referrals awaiting consultant opinion
• Pharmacy preparation of medications while nursing assessment continues
• Social care or therapy assessments running alongside medical treatment

Without parallel paths on the map, these concurrent processes are invisible. Making them visible explains why patients wait.

Two Ways to Record a Parallel Path

Quick Label — a named box with a manually entered lead time. Use when you know the process and its duration.

Full VSM (Child Project) — a linked VSM project for the parallel process. Use when it is complex enough to warrant its own map.

Creating a Parallel Path

Click “Add Parallel Path” in the map toolbar. Enter the label, select departure and return steps, indicate whether the main pathway waits, and choose quick label or full VSM.

Wait Time and Metrics

If the main pathway waits, the parallel path’s lead time is added to the delay on the timeline, affecting total lead time and process efficiency.

Navigating Between Projects

Click the parallel path box to open the child project. A back-link in the child returns you to the parent.

A single cycle time is a snapshot. What you see on the ward is variation — the same assessment takes 10 minutes with one doctor and 25 with another, 8 minutes on a quiet morning and 20 during the afternoon surge. The gap is where the coaching conversation lives.

Cycle Time Observation Log

Record multiple timed observations with context (who, what time, what conditions). The app calculates min, max, mean, and range automatically.

WIP Range

Record minimum and maximum patient counts with peak timing. “2 patients waiting at 8am, 14 at 4pm” tells you more than “average queue: 6.”

Generate a structured coaching prompt from your data. Copy it into Microsoft Copilot, Claude, or Google Gemini for guided gemba reality validation.

Project Management

Manage multiple maps from the project bar. Auto-saves as you work. Child projects from parallel paths appear in the same list.

JSON Export

Complete backup of metadata, steps, variation data, parallel paths, and photos. Re-import on any device.

CSV / Excel Export

Full data table with variation columns and parallel paths section.

SVG Export

Print-quality vector map for documents and presentations.

Printing

Landscape, fit to page.

Importing

Creates a new project automatically — never overwrites existing data.

Further Reading

NHS Improvement Diagnostic Team. “Bringing Lean to Life.” 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.

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