Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Swimlanes & responsibility

Group flow steps into lanes so the diagram shows who owns each step, and every handoff between owners shows up as a line crossing lanes.

Whose move is it?

A tenant reports a leak on Monday. On Thursday the ceiling is still dripping, and the tenant, the property manager and the plumber each believe they are waiting for one of the others. The flowchart of the repair process is correct step by step: report the leak, book a plumber, fix it, confirm it is fixed. What it leaves out is who does each step, and so it cannot show the moments where the work changes hands, which is where this repair stalled.

Lanes add that missing piece. A Swimlane draws a band-ruled background (three lanes); name the lanes with Text shapes placed in each band and place each step in the lane of whoever owns it, so a handoff between roles is visible as a line crossing lanes. The Swimlane is in the Shapes palette, and the names go in Free Text shapes, one per band. The Swimlane's own label sits once, in its top-left corner, so it names the whole shape rather than any one lane.

A handoff across lanes

The boxes say what happens; the lines between lanes say where it can stall. Three lines cross from one lane to another, and each one is a handoff: the moment a step finishes for one owner and the next step sits in someone else's queue. That is why each crossing carries a label saying what is handed over. A reader who sees only "Book plumber" cannot tell whether the plumber got an address and a photo or a phone number to call. The last line passes through the manager's band without stopping there, and it raises a question the plain flowchart never did: who tells the manager the job is done?

Counting the crossings

Once the steps sit in lanes, the crossings can be counted, and the count is worth reading. Every crossing is a place where the work can wait until the next owner picks it up, and where something can be lost in transit. A flow that bounces between the same two lanes several times is often a sign that the handoff carries too little, so the second owner has to come back and ask, or that one owner should do both steps. When the lanes are services rather than people, each crossing is a handoff between services, usually a call or a message, and Microservices vs monolith covers what those boundaries cost.

What the Grid does with a lane, and what it leaves to you

On the Grid a Swimlane is a background shape, like a Frame: drawn behind the steps, never the end of a connection, and dragging it moves every node that sits fully inside it. It always draws three bands of equal height, so a fourth owner needs a second Swimlane placed under the first. It works on any Diagram Grid, but a Challenge Grid offers only its own palette, and shapes are not in it. A lane constrains nothing. The Grid does not record which lane a step belongs to; position is all there is, so an edge can go to any lane and a step can sit across a band line, belonging to nobody. Those are checked by eye. BPMN puts lanes inside a pool, one per participant such as a separate company, and draws what passes between pools as a message flow; the Grid draws lanes only, so a handoff to an outside party is a labelled edge like any other.

An expense with several owners and no lanes

The Expense Approval Workflow challenge changes owner at almost every step: an employee submits a report, automatic policy checks decide by amount, a manager approves the larger ones by hand, an unanswered request escalates to the next approver after a wait, and the employee sees the outcome. Its palette has no Swimlane, and a node type says what kind of step it is, not whose: Manual Input and Display can both be the employee's. So the owner goes in the title, as in "Manager: approve". Each edge that runs from one owner's node to another's is a crossing that would sit on a lane line, and it is the edge to label. The requirement that tests ownership hardest is the escalation: a manager who never answers is a handoff with nobody on the other end, and the flow needs a Delay and then, if the request is still pending, a handoff to the next approver.

Practice this