Raymond Lewallen

Sponsors

The Lounge

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
The purpose of value stream maps are not the value stream maps

Value stream mapping is an activity that stems from lean methodologies used to capture and report on processes from beginning to end.  Once the value map stream is complete, you have a visual representation of the process and its activities such as inventory pulls, kanban signals, “milk runs”, buffers, load leveling and value processes themselves.

Once a VSM is complete, is now becomes a communication artifact, and to a certain degree, obsolete.  Once you have the VSM, you now have the information you went in search of, and the VSM is nothing more than a representation of knowledge.

The identification of steps that create value and steps that create waste are the ultimate goals of production of the VSM.  The purpose of the map isn’t the map, but the learning processes.  Its the granular evaluation of specific processes within a process that produces the knowledge required to trigger kaizen events and make process improvements.

Once the knowledge is acquired and understood and a kaizen event triggered, future state maps can be produced to show where process improvements can be made – increasing (where applicable) and streamlining value adding processes, and removing wasteful activities.  The future state map shows a more desirable VSM which is used to produce an action plan that can be introduced into the process and improvements made.

I was in the process of putting together VSM templates for Excel, and a colleague of mine made a good point when I asked him for input.  Paper is portable.  Pencil can be erased.  The longer you sit and evaluate a process, the more you find yourself erasing and making changes.

That being noted, and taking into consideration what I said above, I’m not sure I see value in digital VSMs at all.  They are short lived (when acted upon) artifacts the don’t require the effort it takes to screw with a tool outside of standard pencil and paper.


Posted 12-05-2008 10:42 AM by Raymond Lewallen
Filed under: , ,

[Advertisement]

Comments

James Thigpen wrote re: The purpose of value stream maps are not the value stream maps
on 12-05-2008 1:11 PM

I think this lesson applies to things outside of this particular scenario as well. Us techy people typically have a great temptation to do everything on the computer when pen (or pencil) and paper can often equal or even surpass such an effort.

A friend of mine asked me for recommendations for software for taking notes, and I was a bit confused honestly, because I had never really considered replacing pen and paper with something I have to turn on, open, prepare and maintain.

load leveling | Digg hot tags wrote load leveling | Digg hot tags
on 12-06-2008 9:09 AM

Pingback from  load leveling | Digg hot tags

Dew Drop - Weekend Edition - December 6&7, 2008 | Alvin Ashcraft's Morning Dew wrote Dew Drop - Weekend Edition - December 6&7, 2008 | Alvin Ashcraft's Morning Dew
on 12-06-2008 9:26 PM

Pingback from  Dew Drop - Weekend Edition - December 6&7, 2008 | Alvin Ashcraft's Morning Dew

Steve Strong's Blog wrote Weekly digest of interesting stuff
on 12-10-2008 4:17 PM

Weekly digest of interesting stuff

Add a Comment

(required)  
(optional)
(required)  
Remember Me?