Priorities & Tradeoffs

If you have ever watched a company declare ten “top priorities,” you already know the problem. When everything is a priority, nothing is. A priority only does its job when it is ranked above something else — when leaders are willing to say this gets resources first and that waits. The other half of the same truth is the tradeoff: every choice spends one thing to gain another. Get comfortable with both ideas and you will understand most of the tense decisions that happen above your pay grade.

A priority is a ranking, not a label

The word priority comes from “prior” — the thing that comes first. By its original meaning, you can only have one at a time. Modern work loosened that to “the few things that come before the rest,” but the spirit is the same: a priority is only real if other things are explicitly lower. Sticking a “high priority” label on every request is the most common way teams quietly drown.

Here is the tell. If a manager says everything on a list is urgent, ask: “If we could only finish one this week, which one?” A real set of priorities survives that question — someone can name the top item without flinching. A fake set of priorities falls apart, because nobody was ever willing to rank. Ranking is uncomfortable precisely because it forces a choice, and that discomfort is the whole point.

Every decision has a tradeoff

A tradeoff is what you give up to get something else. There is no free lunch in a company with finite people, time, and money. Say yes to building a big new feature, and you have said no to three smaller fixes the team could have shipped instead. Push a deadline earlier, and you usually pay with reduced scope or extra cost. The decision was never “should we do this good thing?” — almost everything sounds good in isolation. The real decision is “what do we give up to do it?”

The classic shorthand is the project triangle: fast, cheap, good — pick two. Want it fast and good? It will not be cheap, because you will throw more people at it. Want it cheap and good? It will not be fast. Want it fast and cheap? Quality slips. The triangle is a simplification, but it captures the honest truth that you cannot max out everything at once, and pretending otherwise is how projects quietly fail.

Naming the tradeoff out loud

The skill that marks experienced people is not avoiding tradeoffs — it is naming them. Junior thinking says, “Can we add this?” Senior thinking says, “We can add this if we drop that, or push the date two weeks — which do you prefer?” The second version respects that resources are finite and hands the decision-maker a real choice instead of a wish.

Saying yes to one thing is always saying no to another. The only question is whether you say the “no” out loud or let it happen by accident.

When tradeoffs stay hidden, they do not disappear — they leak out as missed deadlines, burned-out teams, and half-finished features. Surfacing the tradeoff early feels harder in the moment but is far kinder than discovering it the week before launch. The people who do this become trusted, because they make the cost of a decision visible before it is paid.

How to use it

You can raise the quality of almost any planning conversation with a few honest phrases:

• “If we could only ship one of these this week, which comes first?” (forces a real ranking)
• “Happy to add it — what should we drop or delay to make room?” (names the tradeoff)
• “Do we want this fast, cheap, or good? We can pick two.” (sets honest expectations)
• “What are we giving up by saying yes here?” (makes the hidden cost visible)

None of this is about being negative. It is about being honest that time and people are finite. Master ranking and tradeoffs and you stop being the person who overpromises — and become the one whose plans actually hold up.

Spot the tradeoff

Read each scenario and decide what is being traded. Tap a card to flip it and check your answer.

Sort the decisions

Drag each decision into the category it belongs to — or tap a decision, then tap a category. Hit Check placement when you’re done.