A launch readiness review agenda for cross-functional teams
Check whether a launch is ready, at risk, or needs a deliberate scope change.
Understand the decision
Restate the objective, audience, promise, and observable success signals. Confirm that product behavior, sales language, support guidance, and public claims describe the same release before discussing individual deliverables.
Put the practice to work
Inspect only dependencies that can change readiness: product acceptance, legal or security review, measurement, customer communication, enablement, support, and rollback ownership. Give every risk an impact, evidence, mitigation, owner, and decision date.
Review and improve
End explicitly: proceed, proceed with named conditions, or change the date or scope. Record who made the decision and which risks were consciously accepted. Schedule the first post-launch review while context is fresh.