Value Stream Mapping Workshop Kit

Purpose

This workshop kit helps a cross-functional team map end-to-end material and information flow for a selected product family, expose hidden waste and delays, and convert findings into a short list of owner-backed experiments and a sustainment plan. Emphasis: pragmatic, measurable experiments that preserve system-level performance.

Desired outcomes

• A validated current-state value stream map with key metrics annotated.
• Three prioritized experiments (small, fast, measurable) ready to run within 30 days.
• An owner-assigned improvement roadmap with measures, cadence, and sustainment checks.

Quick orientation for facilitators

Keep the workshop evidence-first: confirm data at the point of work, engage frontline operators, and avoid designing solutions in isolation. The map is a hypothesis—treat it as a live artifact to be tested.

Pre-work (what to do before the workshop)

1. Select a product family (criteria: similar routing, common suppliers/customers, meaningful volume or strategic value).
2. Gather baseline data for the product family (use the Data Collection Checklist below). Aim to validate numbers on the floor before the workshop.
3. Invite a cross-functional team: frontline operators, supervisor, engineering/production planning, quality, maintenance, and a customer/sales touchpoint if practical.
4. Reserve a visible mapping space (whiteboard, floor+sticky notes, or a large printout) and provide basic materials: tape, sticky notes, markers, timer.
5. Assign roles: facilitator, timekeeper, scribe, data verifier, and owner for each experiment later.

Data Collection Checklist (minimum data to collect & validate)

Collect or estimate these before mapping; validate at the point during the workshop.

• Customer takt time (or target cadence)
• Cycle time for each process step
• Changeover time / setup frequency
• Batch sizes and lot quantities
• Uptime/availability (shift-level)
• Number of operators at each step
• Queue inventory / WIP between steps (count pieces/boxes/totes)
• Defect rates or scrap per step
• Lead time from order to delivery and order backlog
• Information handoffs: how are orders communicated (system, paper, verbal)?
• Common delays or rework causes (short notes from frontline)

Workshop agenda (example templates)

Choose the duration that fits your scope. Below are two practical options.

Half-day (4 hours) — Rapid scan

1. Welcome, purpose, expected outcomes (10 min)
2. Confirm product family and review pre-work numbers (20 min)
3. Walk the flow on the floor or visual area; collect missing data (40–60 min)
4. Build current-state map collaboratively (45 min)
5. Identify wastes and constraints; cluster opportunities (30 min)
6. Prioritize and select up to 3 rapid experiments (25 min)
7. Assign owners, measures, and due dates; create roadmap handoff (20 min)
8. Close and immediate next steps (10 min)

Full-day (7–8 hours) — Deeper analysis and planning

1. Intro and context (15 min)
2. Floor walk + data verification (90 min)
3. Construct current-state map (60–75 min)
4. Value-add time calculation and identify non-value steps (45 min)
5. Root-cause mini-sessions for top 2 problems (60 min)
6. Design running experiments, measures, and control gates (60 min)
7. Build owner-backed improvement roadmap and sustainment checklist (45 min)
8. Wrap-up, communication plan, and next meeting cadence (15 min)

How to map (practical steps)

1. Start from the customer and walk upstream to raw material—capture process boxes in order.
2. For each process box, note: cycle time, available time, uptime, operators, changeover, batch size, first-pass yield.
3. Between boxes, record WIP, transfer method, and average wait time.
4. Show information flows (orders, schedules, kanban, spreadsheets) and their frequency and accuracy.
5. Annotate where decisions, rework, or inspections occur.

Identify wastes and opportunities

Look for transport, waiting, excess inventory, motion, over-processing, defects, and underutilized people. Use evidence—numbers and observations—when marking waste. Cluster opportunities by impact vs. ease to run experiments.

Selecting experiments—criteria and examples

Prioritize experiments that are:

• Small and reversible
• Measurable within the experiment window (7–30 days)
• Led by a named owner with authority to act
• Designed to test a hypothesis about flow, not only to implement a solution

Typical experiments:

• Reduce batch size at one bottleneck for 2 shifts and measure lead time and throughput.
• Introduce single-minute exchange-of-die (SMED) steps for a specific changeover and track setup time.
• Pilot a visual kanban between two adjacent steps to limit WIP and measure queue reduction.
• Trial a simple standardized work sheet at one operator station for one product variant and measure first-pass yield change.

Rapid Improvement Roadmap (template)

Use this structure to capture experiments and follow-through. Keep entries short and measurable.

1. Experiment title — one line description
2. Owner — person accountable
3. Hypothesis — "If we..., then..."
4. Measure(s) — primary metric and baseline
5. Duration — start date and end date
6. Success criteria — what counts as a win
7. Checkpoints — daily/shift checks and a 30-day review

Example row (copyable):

Post-work: handoff & sustainment

1. Document the map and experiments in a shared location. Ensure owners have edit access.
2. Set a short cadence for reviews: a daily or shift check during the experiment, and a formal 30-day retrospective.
3. Define how changes will be standardized (update work instructions, training, and control charts if successful).
4. Assign a sustainment owner who will monitor metrics for at least one product cycle after changes are adopted.

Facilitator tips & common pitfalls (avoid these mal-hungers)

• Don't end with slides and no owners. Capture experiments with named owners and dates before the workshop closes.
• Avoid optimizing an isolated workstation—always test system-level impact (e.g., move WIP from one spot to another may hide the problem).
• Don't let mapping become blame-focused. Keep conversations about process and evidence, not people.
• Validate data on the floor. Estimates are okay for scoping but not for deciding experiments.
• Ensure frontline voices lead the details—process knowledge lives there.

Suggested artifacts to produce during the workshop

• Physical or digital current-state map with metrics annotated
• Short list of clustered wastes with evidence notes
• Three prioritized experiments with owners, measures, and timelines
• Rapid improvement roadmap document and a communication plan

Appendix: Quick mapping notation & symbols

• Process box: name + cycle time + uptime + operators + batch size
• Inventory triangle: WIP count
• Arrow with frequency: material transfer method & frequency
• Information arrow: order, schedule, or signal source with frequency

Next steps and options to make this kit interactive

This HTML kit is a complete facilitator guide. For teams using the platform, consider adding interactive forms to collect baseline data before the session, record experiment submissions during the workshop, and save checkpoint reports that automate reminders and build organizational memory.