Weekly Priorities From Your Own Carry-Over Pile: A Working Method
Most weekly planning starts with a blank page. Someone asks what the team should accomplish, and the answers pile up until the list has twenty items and no hierarchy. A different starting point is often more honest: begin with what is already on the board, what carried over from last week, and what is waiting on someone. This article describes a method for setting weekly priorities by reading the carry-over pile first, so that new commitments are chosen against real work instead of imagined capacity.
Why the carry-over pile is the right starting point
Every team has work that did not finish last week. Some of it is almost done, some is stuck, and some was quietly dropped when something urgent appeared. Treating that pile as the starting input makes the planning conversation concrete. Instead of asking whether a task feels important, you ask whether it is already in motion, how far along it is, and what would be lost by pausing it.
Starting from carry-over also exposes a common planning error: adding new commitments on top of unfinished ones without deciding what gives way. When the carry-over is visible first, the team has to make that trade-off on purpose.
A step-by-step method
Step one: list every open item that carried over from the previous week. Include items in progress, items waiting on review, and items waiting on someone outside the team. Do not reorder them yet. The goal is a complete inventory, not a ranking.
Step two: sort the carry-over into three groups. The first group is work that is nearly complete and needs a small push to finish. The second is work that is active but has real remaining effort. The third is work that has stalled, either because it is blocked or because nobody has touched it in a while. Be candid about the third group; it is often where the real planning decisions live.
Step three: for each stalled item, ask one question: is this still worth doing? If the answer is no, close it or move it to a parking area with a clear note. If the answer is yes, record the specific thing that must happen before it can move, and who owns that step.
Step four: choose the weekly priorities from the first two groups before considering anything new. Aim for three priorities at most. If nearly complete items and active items already fill the week, that is a signal that new work should wait, not that the team should try harder.
Step five: only then consider new requests. Place each one against the chosen priorities and ask which existing commitment it would displace. If the honest answer is none, the request belongs in a later week.
A practical checklist
Before the planning session, confirm the following. Every carry-over item is visible on the board or in whatever list the team uses. Each item has a named owner, or is explicitly marked as unowned. Each stalled item has a note on what blocks it. A count of open items per owner is available, so overload is visible.
During the session, check the following. Priorities were chosen from carry-over before new requests were discussed. No more than three priorities were selected. Every priority has an owner and a definition of done that fits in one sentence. Any item dropped from the plan was closed or deliberately parked, not silently abandoned.
After the session, review whether the same items appear week after week without progress. Repeated carry-over is a diagnostic: it usually points to unclear scope, missing dependencies, or priorities that were never really agreed on.
Questions to ask when the method feels slow
Teams sometimes find that auditing carry-over takes longer than they expected. That is useful information. Ask whether the board holds too many open items, whether statuses are updated often enough to be trusted, and whether the same owners are repeatedly overloaded. Each of these is a process question rather than a discipline problem, and each has a process answer: fewer items in progress, a shorter update cadence, or a rebalanced set of commitments.
It is also reasonable to ask whether the method is being applied to the right scope. A team of two does not need the same ceremony as a team of twelve. Adjust the length of the session to the number of open items, and keep the three-step structure even when the meeting is brief.
What good looks like after a few weeks
When the method is working, the carry-over pile shrinks or stabilizes instead of growing. Priorities feel like a short list the team can explain in one breath. New requests arrive with an explicit trade-off attached, and people stop being surprised by what did not get done. The clearest sign is that the weekly conversation spends less time debating what matters and more time checking whether committed work is moving. That shift is the real goal: priorities chosen from the work already in motion, with trade-offs made in the open.