In Process Mapping The Following Indicates Waiting

Understanding Waiting Symbols in Process Maps

Process mapping is one of those things everyone says is essential and nobody actually does right. I spent about five years doing this with operations teams who wanted to fix bottlenecks, and the waiting symbol kept getting ignored, misused, or just plain wrong. Here is what it actually looks like and how to use it without making the map useless. There is no single universal symbol, which is the whole problem. Different methodologies use different notations. In standard flowcharting, waiting is typically represented by a triangle pointing downward or sometimes parallel horizontal lines like this: =. In value stream mapping, the standard is an inverted triangle placed between process steps, often with the duration written inside or below it. BPMN uses a queue symbol — a small rectangle with vertical lines or a dedicated waiting task annotation. APQC and Lean practitioners often use a circle with a "W" inside it. The triangle is the most common one you will encounter. It is small, unobtrusive, and sits between boxes on your map. The duration goes inside or right beneath it. A 3-day wait gets written as "3 days" inside the triangle. If you do not write the duration, the symbol is almost meaningless — it tells someone there is a pause but not how painful the pause is.

I ran into a specific issue with a manufacturing client where the waiting triangles were everywhere but the numbers were blank. Every step had a triangle. Their process map looked like a field of little mountains. When I asked why, they said "we know there are waits, we just don't know how long." That was the entire problem. Without the time data, the symbol is decorative, not analytical. The workaround I used was simple: I walked the floor and timed the waits myself for one week. I came back and populated every triangle with actual cycle times. The map went from a pretty diagram to a diagnostic tool that identified a single 47-hour wait between the finishing line and the packaging station — a wait that was invisible before because nobody had forced themselves to write down what they already suspected. Here is what most people miss about waiting symbols. They treat them as neutral markers. They are not. The presence, size, and placement of a waiting triangle is information in itself. If you see a wait that is longer than the processing time of the next step, you have a pacing problem, not a capacity problem. That changes which lever you pull. Most teams go straight to adding headcount when they see a long wait, which usually makes the situation worse by creating more work-in-process inventory. Another thing that trips people up: waiting and transportation are frequently confused on maps. Transportation is the D-shape or arrow symbol in value stream mapping. It means movement. Waiting is the triangle. Both add zero value. Both get lumped together as "non-value-added time" in analysis, but they require completely different fixes. Transportation gets reduced by rearranging layout. Waiting gets fixed by changing scheduling, batch sizes, or process balancing. If you cannot tell them apart on the map, you will try to solve a timing problem with a furniture-moving strategy.

The downside most people do not talk about is that process mapping only captures waiting if someone actually draws it. In many organizations, especially ones using digital workflow tools, the waiting happens in email queues, approval pipelines, and shared drives that do not show up on the map at all. I have seen maps that looked perfectly smooth with maybe two or three small triangles between steps, only to discover later that the actual cycle time was six times the mapped time because the waiting was happening in systems nobody had mapped. The workaround for that is to do a time-motion study alongside the mapping exercise, not instead of it. The map shows the logic. The stopwatch shows the reality. If you are starting from scratch and need a reference, the ASME standard symbols for process mapping include the delay/wait symbol. You can find the full symbol set on the Society of Manufacturing Engineers website or in the ANSI/ASME Y14.21 standard. For Lean value stream mapping specifically, the Toyota Production System handbook has the clearest breakdown of the triangle symbol and how to pair it with lead time and process time calculations. The practical takeaway is that the waiting symbol is only as good as the data inside it. Draw the triangle. Write the time. Check whether it is actually a transportation issue. Then decide if the fix is scheduling, batching, or layout — not just "more people." That last one is the most expensive mistake you can make on a process map.