Directory · P
Not sure this is the right entry? Run the check · New here? Start with the premise
Priorities
2 min read · 409 words
Demands always exceed capacity — that's structural, not a bad patch. So you're always prioritising. The only question is whether you're doing it deliberately or letting whatever makes the most noise decide.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Priorities are the operator’s ranking of what gets the limited resources first.
The hardware has finite bandwidth — finite time, finite energy, finite attention. Every operation consumes some of these. The total demands always exceed the total capacity. This is structural, not a temporary condition. There is no future state where the operator has bandwidth for everything. Priorities are the ranking that determines which demands are funded and which aren’t.
Most operators have implicit priorities, established by default rather than by design. The squeaky demand gets funded. The familiar demand gets funded. The demand someone else cared about gets funded. The actual most-important demands often go underfunded, because they don’t make noise, or because they require sustained attention rather than reactive response, or because they are about long-term outcomes the system doesn’t feel pressing today.
The cost of unconscious prioritization is large. The operator at the end of a year, looking back, finds that the things they would have said were most important got the least time, while peripheral demands consumed the bandwidth. This isn’t because they didn’t care. It is because the priorities running their schedule were not the priorities they would have chosen. The defaults were running, and the defaults had different priorities than the operator did.
From the chair: priorities have to be made explicit and applied as filters. Not aspirations. Filters. This is what gets the bandwidth this week. The operations that align with the priority get funded. The ones that don’t get declined, deferred, or done at lower investment. The decline is uncomfortable. It is also the entire mechanism by which priorities become real. Priorities that don’t produce decline of competing demands are not priorities. They are wishes.
The hard part: priorities require the operator to disappoint or refuse some demands that have legitimate claims. Not every reasonable request can be funded. The operator who tries to fund every reasonable request ends up funding the loudest ones at the cost of the most important ones. Saying no to the legitimate is the only way to say yes to the priority. This is not selfishness. It is the operating constraint of a system with finite bandwidth.
Set the priorities. Apply them. Notice what gets refused and accept the discomfort of refusing it. The alternative is the year of misallocated bandwidth that the operator can no longer recover.
Implicit ranking, set by noise
Time, energy and attention are finite, every operation consumes some, and total demand always exceeds total capacity. That's a permanent structural condition rather than a temporary squeeze — there's no future state where you have bandwidth for everything, which is why waiting for one is waiting indefinitely.
So prioritising isn't optional. You're doing it constantly. What varies is whether the ranking was designed or arrived by default.
The default ranking is set by noise. The demand that squeaks gets funded. The familiar one gets funded. The one someone else cared about gets funded. Meanwhile the genuinely important things go underfunded — because they don't make noise, because they need sustained attention rather than reactive response, or because they concern outcomes that don't feel pressing today.
Which explains the specific frustration of a busy year that produced nothing you cared about. Nothing went wrong, nobody made a bad decision, and the ranking was simply never made explicit — so it was made for you, continuously, by whoever was loudest.
Fund the top one first
Ranking on paper changes nothing. Allocating capacity before the noise arrives does.
Real questions
Why does the urgent always beat the important?
Because urgency is a signal and importance isn't — the urgent thing announces itself, has a deadline and usually has a person attached, while the important thing sits quietly and can be deferred indefinitely at no immediate cost. That asymmetry means the default ranking funds noise. Which is why the only reliable counter is allocating capacity to the important thing before the urgent arrives, rather than hoping to get to it.
How do I prioritise when everything is important?
By accepting that the constraint is real rather than a sign you've failed to organise properly. Demand always exceeds capacity, so something will be underfunded whether or not you choose which — the choice is only between deciding and defaulting. A list of seven priorities isn't a ranking; it's a refusal to make one, and it reliably resolves into funding whatever is loudest.
Why does nothing I care about get done?
Usually because it's being funded from what's left over, and nothing is ever left over. Things that need sustained attention lose every contest against things that need reactive response, because the reactive ones have deadlines and people attached. The fix is ordering rather than effort: the thing that matters gets capacity first, before the day starts making the decision for you.
Isn't it ruthless to deliberately underfund things?
It's happening regardless — the only question is whether you chose it. Undeclared underfunding is worse for everyone involved, because people keep expecting the thing and you keep half-attempting it. Saying explicitly what isn't getting attention this quarter is more honest than quietly failing at it, and it's usually received better than people expect.
What about when everything genuinely is urgent?
Some periods are like that and they're survivable short-term. What matters is whether it's a period or a permanent state. If every quarter is an emergency, the demand level is structurally beyond capacity and no prioritising method will fix it — that's a scope problem, and the available moves are reducing what's taken on or getting more capacity, not better triage.
Why do my priorities keep drifting back?
Because the default ranking is set by noise and noise is continuous, so any deliberate ranking erodes unless maintained. That's not a failure of resolve; it's the system returning to its default state. Treating it as a monthly maintenance operation rather than a decision you made once is the difference between a ranking that holds and one that lasts three weeks.