Weekly Priorities Built From Your Board's Carry-Over Pile

Most weekly planning starts with the newest ideas. A founder adds a request, a teammate flags a deadline, and the list grows before anyone asks what already sits unfinished. The result is a week that looks ambitious on paper and ends with the same cards still in progress. A different starting point helps: begin with the carry-over pile, the work that moved into this week without being completed. Carry-over is information. It shows where effort is leaking, which tasks are harder than estimated, and which commitments have been quietly postponed. This article walks through a method for turning that carry-over into a short, honest list of weekly priorities that a busy team can actually finish.
Start by Naming the Carry-Over Honestly
Before choosing anything new, gather every card that did not finish last week. Include cards that moved from one column to another without reaching a done state, cards that were reopened, and cards that were started but never touched again. Put them in one place, whether that is a filtered view on your board or a simple shared list. Seeing the full set at once changes the conversation. A team that thinks it had a productive week often discovers that a third of its committed work is still open.
Resist the urge to judge each item as it appears. The goal in this first pass is inventory, not triage. Note the owner, the original intent, and the date the work first entered progress. You are building a picture of what your team is carrying, which is the basis for every decision that follows.
Sort Carry-Over Into Three Groups
Once the pile is visible, sort each item into one of three groups. The first group is work that is nearly finished and needs a small, specific push. These items usually have a clear next step and a single owner who can close them within a few days. The second group is work that is blocked, waiting on a decision, another person, or an external input. The third group is work that no longer matches current priorities and should be closed, paused, or explicitly deprioritized.
This sorting prevents a common failure: treating every carried-over card as equally urgent. Near-finished work deserves protection because finishing it frees capacity and creates a visible win. Blocked work needs a different response, usually a named person to resolve the block. Stale work needs a decision rather than another week of silent drift. Keeping these groups separate keeps the weekly list from filling up with items that were never going to move.
Ask Four Questions Before Adding Anything New
After sorting carry-over, examine any new candidates for the week against four questions. First, does this item unblock someone else? Work that releases a teammate often delivers more value than work that only advances a single project. Second, is there a clear definition of done that the team can verify by the end of the week? Vague items tend to roll over. Third, does this item depend on something outside the team's control? If so, either secure the dependency first or schedule the item for a later week. Fourth, what would be dropped to make room for it? If nothing comes to mind, the team probably has not yet made a real choice.
Applying these questions reduces the weekly list to a manageable size. Many teams find that three to five priorities, with the near-finished carry-over placed first, is a realistic number. Anything beyond that should be recorded as a candidate for next week rather than quietly added to the plan.
A Practical Checklist for the Planning Session
Use the following sequence in a planning session of thirty minutes or less. Begin by reviewing the full carry-over list and confirming it is complete. Assign each carried-over item to one of the three groups: near-finished, blocked, or stale. For stale items, make an explicit decision to close, pause, or re-scope, and record the decision on the card. For blocked items, name the person responsible for clearing each block and the date by which they will report back. For near-finished items, confirm the single next step and the owner. Then evaluate new candidates against the four questions. Finally, select no more than five priorities for the week and write the definition of done next to each one.
Close the session by confirming that every priority has an owner and every blocked item has a named resolver. Teams that skip this final confirmation often discover on Wednesday that nobody remembered to chase the dependency.
Reviewing the Pattern Over Several Weeks
A single planning session helps, but the larger benefit appears when you compare carry-over across weeks. If the same cards keep returning, the issue is rarely effort. It is usually estimation, unclear ownership, or a hidden dependency that the board does not show well. Ask what kind of work keeps rolling over and whether the cause is consistent. You might find that all of the stalled items belong to one person who is overloaded, or that every blocked item waits on the same external reviewer.
Use these patterns to adjust the process itself rather than blaming individuals. Shorten the definition of done, split large cards into smaller ones, or move a recurring blocker into the weekly agenda. Over time, a team that studies its carry-over becomes better at choosing work it can finish, and the weekly priority list becomes a commitment the team keeps rather than an aspiration it revises every Friday.