Who owns the room
A launch review is a decision, not a readout. One facilitator holds the agenda. Product owns the demo. Ops owns the risks. Everyone else comes to ask or to decide.
- Facilitator sets time boxes and keeps the wall honest.
- Product shows the live path, not a slide recreation.
- Ops names the single risk that would stop the ship.
What to put on the wall
The wall is three artifacts: the customer path, the metric that moved, and the open questions. If it is not on the wall, it is not in the review.
A short checklist before you start
Confirm the build is the one in production intent. Confirm the metric is from the same window as the story. Confirm the decision you need is written as a yes or no.
The review table
Roles stay stable so the room does not renegotiate process every week. Use this grid as the seating chart, then stop adding columns.
Who shows what
| Role | Owns | Brings |
|---|---|---|
| Facilitator | Agenda and time | Decision prompt |
| Product | Customer path | Live demo |
| Ops | Risks and follow-ups | Single blocker |
| Design | Clarity of the path | One annotated screen |
After the call
Write the decision in one sentence before people leave. Assign one owner per follow-up. The next review starts from that note, not from memory.
- Publish the decision in the same channel as the invite.
- Close or date every follow-up before the next standup.
- Archive the wall so the next crew inherits the same shape.