EditorialDiagram
Diagrams

Product & Planning

Editorial Swimlane Diagram Designer — No Shadows, No Mermaid Slop

Make ownership visible across Customer, Support, Warehouse and Finance. The eight-step return example distinguishes team activities from the handoffs that move the item toward inspection, refund and notification.

Explore the example for free
100%
Example preview
A returned item changes hands four times.Every activity belongs to one team. Handoffs cross lane boundaries without splitting ownership.A returned item changes hands four times.ILLUSTRATIVE SAMPLE / ENGINEERCUSTOMERSUPPORTWAREHOUSEFINANCEEvery activity belongs to one team. Handoffs cross lane boundaries without splitting ownership.Request returnCheck policyApprove returnPack itemReceive itemInspect itemIssue refundNotify
Checking geometry…

Take it with you

Free PNG includes an EditorialDiagram watermark.

Thin lines. Considered type. No shadows.

Layout Grammar & Anti-Patterns

Four rules for this diagram

  1. 01

    Give each actor or team a named lane and separate lanes with 1px hairlines. A lane with one activity is valid.

  2. 02

    Place each activity entirely inside its owner’s lane. Ownership belongs to the activity, not to the connector that crosses the boundary.

  3. 03

    Keep progress mostly left to right, reserving clear orthogonal corridors for cross-lane handoffs instead of repeated backtracking.

  4. 04

    Choose one consequential handoff or refund responsibility as the focal accent. Unequal activity counts are preferable to invented filler steps.

Three mistakes to avoid

  • Unlabelled lanes leave the reader guessing who performs each action.
  • A step spanning two lanes creates ambiguous accountability.
  • Forcing equal activity counts or snaking arrows back and forth hides the important handoff.

Engineer vs. Executive

The two renders use the same illustrative source. Executive mode groups detail deliberately; read the captions before using an overview for a technical review.

Engineer / source detail
A returned item changes hands four times.Every activity belongs to one team. Handoffs cross lane boundaries without splitting ownership.A returned item changes hands four times.ILLUSTRATIVE SAMPLE / ENGINEERCUSTOMERSUPPORTWAREHOUSEFINANCEEvery activity belongs to one team. Handoffs cross lane boundaries without splitting ownership.Request returnCheck policyApprove returnPack itemReceive itemInspect itemIssue refundNotify

Eight activities keep policy checks, packing, inspection, refund and notification in their owning lanes.

Executive / decision overview
A returned item changes hands four times.Four owned stages summarize the return. Engineer mode keeps each check, handoff and notification.A returned item changes hands four times.ILLUSTRATIVE SAMPLE / EXECUTIVECUSTOMERSUPPORTWAREHOUSEFINANCEFour owned stages summarize the return. Engineer mode keeps each check, handoff and notification.Request returnApproveInspect returnIssue refund

Four owned stages retain the cross-team return story without the operational substeps.

Questions about this diagram

How should a step owned by both Support and Finance be drawn?

Choose the team accountable for performing the action and place the rectangle in that lane. If there are genuinely two separate actions, split the step and connect them as a handoff. A rectangle across the lane boundary would make ownership ambiguous.

Why does Finance have only one step in the return example?

Finance owns Issue refund, while other teams own policy checks, packing, receipt, inspection and notification. Lanes do not need equal step counts. Adding filler activities for visual symmetry would misrepresent the process and distract from the refund handoff.

What does the four-stage Executive view omit?

It groups the return into Request, Approve, Inspect return and Issue refund, with one owned stage per lane. Detailed policy checks, packing, warehouse receipt and customer notification remain in the eight-step Engineer view. Use that full view when reviewing operational responsibilities.

Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.

Cached examples are free. Starter Pack is $9.9 once; Pro Pass is $8.9 per month. Every generation costs 10 credits, including one automatic geometry repair. Pricing