The Uncharted Line on Value Stream Maps: A Five-Step Guide to Mapping Information Flow
1. Introduction: The Delivery Cycle Can’t Be Reduced Without Addressing the "Invisible Half of the Map"
When a certain electronics component factory was creating a value stream map (VSM), the team meticulously measured working hours and inventory levels on-site, detailing the material flow with precision: the cycle time for each process, changeover times, work-in-progress (WIP) quantities, and inventory days were all meticulously noted. However, the information flow area was only loosely represented with a few arrows, from "Customer" to "Planning Department" and then to "Workshop," which barely sufficed to explain the process. The team focused on material flow improvements: reducing changeover times, cutting inventory, and merging processes. After six months of effort, the delivery cycle only decreased from 12 days to 10 days and then plateaued.
Upon further investigation, it was discovered that the order from the customer first landed in the hands of the sales clerk, who then organized it into an Excel file and sent it to the planner. The planner waited until the end of the week to compile all orders before scheduling production. The production schedule was then printed and delivered to the workshop supervisor, who arranged production based on their own interpretation. From the time the customer placed the order to the actual start of production, the information took 3 days to travel, with actual processing time being less than 1 hour, and the rest was spent waiting and being passed around. The longest wait in the entire value stream was not in material handling but in information transmission.
This is a common issue with many companies' VSMs: the material flow is drawn in great detail, while the information flow is often glossed over. However, a VSM has two lines—material flow at the bottom and information flow at the top. The information flow is the command system for the material flow: a one-day delay in instructions means one more day of waiting for materials; a single miscommunication can lead to excess inventory. A VSM that only maps material flow is merely a half-finished map.
2. Three Common Mistakes in Information Flow Mapping
First, check if your VSM has these three common issues.
Mistake One: Drawing Only Arrows, Not Carriers. An "order" arrow is drawn from the customer to the planning department, but how is the order transmitted—via ERP, email, phone, or Excel? No one labels this. Different carriers have vastly different speeds: ERP direct connection is instantaneous, while email plus manual processing can take days.
Mistake Two: Drawing Only the Main Line, Not the Branches. Only the main line "Customer → Planning → Workshop" is drawn, while parallel information lines such as procurement, subcontracting, quality verification, and design changes are omitted. The result is a clean-looking map, but the actual information flow is three times more complex than what is shown.
Mistake Three: Marking Only Direction, Not Time. Each information line lacks the frequency and timing of transmission: how often does the planner schedule production? How frequently are reports updated? Is the information real-time triggered or batch-processed? Without time, the information flow is as good as not drawn.
These three mistakes share a common root: the person drawing the map treats the information flow as background decoration, assuming it doesn’t affect the calculations. In reality, the waiting time in the information flow must be marked on the time axis just like inventory days—it is a tangible part of the delivery cycle.
3. Five-Step Method: Making the Information Flow the Second Main Map
Step One: Trace a Complete Path from "Order to Instruction." Start from the customer order and follow it through: sales order entry → production scheduling → procurement order placement → workshop job assignment → quality release. At each step, note three things: who processes it, what tools are used, and how much time it takes. Don’t just ask from the office; spend half an hour at each position to observe the actual actions.
Step Two: Label the Information Carriers. Mark the transmission method on each information line: ERP direct connection, email, Excel file, paper document, verbal communication, kanban. Highlight any step that requires manual handling with a circle—manual handling is a high-risk area for delays and miscommunications.
Step Three: Mark the Information Lead Time on Each Line. How long does it take for information to travel from its origin to the next step? For example, if the planner schedules production every Friday, an order received at noon on Friday has a lead time of 5 days. Write the lead time for each step above the information line and add it to the time axis. You will find a significant portion of the delivery cycle that has never been accounted for, which is the information inventory.
Step Four: Differentiate Between Push and Pull Signals. Determine whether the information at each step is batch-processed or triggered on demand: batch-processed information is push, and it becomes increasingly outdated; on-demand triggered information is pull, and it is the freshest. The more push signals on the VSM, the thicker the information inventory.
Step Five: Reverse Verification. After completing the map, review it from the beginning: is there a corresponding information input line above each process? Any process without an information line is a blind flow—relying on experience, these processes are the least controllable in terms of quality and delivery time and should be prioritized for improvement.
4. Three Types of Waste in Information Flow and an Example
Once the information flow is mapped, the improvement points become clear. There are three main types of waste in information flow:
Information Delay—relying on people to wait and scheduling based on batch accumulation, resulting in outdated instructions by the time they reach the production floor; Information Distortion—the same data stored in Excel, ERP, and paper documents, leading to errors with each transfer; Information Overload—a pile of reports that no one reads, consuming valuable manual time.
Here is a simple example. In a certain injection molding factory, orders went through three layers of manual handling—sales clerk, planner, and workshop supervisor—each layer averaging a one-day wait. Production scheduling always lagged behind actual demand, and urgent orders were handled by phone calls. The improvement involved only one change: converting the three layers of manual handling into a shared order pool, where the planner triggers production in the workshop directly according to kanban rules, and urgent orders are automatically prioritized. As a result, the information lead time was reduced from 3 days to 2 hours, the delivery cycle decreased from 9 days to 6 days, and inventory turnover improved by nearly 20%. The entire process did not require any new equipment; it was all about optimizing how information flows.
5. Summary
A VSM has two lines: the material flow shows how materials move, and the information flow shows how instructions are transmitted. A VSM that fails to map the information flow is just a half-finished map; marking the information lead time on the time axis reveals the largest hidden waste in the delivery cycle.
Information flow is the command system of the value stream. A VSM that doesn’t map the information flow is just a half-finished map.
Knowledge code: 7.1.1
Version: v20260823
Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management professionals, helping companies continuously enhance their quality capabilities.