Ask a busy team how they decide what to work on next and you’ll often hear the same quiet answer: whatever’s loudest. The client who emailed twice. The task someone Slacked about five minutes ago. The thing the boss walked over to mention. It feels responsive, but it’s really just letting volume set your priorities – and volume has nothing to do with importance. The result is a board where the genuinely urgent and the merely noisy get treated exactly the same, and the slow, important work quietly never happens.
There’s a simple fix that kanban practitioners have used for years, and it doesn’t require a priority meeting or a scoring spreadsheet. It’s called classes of service: a small, agreed-upon set of categories that decide how a piece of work is treated. Not how important it is on some abstract scale – how it flows. Which cards jump the queue, which ones get protected, and which ones simply take their turn. Let’s build a set you can actually use.
Why “everything is urgent” breaks a board
When every request is treated as top priority, priority stops existing. You get constant context-switching, half-finished cards piling up because the newest shiny task keeps interrupting the last one, and a team that feels frantic while somehow shipping less. The problem isn’t effort. It’s that the board has no way to say “this one truly can’t wait” that’s different from “this one came in most recently.”
Classes of service give you that language. Instead of a single, exhausting queue where the loudest voice wins, you sort work into a handful of types, each with its own simple handling rule. The card doesn’t need a long debate – its class already tells everyone how to treat it. This pairs naturally with the work-in-progress limits you may already use: classes decide what flows first, while WIP limits keep any one class from swamping the rest.
The four classes that cover almost everything
You don’t need a dozen categories. Most small teams are well served by four, borrowed from classic kanban and stated in plain language:
Expedite (drop-everything urgent). A true emergency – the site is down, a paying client is blocked, something is actively costing money. This work jumps the queue and may even interrupt work in progress. The catch, which we’ll come back to, is that it must be genuinely rare.
Fixed date. Work tied to a real, external deadline: a filing due the 15th, an event on Friday, a contract that lapses month-end. It isn’t urgent today, but it becomes an emergency if ignored – so it gets started early and watched closely.
Standard. The everyday majority of your work. It flows in order, first in and first out, at a normal pace. Most cards live here, and that’s exactly how it should be.
Intangible. Valuable work with no deadline and no immediate payoff – cleaning up a messy process, writing documentation, fixing the small annoyance that slows everyone down. It’s easy to postpone forever, which is precisely why it deserves a named slot.
Give each class a rule, not just a name
A class of service only helps if it changes behaviour, so each one needs a written handling rule your whole team can see. This is really just a specialised form of the explicit policies a healthy board already runs on. For example: Expedite – maximum one at a time; it goes to the front and we may pause a standard card to do it. Fixed date – pull it early enough to finish comfortably; never let it sit in the backlog past its safe-start date. Standard – first in, first out, no jumping. Intangible – reserve at least one slot of capacity a week so it never gets fully crowded out.
Write those rules down and keep them next to the board. The whole point is that when a new request arrives, you’re not negotiating from scratch – you’re just asking “which class is this?” and the handling follows automatically.
Protect the expedite lane like it’s precious – because it is
The expedite class is powerful and dangerous in equal measure. Used sparingly, it means real emergencies get the instant response they deserve. Used loosely, it becomes the lane everyone claims their work belongs in, and you’re right back to “everything is urgent” with extra steps. The single most important rule on your whole board might be the limit on this one lane: only one expedite card at a time, full stop.
A good gut check is to ask what actually happens if this waits until tomorrow. If the honest answer is “not much,” it isn’t an expedite – it’s a standard card with a loud sender. Keeping the bar high protects the meaning of the word. When a genuine expedite does appear, it’s often about clearing an obstacle fast, which is why it sits close to how you already handle blocked cards: both are about making the exceptional visible and getting it moving before it stalls everything else.
Show the classes on the board
Classes of service work best when you can see them at a glance rather than reading a tag on each card. The most common way is horizontal lanes – an express lane across the top for expedite, a fixed-date lane beneath it, then standard, then intangible – which is exactly what swimlanes are built for. A card’s vertical position instantly tells you how it’s being treated, no explanation needed.
If lanes feel like too much structure for your board, a simple colour or a small badge per class does the same job. A digital board can use a coloured label; a physical one can use different sticky-note colours. The mechanism matters less than the outcome: anyone glancing at the board should be able to tell, in a second, which work is jumping the queue and which is taking its turn.
Start small and let it earn its place
You don’t have to roll out all four classes on day one. In fact, the cleanest way to begin is with just two: standard for almost everything, and expedite for the rare true emergency. Live with that for a couple of weeks and you’ll quickly feel where it strains – maybe a recurring deadline that keeps sneaking up on you, which tells you it’s time to add a fixed-date class, or a backlog of improvement work that never moves, which is your cue for an intangible slot.
Add each class only when a real pain point asks for it, and you’ll end up with a system that fits your actual work instead of a borrowed template. Review the mix during your weekly board check: is the expedite lane staying rare? Is intangible work still getting its slot, or has it quietly been starved again? A class of service isn’t set in stone – it’s a small agreement you tune as you learn.
The quiet payoff
The best sign that classes of service are working is that the panic fades. Real emergencies get handled fast because there’s a clear lane for them. Deadlines stop turning into crises because fixed-date work gets started on time. The everyday majority flows steadily without being constantly shoved aside. And the important-but-invisible work – the cleanup, the documentation, the small fixes – finally gets its turn instead of living permanently at the bottom of someone’s mental list.
None of that requires a heavier process. It just requires deciding, once and out loud, how different kinds of work should be treated – and then letting the board carry that decision for you. Give your work two or three honest classes, write down how each one flows, and make them visible where the cards live. If your board is digital, a simple kanban tool with lanes or colour labels makes it a five-minute change – and the next time something lands with a loud “URGENT” attached, you’ll have a calm, honest way to ask the only question that matters: which lane does this really belong in?
Sources & further reading:
- What Is Kanban? An Overview of the Kanban Method
- 8 Popular Project Management Tools and What They’re Useful For – Coursera