|

Units of Measure
Because the purpose of a value stream is to transform the thing being processed...
it is not uncommon for a single value stream to have teams that work on components that have a unit of measure that is different from the end product or service that gets delivered to the ultimate customer.
Video: Units of Measure
For example
Your customer might purchase a "case" of soda, but your team is making "bottles".
Or your customer might purchase a "wedding event", but your team is making 30 "table settings".
If you are using overly-simplistic value stream mapping software, then everything in the entire value stream must use the same unit of measure.
For example, your team would need to change its thinking to something like "how many cases of bottles do we need to make today?" Or "how many weddings worth of table settings are needed?"
In other words
If you are using over-simplistic value stream mapping software, then it is not uncommon for some teams to simply glaze over as you try to get them to see how their process affects and is affected by your other inter-related upstream and downstream processes.
What if your value stream
mapping software was able to measure everything in the Bottling Department in the unit of measure of "bottles"?
And still ensure that all the math is correct for the bottom-line end-customer deliverable unit of measure of "cases"?
Welcome to Systems2win
where our mission is to develop process improvement tools that you won't outgrow.
|