Weekly Priorities Through Your Board's Recent Velocity: Reading Last Month Before Planning Next Week
Most weekly planning starts with a list of what people hope to finish. The list grows, the week fills up, and by Thursday everyone is quietly reprioritizing on their own. A different starting point is the record of what your team has actually finished. Your board already holds that record in the movement of cards between columns, the dates when items closed, and the items that sat in one place for weeks. Reading that history before you pick next week's priorities turns a wish list into a forecast grounded in how your team really works. This article walks through a practical way to do that, without assuming any particular tool features beyond the basic act of looking at what has moved.
Why Recent History Beats Ambition
Ambition is a poor predictor of output. A team that wants to ship eight things in a week will often ship three, and the gap is rarely laziness. It usually comes from interruptions, reviews that take longer than expected, and work that depends on someone else's answer. Recent history captures those realities. If your team closed roughly five meaningful items per week over the last month, that number is a far better planning input than the number of cards currently in your to-do column.
The goal is not to punish optimism or to lock the team into a single pace forever. The goal is to give the weekly plan a baseline. You can always choose to stretch above that baseline, but stretching should be a deliberate decision with a named reason, not the default that quietly breaks the week.
Gathering the Right Four Weeks of Signal
Start by looking back across roughly the last four weeks. Four weeks is long enough to smooth out one unusually quiet or unusually busy stretch, and short enough that the patterns still reflect current staffing and priorities. Count what closed in each week, but also note what did not close even though someone worked on it. Those carryover items are often the most informative part of the record.
Separate completed work from moved work. A card that went from In Progress to Done is a finished unit. A card that bounced between columns several times, or that was reopened after review, tells you that estimates for that kind of work tend to be optimistic. Note these patterns in plain language rather than building an elaborate scoring system. A short paragraph in your planning doc saying that reviews consistently add two days to design work is more useful than a spreadsheet nobody maintains.
Turning History Into a Weekly Capacity Estimate
Once you have four weeks of rough counts, look for a range rather than a single number. If the weekly closes were four, six, five, and three, your realistic planning band is perhaps four to five meaningful items, with a clear note that six is possible but should not be assumed. Ranges protect the plan from the most common failure, which is treating the best week as the average.
Then translate the range into a priority count. If your band is four to five items, choose three priorities for the week and treat the remainder as useful spillover rather than commitments. Three priorities give the team room to absorb an unexpected support request or a late review without the whole plan collapsing. Priorities should be the items whose completion would most change the team's situation, such as a launch blocker, a customer-facing fix, or a dependency that other people are waiting on.
A Short Checklist for Next Week's Plan
Use the following questions as a plain checklist during your weekly planning session. First, how many meaningful items closed in each of the last four weeks, and what is the realistic range? Second, which cards carried over repeatedly, and what caused them to stall? Third, which of the candidate priorities depend on another person's answer, and has that answer been requested? Fourth, does the total of chosen priorities fit within the lower end of the range, leaving headroom for interruptions? Fifth, is there one priority whose delay would cause a visible problem for someone outside the team?
If the answer to the fourth question is no, remove items until it becomes yes. This step feels uncomfortable because it means saying no to work that someone cares about. Frame it instead as protecting the commitments the team can actually keep. A plan with three finished priorities earns more trust than a plan with eight half-finished ones.
Finally, after the week ends, compare the outcome to the plan. Record which priorities closed, which did not, and why, in one or two sentences each. Over a few cycles, these notes will sharpen your sense of the team's true pace far more reliably than any general advice about productivity.