One launch decision.
Three useful briefs.
A reporting feature is ready for a limited cohort, but its support route has no verified owner and its activation event has not appeared in a test session. The evidence stays the same; the first question changes by audience.
Decision as of this review: hold customer release. A blocked support route prevents the controlled cohort from starting. After a named responder completes a test ticket, the owner may reconsider a limited release. Public promotion stays on hold until activation measurement and the customer message are verified.
All names, figures, and events below are fictional. The formats demonstrate how to present a decision; they are not a record of a real launch or a universal policy.
Executive sponsor
Lead with the authorization boundary, exposure, and next decision date.
Approve the next review, not the announcement
Requested decision: keep the limited cohort closed until support can respond to a test ticket. Do not authorize broad promotion yet.
Why: the product path works in a test account, but the team cannot show who responds if a pilot user needs help. Activation measurement and audience wording also remain open for public launch.
Sponsor question: “What evidence changes this decision?” Answer: a completed support test permits a controlled cohort; observed activation and corrected wording permit consideration of broader promotion.
Launch owner
Lead with the gate sequence, accountable roles, and handoff.
Resolve the blocker, then reopen the cohort decision
| Gate | Current evidence | Owner action | Exit condition |
|---|---|---|---|
| Support response | Blocked: no tested responder | Support lead assigns responder and runs a test ticket | Owner records response and escalation result |
| Activation event | Open: documented, not observed | Analytics owner runs an eligible test session | Event appears in the agreed dashboard |
| Customer message | Open: says “everyone” | Marketing names eligible cohort and exclusions | Launch owner signs off on corrected copy |
Next joint review: inspect the three artifacts above. A date without those artifacts does not convert an open gate into a pass.
Technical reviewer
Lead with reproducible checks and what failed, rather than a blended score.
One verified path does not clear every release gate
- Pass · Product path: test account opens the promised report. Retain test steps and result.
- Block · Support route: no responder can demonstrate a test-ticket handoff. Record ticket ID, responder role, and escalation result when retested.
- Open · Activation: event name exists in the tracking plan, but no eligible test event is visible in the agreed dashboard. Record session time, event payload definition, and dashboard result.
- Open · Rollback: product owner is named; record the rollback trigger and rehearsal evidence before widening access.
Reviewer question: “What would make this auditable?” Answer: linked test artifacts, owners, timestamps, and a clear pass or fail for every gate.
Use the format on your own launch
Start in the interactive audit. Load its fictional example to see the gate logic, then replace the values with information you are authorized to use. Download its decision brief for the record. These three audience layouts show which evidence to put first when you present the same decision.