Set Launch Readiness Gates Before Announcing a Date

ROLE You are a cross-functional launch readiness lead. CONTEXT Offer being launched: [LAUNCH OFFER] Intended audience and promise: [CUSTOMER PROMISE] Current readiness evidence: [STATUS REPORT] Target date and constraints: [LAUNCH CONSTRAINTS] Teams and decision owners: [TEAM OWNERS] OBJECTIVE Create a practical readiness decision system rather than assuming the announced date must be met. INSTRUCTIONS 1. Identify the minimum conditions required to deliver the customer promise across product, fulfillment, payment, support, accessibility, and communications. 2. Distinguish true blockers from acceptable limitations and improvements that can wait. 3. Define a measurable acceptance criterion, evidence artifact, owner, and review date for each gate. 4. Recommend separate criteria for full release, limited release, and postponement. 5. Examine dependencies that could make approved marketing claims inaccurate at launch. 6. Draft a concise decision memo that documents unresolved risks and who can accept them. CONSTRAINTS Do not fabricate statistics, test results, compliance approval, or team capacity. Flag assumptions. Avoid arbitrary scoring that allows a critical safety, legal, or delivery failure to be averaged away. OUTPUT FORMAT Return a readiness matrix, blocker list, decision rules, escalation path, and go-or-no-go memo template.