Guide
Turn steps, owners and named decision branches into a downloadable swimlane process map. Include feedback loops and clear end points.
Capture one real case first
Choose a specific trigger, such as a customer requesting a refund, and follow an actual case until a clear end. Name steps with a verb and an object: verify receipt, approve refund, notify customer. Assign the team that owns the action in the owner column. Keep policies and long explanations outside the map so the path stays readable.
Write decisions as explicit branches
A decision starts with a question mark and requires two named destinations. For example, review | Support | ?Eligible? | yes:refund,no:decline creates two visible paths. Use a final empty next column to end a path. When the next column is omitted, the flow continues to the following line. Explicit IDs let a rejected item return to an earlier step without duplicating it.
Review handoffs and failure paths
Walk the diagram with someone from every swimlane. Ask what starts their step, what information they need and how the next owner knows work is ready. Check both decision outcomes and every loop. An arrow does not enforce a deadline or assign an automation; record those responsibilities separately. Save the SVG with a revision date and repeat the review after the process changes.
How the result is made
A small text parser validates step IDs, owners and branch targets. Each owner becomes a vertical swimlane; input order determines vertical placement. Named decision links and feedback loops are drawn as SVG arrows. This is a visual documentation tool, not a BPMN validator, workflow runner or automatic process optimization system.