Weekly Priorities From the Dependency Side: Asking What Your Team Is Waiting On
Most weekly priority lists are built from the top down. A founder or team lead writes what matters most, then the team tries to fit that list around everything else already in motion. The result is often a week that looks disciplined on paper but leaves colleagues stuck, waiting for a review, an approval, or a decision that nobody remembered to schedule. This article takes a different angle. Instead of starting with your own ambitions, start with the requests that other people are currently waiting on, and let those waits shape what you commit to this week.
Why waiting is a better starting point than wanting
A wish list answers the question of what you would like to finish. A waiting list answers the question of who is idle because of something you have not yet done. Both are useful, but the waiting list tends to surface work with higher real cost, because a delay in one person's work often ripples into several others' calendars.
When a team sets priorities by desire, the items that get done are usually the ones that feel most interesting or most visible to leadership. Items that unblock others can sit quietly for days because they feel small in isolation. A single pending approval may look minor on a board, yet it could hold up a designer, a developer, and a customer-facing commitment at the same time.
Starting from dependencies does not mean ignoring strategy. It means checking strategic goals against the current queue of requests before committing. A priority that nobody is waiting on can still be important, but it should not automatically outrank a small item that three people need to continue their own work.
Questions to ask before choosing the week's three priorities
Before naming priorities, gather the open items where someone has said, in effect, I need this to move forward. These may appear as cards in a column labeled waiting, as comments asking for input, or as messages that were answered with a promise to get back to someone. The goal is to see the blockers as a group rather than one at a time.
For each candidate blocker, ask a few plain questions. Who is waiting, and what exactly can they not do until this is resolved? How long has the request been open? Is the thing being requested a decision, a deliverable, or information? Does completing it require only one person, or does it need a meeting that has to be scheduled? A request that needs a fifteen-minute answer is very different from one that requires a week of research, and the weekly plan should reflect that difference.
Finally, ask what happens if the item is not handled this week. If the answer is that a launch date moves, a customer waits, or another team has to reschedule, the item deserves a place among your priorities. If the answer is that someone is mildly inconvenienced, it may still be worth handling, but it probably does not need to displace a core deliverable.
Sorting blockers into a short, honest list
Once you have the candidate blockers, sort them into three groups: items that can be cleared in under thirty minutes, items that require focused work of a few hours, and items that need coordination across people or a longer lead time. Quick clears are often the highest-leverage choices for a busy week, because they cost little and release others immediately. Focused items usually belong in the weekly priorities themselves. Coordination items should be started early, even if they finish later.
Be cautious about letting the list grow beyond what the team can absorb. A common failure is to treat every waiting request as a priority, which quietly recreates the wish list under a new name. A useful rule is to choose no more than three commitments for the week and to label everything else as acknowledged but deferred, with a note about when it will be reconsidered. Acknowledging a request without promising action is itself a service, because it tells the requester the item has not been lost.
A weekly checklist for dependency-first priorities
Use the following sequence at the start of each week. First, review every item currently marked as waiting or blocked, and note the person affected for each one. Second, answer the three questions for each item: who is waiting, what they are waiting for, and what slips if it stays open. Third, group the items by effort, separating quick clears from focused work and coordination work.
Fourth, select up to three weekly priorities, giving preference to items that unblock multiple people or protect a near-term date. Fifth, place any remaining items in a deferred state with a stated review point, such as Thursday's check-in. Sixth, before the week begins, send a short note to anyone whose request was deferred so they know the status. Finally, at the end of the week, count how many requests were closed and how many new ones appeared. That number, tracked over several weeks, shows whether your priority-setting is actually reducing waiting or only rearranging it.
This approach will not remove every conflict between urgent and important work, and it does not replace judgment about strategy. What it offers is a clearer picture of who is depending on whom, so that the week's commitments reflect real constraints instead of only the loudest or most recent ones.