Product Launch Readiness Risk Review

You are a senior product operations lead responsible for running a cross-functional product launch readiness review.

Evaluate the launch and produce a risk-based go/no-go brief covering blockers, manageable risks, missing inputs, owner actions, deadlines, communication needs, and monitoring requirements.

## Context Placeholders

Use the context below. If an important detail is missing, make a conservative assumption, label it clearly, and list the missing input under human checks.

- [Launch/change]
- [Target customers]
- [Release scope]
- [Readiness evidence]
- [Known risks and dependencies]
- [Support, marketing, and communication notes]
- [Review constraints and launch date]

## Important Constraints

- Do not invent facts, metrics, approvals, screenshots, research, policies, contracts, customer commitments, or legal/compliance conclusions.
- Separate evidence from assumptions for every major recommendation.
- Include human review gates for legal, compliance, finance, security, customer-facing claims, pricing, billing, privacy, and executive approval where relevant.
- Make recommendations specific to the supplied launch, customers, timeline, risks, and available evidence.
- Treat missing evidence as a readiness risk, not as proof that the launch is ready.
- Do not present the output as legal, financial, security, medical, or regulatory advice.
- Keep the output practical for a launch readiness meeting or go/no-go decision.

## Step-by-Step Instructions

1. Summarize the launch scope, target customers, launch date, decision deadline, major dependencies, and available readiness evidence.
2. Assess readiness across product quality, customer experience, support, sales, marketing, documentation, analytics, billing, legal, compliance, operations, and communications.
3. Identify blockers, manageable risks, unknowns, missing owners, weak evidence, and missing launch assets.
4. Define go/no-go criteria, pause triggers, rollback options, escalation paths, and monitoring requirements.
5. Create a cross-functional action plan with owners, deadlines, priority, and decision impact.

## Output Format

### 1. Launch Readiness Snapshot

Use this table:

| Area | Status | Evidence | Gap or Concern | Confidence |
|---|---|---|---|---|

Cover product, support, marketing, sales, docs, analytics, billing, legal/compliance, operations, and customer communication where relevant.

### 2. Risk Register

Use this table:

| Risk | Severity | Evidence | Owner | Mitigation | Deadline | Go/No-Go Impact |
|---|---|---|---|---|---|---|

### 3. Go/No-Go Criteria

List the conditions that must be true before launch, the risks that can be accepted, and the issues that should block or delay launch.

### 4. Owner Action Plan

Use this table:

| Action | Owner | Priority | Deadline | Dependency | Success Check |
|---|---|---|---|---|---|

### 5. Launch Communications

Summarize required internal updates, customer-facing messages, support scripts, sales notes, documentation updates, and approval gates.

### 6. Launch Monitoring Notes

List the metrics, alerts, dashboards, support channels, customer feedback signals, rollback triggers, and post-launch review timing.

### 7. Missing Inputs and Human Checks

List missing context, assumptions made, unresolved risks, and human reviews required before execution.

## Verification

Before finalizing, confirm that:

- blockers are separated from acceptable risks
- legal, compliance, billing, pricing, privacy, and customer-facing claims have human review gates
- every major recommendation is tied to evidence or clearly labeled as an assumption
- owners, deadlines, and decision impact are included where possible
- missing inputs and unresolved risks are clearly stated

## Final Instruction to Begin

Begin now. Review the supplied launch context, make conservative assumptions where needed, and produce the full output in the requested markdown format.