The meeting starts with a demo. The team walks through what has been built, the room nods, someone asks about the edge case in the third screen, and the deck moves to the next item. Forty-five minutes later, the review is over. Nothing has changed.

This is the most common product review in the world: a presentation of work, followed by approval by exhaustion. It feels productive because a lot of information moved. But no decision was made, no assumption was tested, and the riskiest part of the plan was never examined.

A review is a decision, not a report

The purpose of a product review is not to inform senior people about what the team is doing. It is to improve a decision that the team is about to make or has made.

That distinction changes the entire format. If the purpose is information, slides are fine. If the purpose is judgement, you need a specific question, the evidence behind it, the options considered, and the trade-off being proposed.

A useful review has one decision at its centre. Not a status update with a decision somewhere inside it. One decision, stated at the top.

A one-page brief

The most effective format I have used is a single page, shared in advance:

  • The decision. Stated as a question with options.
  • The problem. Who is stuck, at what moment, and what it costs them.
  • The evidence. What we know, how we know it, and how confident we are.
  • The options. What we considered, including doing nothing.
  • The trade-off. What we give up with the recommended option.
  • The ask. What we need from the room: a decision, a constraint, a resource, a challenge.

The pre-read matters more than the meeting. People who have read the page arrive with questions. People who have not will ask for a summary, which is the meeting’s first failure.

Questions that change the room

The quality of a review is largely the quality of its questions. A few that reliably move a conversation from presentation to judgement:

What would make this fail? Not “what are the risks,” which invites a generic list. Ask for the specific failure mode the team is most worried about.

What are we not seeing? A direct invitation to the people outside the team, who often hold the missing constraint.

What is the cost of being wrong? If the answer is “we learn something and try again”, the decision can be made quickly. If it is “we commit to a data model for two years”, it deserves more scrutiny.

What would we do differently with half the time? This reveals the core of the value. If the answer is “cut the part we are most excited about”, that part may be optional.

Who disagrees, and why? A review with no dissent is usually a review with no examination.

Separate review from approval

Approval is a governance step: someone with authority says yes. Review is a thinking step: a group improves the quality of the decision.

When the two are combined, the room optimises for approval. People present the strongest case, hide the uncertainty, and avoid the question that might derail the plan. The result is a decision that looks unanimous and is actually unexamined.

Separating them is not always possible, but it is worth trying. A review can happen with peers and stakeholders before the approval meeting. The approval meeting can then be short, because the thinking has already happened.

Record the decision

A review that ends without a written decision will be relitigated. The rationale disappears, the context changes, and six weeks later someone asks why the team chose the expensive option.

A decision record does not need to be elaborate. Five lines:

  • What we decided.
  • What we considered and rejected.
  • What evidence we used.
  • What we are uncertain about.
  • What would make us revisit it.

That record is also a gift to the future team, who will inherit the decision without the meeting.

The test of a good review

At the end of the review, ask: did anything change?

Sometimes the answer is no, and that is fine. The decision was sound and the review confirmed it. But the confirmation should come from examination, not from politeness. If the plan, the evidence and the confidence level are all exactly as they were before the meeting, the review was a presentation.

A good review leaves the team with a sharper question, a clearer trade-off, or a decision they can defend. Anything less is a status update with better chairs.