Weekly Priorities Through a Capacity Audit: Matching Commitments to Real Hours
Most weekly planning fails at the same point: the list of priorities is written before anyone checks how many hours the team actually has. A founder schedules three major deliverables, a designer has two review meetings nobody mentioned, and a developer is pulled into a customer escalation on Wednesday. By Friday the list looks like a record of good intentions. This article takes a different angle from the usual advice about picking priorities. Instead of starting with what matters most, it starts with what the week can hold, then uses that number to shape what gets committed to. The method is simple, but it requires honesty about time, and that honesty is where most of its value comes from.
Start With the Hours That Exist, Not the Hours You Hope For
Begin every weekly planning session with a rough capacity figure for each person on the team. Take the number of working days, subtract scheduled meetings, known travel, and time already committed to ongoing support or maintenance, and see what remains. A common mistake is to count a full eight-hour day as available time. Meetings, messages, context switching, and the ordinary friction of a shared workspace consume a meaningful share of any day, so treat the remainder as a ceiling rather than a target.
Write the capacity number down next to each person's name in your planning document. It does not need to be precise to the quarter hour. A reasonable estimate that everyone agrees on is more useful than a precise guess that nobody trusts. The purpose is to create a visible constraint, so that when someone proposes adding a fourth priority, the group can see the math without anyone having to argue about it.
Estimate Commitments in Blocks, Then Compare Totals
Once capacity is visible, estimate each candidate priority in rough blocks: half a day, one day, two days, or a week. Avoid false precision here. The goal is to compare the total of committed blocks against the capacity figure, not to build a detailed schedule. If a team of three has roughly fifteen available days and the proposed priorities add up to twenty-two, the gap is obvious before the week starts.
When the totals do not fit, the team has three options. It can remove or defer a priority, reduce the scope of one so it fits a smaller block, or explicitly accept that some other work will slip. Each choice is legitimate. The failure is pretending the totals fit when they clearly do not. Writing the comparison down makes the trade-off a deliberate decision instead of a quiet surprise on Thursday afternoon.
A Practical Checklist for the Planning Session
Use this sequence each week. First, list known fixed commitments such as client calls, recurring reviews, and on-call duties, and subtract them from available hours for each person. Second, record any known absences, including planned leave, travel, and training. Third, list candidate priorities, aiming for no more than three to five items that would each change something important if completed. Fourth, assign a block estimate to each candidate and a single named owner.
Fifth, compare total blocks against remaining capacity and resolve any gap using one of the three options above. Sixth, confirm that each owner agrees they can deliver their block, and note any dependency that could stall the work. Finally, record the agreed list in the place the team actually looks during the week. A planning session that ends in a document nobody reopens has produced a list, not a commitment. The checklist works best when it is short enough that a team will still run it in a difficult week.
Questions to Ask When the Numbers Do Not Add Up
When the comparison fails, the most useful response is a set of pointed questions rather than a quick decision. Ask which priority would be most damaged by being delayed by a week, and which would merely be inconvenienced. Ask whether any candidate is really two separate pieces of work that could be split across weeks. Ask whether a dependency on another team is the real bottleneck, in which case the honest priority may be to unblock that dependency instead of adding more work.
Also ask what the team has stopped doing in order to make room. If nothing has been removed, the list is probably still a wish list. Finally, ask whether last week's estimates were accurate. If the same kind of task has consistently run over, adjust the block sizes for this week rather than repeating the same optimistic plan. Over several cycles, these questions improve the team's estimates faster than any tool or template could.