VSM during early stages of Lean implementation

How many Value Stream Maps should be created at the start of Lean implementation?
We typically hear this question from...
1. Users who have recently learned the Value Stream Mapping tool
2. Organizations who are new to Lean implementation, just starting out on their lean journey

Start the Lean implementation with a few (say 2 to 3) value stream maps for processes that have the most non value adding activities (waste).

Why just 2 to 3?
Because of several reasons..
1. Creating Value Streams is a time consuming activity.
- Teams creating these maps have to walk the value stream and capture information
about material and information flows.
- Teams have to then create the current state map, identify waste and the Lean
tools they plan to use, create the future state map.

2. After creating the maps in the meeting room, now teams have to actually go and implement the Lean tools in the value stream. This is the most challenging part as this may take anywhere from a few days to few weeks. There are many aspects of the implementation like corporate culture, motivation level of people, management involvement, complexity of the process that could play a role.

3. Getting rid of all the waste in the process may require several cycles of going from the current to the future state. After all Lean is a journey of continuously removing waste.

How many value streams have you worked with? How many value streams did you start with when your organization was in early phases of Lean implementation?
Send us your questions or comments at info@Sybeq.com

Where to begin mapping Value Streams?

In the last post we talked about the different questions lean pratitioners have about implementing Value Stream Mapping.

The question of where to begin mapping value streams actually requires understanding the definition of value stream.
Lean practitioners need to have the ability to clearly identify and define a value stream.

A Value Stream is a stream of activities required to satify a customer need. The value stream starts with the customer who may be external or internal and ends where it is has a logical end. What this means is...
1. Start with the customer. First, define who is the customer and what do they need.
2. With this defined, start Walking the value stream backwards one step at a time.
3. Stop wherever it seems to be a logical stopping point.

While doing the above steps do not restrict the value stream by functions or departments. This is because a value stream may cross multiple departments. The ultimate goal of value Stream Mapping is to map how the stream works starting with the customer first and ends where it is a logical stopping point.

Do you face the challenge of where to begin mapping value streams? Tell us about your VSM implementation. Email: info@sybeq.com