The Subtraction Problem: Every Leader Can Add a Priority. Almost None Can Remove One.

Watch a leadership team set priorities for the year and you will see a well-run process.

Discussion. Debate. Real thought about what matters. A short list at the end, usually 3 or 4 priorities, and genuine commitment to it.

Now watch the same team a year later. The list of the work that was prioritized has five things on it. Nobody remembers when the fourth and fifth arrived, and nobody removed anything to make room.

That is the subtraction problem, and it is nearly universal.

Why adding is easy and removing is not

Adding a priority is socially free. It signals ambition. Nobody in the room has to defend a loss, because at the moment of addition there is no visible cost. The cost arrives later, distributed across many weeks, borne by people who were not in the room.

Removing is the opposite. It is a visible, attributable decision with an identifiable loser. Somebody's project. Somebody's headcount. Somebody's idea from last year.

So, the arithmetic of organizational life is one-directional. Things accumulate because accumulating is comfortable and pruning is not.

The tell

Here is how to know whether your team set priorities or made a wish list.

Ask what got removed.

If the answer is nothing, you did not prioritize. Prioritizing means ranking, and ranking means some things went below the line. A list where everything stayed above the line is not a ranking. It is an inventory.

The second tell is what happens when something new arrives mid-year. If a genuinely good opportunity shows up in April and gets added without anything coming off, you have your answer about how the original list was made.

The question that forces the issue

There is one question that turns a wish list into a strategy, and most teams avoid it.

What are we willing to be bad at?

Not what will we deprioritize, which is a soft word that lets everyone keep their thing. What are we willing to be visibly, deliberately worse at this year than we were last year, because we chose to put the effort somewhere else.

Watch a room when you ask it. The discomfort is the point. If nobody is uncomfortable, nothing has been decided.

A priority that costs nothing to declare is not a priority. It is a preference.

Building the practice

Three things, and none of them are complicated.

One. Make removal part of the addition. No new priority enters without a named tradeoff. Not a vague acknowledgment that resources are finite. A specific thing that comes off, or a specific thing that gets consciously slowed.

This feels bureaucratic for about two cycles and then it becomes the most valuable rule you have.

Two. Give the list a hard number. Three is a good number. Five is a stretch. Anything past five is an inventory wearing a strategy's clothes, and everyone below you knows it.

The number matters more than which items make it, because the number is what forces the conversation.

Three. Name a subtraction owner. Someone whose job is to notice the drift. Not to make the call, just to raise the question when the list grows without anyone deciding it should.

In most organizations this belongs to nobody. Everybody owns their addition. Nobody owns the pattern.

The leader's version

Everything above applies to your own week, and the same failure mode shows up.

You know how to take something on. You have almost certainly never built a practice for putting something down.

So do the small version. Once a month, name one thing you will stop. Not the biggest thing. The one you could stop in thirty days without anything breaking. Name who it goes to or what happens instead. Tell one person.

One a month is twelve a year, which is more subtraction than most leaders manage in a decade.

Before your planning cycle

Late September and October is when most organizations start next year's planning. That is the window where this is still cheap.

Once the list is written, socialized, and tied to compensation, it hardens. Asking what comes off is a very different conversation in September than it is in February, and nearly impossible in June.

So, ask it now. What are we willing to be bad at?

If your priority list has only ever grown, that is the conversation. Let's have it.

Find the real problem. Do the real work. Build what lasts.