Swimlane process
Show who does what across functions during a timed procedure.
Related: Numbered process
When to use
Use when multiple owners act in one procedure. Do not use for a single-team loop (numbered process). Do not use for system fan-out without people.
Guidelines
Lanes are functions. Junctions are verbs. Title is the freeze/open rule.
Example
Wave 1 cutover hour
Ops freeze inbound; App drains the queue; Warehouse counts then opens.
Ops
Freeze inbound
App
Drain queue
Flip flag
Warehouse
Cycle count
Open outbound
Owners are lanes, not colors
Three lanes, verbs in cells. Steal owner-as-lane, not a RACI spreadsheet screenshot.
Rules
- Each lane has a function name, not a person-only name (unless that person is the function).
- Junctions are verbs.
- Time flows left to right inside lanes.
- Title states the coordination rule.
- No unlabeled arrows.
User recipe
Pick family: Cloud architecture first.
Insert objects:
- Text: title stating the coordination rule, kicker, source line
- Swimlane: one per function or owner
- Junction: verb actions inside each swimlane
- Connector: arrows showing handoffs between swimlanes
Assemble:
- Label each swimlane with a function name
- Place junction (verb phrase) actions inside appropriate swimlanes
- Time flows left to right
- Connectors show where steps hand off between functions
Anti-patterns
- A table labeled “RACI” with no flow.
- One lane with twelve boxes and two empty lanes.