SwimlaneCross-team processMedium

Order fulfilment swimlane

PlantUML swimlane that shows how an order moves from customer to order system to warehouse to logistics and back.

What this diagram shows

Step 01

Owner per column

Each lane owns the steps it is responsible for — Customer pays, Order System reserves stock, Warehouse picks, Logistics delivers.

Step 02

Handoffs are explicit

Every cross-lane arrow is a real responsibility transfer, not just a layout artifact.

Step 03

Loop back to closure

After delivery the flow returns to Order System to close the order and request a rating.

About swimlane diagrams

Swimlane diagrams split a process into vertical columns — one per team, system, or role — so handoffs between owners are visible at a glance. They are the natural fit for PRD user flows, approval chains, order fulfilment, and incident response runbooks where who-does-what matters as much as what-happens-next.

This template is written in PlantUML — plain text you can edit, version in git, and regenerate the image from any time.

View PlantUML sourcePlain-text diagram syntax — copy or edit directly.

diagram.mmd

1@startuml
2|#FFE4B5|Customer|
3start
4:Place order & pay;
5|#B0E0E6|Order System|
6:Reserve stock & create order;
7|#FFB6C1|Warehouse|
8:Pick & pack;
9|#90EE90|Logistics|
10:Pick up & deliver;
11|Customer|
12:Sign for delivery;
13|Order System|
14:Close order & request rating;
15stop
16@enduml

Related templates

More templates that cover similar workflows.

SWIMLANE

Atelier

Reimbursement approval swimlane

PlantUML swimlane covering a request for reimbursement that branches by amount, escalates to the department head, and returns to finance.

Cross-team processComplex11 nodes

SWIMLANE

Obsidian

Incident response swimlane

PlantUML swimlane runbook for an incident — monitoring fires, on-call diagnoses, SRE escalation, and customer comms close the loop.

Cross-team processComplex11 nodes