Weekly Product Call
The quarterly roadmap sets the direction. The weekly product call keeps it alive.
It serves two people at once. For leadership, it is the mechanism that keeps them grounded: close enough to what is actually happening to make good calls, without needing to be in every conversation. For the team, it is the mechanism that maintains direction: a regular forcing function that surfaces drift before it compounds and keeps the quarter’s commitments visible and real.
This is not a status meeting. It is a decision meeting. Its job is to make sure the roadmap is on track, surface blockers that need a call, and force an explicit decision on every ad hoc that has come in. Done well, it takes 30 minutes. Done poorly, it becomes a status dump that wastes the time of everyone in the room and resolves nothing.
Who and When
Who: PM and the delivery owner for the team. Not the full team. The people who can answer the three questions and make the calls.
When: 30 minutes, weekly. Same slot every week.
What comes before it: PM prepares. The call is not where you figure out the status. By the time the call starts, PM knows whether the team is on track, what has come in since last week, and what decisions are needed. If PM arrives unprepared, reschedule.
The Three Questions
Every call moves through three questions, in this order.
1. Are we on track?
One answer: on track, at risk, or off. Not a project-by-project update. A clear read on whether the quarter’s commitments are still achievable at current pace.
If on track: note it and move to question two.
If at risk: name the specific item, why it is at risk, and what decision is needed in this call to address it. The call does not end without a named resolution — whether that is a scope cut, a date shift, a dependency escalated, or a named owner for the next action.
If off: same process. The worst outcome is leaving the call with the team still at risk and no one assigned to resolve it.
2. What is blocking us?
Blockers the team cannot resolve without a decision from PM, leadership, or an external party. Not every open question. Only the ones where work cannot continue until someone decides.
Each blocker gets a named owner and a resolution date before the call ends. If a blocker requires escalation outside the call, PM owns taking it out of the room.
3. What ad hocs have come in?
Everything that has arrived since the last call that was not on the original roadmap. Bugs, urgent requests, new asks from clients, internal pressure to reprioritize.
Each item gets one of two answers in the call: it goes on the list, or it waits. There is no third option.
If it goes on the list: something else comes off, or capacity is explicitly named. No item gets added without a named trade-off. If the team adds without removing, the quarter becomes undeliverable quietly, not all at once.
If it waits: it goes into the backlog with a named reason. Not ignored. Deferred with intent.
What This Is Not
This call does not replace the quarterly roadmap. The roadmap is where the quarter gets shaped — the problems chosen, the bets made, the capacity allocated. The weekly call does not redo that work. It checks whether the work is on track and makes the small course corrections that keep the original plan viable.
This call does not cover work that is progressing normally. If an item is on track and has no blockers, it does not need to be discussed. Time in the call goes to risk, blockers, and decisions.
This call does not replace async updates. The written weekly update covers what shipped, what is in progress, and what is coming. The call handles what the update cannot: decisions that require a conversation.
When Things Go Wrong
The call becomes a status report. This happens when PM is not prepared or when the room defaults to each person explaining what they did last week. The fix is PM owning the agenda and keeping the call on the three questions. If someone starts narrating their work, redirect: “Are we on track? Is there a blocker?”
Ad hocs accumulate without a decision. If items keep coming in and the team keeps saying “we’ll figure it out,” the backlog grows invisible and the quarter gets quietly overcommitted. Every ad hoc gets a decision in the call it is first raised.
The call keeps going past 30 minutes. This is a sign that either too many topics are on the agenda or a blocker is being debated rather than assigned. Debates belong outside the call. Assign an owner and a date, then take the debate offline.