Weekly Priorities When Last Week's Commitments Refuse to Leave
Most teams plan each week as if it begins from zero. The new list gets written, the old one is quietly abandoned, and whatever did not finish last week is either forgotten or reappears unannounced on Thursday. The unfinished work is not random. It usually clusters around a few causes: commitments that were vague from the start, work that was waiting on someone else, and tasks that expanded beyond their original size. A weekly priorities process that starts with the carry-over pile, rather than the wish list, tends to produce a shorter and more honest plan. This article describes one way to run that review, using only the general methods a team can apply with any task tool or even a shared document.
Start With What Carried Over, Not What Is New
Before anyone proposes a new priority, collect everything that was open at the end of last week. Include items that were in progress, items that were promised but not started, and items that were marked done but did not actually reach the person who needed them. Put them in one list. Seeing the full carry-over pile at once changes the conversation. A team that begins with a blank page tends to add ambitious work on top of unresolved work, and the new plan quietly assumes the old commitments will somehow finish themselves.
Ask a simple question of each carried item: is this still true? Some items will be obsolete because the situation changed. Others are still valid but have lost their urgency. Mark obsolete items for removal, and say so out loud rather than letting them sit in a column indefinitely. Removing a dead commitment is a real decision, and it frees the week for work that matters.
Separate Three Kinds of Unfinished Work
Carry-over is not one category. Sorting it into three groups makes the next step much easier. The first group is work that is simply unfinished because it ran out of time. This is usually the easiest to re-plan, since the scope is known and the only question is whether it still deserves hours this week. The second group is work that is blocked, waiting on a decision, an approval, an input from another person, or a dependency that has not shipped. Blocked work should not be scheduled as though it can proceed. Instead, the priority for that item becomes the unblocking action. The third group is work that was never clearly owned. These items often appeared in a meeting, were nodded at, and then drifted. They need an owner before they can need anything else.
This sorting also reveals patterns. If most of the carry-over is blocked, the problem is upstream of execution and the weekly plan should focus on clearing those blockers. If most is unfinished but unblocked, the team probably overcommitted and should reduce intake. If much of it is unowned, the team has an acknowledgment problem, where commitments are made without a clear person attached.
Choose Three Priorities With a Cost-of-Delay Check
Once the carry-over is sorted, select a small number of weekly priorities. Three is a useful ceiling for most teams, because it is small enough to hold in mind and large enough to reflect real work. For each candidate, ask what it costs to delay it by one week. Some work has a cost that grows quickly, such as a launch dependency, a customer-facing commitment, or a task that other people are waiting on before they can start. Other work has a cost that stays flat, such as an internal cleanup that would be nice to finish. Prioritize the items whose delay cost is high, even if they are less interesting.
A useful check is to picture the Friday review. If an item is not finished, will someone be surprised, or will they say they expected it to slip? Items that produce surprise are the ones worth protecting. Items that produce a shrug are often better moved off the list entirely.
A Short Checklist for the Weekly Review
The following checklist can be run in roughly thirty minutes with a small team. First, list every open item from the previous week, including promised items that never started. Second, mark each item as finished, obsolete, blocked, unfinished but unblocked, or unowned. Third, remove obsolete items from the active view and record the removal. Fourth, assign an owner to every unowned item, or decide it is not happening. Fifth, for each blocked item, write down the specific unblocking action and who is responsible for it. Sixth, select up to three weekly priorities using the cost-of-delay check. Seventh, confirm that the total planned work fits realistic capacity, and cut scope if it does not. Eighth, state the three priorities aloud so each owner hears what they have committed to.
Teams using a board, a document, or a spreadsheet can apply this checklist with whatever tool they already have. The method does not depend on any particular software. It depends on a habit of looking honestly at unfinished work before adding anything new.
Keeping the Review Honest Over Time
The first few weekly reviews often feel heavy, because they surface work that has been quietly stuck for a while. That discomfort is useful information. Over several weeks, the carry-over pile should shrink, or at least become more accurate. If it keeps growing, the team is probably committing to more than it can deliver, and the right response is to reduce intake rather than to plan more aggressively. Track two simple numbers: how many priorities were completed, and how many carried over. Over time, these figures show whether the weekly plan matches reality.
Weekly priorities are not a contract to finish everything on the list. They are a shared statement of where attention will go during the week, and a record of what the team chose to leave behind. A review that starts from the unfinished pile keeps that statement tied to what actually happened, which is the only reliable basis for planning the next week.