What a process map is
A process map documents each step and decision point in a workflow. Mapping the process as it truly runs, rather than as the manual describes it, is usually where the improvement opportunities appear.
When to use one
- Documenting a current state before improving it
- Handing a process over to another team or a new hire
- Finding rework loops and redundant approvals
The data format
Branching: id, type, text, next1, next2 (decisions). Or simple: one step/line, ? prefix = decision.
Paste rows like this — copy the example straight into the builder to see it render:
n1, start, Receive order, n2 n2, process, Verify stock availability, n3 n3, decision, In stock?, n4, n5 n4, process, Pick and pack the items, n6 n5, process, Create backorder and notify customer, n6 n6, end, Ship order
How to make one
- Paste your data into the Studio, or upload a CSV or XLSX file.
- Set your colours — by hand, from pasted brand hex codes, or extracted from your logo.
- Generate and export as PNG or SVG for your deck or report.
One thing people get wrong. Map what actually happens, including the workarounds. A map of the official process finds nothing, because the official process is not where the waste lives.
Why it runs in your browser
Charts are parsed and drawn entirely on your own device. No rows, files or logos are uploaded, so a process map built from confidential project or process data never touches a server. You can verify it: open your browser's network tab while you generate one.