Start with the question your diagram should answer. A simple flowchart explains steps and decisions; a swimlane makes ownership visible. The related notations here help when choices, parallel work or changing states matter more than a single sequence.
Choose this for a small process with a yes/no decision. Its input-validation example keeps the successful and error paths visible, making it a useful starting point for a procedure or a short tutorial.
Studio · Free plan available · Sign-in required to edit
Choose this when a process crosses roles or teams. The Customer, Sales and Warehouse groups make hand-offs explicit; rename the lanes before adding more steps so responsibilities stay clear.
Studio · Free plan available · Sign-in required to edit
Choose this when alternatives have uncertain outcomes you want to compare. Decision and chance nodes carry different meanings; replace the illustrative product-launch probabilities and payoffs before interpreting the calculated results.
Studio · Free plan available · Sign-in required to edit
Choose this for an order-processing workflow with several decisions and exception paths. Review the stock and payment branches and where work rejoins; a line of boxes would hide the backorder and cancellation outcomes.
Studio · Free plan available · Sign-in required to edit
Choose this when one thing changes state in response to events, such as an order moving through payment and shipping. Label transitions with their triggers and guards; use a flowchart when you instead need the steps performed by several people.
Studio · Free plan available · Sign-in required to edit
Choose this for a small process with a yes/no decision. Its input-validation example keeps the successful and error paths visible, making it a useful starting point for a procedure or a short tutorial.
flowchart TD
A([Start]) --> B[/Read input/]
B --> C{Valid?}
C -- yes --> D[Process]
C -- no --> E[/Show error/]
D --> F[/Write output/]
F --> G([End])
E --> G
Editable source from the template. Open its detail page for the rendered preview.
Choose one level of detail
Keep a page focused on one process and one audience. Start with a few meaningful stages, then make a separate diagram for a complicated subprocess. Mixing a strategic stage with individual clicks makes both harder to follow.
Trace an exception as well as the happy path
Walk through the diagram with a real example. At each decision, ask whether every outcome is named and whether each branch has a destination. Confirm loops, stopping conditions and hand-offs before adjusting colour or spacing.
Make the example your own
Reading the public examples and source is free. Editing requires an account with access to the named workstation. Free includes the Studio with up to 3 saved figures and 3 cloud Library projects; dedicated workstations such as Weave and BPMN start on Starter.
Replace example labels, counts and policies before using a template for your work. Optional AI features and exports have their own plan and usage limits.