Most recurring product reviews are status theater. A team presents, leadership nods, someone asks a question that cannot be answered without a week of analysis, and everyone leaves with the same open questions they arrived with. The meeting is expensive — often the most expensive hour on the calendar by headcount — and it changes nothing.
The fix is not a better deck. It is a different contract about what the hour is for.
The contract
A product review exists to make decisions that the team cannot make alone. That is the whole purpose. If a review ends without a decision recorded, it was a demo, and demos should be shorter and asynchronous.
Everything below follows from that one rule.
Pre-read, not a walkthrough
The material goes out at least a day ahead in writing. Nobody presents it live. Live presentation burns the majority of the hour on transmission and leaves the minority for the thinking, which is exactly backwards — and it lets a team fill the time so that hard questions never get raised.
If people arrive without having read it, spend the first ten minutes reading in silence. This feels awkward once and then becomes the most productive ten minutes in the meeting.
What the written doc contains
- What changed since last time. Shipped, moved, dropped. Short.
- What we learned. Evidence, not activity. What we now believe that we did not believe a month ago, and what changed our mind.
- The decision requested. Stated as a question with options and a recommendation. Not "discussion of pricing" — "we recommend option B; we need a call on whether existing customers are grandfathered."
- What we need from this room. Budget, a tiebreak, access to a customer, an exception to a policy. Name it.
The decision-requested section is the one that changes the meeting. Teams resist writing it because a stated recommendation can be rejected, and a vague update cannot. That discomfort is the mechanism working.
Who is in the room
The people who can decide, plus the people who hold the context. Everyone else is optional and should be told so explicitly, because a standing invite list grows until the room is too large for anyone to disagree in.
A room of fifteen produces consensus-shaped non-decisions. A room of six produces calls.
How it ends
The last five minutes are for reading back what was decided, who owns each item, and by when. Someone writes it into the decision log during the meeting, not after. The log entry includes the reasoning, because the reasoning is what stops the same debate from reopening in six weeks.
If nothing was decided, say that out loud too, along with what is blocking the decision and who is getting the blocker cleared.
The metric for whether your review works is not attendance or satisfaction. It is the time between a question being raised and a decision being recorded. Measure that for a quarter and the meeting fixes itself.
Failure modes
Only good news gets presented. If reviews are where teams get graded, teams will bring wins. Ask directly what is not working, and respond to the first honest answer in a way that makes the second one likely.
The cadence does not match the decisions. Monthly reviews for decisions that arrive weekly means the roadmap is set in hallway conversations and the review just ratifies it. Match the cadence to the real decision rate.
Questions that cannot be answered in the room. A senior leader asks for a number nobody has, the team spends a week producing it, and the answer changes nothing. Before requesting analysis, say what decision the number would change. If the honest answer is none, skip it.
Reviews that turn into design critique. Legitimate, but a different meeting. Route it.
The version that runs on a part-time week
This format holds up under severe time constraints, which is why it works in a fractional engagement — a written pre-read plus a decision-focused hour is close to the minimum viable senior product presence. There is more on how that week gets allocated in what fits into ten hours of product leadership, and the how I work page shows the actual artifacts, including the decision log format.