Sub-Process Mapping: How to Map Feeding Processes Without Losing the Main Flow

Sub-processes are where the real constraint often lives. Here is how to map them without creating a map that nobody can read.

Why sub-processes matter

The main flow of a VSM is the path your primary product or service takes from start to finish. But that path depends on other processes feeding it. A sub-process makes a component, prepares materials, generates information, or delivers inputs that the main flow needs.

The constraint in many operations is not on the main flow at all. It is in a sub-process that the main flow assumes will always deliver on time. When the sub-process is late, the main flow stalls. But because the stall appears on the main flow, the team keeps trying to fix the main flow and never addresses the actual cause.

The lane structure

Sub-processes map as horizontal lanes above or below the main flow. The point where a sub-process feeds into the main flow is shown as a connection arrow at the relevant main flow step. Multiple sub-processes each get their own lane.

The same VSM notation applies to sub-process lanes: sticky notes, data strips, CT, wait time, WIP. The analysis metrics — PCE, lead time, takt comparison — also apply to each sub-process lane independently.

Scope rules for sub-processes

Map a sub-process when it has its own dedicated resources, when its output is only used by the main flow at a specific point, and when its timing has historically caused main flow delays. Do not map a shared service function as a sub-process unless its capacity is genuinely constraining your value stream.

The common mistake

The most common mistake is trying to map every sub-process in the first session. A first VSM with three or four sub-process lanes is usually too complex to complete in a single workshop. Map the main flow first. Then map the one or two sub-processes that are most likely to be constraining it. Add others in subsequent sessions once the main flow analysis is complete.

Nesting depth

Sub-processes can themselves have sub-processes. In complex operations, three levels of nesting are not unusual. The practical rule: map to the depth where the data answers the question you are trying to answer. If the question is why the main flow has long lead time, map to the level that reveals the answer. Stop there for now.