Classes of Service: Prioritize Work Beyond 'First In, First Out'

WHY IT EXISTS: Simple backlogs often treat all work as equal, leading to a 'first-in, first-out' (FIFO) mentality. But the business impact of delaying a critical bug fix is vastly different from delaying a minor feature. Classes of Service were created to manage these different risk profiles and optimize for overall value delivery, not just task completion speed.

THE MENTAL MODEL: Think of airport security lines. There's the regular line (Standard), the TSA PreCheck line for frequent flyers (Fixed Date/known travelers), and a diplomat or pilot line that goes straight to the front (Expedite). Each 'class of service' has different rules and expected wait times. CoS applies this same logic to your team's workflow, ensuring different types of work are handled according to their urgency and impact.

HOW IT WORKS: A team defines a few distinct classes, typically three to five. Each class has an explicit policy for how work is treated. For example, an 'Expedite' class might allow you to break the Work-in-Progress (WIP) limit and requires the team to swarm. A 'Standard' class follows all normal WIP and queuing rules. These classes are often visualized as swimlanes on a Kanban board, making the policies visible to everyone.

WHEN TO USE IT: Use CoS when your team's workflow is interrupted by different types of demand with varying urgency. It's essential for teams that handle both planned project work and unplanned operational work, like bug fixes or support escalations. It brings order to chaos by making prioritization policies explicit and visible.

WHEN NOT TO USE IT: If all your work is homogenous and has a similar cost of delay, CoS adds unnecessary complexity. A new startup team working on a single product from scratch might not need it initially. It's a tool for managing a complex, mixed flow of work, not for simple, sequential task lists.

ONE CANONICAL EXAMPLE: A common setup includes four classes. First, Expedite for critical, unforeseen work like a production outage; it bypasses queues and WIP limits. Second, Fixed Date for items with a hard deadline, like a regulatory feature; its priority increases as the deadline nears. Third, Standard for regular, planned features that form the bulk of the work. Fourth, Intangible for work with no specific cost of delay, like tech debt cleanup, which is pulled when capacity allows.