Design a go/no-go review template

Go/No-Go Reviews Need a Yes/No Recommendation, Not a Deck

Status decks are the enemy of decisions — they bury the recommendation under context, and reviewers escape into "let's discuss next time." First Round Review's writing on executive decisions documents the pattern and the fix: a two-page go/no-go forces the recommender to commit to a binary recommendation on page 1, and reserves evidence for page 2. Basecamp's Getting Real makes the same point in code review form — if you cannot name the recommendation in one sentence, you are not ready to review it.

How the Design a go/no-go review template Prompt Works

The prompt constrains the deck to two pages with a binary recommendation on the first line, the 1-sentence reason, and the single biggest risk with a 30-day detection plan. The "1 question that would change my recommendation" item is the forcing function — it reveals where the recommender's confidence is thinnest and lets the reviewer focus there instead of circling ambient concerns.

When to Use It

• Leadership needs a binary decision this week.
• A previous go/no-go stalled in review and the team lost momentum.
• A cross-functional team needs alignment before the next sprint.
• You are a new product leader establishing decision hygiene.
• A board meeting is asking for a clear recommendation on a bet.

Common Pitfalls

• Burying the recommendation. If the reviewer has to dig for GO/NO-GO, the review will stall.
• No steelman of the counter. Recommendations that do not acknowledge counter-evidence look biased. Steelman.
• Open-ended decision window. A go/no-go without a deadline becomes a forever-pending item. Set the window.

Sources

• First Round Review — First Round
• Getting Real — Basecamp
• Google re:Work — Google
• Product Strategy Overview — Silicon Valley Product Group