Product Strategy Memo (Amazon 6-pager)

Write a compelling product strategy memo using a six-page format inspired by Amazon narrative memos for executive decision-making

leadershipNewadvancedAmazon 6-PagerWorking BackwardsStrategic Narrative2000-2500 words
Customize Your Prompt
Fill in the variables to generate your personalized prompt
Preview
See how your prompt will look with the current variables
You are a VP of Product at a top tech company. You are writing a strategy memo for [Product/Feature Name]. Strategic question: [Strategic Question/Decision].

Role: Expert in strategic writing, data-driven argumentation, and executive communication. You write memos that drive alignment and confident decision-making at the highest levels.

Instructions:
1. Frame the strategic question with full context and urgency
2. Present a data-driven analysis of the opportunity and risks
3. Propose a clear recommendation with supporting evidence
4. Anticipate objections and address them proactively
5. Define the decision-making criteria and next steps

## STRATEGY MEMO: [Product/Feature Name]

### 1. INTRODUCTION AND FRAMING (Page 1)
**Strategic Question:** [Restate the decision to be made]
**Why now:** [Timing considerations from the evidence; do not invent urgency]
**Scope of Decision:** [What are we deciding, and what are we NOT deciding?]

**Context:**
[3-4 paragraphs providing the full background needed to understand this decision. Include market dynamics, competitive landscape, internal capabilities, and customer signals. A reader with no prior context should be able to understand the situation after reading this section.]

### 2. TENETS (Guiding Principles for This Decision)
1. [Tenet 1: e.g., Customer experience over short-term revenue]
2. [Tenet 2: e.g., Move fast but ensure regulatory compliance]
3. [Tenet 3: e.g., Build for scale, not for a single market]

### 3. THE OPPORTUNITY (Page 2-3)
**Market Size:**
- TAM: [Total addressable market with source]
- SAM: [Serviceable addressable market]
- SOM: [Serviceable obtainable market -- realistic 3-year target]

**Customer Problem:**
[Detailed description of the customer pain point, backed by data. Include quotes from customer research, support data, or market research.]

**Competitive Landscape:**
| Competitor | Market Share | Strength | Weakness | Our Advantage |
|-----------|------------|----------|----------|---------------|
| [Comp 1] | [Share] | [Strength] | [Weakness] | [Our edge] |
| [Comp 2] | [Share] | [Strength] | [Weakness] | [Our edge] |
| [Comp 3] | [Share] | [Strength] | [Weakness] | [Our edge] |

**Key Data Points:**
- [Data point 1 supporting the opportunity] -- [Source]
- [Data point 2] -- [Source]
- [Data point 3] -- [Source]

### 4. PROPOSED APPROACH (Page 3-4)
**Recommendation:** [Clear, unambiguous statement of what you recommend]

**How it works (Working Backwards -- Future Press Release):**
[An explicitly hypothetical future press release describing the intended customer experience and outcomes. Do not present it as a completed launch or invent customer quotes.]

**Phased Execution:**
| Phase | Timeline | Scope | Investment | Expected Outcome |
|-------|----------|-------|------------|-----------------|
| Phase 1 | [Timeline] | [Scope] | [Investment] | [Outcome] |
| Phase 2 | [Timeline] | [Scope] | [Investment] | [Outcome] |
| Phase 3 | [Timeline] | [Scope] | [Investment] | [Outcome] |

**Resource Requirements:**
- Engineering: [FTEs and duration]
- Design: [FTEs and duration]
- Go-to-market: [Investment]
- Total investment: [ESTIMATE]

### 5. FINANCIAL MODEL (Page 4-5)
| Metric | Year 1 | Year 2 | Year 3 | Assumptions |
|--------|--------|--------|--------|------------|
| Revenue | [ESTIMATE] | [ESTIMATE] | [ESTIMATE] | [Key assumptions] |
| Costs | [ESTIMATE] | [ESTIMATE] | [ESTIMATE] | [Key assumptions] |
| Contribution margin | [ESTIMATE] | [ESTIMATE] | [ESTIMATE] | |
| Payback period | [ESTIMATE] | | | |
| ROI | | | [ESTIMATE] | |

**Sensitivity Analysis:**
| Scenario | Revenue Impact | Key Variable Changed | Probability |
|----------|-------------|---------------------|------------|
| Optimistic | [+X%] | [Variable] | [%] |
| Base case | [Baseline] | N/A | [%] |
| Pessimistic | [-X%] | [Variable] | [%] |

### 6. RISKS AND MITIGATIONS (Page 5)
| Risk | Probability | Impact | Mitigation | Owner |
|------|------------|--------|------------|-------|
| [Risk 1] | [H/M/L] | [H/M/L] | [Mitigation strategy] | [Role] |
| [Risk 2] | [H/M/L] | [H/M/L] | [Strategy] | [Role] |
| [Risk 3] | [H/M/L] | [H/M/L] | [Strategy] | [Role] |
| [Risk 4] | [H/M/L] | [H/M/L] | [Strategy] | [Role] |

**What could kill this initiative?**
[1-2 paragraphs on the biggest existential risks and what would cause you to recommend stopping]

### 7. ALTERNATIVES CONSIDERED (Page 5-6)
| Alternative | Pros | Cons | Why Not Recommended |
|------------|------|------|---------------------|
| [Alt 1: Do nothing] | [Pros] | [Cons] | [Rationale] |
| [Alt 2] | [Pros] | [Cons] | [Rationale] |
| [Alt 3] | [Pros] | [Cons] | [Rationale] |

### 8. DECISION AND NEXT STEPS (Page 6)
**Decision requested:** [Specific approval or decision needed]
**Deadline for decision:** [When this needs to be decided]

**If approved, immediate next steps:**
1. [Action item with owner and timeline]
2. [Action item with owner and timeline]
3. [Action item with owner and timeline]

**Key milestones and check-in points:**
| Milestone | Date | Decision Point |
|-----------|------|---------------|
| [Milestone 1] | [Date] | [Go/No-Go criteria] |
| [Milestone 2] | [Date] | [Check-in criteria] |
| [Milestone 3] | [Date] | [Final review] |

## APPENDIX: FAQ
[Address 5-7 anticipated questions with concise answers]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.
How to use this prompt

When to use it

Making the case for major strategic decisions with executive-level rigor

Before you use the output

  • •Fill in the variables with the facts and constraints you have.
  • •Check the output against your source material and revise any mistakes.
  • •Add relevant context when the first draft misses part of your task.

Expected output

Six-page strategy memo with financial model and risk analysis

Quick Info
Categoryleadership
Output Length2000-2500 words
Web SearchNot Required
Frameworks
Amazon 6-PagerWorking BackwardsStrategic Narrative
Try PM Toolkit Calculators

Use the calculators to check the numbers behind a proposed product decision.