Value Stream Mapping – Current-State Workshop Workbook

Welcome

This workbook helps a facilitator and team run a current-state Value Stream Mapping (VSM) workshop that produces a data-backed map, identifies real bottlenecks, and creates an action plan with owners and deadlines. Use the templates and data-collection guidance to avoid anecdote-driven maps that miss hidden delays.

Workshop Purpose & Outcomes

• Produce a verified current-state value stream map showing process boxes, information flow, inventory, lead time ladder, and basic metrics.
• Quantify takt time, cycle time, uptime, changeover, and WIP for each process step.
• Identify true constraints and non-value work (waste).
• Create a short list of Kaizen items with owners, deadlines, and follow-up commitments.

Who Should Attend

• Facilitator (leads workshop and timeline)
• Scribe/Mapper (draws map in real time)
• Process Owners and Operators (for each major step)
• Material/Inventory owner
• Customer or downstream representative (internal or external)
• Data recorder(s) for time & inventory studies
• Observer(s) for pull/trigger information flow

Pre‑work (recommended)

• Collect daily/weekly customer demand numbers and variability.
• Bring recent production schedules and any historical downtime logs.
• Prepare floor access; secure permissions for observations and timing.
• Print participant worksheets and ensure a whiteboard or large paper for mapping.

Suggested Agenda (half‑day to full‑day)

1. Welcome, objectives, scope, and timeline (15–30 min)
2. Review demand and takt time calculation (15 min)
3. Walk the process and confirm step boundaries (30–60 min)
4. Data collection: cycle time, uptime, changeover, inventory counts (60–120 min, possibly in parallel)
5. Build map on wall/board (30–60 min)
6. Identify bottlenecks, delays, and sources of waste (30–45 min)
7. Prioritize Kaizen items and capture action log with owners and deadlines (30–45 min)
8. Wrap-up and next steps (15–20 min)

Facilitator Checklist

• Confirm scope and start/end points for the value stream.
• Assign data recorders for each process step.
• Ensure timing devices, clipboards, cameras (optional), and sticky notes are available.
• Agree ground rules: observe facts, avoid premature solutions, use measurements to test assumptions.
• Plan for immediate capture of Kaizen actions and assign owners before ending workshop.

Data Collection Templates & Guidance

Takt Time

Formula: Takt = Available production time per period / Customer demand per period.

Example: If available time = 7.5 hours (27,000 seconds) and demand = 1,500 units/day, takt = 18 seconds/unit. Use the agreed period (shift/day/week) and exclude planned breaks.

Cycle Time (per process step)

How to measure: time at least 5 consecutive cycles (or more for variable processes), record each cycle, use the median or average after removing obvious outliers. Note whether the measured cycle is for a single piece or batch.

Uptime / Availability

Record planned time vs actual running time during observation period. Uptime = (Runtime) / (Planned production time). Capture common downtime reasons.

Changeover

Record observed changeover start and finish. Distinguish internal (machine stopped) vs external activities that can be prepared in parallel.

Inventory & WIP Counts

Count physical units or standard containers between process steps. Note location, storage conditions, and reasons for build-up (batching, takt mismatch, buffers).

Process Box Template

Lead Time Ladder

Capture the sequence of processing time and waiting time from order to delivery. The ladder helps show where most lead time is spent.

Action Log (post‑workshop)

Capture Kaizen items with clear owners and deadlines. Review ownership before ending the workshop.

Common Mistakes & How to Avoid Them

• Relying on memory or opinions instead of measured cycle times — do short time studies.
• Ignoring inventory counts — physically count WIP during the workshop.
• Mapping only visible shop-floor steps — include upstream information flow, suppliers, and downstream constraints.
• Not assigning owners — every improvement must have a named owner and a deadline.

Turning the Map into Action

1. Prioritize items that reduce lead time or remove critical constraints.
2. Run small experiments (PDCA) for proposed changes and measure impact on cycle time, uptime, and lead time.
3. Standardize successful changes into standard work and update visual controls.
4. Schedule a follow-up review (typically 2–6 weeks) to verify implemented changes and update the map.

Templates & Exports

Use the process box, cycle time table, lead time ladder, and action log as your workshop forms. Convert them to spreadsheets or interactive forms for ongoing data capture and tracking.

Quick Tips to Prevent the Mal‑Hunger of Local Optimization

• Keep the system boundary and overall lead time visible during prioritization.
• Ask "who else is affected?" for every proposed change.
• Prefer experiments that measure both local performance and downstream impact before broad rollout.

Appendix: Measurement Quick Reference

• Takt time: available time / demand
• Cycle time: observed time per unit at the process
• Uptime: runtime / planned runtime
• Lead time: sum of processing and waiting times

End of workbook. Use these templates as living documents — update them after each workshop and keep the action log current so the VSM produces measurable improvements.