What is Value Stream Mapping?
What is Value Stream Mapping?
Value Stream Mapping is a set of exercises for visualizing and analyzing the flow of work through multiple processes from end to end, with the goal of identifying waste, delays, and bottlenecks so you can design more effective and efficient processes.
Why would you use Value Stream Mapping in your Technology teams?
- Onboard new customers faster to keep up with growing demand
- Catch quality problems during testing instead of in production
- Simplify processes to reduce back-and-forth communication
- Deliver software more often
- Reduce delays and re-work
- Waste less time
- Align teams on common goals and processes
We’ll go into how we aim to acheive this.
Here is an overview of each milestone in a Value Stream Mapping project:
- Outcome Mapping
- Current State Mapping
- Dependency Mapping
- Future State Mapping
- Improvement Roadmap
- Final Presentation
- Follow-up Period
Outcome Mapping
We work together to define improvement needs, goals, benefits, participants, obstacles, and next steps.
Depending on complexity and time, we might keep it simple with an Outcome Map, or use a Charter for a more iterative approach.
Learn more about Outcome Mapping.
Current State Mapping
Map the main processes required to deliver value to the customer, measure the work and wait time, and find the constraint slowing us down.
Note: Typically, teams are pretty good at improving their own processes and know where the bottlenecks are. It’s where there are dependencies with other teams that it becomes challenging to improve.
Learn more about Current State Mapping
Dependency Mapping
Identify dependencies and contributing factors for the constraint. Build a case for collaboration, why it benefits the customer and the company.
Learn more about Dependency Mapping
Future State Mapping
Identify sources of waste in the value stream and redesign it for reduced waste and improved flow.
Sources of Waste: Defects, Waiting, Handoffs, Non-Utilized Talent, etc.
Learn more about Future State Mapping
Improvement Roadmap
Sequence improvement actions into a roadmap based on importance and feasibility, with progress measures and owners.
Learn more about the Improvement Roadmap
Final Presentation
The team shares what they have learned with a wider stakeholder audience. This is a great opportunity to get buy-in for the upcoming improvements.
Follow-Up Period
After the workshop we measure progress against the metrics set by the team, discuss blockers and changes to the plan.
Logistics and Time Commitment
You can start by booking a 30 minute call with me and we can draw a quick outcome map and see if you’re interested in doing more.
The full workshop is 5 sessions of 1h30min + a final presentation and follow-up sessions if you wish.
A full workshop will take up roughly 8 hours of your team’s time over 2 weeks.
| Sessions | Duration | Date | Purpose |
|---|---|---|---|
| Outcome Mapping | 1 session of 1h30min + interviews | Week Before | Define improvement needs, goals, benefits, and next steps |
| Current State Value Stream Mapping | 1h30min | Monday | Find and measure key constraints |
| Dependency Mapping | 1h30min | Tuesday | Connect constraints to dependencies |
| Future State Value Stream Mapping | 1h30min | Wednesday | Design improved flow |
| Improvement Roadmap | 1h30min | Thursday | Create and plot clear next steps |
| Final Briefing | 30min | Friday | Share workshop findings, create buy-in |
| Follow-up | 30min every 2 weeks | Following 3 months | Measure progress, adjust, remove blockages |
Inspiration
This approach is heavily inspired by Karen Martin and Mike Osterling’s Value Stream Mapping book, and Steve Pereira and Andrew Davis’s Flow Engineering book.