Swimlanes & Classes of Service

---

The Underlying Insight

Not all work is the same. Some items are routine; some are urgent; some have hard deadlines; some are technical investment without immediate visible value. Treating all work identically wastes the right kind of attention on the wrong items — overprotecting routine work, underprotecting urgent work, indefinitely deferring technical investment.

The remedy, developed by David Anderson, is Classes of Service: explicit categories that govern how each type of work flows through the system.¹ Swimlanes are the visual implementation — horizontal rows on the kanban board, each dedicated to one class.

The Four Standard Classes

Expedite

Genuinely urgent work that bypasses the normal queue. Production outages, security vulnerabilities, customer escalations. Limited to one item at a time (the WIP limit on the expedite lane). The team commits to dropping other work to address it.

Fixed-Date

Work tied to a specific date — regulatory deadlines, marketing launches, contract milestones. The class signals: this isn't urgent today but will be urgent if it isn't done by date X. Allows the team to sequence it appropriately rather than treating it as either routine or emergency.

Standard

Most work falls here. Normal priority, normal flow, no special treatment. The class is the default; it earns no extra attention but also receives no penalty.

Intangible

Work that produces no immediately visible customer value but matters: technical debt, refactoring, infrastructure improvements, learning investments. The class exists to prevent intangible work from being permanently crowded out by visible work.

What Each Class Actually Provides

The mere existence of a class isn't useful; the policies that govern it are. For each class, the team defines:

• Selection policy. When does a new item enter this class?
• WIP limit. How many items can be in this class at once?
• Service Level Expectation (SLE). What cycle time is expected for items in this class?
• Capacity allocation. What percentage of overall team capacity is reserved for this class?
• Cost-of-delay characteristics. How does the cost grow with time for this class?

Capacity Allocation

The most important policy: what percentage of capacity goes to each class? A common starting point:

• Expedite: reserve 10% (often unused, but available).
• Fixed-date: 20%.
• Standard: 60%.
• Intangible: 10%.

The specific percentages depend on the team's context. The point is to make the allocation explicit so that intangible work doesn't get crowded out and expedite work doesn't dominate.

Visual Implementation: Swimlanes

The kanban board is divided horizontally:

• Expedite lane at the top (visually prominent).
• Fixed-date lane.
• Standard lane (largest, default).
• Intangible lane.

The columns (To Do, In Progress, etc.) are the same across all lanes; the lanes differ in which class of work they carry. A glance at the board shows what's in each class.

Common Failure Modes

• Class inflation. Every item becomes "expedite" or "fixed-date." The signal value collapses. Stick to actual definitions.
• No policies. Classes exist on the board but no rules govern them. The labels are decorative.
• Intangible-lane neglect. Allocated capacity isn't actually used; intangible work piles up. The percentage must be enforced.
• Too many classes. Adding "Strategic Priority," "Customer A," "Customer B" classes turns the board into a directory. Stick to the four standard classes plus genuinely-distinct ones.
• Expedite as routine. If expedite is used weekly, the team isn't running expedite — it's running chaos. Address the root cause.

The Strategic Use

Classes of service are particularly powerful at the program level (multiple teams). Different teams may have very different class mixes — a platform team might be 90% intangible; a customer-facing team might be 70% standard plus 10% expedite. Explicit classes make these differences visible and discussable rather than hidden in aggregate metrics.

Coaching Tips

Define each class explicitly.

What qualifies as "expedite"? What counts as "fixed-date"? Without explicit definitions, classes drift into meaninglessness.

Set capacity allocation percentages.

Without explicit percentages, intangible work gets crowded out by visible work. The allocation is the protection.

Treat expedite as rare.

Weekly expedite items mean the system isn't being run. Address root causes rather than normalizing emergency.

Enforce intangible-lane usage.

If intangible work isn't actively pulled into the lane, the percentage becomes fictional. Make it real.

Limit class proliferation.

Four classes is usually enough. Six is a board hard to read. Twelve is no system at all.

Report cycle time by class.

Aggregate cycle time hides the differences. Per-class metrics show which class is healthy and which isn't.

Summary

Classes of service and swimlanes are the second most leveraged kanban discipline after WIP limits. By naming the different types of work and giving each its own policies, the team avoids the trap of treating all items identically. The framework makes urgent work genuinely urgent, protects technical investment from being permanently deferred, and gives stakeholders honest expectations about cycle time. The discipline is in the policies, not the lanes — without explicit policies, the lanes are decoration.

Back to Flow & Forecasting