Weekly Priorities by Naming What Won't Happen This Week
Most weekly planning fails at the same point: the list of priorities keeps growing until it describes everything the team hopes to finish. A week with twelve priorities is really a week with no priorities. This article takes a different angle from simply picking the top few items. Instead, it starts by naming what will not happen this week, then builds the priority set from what remains. The approach works because deferral decisions are harder to make later than they are to make at the start, and writing them down gives the whole team a shared reference point.
Why additive planning breaks down
Teams usually plan by adding. Someone brings a request, a founder mentions a customer concern, and a bug from last month resurfaces. Each item looks reasonable on its own, so each gets added to the week. By Tuesday the board holds more work than anyone can finish, and the team begins to make silent tradeoffs without discussing them.
The silent tradeoffs are the real problem. When nobody has said that a feature is paused, it stays half-open and keeps pulling attention. Stakeholders assume it is still coming. Owners feel guilty for not touching it. The result is a board that looks busy while the important work stalls.
Subtractive planning reverses the order. Before choosing what to do, the team lists the candidates and marks which ones explicitly will not move this week. Naming deferrals early makes the cost of each commitment visible, and it gives people permission to say no without a long argument.
A subtraction pass before the priority pick
Start the planning session with the full list of open candidates, including requests that arrived through chat, email, and meetings. For each one, ask three questions: Does waiting one week create real harm? Is there a named owner with capacity this week? Does finishing this unblock something else that is already committed?
Items that fail all three questions are candidates for deferral. Write them in a separate column labeled something like Not This Week, and record the date they will be reconsidered. This is not a graveyard. The column makes deferral an explicit decision with a review point, which is much healthier than letting items drift.
Be wary of deferring only the easy-to-drop items. If the deferral list contains nothing that anyone cares about, the pass was probably too gentle. A useful subtraction pass usually moves at least one thing someone wanted, and the team should be willing to say so out loud.
Choosing the priority set from what remains
Once deferrals are named, the remaining candidates can be ranked. A practical limit is three to five weekly priorities, each with one owner and one observable definition of done. A priority like Improve onboarding is too vague to finish. A priority like Ship the revised welcome email to all new signups by Thursday can be checked on Friday morning.
Test each priority against the capacity of its owner. If one person holds three of the five priorities and is also the only reviewer for the team, the plan is fragile regardless of how good the ranking looks. Spread ownership where possible, and mark any priority that depends on someone outside the team so the dependency is visible from the start.
Finally, reread the deferral list alongside the priority set. If a deferred item would make a priority impossible to finish, either move it into the priorities and drop something else, or accept that the priority is at risk and say so in the planning notes.
A short checklist for the planning session
Use this sequence each week. First, collect every open candidate in one place without ranking yet. Second, run the three subtraction questions on each candidate and sort the results into a deferral column with a review date. Third, choose three to five priorities from what remains, assigning one owner and one checkable definition of done to each. Fourth, check each owner's load and flag external dependencies. Fifth, reread the deferral column against the priorities and resolve any conflicts. Sixth, publish both lists so the whole team sees what is in and what is out.
Teams often skip the last step, and it matters most. A deferral that only the planner knows about is not a decision, it is a secret. When the Not This Week list is visible, people stop lobbying for their items through side channels, and the priority set becomes the team's shared commitment rather than one person's opinion of the week.
Review the approach after a month. Look at how many deferred items were eventually reconsidered and how many quietly disappeared. If many items vanish without anyone choosing to drop them, the review dates need tightening. The goal is not to defer more, but to make every choice about the week deliberate and recorded.