Value Stream Mapping Training


How to show

Multiple Scenarios
in a single Flowchart or Value Stream Map



Rule #1) Don't

Why bend the rule?

How to show Alternate Paths

How to show Different Numbers




Rule #1) Don't

Although it can be tempting to try to show multiple "things that sometimes happen"

the rule is: Don't

Why Not?

1) Avoid confusion

It's hard enough to keep your team focused on "doing a deep dive" into one specific condition,
without chasing rabbit trails of (ever-multiplying) alternative circumstances.

2) Avoid non-value-add time

Mapping teams consist of 5-10 high-paid high-demand team members.
Chasing rabbit trails is a waste of everyone's time.

3) You haven't lost much

Although your Current State Map might narrowly focus on one type of request from one type of customer
that might account for only perhaps 5-10% of demand served by this value stream or process

and yet the innovations and changes that you propose for your Future State will often benefit many other (somewhat similar) types of requests from similar customers. (perhaps applying to 50-80% of demand)

Narrowly define the scenario to map

Caution: This is where a lot of mapping teams go wrong

Your map should focus on one very narrowly defined scenario

even though the future state will almost always apply to a far broader range of scenarios.

Try It

If you personally don't have a lot of experience creating value stream or process maps...
then please just trust us on this one.

Define one VERY specific scenario, and focus all of your attention on just that one scenario.

Leadership Tips

Exceptions and Scenarios text box

Team members will often want to discuss exceptions to the narrowly-defined scenario that your team chose to analyze.

When that happens, simply jot those exceptions down in the 'Exceptions and Scenarios' text box

then gracefully steer the conversation back on track, with the assurance that the team WILL come back to those exceptions AFTER doing a thorough deep dive into your one chosen scenario.

As you dive deeper into your chosen Scenario,

continue to add conditions to your Scenario field (as they arise)...
to further clarify the conditions that define the one (and only) scenario
that your team is focused upon.

If you are leading a value stream mapping event,

then (if you didn't ignore the instructions for how to do value stream mapping),
you will have already used your Product Family Matrix template
to intelligently segregate your offerings into product families,

and remember, there should usually be one value stream map per product family.

Why bend the rule?

Current State Map

In our humble opinion...

Don't. Ever.

Future State Map

After your team has thoroughly exhausted improvements to the one narrowly defined offering...

and your team is now (months later) seeking to expand those learnings
to other somewhat dissimilar offerings in the same Product Family,

then a valid case might be made to depict and analyze multiple scenarios on a single map.


1) Avoid non-value-add time

re-creating (and maintaining) almost-identical process maps
that only have few minor differences

2) Easy mental comparison

the human mind is able to quickly notice differences
between multiple possibilities illustrated on a single flowchart

Value Stream Map

Never a decision diamond.
Percentage flows are popular, but almost never a good idea.
Paths and Scenarios can be very useful.

See the next section for explanations of each.

Cross Functional Flowchart

When used for Current and Future State process improvement,

it is almost always best to stay focused on one narrowly defined scenario

When used for Standard Work...

then it is very popular to use your functional flowchart as a decision tree, depicting different paths where "the thing being processed" might flow.

Examples: Rush order vs. Typical Order. Regular vs. Expedited.
Typical vs. Escalated Support Request...

How to show Alternate Paths

You might use any or all of the following...

Use your Exceptions text box

Rather than cluttering your flow chart or value stream map with too much complexity...
it is often a better idea to:

Exceptions and Scenarios text box
  1. Choose one clearly defined Scenario to observe and map
  2. Use your Exceptions text box to add a few brief notes regarding note-worthy exceptions
    that differ in some ways from the scenario that your team has chosen to study and map

Use a Decision Diamond

If you're making a flowchart

then the most popular way to illustrate divergent possible paths
is to use a Decision Diamond.

If you are just making a flowchart that doesn't attempt to calculate any math,
this is a real easy and practical way for the human mind to follow the alternate logic paths.

If you're using your Swim Lane Cross Functional Flowchart template

then you're going to need to supplement your visual Decision Diamond symbol
with a way to get the math right. (using 'Path Codes' described below)


There should be no data in any of the cells surrounding a Decision Diamond.

You might, however, use small transparent text boxes to clarify the path branches.

For example... Yes, or No
or 70%, 30%

Use Percentage Flows

If you're making a value stream map

then you really shouldn't use a decision diamond.

If there is a decision diamond on a value stream map,
most experts will cringe and dismiss you as "amateur".

vsm percentage flows

Some of those same experts, however,
will bend the rules

by assigning percentages of flow
to alternate flow paths on their value stream maps

(which technically serves the exact same purpose as a decision diamond... but just do it their way.)

If your sensei allows you to bend the rules by assigning percentages to alternate flow paths,

keeping in mind that about half of lean sensei's won't allow it at all... insisting that a value stream map should depict one and only one flow path. But if your sensei does allow it...

then you will need to get the math right.

(using 'Path Codes' described below)

Bookmark = FF

Path Codes in a Cross Functional Flowchart

Let's start with your Cross Functional Flowchart template (FunctionalFlow.xlsx)

(and then we'll look at how to use Path Codes for a value stream map)

On the same flowchart, you can use 'Path' codes to illustrate (and calculate) different paths
through which the thing being transformed might flow.

In the animated picture below, we illustrate two different scenarios:

  1. The Typical Path
  2. A Rush Order
Cross functional flowchart - animiated gif

Things to notice

Things to notice as you play with and learn to use Paths in your functional flowchart template

Look at the Path field in the upper right corner of your flowchart

If that Path field is blank, then all fields will simply calculate as expected.

In other words, it is okay to completely ignore and simply don't use Path codes.

If you have selected a Path code

If you have selected a Path code in that cell (in the upper right corner of your flowchart)


  1. The background color changes to highlight
    those Processes that are included within your currently-selected Path
  2. All of the Lean metrics are calculated based on only
    those Processes that are included within your currently-selected Path

How to change the Path code for your flowchart

Path code

In that Path code cell (in the upper right corner of your flowchart)

select a Path code

using the dropdown list of Path codes
that you defined on the DV sheet

then recalculate (CTRL+SHIFT+ALT+F9)

to get rid of the #N/A errors

How to include or exclude processes from a Path

In the cell just above and to the right of each Process box

there is a dropdown list where you can (optionally) select a Path code

(Optionally define your list of Path codes on your DV sheet)

If you have selected a Path code in the upper right corner of your flowchart, then...

Path code

To include a Process within the currently-selected Path,
the Path code for the process must

  1. match the currently-selected Path, or
  2. be blank

If you are using an older template (v15 R160800 or lower),
then the Path code has to match. Blanks are not included in the old version.

To exclude a Process from the currently-selected Path,

simply choose a Path code other than the currently-selected Path code.

In the newer version, the very first choice in the dropdown list is a black square symbol,
which makes a very visual way to indicate that a process is excluded for your currently-chosen Path.

If you imported old state comparison data

Import Old State Data

If you used the button to Import Old State Data,

(for side-by-side comparisons of lean metrics)

then if the currently selected Path code (in the upper right corner)
does not match the Path code for the Import Old State Comparison Data,
then the error-checking cell turns purple

thereby alerting you that if you want to view valid comparisons,
you would need to view comparison data for the same Path code

Bookmark = vsm

Path Codes in a Value Stream Map

As of February 2015, your Systems2win Value Stream Mapping template now allows you to use optional 'Path' codes.

Enter the Path code for each Process in the (unmarked) cell immediately above each Process Box.

value stream map path codes

If a process has a Path code,

value stream map path header

it will only be included in calculations
if it matches the Path code in the header

near the top of your value stream map >>>>>

If a process does not have a Path code,

it WILL be included in calculations.

Learning Experiment:

On the Sample sheet of your VSM template,
use the 'Hide/Show Row's button
to unhide Simultaneous Processes Tier 2

Baby awe

Path Codes... Wow

My programmer says
he wouldn't know how to do that

and I've already paid him
more than it would cost
for all 150+ Systems2win templates

and notice that each of those processes have a Path Code = S.


the math for those "S" processes will only calculate
if the Path Code in the value stream header is "S".

Learning Experiment:

Enter 'S' in Path Code cell in the value stream header, (cell H78?)

and then Recalculate (CTRL+SHIFT+ALT+F9)

and notice that the calculations become active
for any process that has Path Code = S

Delete or change the Path Code in the value stream header, (cell H78?)
and notice that the calculations become disabled
for any process that has Path Code = S

How to show Different Numbers

The Path might stay the same for all products in the Product Family depicted on your Value Stream Map,

but you might want to show different numbers for high, low, and average

or different numbers for each product within the Product Family

How do you do it?

Option 1) Don't

By far the most common practice is to enter data for (only) a single set of numbers,

Familiar Excel

usually the typical median or average

Remember, this is familiar Excel.
You can always open a temporary second copy of the document,
and then type in experimental numbers to do quick one-time analyses.

Use Comments

Rather than entering multiple sets of data, perhaps enter only the typical median or average,

and then use Comments to make note of the range of variability.

Comments might be entered using:

Use User-Defined Rows

Your Systems2win values stream mapping template allows you to easily copy 3 different types
of correctly-formatted rows for user-defined fields:

value stream map user fields - 3 types of rows
  1. Within a process
  2. Between a process
  3. Both Within and Between a Process

Learn how to easily copy rows of user-defined fields ANYWHERE in your template.

Tip: If you need to use the button to 'Unprotect' the sheet, just be sure to immediately re-protect, so that you don't accidentally mess up unprotected formulas.

How to use User-Defined Rows to show Different Numbers

Copy the (correctly formatted) row,

then paste as many new rows as you need
just beneath any data input row that might have variable data.

Notice that cells that can receive data input have a double border.
Don't accidentally overwrite formulas in cells that don't have a double border.

And then at any time, you can copy the data from any one of your user-defined rows

and paste it into the data input cells for the (original) row (that is referenced by Systems2win formulas)

user-defined rows


In this illustration >>>>>

just below the row for
'Process Time', there are 3 rows of user-defined data for:

  1. Typical Median Average
  2. High
  3. Low

The data input row for 'Process Time' is the ONLY row that is referenced by all calculations.

The 3 rows of User-Defined data are usually hidden, but can be unhidden at any time,

so that you can copy the data from any one of those rows,
and paste that data into the row for 'Process Time'

thereby changing all calculations to show what happens when 'Process Time' is 'High' or 'Low' or 'Average'.

In this same way, you can add (usually hidden) user-defined rows for ANY data input that might vary:

perhaps Lead Time, Distance Traveled, Cost, Steps...
ANY data input cells (that have a double border)

Use Excel Scenarios

After watching our short training video to learn how to use Excel Scenarios,

you will see how you can instantly switch between different sets of data
with a single click of your mouse

and you will soon grow to love this powerful feature
that is not available with any other value stream mapping software


Scenario field in header



Tip: Use the 'Scenario' field in the header
to let you readers know which Scenario they' re looking at


Excel Scenarios can be used with both your value stream mapping template,

and (even more popularly) with your Swim Lane Cross Functional Flowchart.

Combine Path codes and Scenarios

cartoon - home run

Use your Systems2win templates
to hit your next assignment
out of the park

Path codes are even more useful when combined with Excel Scenarios.

If 'Path' codes are included in the cells that get changed when you switch between the Scenarios that you define, then your bottom-line metrics will instantly change to reflect the totals for your currently-selected Scenario/Path, thereby making it extremely easy to illustrate multiple scenarios within a single swim lane flow chart or value stream map.

Using any combination of Path Codes and Scenarios,

you can depict and analyze multiple possible process flows on one flowchart or value stream map —

without wasting your time re-drawing an almost-identical map for each scenario.