Skip to main content
← Go/No-Go (full guide)
Spoke · Meeting · 7 min read

The Go/No-Go meeting — agenda, roles, pacing

Most Go/No-Go meetings produce discussion, not decision. Here's how to run one that actually ends with GO, WAIT, or NO-GO — and the facilitation traps that turn binary decisions into endless re-litigation.

The 4 roles

Roles can overlap in small teams (founder = owner = facilitator), but separating owner from facilitator is the single biggest improvement most teams can make.

Owner

Convenes the meeting, owns the decision afterward. Frames the question, presents pre-read, owns next steps. Should NOT score (would be conflict of interest).

Facilitator

Runs the meeting. Times each phase, enforces silent scoring before discussion, prevents one voice from dominating. Can score (separate role from owner).

Voters (2–4)

Functional leads + external perspective. Each scores all 7 criteria. Should be empowered to vote NO-GO without political risk.

Note-taker

Captures scores, key disagreements, and decisions. Outputs the decision record within 24 hours. Can be the facilitator if attendance is small.

The 75-minute agenda

Each phase has a specific output and a specific facilitator action. Skip any phase and the meeting drifts.

0:00–0:05

Frame

Owner states what we're deciding, what success looks like, what failure looks like. References pre-read. No discussion yet.

Facilitator:Cut off attempts to start scoring or debating before the question is clear.

0:05–0:50

Round 1: Score each criterion

For each of 7 criteria: owner presents evidence (60s), each voter scores 1–5 silently (30s), scores revealed simultaneously, discuss disagreements (3–5 min).

Facilitator:Enforce silent scoring before any discussion. Time-box discussion per criterion. Surface dissenting votes — don't let majority steamroll.

0:50–1:05

Round 2: Aggregate and decide

Calculate per-criterion averages and overall average. Compare against the decision threshold (set in pre-read, NOT during meeting). Output: GO / WAIT / NO-GO.

Facilitator:Lock the threshold — don't let the room renegotiate it after seeing scores. That's how teams talk themselves into bad decisions.

1:05–1:15

Round 3: Commit or kill

GO → owner names next steps + budget + timeline + kill triggers. WAIT → owner names experiment + deadline + re-decision date. NO-GO → owner commits to write postmortem within 48h.

Facilitator:No vague commitments. "We'll think about it" = NO-GO disguised. Force specifics.

5 facilitation traps

These are the patterns that turn Go/No-Go meetings into discussion theater. Recognize them and you can prevent them.

Discussion before silent scoring

The first person to speak anchors the room. Even with great facilitation, attendees adjust their unscored opinion to match.

✓ Fix: Strict rule: silent score on paper or in chat first, reveal simultaneously, THEN discuss. No exceptions.

Renegotiating the threshold mid-meeting

"4.0 is too strict, let's say 3.5 is GO" — you just lowered the bar to fit the result you wanted. Sunk-cost reasoning.

✓ Fix: Set threshold in pre-read. Once scores are visible, threshold is locked. If the threshold was wrong, that's a lesson for next meeting.

"Let's give it another month and see"

This is a hidden NO-GO. You commit resources without committing belief. A month later you're still stuck, minus a month of runway.

✓ Fix: WAIT must come with: specific experiment + deadline + re-decision date. If you can't name those, the answer is NO-GO.

Founder dominates every disagreement

Founders have highest conviction and highest title. Combined, they steamroll legitimate concerns from juniors who saw something the founder missed.

✓ Fix: Facilitator role is critical. Owner should NOT be facilitator. When founder pushes back, facilitator says "let's hear [dissenter] finish their concern first."

Skipping criteria you're not confident in

"We don't have data on unit economics, let's skip that one." But unit economics are exactly what you need to score honestly — even with rough numbers.

✓ Fix: Score all 7 criteria. Score 1 ("no data") IS a valid score. Skipping is what corrupts the average.

Cut your meeting time in half

Most of the 75 minutes is spent presenting evidence and surfacing disagreements about facts. We built GoNoGo to do the prep — voice intake, market sizing, scored output — so the real meeting is 30 minutes of decision instead of 75 minutes of discovery.

Generate the decision packet free →

30 min · up to 25 reports · Bring it to the real meeting

Frequently asked questions

How long should a Go/No-Go meeting be?+
60–75 minutes is the sweet spot. Less than 60 means you skipped silent scoring or rushed disagreements. More than 90 means the meeting drifted into discovery (which should have happened in pre-read). If you can't finish in 75 minutes with prepared attendees, the decision wasn't actually ripe — postpone and address the missing data.
Who should attend?+
3–5 people who can challenge each other honestly. The owner of the decision (usually founder or product lead), 1–2 functional leads with relevant context (engineering, sales, finance), and 1 external perspective if available (advisor, investor, fellow founder). Avoid stacking with people who report to the owner — they vote with job security.
What if attendees disagree strongly?+
Strong disagreement is signal — surface it, don't paper over it. The most common pattern: one person sees a critical risk the others missed (or dismissed). Spend 5 extra minutes letting them explain. If after 5 minutes the room still disagrees, the decision is WAIT, not GO — you don't have alignment on the most important risks.

More on this topic