Simulating a process in Visio: why it does not work — and what to do instead
Visio, Lucidchart, draw.io and Miro are drawing tools without an engine: they have no concept of volume, capacity or queue, and a box labelled “Review, 10 min” is just text in a rectangle to them. Simulation is therefore not possible, not even indirectly. If you need defensible numbers you have three routes: calculate utilisation per step by hand, export the diagram into a simulation tool, or model directly in a tool that computes.
Search for “simulate a process in Visio” and you get plenty of results but no solution. The reason is simple: it does not work. But the search is legitimate — it just describes a different problem than it appears to.
Why drawing tools cannot compute
Visio, Lucidchart, draw.io, Miro and Whimsical produce a picture. That picture contains shapes, connectors and text. What it does not contain:
- Time. A box does not know it takes ten minutes. The text “10 min” is a string like any other.
- Volume. There is no concept of 120 cases flowing through per day.
- Capacity. Nobody is assigned to the step, and if they are, only as a label.
- A queue. And that is the decisive point: without a capacity limit nothing can pile up — and without a pile-up there is no lead time, only a sum.
Visio Professional has validation rules that check whether a diagram is structurally sound (dead ends, unconnected shapes, BPMN conformance). That is useful, but it is a spell-checker, not arithmetic.
Third-party add-ons change little: they export the diagram into another tool, which then computes. That is a sensible route — but it is not Visio simulating.
What you are actually looking for
Behind this search there is almost always one of four questions:
- “Where does my process break?” — you want to find the constraint.
- “How long does this really take?” — you want lead time, not the sum of processing times.
- “What does this change achieve?” — you have to justify an investment.
- “Will our capacity hold next year?” — you are planning headcount against volume growth.
None of these needs a prettier diagram. All four need numbers.
Route 1: calculate by hand (costs one morning)
For questions 1 and 4, hand calculation is enough — and more honest than any half-fed model.
Per step you need three inputs: volume per day, processing duration, available working time.
Utilisation ρ = (volume × duration) ÷ available working time
The step with the highest value is your constraint. Anything above 85 % is an alarm — not just 100 %, because waiting time grows with the factor ρ/(1−ρ) and explodes near the limit. The full method with a table is in How to calculate a bottleneck.
Cross-check with Little's Law: count the waiting cases in front of each step and divide by daily throughput. That gives you actual lead time — usually a multiple of what the diagram suggests.
Limit of this route: it does not answer question 3. As soon as you want to know what a change achieves, hand calculation fails — because it cannot see that the constraint migrates to another step once you relieve it.
Route 2: export the diagram
If you already maintain a clean BPMN diagram, it can be carried into a tool with an engine. The BPSim standard exists precisely for this: it attaches simulation parameters to a BPMN model without changing the notation.
In practice you still enter arrival rates, distributions, capacities and calendars from scratch. The diagram saves you the structure, not the data — and the data is the work. More on that in BPMN with simulation.
Worth it if: you maintain BPMN anyway and the model is large. Not worth it if: your process has five to ten steps. Remodelling is then faster than any export.
Route 3: model in a tool that computes
For questions 2, 3 and 4 there is no way around it. Which kind of tool is right depends on purpose — the four categories and their limits are in Process simulation software compared.
The short version:
| Your goal | Right category |
|---|---|
| Document the process, training, audit | stay with Visio |
| Design a production line, warehouse, clinic | simulation lab (Arena, Simul8, AnyLogic) |
| Govern and approve 300 processes | BPM suite (Signavio, ARIS, Bizagi) |
| Justify an investment in one process | decision instrument (FlowVisual) |
The mistake that gets expensive
The most common detour is a halfway house: entering numbers into the diagram — “10 min”, “74 % utilisation”, “3 days” — and then treating the result as if it were a calculation.
That is worse than no numbers at all. A diagram with numbers looks like somebody did the maths. In a steering committee nobody will ask where the 74 % came from — until the project runs and the numbers fail to appear.
If you carry numbers in a diagram, write down where they come from and what they do not mean. “Processing time, estimated, excluding waiting” is an honest label. “74 %” on its own is a claim.
Practical recommendation
- Keep Visio for what it does well. For documentation, training and audits there is little better.
- Calculate utilisation per step by hand. One morning, and you know your constraint.
- Only once you have to justify a change do you need a tool with an engine — and then one that reports ranges rather than a single number.
FlowVisual is built for step 3: assemble the process from building blocks in minutes, run it under load, get before/after in money with a P10–P90 band. It does not replace Visio — it answers the question Visio is not wrong about, merely not responsible for.
Frequently asked
Can Visio simulate processes?
No. Visio is a drawing tool without an engine: it has no concept of volume, capacity or queues. Visio Professional offers validation rules that check a diagram's structure — that is a spell-checker for diagrams, not a simulation.
Is there an add-in that lets Visio simulate?
There are tools that import Visio or BPMN diagrams and then compute themselves. The computing happens there, not in Visio. The structure carries over; the actual work — arrival rates, distributions, capacities, calendars — still has to be done.
Can Lucidchart or draw.io simulate processes?
No, for the same reason as Visio: both are drawing tools. They are excellent for shared understanding and documentation, but have no concept of time, capacity or queues.
What is the fastest route to a defensible number?
Calculate utilisation per step (volume × duration divided by available working time) and cross-check with Little's Law (waiting cases divided by daily throughput). That costs one morning, needs no software and reliably finds the constraint. For the effect of a change it is not enough — that needs a model that actually runs the process.
Run the numbers on your own process
FlowVisual turns the figures in this article into a model that runs — with your volumes, your capacities, your range.
- Comparison
BPMN with simulation: what the notation can compute — and what it cannot
“Our BPMN tool does simulation” means anything from a plausibility check to a full discrete-event engine, depending on the product. Five questions that tell the difference in ten minutes.
Read - Comparison
Process simulation software: four categories, four purposes
“Which tool should I buy?” is the wrong question. Software for business processes falls into four categories with four different purposes — and most bad purchases happen because someone bought from the wrong category.
Read - Use case
Invoice approval: why OCR does not halve your lead time
Invoice approval is the most automated administrative process — and the one where the promised savings most often fail to appear. A worked example model shows why.
Read