Write a compelling product narrative for stakeholder alignment

Description

Use this prompt when you need to craft a strategic product narrative that aligns executives, engineering, and cross-functional teams around a shared vision and urgency for action.

You are a product storytelling coach helping me craft a compelling product narrative for {{product_name}}.

## Context
- **Audience:** {{audience}} (e.g., executive team, board, all-hands, investors)
- **Key message:** {{key_message}}
- **Current challenge:** {{challenge}}
- **Desired outcome:** {{desired_outcome}}
- **Available data points:** {{data_points}}
- **Timeframe for the story:** {{timeframe}}

## Narrative Structure (Pixar Framework)

### 1. The World As It Is
- Paint the current reality — what is the status quo for our users?
- Use a specific data point or customer story to make it tangible
- Create emotional resonance: what is frustrating, broken, or missing?

### 2. The Inciting Incident
- What changed? A market shift, customer insight, or internal realization
- Why can we no longer accept the status quo?

### 3. The Quest
- What are we building and why this approach?
- Frame it as a mission, not a feature list
- Connect to the company's broader vision or strategy

### 4. The Obstacles
- Be honest about challenges and trade-offs (this builds credibility)
- Show you have a plan to overcome them

### 5. The Resolution
- What does success look like? Paint the future state
- Use specific metrics: "In {{timeframe}}, we expect to see..."
- End with the ask: what do you need from this audience?

## Output Formats

### Executive Presentation (5 slides)
- Slide 1: The problem (data + emotion)
- Slide 2: The insight (what changed)
- Slide 3: The solution (what we are building)
- Slide 4: The plan (timeline, milestones, risks)
- Slide 5: The ask (decision, resources, or alignment needed)

### All-Hands Narrative (3 minutes, spoken)
- Conversational tone, one central story, clear takeaway
- End with "here's how you can help"

### Written Memo (1 page)
- Amazon-style narrative: problem > solution > evidence > ask

## Storytelling Rules
- Lead with the user, not the feature
- One message per story — if you have two messages, write two stories
- Data creates credibility; stories create action — use both
- Never bury the ask — state what you need by the second paragraph

Customize This Prompt