Prioritizing when everything is urgent

Loud is not the same as expensive — sequence by what delay actually costs.

The idea

When every request feels urgent, the loudest one usually wins — which is rarely the right call. Two lenses help. The urgent/important quadrant is fast : it sorts the noise. Cost of delay is for sequencing: for each item, ask what it costs per week to leave undone. That number, divided by how long the work takes, tells you what to do first — and often reveals that the loud item was cheap to park.

The backlog. Six competing items. Set each one’s value and how fast that value decays each week, then sequence them. The counter tallies the total cost of delay for your order.

Tune the backlog

View

Total cost of delay: 0 points · cheapest possible 0

your order —

Set the sliders, then reorder the list — watch the cost of delay change.

How it works

Cost of delay is the money (or value) you lose for every week an item stays undone. Sequence to minimise the total across the whole backlog. When items are done one at a time, the order that minimises total cost of delay is by CD3 — cost of delay divided by duration, highest first. Short, high-cost work goes first; long or cheap work waits.

cost of delay (per week) = value  x  weekly decay
CD3                      = cost of delay / duration

total for an order = sum over items of  (cost/week) x (week it finishes)

item            /wk   dur   CD3
payment bug     36     1    36.0   -> first
security patch  20     1    20.0
exec dashboard   9     2     4.5   (loud, but cheap to park)
onboarding       5.6   3     1.9
pipeline         3.6   4     0.9
ui polish        1     2     0.5   -> last

by CD3 order  = 203.8 points     loudest-first = 234.8 points

When to use it

Reach for…	Because
The quadrant — when you need to triage a pile fast and drop the noise.	It's quick and coarse: good for "do / schedule / delegate / drop," not for fine ordering.
Cost of delay — when items compete for the same scarce time and order matters.	It prices urgency in real terms, so loud ≠ first. But it needs honest value and duration estimates.
Both together — quadrant to filter, CD3 to sequence what survives.	The trap item (urgent, low value) shows up in both: park it.

Watch out for

Confusing loud with expensive. The item with the most Slack pings may have the lowest cost of delay. Price it, don't feel it.
Ignoring duration. A high-value item that takes months can still wait behind a high-value item that takes a day. CD3 divides by duration for exactly this reason.
Everything in "do now." If the whole board is urgent-and-important, your thresholds are wrong — recalibrate so the quadrant discriminates.
Set-and-forget order. Decay changes: a compliance deadline gets closer, a promo window closes. Re-price as the clock moves.
False precision. Cost of delay is a decision aid, not an accounting truth. Use it to compare and sequence, not to bill.

Worked example

Interviewer: "Your sprint has a payment bug, a security patch due Friday, a VP asking daily for a dashboard, and an onboarding revamp. Everything's 'urgent.' How do you order it?"

Name the cost of delay for each. The payment bug loses revenue every hour and is quick — highest CD3, first. The security patch has a hard deadline and is small — second. The VP's dashboard is loud but low value and takes real effort; its cost to park a week is small, so it waits — and you say so plainly, with the number. The onboarding revamp is genuinely important but its value decays slowly, so it's scheduled, not now. That's the whole move: you replaced "who's shouting" with "what does a week of delay cost," and you can defend the order.

Check yourself

Two items both worth doing: A loses 40/week and takes 4 weeks; B loses 20/week and takes 1 week. Which goes first?