Write a product narrative memo that replaces your slide deck

Description

Your product review meetings are death-by-PowerPoint — 40 slides where nobody remembers the key insight by slide 15. This writes an Amazon-style narrative memo that forces clear thinking, structured arguments, and makes the reader understand your product direction in 6 pages, not 60 slides.

Write a narrative product memo for {{initiative_name}} that replaces a slide deck for the upcoming product review.

## Context
- Initiative: {{initiative_name}}
- Product: {{product_name}}
- Audience: {{audience}} (e.g., executive team, board, cross-functional leadership)
- Purpose: {{memo_purpose}} (e.g., propose a new initiative, request resources, share quarterly results)
- Key decision needed: {{decision_needed}}
- Supporting data available: {{data_sources}}

## Memo Structure (6-page max)

### Page 1: The Situation
Write a compelling opening paragraph that:
1. Describes the current state of the customer problem or market opportunity
2. Includes one specific data point that makes the reader care
3. Explains what has changed recently that makes this urgent
4. States the decision this memo is asking the reader to make

### Page 2: The Customer
1. Who specifically is affected? (not "users" — name the segment)
2. What is their current workaround? (how do they solve this today?)
3. Include a direct customer quote or behavioral data point
4. What happens if we do nothing? (the cost of inaction)

### Page 3: The Approach
1. What are we proposing to build/change/launch?
2. What alternatives did we consider and why did we reject them?
3. What is the key insight that makes this approach better?
4. What trade-offs are we consciously making?

### Page 4: The Plan
1. Phased rollout plan with milestones and dates
2. Resource requirements (headcount, budget, dependencies)
3. Key risks and mitigation strategies
4. What we're explicitly NOT doing in this phase

### Page 5: The Evidence
1. Results from any experiments, prototypes, or beta tests
2. Relevant industry benchmarks or case studies
3. Financial projections with stated assumptions
4. Sensitivity analysis: what if our key assumption is wrong?

### Page 6: The Ask
1. Restate the specific decision needed
2. Summarize the recommendation in 3 bullet points
3. Define success criteria and how we'll measure them
4. Propose a review checkpoint (when will we assess progress?)

## Writing Guidelines
- Use prose paragraphs, not bullet points (bullets are for appendices)
- Every claim must have supporting data or a cited source
- No jargon — write as if explaining to an intelligent outsider
- Active voice, present tense, direct sentences
- The memo should be readable in under 20 minutes

## Appendix (optional)
- Detailed financial model
- Technical architecture diagram
- Customer research raw data
- Competitive analysis details

Customize This Prompt