Workboard Pro Weekly Priorities: Choosing Three Outcomes Before Monday Starts

Workboard Pro is built for private workboards that support launches, planning, and fast-moving teams, and most busy founders and team leads use it to see what is in flight. Seeing everything in flight is different from knowing what to focus on this week. A board with forty active cards can feel like a list of obligations rather than a plan. This guide describes a simple method for turning that board into three weekly priorities, along with the questions that keep the choice honest. It makes no claims about any specific feature of the software; it is a general approach you can apply to whatever tool you use to see your work.
Start With Outcomes, Not Activities
The most common reason a weekly priority list fails is that it describes activities rather than results. 'Work on the pricing page' is an activity. 'Pricing page copy approved and live for the launch audience' is an outcome. Activities can be completed without anything changing, while outcomes tell you whether the week mattered.
When you scan your board, read each candidate card and rewrite its title as a sentence that ends in a state of the world. If you cannot describe what would be different on Friday, the card probably belongs in a later planning pass rather than in this week's three. This rewrite takes two minutes per card and usually removes a third of the candidates immediately.
Separate Carry-Over From New Demand
Teams often choose weekly priorities by urgency alone, which means the loudest new request wins and older commitments keep sliding. Divide your candidate cards into two groups: work carried over from last week, and work that arrived since. Review each group on its own before comparing them.
Carry-over work deserves a direct question: why did this not finish last week? The answer is usually one of four things. The estimate was wrong, a dependency was missing, the priority was quietly dropped, or the owner was pulled elsewhere. Each answer leads to a different decision. A wrong estimate may mean the outcome needs splitting. A missing dependency may mean this week's real priority is getting that dependency resolved. A dropped priority should be dropped explicitly, not left to age on the board.
A Three-Question Filter Before Committing
Once you have outcome-shaped candidates, run each through three questions. First, who is waiting on this? If another person's work is blocked by it, its priority rises regardless of how interesting the task is. Second, what happens if this slips by one week? Some slips are cosmetic and others change a launch date or a customer commitment, and the difference should drive the ranking. Third, can one person finish this without asking anyone for something new? Work that requires three approvals in unclear order is often less a priority than a meeting waiting to happen.
Keep the list to three. If you find yourself with five, ask which two could move to next week without anyone noticing. The discipline of cutting is where most of the value lies. A team that commits to three outcomes and finishes two has usually done better than a team that commits to eight and finishes four.
A Short Checklist for Monday
Before you publish the week's priorities, confirm the following in plain terms. Each priority is written as an outcome that could be checked on Friday. Each has a named owner who has agreed to it. Carry-over items have a stated reason for continuing rather than a silent reappearance. Each priority's upstream dependencies are either resolved or have an owner working on them this week. The list contains no more than three items, and the team knows which item to drop first if capacity disappears midweek.
If any answer is unclear, the priority is not ready. Fixing that on Monday morning costs far less than discovering it on Thursday.
Reviewing the Week Without Turning It Into a Report
End each week with a brief look at the three priorities. For each, record whether the outcome happened, partly happened, or did not happen, and write one sentence on why. Those sentences become the input for next week's carry-over review, which closes the loop without requiring a long status meeting.
Over several weeks, patterns emerge. If the same kind of outcome keeps partly happening, the estimates or the dependencies are systematically off. If the same owner keeps carrying items, the team may be assigning priorities without checking capacity. The point of the review is to improve the next planning pass, not to assign blame for the last one.