Guide
How to run a go/no-go meeting
A go/no-go meeting has one job: decide whether something ships. Most of them fail the same way — they turn into a status update, end without an explicit call, and the real decision happens in a DM an hour later. Here's how to run one that ends with a decision on the record.
Updated October 1, 2026 · 6 min read · By the Align team
What a go/no-go meeting is for
A go/no-go (or launch readiness) meeting is a short, time-boxed checkpoint before a release, launch, migration or rollout. Each area owner confirms whether their criteria are met, and the group makes one of three calls: go, no-go, or go with conditions.
It is not a planning meeting and not a status meeting. If people are hearing information for the first time, the prep failed.
Who should be in the room
- The decision owner — the one person who makes the final call if the group splits.
- One owner per readiness area: engineering, QA, product, design, support, marketing, security, ops — whichever apply.
- A facilitator who keeps time and pushes for explicit answers (this can't be the decision owner).
Keep it small. Anyone who is only there to listen can read the decision record afterwards.
Agree the criteria before the meeting
The meeting is only fast if "ready" was defined in advance. Write the criteria down when the work is planned, not the day before launch. Typical ones:
- No open P0/P1 bugs; known issues documented.
- Tests and QA sign-off complete on the release candidate.
- Rollback plan written and tested.
- Monitoring, alerts and on-call cover in place.
- Support has docs and a briefing; customer comms drafted.
- Security, legal or compliance review done where required.
A 30-minute agenda
| Time | What happens |
|---|---|
| 0–3 min | Facilitator states the decision being made and the options: go, no-go, go with conditions. |
| 3–18 min | Each owner gives a one-line status against their criteria: green, yellow (with the risk), or red. |
| 18–25 min | Discuss only yellows and reds. What would it take to make each one acceptable? |
| 25–29 min | Roll call: every owner says go or no-go out loud. Decision owner makes the call. |
| 29–30 min | Read back the decision, conditions, owners and dates. |
Get an explicit yes or no from every owner
Silence is not consent. The single most useful habit in a go/no-go meeting is a roll call at the end: name each owner and ask for their call. It surfaces the quiet "I'm not sure about the migration" that would otherwise come up after launch.
Write the decision down
Record the decision, the reasoning, the conditions and who agreed, in the same place every time. Six weeks later, when someone asks why the rollout stopped at 10%, the answer should be a link, not a debate.
Decision: [Release / launch name] — GO | NO-GO | GO WITH CONDITIONS Date: [YYYY-MM-DD] Decision owner: [Name] Readiness - Engineering: [green/yellow/red] — [note] Call: [go/no-go] ([Name]) - QA: [green/yellow/red] — [note] Call: [go/no-go] ([Name]) - Product: [green/yellow/red] — [note] Call: [go/no-go] ([Name]) - Support: [green/yellow/red] — [note] Call: [go/no-go] ([Name]) - Ops/On-call: [green/yellow/red] — [note] Call: [go/no-go] ([Name]) Why: [2–3 sentences of reasoning] Conditions: [What must be true] — Owner: [Name] — By: [Date] If a condition fails: [Rollback / delay / re-decide] Rollback plan: [Link] Next checkpoint: [Date or "none"]
Common ways go/no-go meetings fail
- Criteria were never agreed, so every item becomes a debate.
- It runs as a status update and ends without an explicit call.
- The decision owner is also facilitating, so nobody pushes them for a decision.
- Yellow items are waved through without an owner or a deadline.
- Nothing is written down, so the decision is re-litigated after launch.
How Align does this for you
Run it in an Align room. Start from the “Make a decision” template, drop the readiness doc on the board and share the link. While you talk, Align pins each concern, the go or no-go and the conditions with their owners onto the board, and @align answers questions from the doc. When you hang up, everyone gets the recap by email and the condition tasks can go straight to Linear or Jira. The room keeps the board, so the follow-up check happens in the same place.
Frequently asked questions
How long should a go/no-go meeting be?
15 to 30 minutes. If it needs longer, the readiness criteria or the prep weren't done; move the discussion to a separate meeting and keep the go/no-go itself short.
Who makes the final go/no-go decision?
One named decision owner, usually the product or release owner. Every area owner gives their call, but if the group splits the decision owner decides, and the record shows who agreed and who didn't.
What's the difference between a go/no-go meeting and a launch readiness review?
A readiness review checks status against the criteria and can happen several times; the go/no-go meeting is the final checkpoint where the decision is made.