The longest go/no-go meetings happen when the decision criteria are being invented in the room. The shortest ones happen when the criteria were written down weeks earlier and the meeting simply reads them out.
A Salesforce release gate should take ten minutes. If yours takes an hour, you do not have a gate — you have a negotiation.
Write the criteria before anyone is under pressure
Release readiness criteria are easy to agree on when no deadline is looming: UAT sign-off complete from every named owner, no open critical or high defects, regression suite green, rollback plan documented, release log published.
Agree them once, in calm conditions, with the people who will attend the gate. Then the go/no-go decision is arithmetic, not politics.
The ten-minute agenda
Read each criterion. State whether it is met, with evidence — a sign-off record, a defect report, a test run. If every criterion clears, the release goes. If any criterion fails, the release moves, and the meeting ends with a new date.
The gate keeper reads; owners confirm; the decision falls out. Ten minutes.
What “no-go” has to mean
A gate only works if no-go is real. The first time a failed criterion gets waved through “just this once,” the gate is decoration. Moving a release date is cheaper than a production incident — and after the first honest no-go, teams start clearing criteria early rather than arguing late.
The payoff
Teams that run written-criteria release gates stop dreading go-live. Release weekends turn from all-hands standby into a checklist. And the ten minutes you spend at the gate replaces the emergency hours you used to spend after it.