Product Launch Risk Assessor

Assess product launch readiness by identifying execution risks, weak assumptions, dependencies, communication gaps, and mitigation actions.

The Prompt

You are a launch operations strategist. Assess the launch plan and identify the biggest risks before the team commits.

## 1. Launch Overview
- Summarize the launch objective
- Define the audience
- Define the launch scope
- State the success metric

## 2. Risk Review
Identify risks across:
- Product readiness
- Positioning and messaging
- Internal enablement
- Customer support readiness
- Analytics and measurement
- Dependencies on other teams or vendors

## 3. Assumption Check
List:
- What assumptions the team is making
- Which assumptions are validated
- Which assumptions remain weak
- What evidence is missing

## 4. Mitigation Plan
For each meaningful risk, provide:
- Risk statement
- Likelihood
- Impact
- Owner
- Mitigation action
- Trigger for escalation

## 5. Output Format
Return:
1. Launch summary
2. Top launch risks
3. Weak assumptions
4. Mitigation table
5. Launch/no-launch questions

Launch plan:
[PASTE PLAN]

Optional context:
- Product type: [CATEGORY]
- Launch date: [DATE]
- Audience: [SEGMENT]
- Team constraints: [OPTIONAL]

How to Use This Prompt

1. Paste the real launch plan, even if incomplete.
2. Include the launch date so timing risk is visible.
3. Ask the model to separate execution risk from strategy risk.
4. Use the weak-assumption section to guide last-minute validation.
5. Review the mitigation table with actual owners, not generic team names.

Example Input

Product type: B2B SaaS workflow feature
Launch date: April 15
Audience: Existing customers and self-serve prospects
Launch plan: [launch doc pasted here]

Example Output

1. Launch Summary

The launch plan is strong on marketing tasks but underdeveloped on support readiness and instrumentation.

2. Top Risks

• The positioning assumes users immediately understand the workflow change
• Success metrics are defined, but event tracking is incomplete
• Support content and escalation guidance are not ready

3. Launch/No-Launch Questions

• Can the team confidently measure adoption within 48 hours?
• Are support and success teams trained on the top failure modes?
• Is the onboarding path clear enough for first-time users?

When This Prompt Is Most Useful

Use this prompt when you need help with product launch risk assessor but do not want a generic answer. It works best for marketers, founders, creators, and small teams turning rough positioning into usable campaigns who already have some context and want the AI to organize it into campaign angles, copy variants, content outlines, landing page sections, or messaging tests. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.

This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.

Inputs to Prepare

Before running the prompt, gather:

• The real goal or decision you are trying to support
• The audience, customer, learner, stakeholder, or user involved
• Any source material the AI should use instead of guessing
• Constraints such as deadline, format, budget, word count, platform, or policy
• Examples of good and bad outputs if you have them
• The exact tone you want the final answer to use

For this page, the most important context is: audience, offer, channel, proof points, objections, tone, conversion goal, and examples of messages that already worked or failed. If you leave that out, the model may still respond, but the result will usually be generic.

Example Input

Audience: solo consultants. Offer: fixed-scope website audit. Objection: worried it will become a sales call.

How to Review the Output

Do not use the first answer blindly. Check whether it:

• connects every claim to evidence or a concrete benefit
• suggests multiple angles with tradeoffs
• defines how to measure whether the copy worked
• makes assumptions visible instead of hiding them in confident language
• gives you something you can act on, test, or revise within the same work session

If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.

Common Failure Modes

• Too little context: the AI fills gaps with generic advice.
• No review criteria: the output sounds polished but is hard to judge.
• Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
• Overclaiming: the model may invent certainty when the source material is weak.

The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.

Practical Variations for Product Launch Risk Assessor

• Positioning mode: Provide audience, promise, proof, objection, and competing alternative. Ask for message angles with risks.
• Content mode: Give channel, format, offer, and call to action. Ask for variants by awareness level.
• Optimization mode: Paste current copy and ask for diagnosis before rewrite.

Follow-Up Prompts

Use these after the first answer:

• “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
• “Give me a conservative version, a direct version, and a version optimized for speed.”
• “Create a final review checklist I can use before I publish, send, ship, or present this.”

What Makes This Page Different

This page is useful when you are working on product launch risk assessor and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.