Using Swimlanes Effectively

Swimlanes are horizontal rows that divide your board. They create separate "tracks" that work can flow through.

Common uses:

• By priority/class of service: Expedite, Standard, Intangible
• By team or person: When multiple people share a board
• By project or epic: Grouping related work
• By customer: If you serve multiple clients
• By type: Features, bugs, support

The right choice depends on your context. What questions do you need the board to answer?

The most powerful use of swimlanes is for classes of service (more on this in the next lesson). But you can start simpler with priority bands.

Example structure:

+-------------+-------------+-------------+-------------+
| EXPEDITE    | Max 1 item - drops everything else    |
+-------------+-------------+-------------+-------------+
| STANDARD    | Normal flow - most work lives here    |
+-------------+-------------+-------------+-------------+
| LOW         | Fill-in work - when capacity allows   |
+-------------+-------------+-------------+-------------+

Rules might be:

• Expedite: Maximum 1 item at a time, must be actively worked
• Standard: Normal WIP limits apply
• Low: Only pull when nothing else is waiting

This visual structure makes priority impossible to ignore. The expedite item is literally at the top.

For small teams or individual boards, swimlanes by person can help visualize workload balance.

Pros:

• See who has too much work at a glance
• Individual WIP limits become natural
• Easy to know who's working on what

Cons:

• Can discourage collaboration ("that's in your lane")
• Doesn't work well for swarming
• May feel like surveillance

When it works:

• Support teams where individuals handle separate queues
• Agencies with per-person client assignments
• Early-stage teams building the habit of limiting WIP

When it doesn't:

• Teams that should be collaborating on shared work
• Cultures where it would feel like micromanagement
• Work that requires handoffs between people

When tracking multiple projects on one board, swimlanes can separate them visually.

Benefits:

• See all projects' progress at once
• Compare relative progress
• Identify projects that are stuck

Challenges:

• Board gets tall with many projects
• May hide that one project is hogging capacity
• Doesn't work well when items belong to multiple projects

Alternative: Use card tags or colors for projects, and reserve swimlanes for something else (like priority). There's only so much visual encoding a board can handle before it becomes noisy.