Weekly Priorities Start With a Subtraction Test, Not a Wish List
Most weekly planning fails at the same point: the list gets written before anyone decides what to drop. A week that begins with twenty open items and a vague hope of finishing them rarely ends with the three things that mattered. Priorities are not a list of what might get done. They are a decision about what gets attention first, and that decision requires removing things, not just ranking them. This article offers a subtraction-first approach for busy teams and founders who need a short, defensible set of weekly priorities without pretending the calendar is empty.
Start with what is already committed
Before choosing anything new, list what is already promised. This includes deliverables with external dates, meetings you cannot move, and commitments a teammate is waiting on. These are not priorities in the aspirational sense; they are constraints. Writing them down first makes the available capacity visible. If the committed work already fills most of the week, the honest conclusion is that the week has room for only one or two additional priorities, not five.
Ask each person to separate committed work from discretionary work in their own list. Committed work has a named person waiting on it. Discretionary work is what someone would like to move forward. Keeping these categories distinct prevents a common failure where a discretionary item quietly displaces a commitment because it felt more interesting.
Run the subtraction test
Once the candidate list exists, apply a simple test to each item: if this did not happen this week, what would actually break, and by when? If the answer is a specific consequence with a near date, the item stays in contention. If the answer is vague, such as the team would feel behind, the item moves to a parking area. The test is blunt on purpose. It forces the team to name a cost rather than a feeling.
Then apply a second cut. Ask which items would still matter if the week were half as long. Items that survive a shorter week are usually the real priorities. Items that only matter in a leisurely week are often nice-to-haves. Keep no more than three weekly priorities; if more survive, the team is still avoiding the decision and should discuss which ones truly outrank the others.
Write a stop list alongside the priorities
Most priority lists name what to do and say nothing about what to stop. A stop list fixes this gap. Next to the three priorities, write two to four things the team is explicitly not doing this week. These might be a redesign that keeps getting pushed, a recurring report nobody reads, or a feature request from a single customer. Naming them openly prevents them from reappearing mid-week as urgent surprises.
The stop list also protects against the quiet drift that happens when someone starts a low-priority task because it feels quick. When a teammate asks whether they should begin something on the stop list, the answer is already written down, and the conversation becomes shorter and less personal.
Questions to ask before committing
Before the priorities are finalized, a short set of questions helps catch errors. Each priority should have one clear owner who can say yes to the commitment. It should have a visible definition of done, so that the team can tell on Friday whether it happened. It should name the first concrete action, because a priority stuck at the level of an intention rarely moves. And it should identify the dependency most likely to block it.
A practical checklist for the weekly session: confirm committed work is listed separately; apply the consequence test to every candidate; cut to three or fewer; write the stop list; assign one owner and one done-definition to each priority; note the first action and the likeliest blocker. A team that completes this in under thirty minutes usually has a more honest week than one that spends an hour debating a long list.
Finally, review the priorities midweek rather than only on Friday. A brief check asking whether any priority has slipped, and whether a stop-list item has crept back in, lets the team adjust before the week is spent. Weekly priorities work best as a small, repeated decision, revised openly, rather than a plan written once and defended until the weekend.