Wait-Time Root Cause Mapping Workshop Guide

Purpose and outcomes

This workshop helps frontline teams quickly map patient flow, identify the systemic root causes of waits, and create measurable rapid tests to reduce delays. Outcomes you should expect by the end of the session:

• A visible flow map of the patient journey with clearly marked touchpoints, waits, and handoffs.
• Clustered causes for the top delays and at least one prioritized root-cause for each top delay.
• A short, owner-assigned PDSA plan for a rapid countermeasure with explicit measures and data sources.

Who should attend and roles

Invite a balanced mix of people who touch the pathway you will map. Typical attendees:

• Frontline staff (nurse, registration, medical assistant, technician)
• Clinician representative (physician, advanced practice provider)
• Data lead (someone who understands timestamps / EHR extracts)
• Manager or operations lead
• Facilitator (neutral, keeps time and process)

Assign these workshop roles up front:

• Facilitator — guide the flow and prompt inquiry.
• Scribe — captures the map in real time (digital photo + transcript).
• Timekeeper — enforces segment times and keeps the session tight.
• Data lead — answers questions about data and will own measurement after the workshop.
• Frontline champion — commits to trying the countermeasure and helping test it in practice.

Pre-work (critical)

Good pre-work focuses the group and avoids speculative causes. Provide a compact data pack 48–72 hours before the session with:

• Scope and sample: which clinic/shift/patient type and date range (e.g., last 30 clinic days).
• Arrival patterns by hour and day (volume heatmap).
• Cycle time extracts: registration, triage, rooming, provider start, provider end, discharge timestamps (median, 90th percentile, IQR).
• Throughput and capacity signals (rooms in use, staffing levels during sample).
• Examples of patient stories or recent complaints that illustrate the problem.

Ask attendees to bring any standard work, checklists, or local protocols related to the pathway.

Materials and room setup

• Room with wall space or large whiteboard
• Large sticky notes in several colors (one color per lane/type), markers, tape
• Flipchart paper, camera or phone to photograph outputs
• Printed data pack for each attendee
• Templates: flow map header, cause clustering grid, PDSA worksheet

90-minute workshop agenda (timeboxed)

1. Welcome & framing — 10 minutes

   Facilitator explains purpose, expected outcomes, scope (which patient group/pathway), and ground rules (focus on processes, not people). Quickly review the pre-work data highlights.

2. Rapid flow mapping — 25 minutes

   Use sticky notes to build a horizontal timeline or swimlanes for patient, staff, and system actions. For each step, capture:

   • Step name (e.g., registration)
   • Typical duration (touch time)
   • Observed wait (wait time) and variability where known
   • Handoffs and decision points

   Tip: Use one color for actions, another for waits. Place waits above the flow and quantify if numbers are known.

3. Identify and prioritise top delay points — 10 minutes

   Vote (dot-vote or quick show of hands) on the top 2–3 delays that most affect patients or throughput. Use criteria: frequency, patient harm or dissatisfaction, variation, and feasibility to act.

4. Cause clustering (affinity mapping) — 15 minutes

   For each prioritized delay, capture causes on individual sticky notes. Then cluster similar causes into 3–5 groups. Encourage system-level causes (policy, staffing, EHR triggers), not just people-level explanations.

5. Root cause digging: Five Whys — 15 minutes

   Pick the highest-priority cluster and use Five Whys (or a brief fishbone if preferred) to reach likely root causes. Stop when the team identifies a root cause that is actionable.

6. Countermeasure ideation & assignment — 10 minutes

   Rapidly brainstorm short tests (quick wins and larger experiments). For each proposed countermeasure, capture Who, What, Where, When, and a proposed measure.

7. Rapid PDSA plan & measurement definition — 5 minutes

   Document a single prioritized PDSA with owner, start date, duration (e.g., 2 weeks), baseline measure, target, data source, and balancing measures. Confirm immediate next steps and communication plan.

Facilitator prompts and sample questions

• "What is the exact handoff happening here? Who is responsible and what does that responsibility include?"
• "Where do patients most commonly wait, and what is our evidence for that?"
• "What variation do we see across different days or staff members?"
• "If this delay were eliminated, what would change for the patient and for the team?"

Measurement examples (choose practical, available measures)

• Median arrival-to-room time (minutes) — data source: registration and room timestamps
• Door-to-provider (median and 90th percentile)
• Length-of-stay for the visit (median)
• % of patients seen within target time (e.g., 30 minutes)
• Balancing measure: % of patients leaving without being seen, or staff overtime hours

Define baseline clearly and prefer median and 90th percentile over mean when waits are skewed.

Common pitfalls and tips

• Don’t stop at symptoms. If solutions only shuffle work downstream, the real bottleneck remains.
• Avoid long debates—capture dissent as hypotheses to test, not decisions to delay action.
• Keep at least one frontline team member who will test the PDSA in the next days; ownership drives change.
• Make measures as simple and automatic as possible—prefer EHR timestamps or short manual logs over complex surveys for initial tests.

Suggested immediate next steps after the workshop

1. Data lead establishes baseline and prepares a simple run chart for the PDSA owner.
2. Owner conducts the test and documents results in 1–2 weeks.
3. Reconvene for a 30–45 minute huddle to review run-chart evidence and either adopt, adapt, or abandon the change.
4. Communicate outcomes to the broader team and capture updated standard work if the change is adopted.

Templates and deliverables to include with this guide

• Pre-work data extract checklist (fields, sample period, anonymization notes)
• 90-minute agenda with timeboxes (ready to print)
• Flow-mapping flipchart template (swimlane layout)
• Cause-clustering grid and Five Whys worksheet
• PDSA worksheet with fields: Owner, Test, Start/End, Baseline, Target, Data Source, Balancing Measures

Why this matters

Structured, timeboxed workshops like this shift teams from opinion to evidence, produce measurable experiments, and reduce the chance of applying superficial fixes. The combination of pre-work data, frontline insight, and timeboxed PDSA testing creates momentum and builds a repeatable improvement cycle.