Write a Post-launch Retrospective for a Shipped Feature

When to use this

Use when you need to write a post-launch retrospective for a shipped feature and want a structured starting point instead of a blank page.

Prompt template

Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.

Task: Write a post-launch retrospective for a shipped feature.

Context to use:
- Feature or initiative: {{feature_or_initiative}}
- Key stakeholders: {{stakeholders}}
- Constraints or deadline: {{constraints}}

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist

Customize

Preview

Act as a senior product manager. Write in plain language a stakeholder could skim in two minutes, and flag anywhere a decision is being assumed rather than confirmed.

Task: Write a post-launch retrospective for a shipped feature.

Context to use:
- Feature or initiative: {{feature_or_initiative}} missing
- Key stakeholders: 
- Constraints or deadline: 

Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklist

Usage instructions

Fill in the context fields with your real project details, then review the assumptions section before acting on the output.

Example output

A short recommendation, a structured deliverable broken into clear sections, a list of assumptions, and a validation checklist, all specific to the write a post-launch retrospective for a shipped feature scenario described above.

Limitations

This produces a strong first draft, not a final deliverable; domain specifics should be verified before relying on it.

Rate this prompt