Value Stream Mapping Workshop Plan (facilitator guide)

Purpose and Outcomes

This facilitator guide helps teams run a focused 2-day Value Stream Mapping (VSM) workshop that results in a sequenced, measurable implementation plan. The goal is to surface real process waste, align stakeholders on a scoped value stream, design a future state that reduces lead time and improves quality, and create a Kaizen backlog and pilot plan with owners, deadlines, and measures.

Primary workshop outcomes

• A validated current state map with data-backed metrics.
• A practical future state map that targets clear wastes and bottlenecks.
• A prioritized implementation roadmap (Kaizen backlog) with owners and pilot plans.
• A measurement and governance plan for tracking progress.

Who should attend

Invite a cross-functional group that includes process owners, frontline operators, supervisors, engineering/maintenance, material handlers, quality, planning/scheduling, a customer or customer representative (internal/external), and a facilitator who will manage the workshop flow.

Pre-work (must complete before Day 1)

Good preparation makes the difference between actionable maps and wish lists. Send requests to stakeholders at least 7–10 business days before the workshop.

Data request template (send to data owners)

• Process list and approximate sequence (names and locations)
• Cycle time, setup/changeover time, and available work time for each process
• Shift patterns, breaks, and planned downtime
• Batch sizes and lot flow rules
• Inventory levels between processes (kanban or days on hand)
• Demand profile: customer orders per day/week/month and variation
• First-pass yield / defect rates and scrap reasons (by process if available)
• Current lead times (order to delivery) and known delays
• Key performance indicators currently tracked (OEE, OTIF, cycle time, etc.)
• Relevant SOPs, work instructions, layout or shop-floor photos

Customer / supplier alignment checklist

• Confirm the customer(s) served by the value stream and their critical needs (quality, delivery cadence, features).
• List primary upstream suppliers and hand-off expectations.
• Agree scope boundaries (start and end points for the VSM).
• Confirm who will sign off on the future state and the implementation roadmap.

Workshop materials (facilitator checklist)

• Large paper rolls or digital mapping tool, value-stream symbols, sticky notes, markers
• Printed data request responses and process photos/layouts
• Data-capture template printouts or tablets for entering values
• Action-plan and Kaizen backlog templates
• Timer, projector, whiteboards, tape for floor layout sketches

Agenda — Day 1: Current State

Suggested timeboxing and facilitator prompts. Adjust times to the complexity of the stream.

Opening and alignment (30–45 minutes)

• Welcome, introductions, scope review, and desired outcomes. Prompt: "If we succeed in two days, what difference will it make for our customers?"
• Ground rules: speak plainly, challenge processes not people, validate data on the floor, timebox discussions.

VSM basics & symbols (20 minutes)

Quick training on map elements (process boxes, inventory, timeline, information flow). Provide a one-page legend.

Process walk and data validation (90–120 minutes)

Teams walk the process or review photos/layouts. Confirm data requested earlier. Capture actual cycle times, changeovers, scrap rates, inventories.

Build the current state map (90–120 minutes)

Facilitate creation of the process boxes, material/inventory locations, timeline at bottom (process time, wait time, lead time). Use the Data Capture Template below for every process box.

Identify wastes and bottlenecks (60 minutes)

Use a simple 3-question test for each step: Does the customer see value? Can it be done at takt? Is there unnecessary movement or waiting? Capture ideas as candidate kaizens with estimated impact and difficulty.

End of day synthesis (30–45 minutes)

Agree on the most critical gaps to address in the future state. Prioritize 3–5 target opportunities to design against on Day 2.

Agenda — Day 2: Future State & Implementation Roadmap

Recap & set targets (30 minutes)

Review Day 1 findings, confirm metrics to improve (lead time, FTY, inventory days), and select design constraints (Takt time, batch size, staffing limits).

Brainstorm countermeasures (60–90 minutes)

For each prioritized problem, brainstorm lean responses (flow, pull, level scheduling, SMED, mistake-proofing, standard work, visual controls). Consider quick wins vs. capability projects.

Design the future state map (90–120 minutes)

Create a future state showing new material/information flow, target inventories, takt-aligned cycle times, and required changes. Explicitly document assumptions and enablers needed (equipment, training, IT changes).

Build the implementation roadmap (120 minutes)

For each improvement, capture: project title, problem addressed, owner, start date, target completion, required resources, measures of success, dependencies, and pilot plan. Populate the Kaizen backlog template.

Governance and measurement (45 minutes)

Agree on review cadence (daily huddles for pilots, weekly progress review, monthly steering check-ins), required dashboards, and a go/no-go criteria for pilots.

Final presentation and sign-off (30–45 minutes)

Present current/future maps and roadmap to stakeholders. Obtain commitment for owners, resources, and first review date.

Roles and Responsibilities

• Facilitator: Keeps schedule, manages conflict, ensures decisions and owners are recorded.
• Process Owner: Responsible for follow-through for assigned projects.
• Data Lead: Ensures requested metrics and evidence are available and accurate.
• Scribe/Map Keeper: Records maps, actions, and decisions in the canonical repository.
• Improvement Coach/SME: Advises on lean methods and pilot design.

Data capture templates (use for each process)

Kaizen Backlog / Action Plan template

Metrics to collect and track

• Lead time (order to delivery)
• Process cycle times and total value-add time
• Takt time and adherence
• Changeover times (SMED opportunities)
• Inventory between processes (days on hand)
• First Pass Yield / defect rates
• On-time in full (OTIF) to customer
• Project-level impact estimates (days saved, cost reduction)

Facilitation tips and common pitfalls

• Collect and validate data on the shop floor; don't accept assumptions without verification.
• Timebox discussion and use a parking lot for side issues.
• Avoid over-scoping. Keep the map focused on the agreed start/end points.
• Distinguish quick wins from capability-building projects and sequence them realistically.
• Make ownership explicit (name, not role) and get sign-off on first review dates before closing the workshop.

Post-work: turning maps into results

1. Within 48 hours, publish the canonical current and future maps and the Kaizen backlog.
2. Hold a short governance call to confirm owners, resources, and first pilot dates.
3. Begin pilots with clear success criteria and daily huddles to remove roadblocks.
4. Track metric changes weekly; update the roadmap based on pilot results and course-correct.
5. After initial pilots, scale successful changes and institutionalize standard work and visual controls.

Deliverables to produce during and after the workshop

• Completed current state map with validated data
• Future state map with assumptions and target metrics
• Kaizen backlog and prioritized implementation roadmap
• Pilot charters for first improvements
• Measurement plan and agreed review cadence

Quick reference: typical time allocation (2-day)

Day 1: 60–70% mapping and validation, 30–40% problem identification and prioritization. Day 2: 60–70% future design and roadmap development, 30–40% governance, sign-off, and presentation.

Use this facilitator guide to make the workshop practical, data-driven, and owner-focused. The value is realized after the workshop when owners run pilots, measure effects, and embed improvements into daily work.