# Product Vision Statement

> Craft a compelling product vision that aligns teams on the long-term destination. Uses the vision-mission-strategy hierarchy to create an inspiring yet actionable north star.

- Skill: `nandanosql/product-vision-statement` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nandanosql/product-vision-statement`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nandanosql/product-vision-statement/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: nandanosql (https://skillmd.com/u/nandanosql)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nandanosql/product-vision-statement

---


## Purpose

Craft a compelling product vision that answers **"Where are we going and why does it matter?"** — aligning the team on a shared long-term destination. The vision provides the north star that guides every roadmap, prioritization, and hiring decision.

---

## Key Concepts

### Vision–Mission–Strategy Hierarchy

| Level | Time Horizon | Answers | Example |
|-------|-------------|---------|---------|
| **Vision** | 5-10 years | Where are we going? | "Every PM makes data-driven decisions instantly" |
| **Mission** | 1-3 years | How will we get there? | "Unify product metrics into one intelligent platform" |
| **Strategy** | Quarterly | What do we focus on now? | "Win mid-market SaaS through automated reporting" |

### Great Vision Characteristics

- **Aspirational** — Describes a future state, not the current product
- **Customer-centric** — About the user's world, not your technology
- **Memorable** — Can be remembered and repeated without notes
- **Durable** — Doesn't become irrelevant in 2 years
- **Inspiring** — Makes people want to contribute
- **Clear** — No jargon, any new hire understands it

---

## Application

### Step 1: Define the Future State

```markdown
**The world we want to create:**
[Describe the customer's world AFTER your product succeeds — not what the product does,
but how the customer's life/work is different]

**Timeframe:** [5-10 years out]
```

### Step 2: Write the Vision Statement

```markdown
**Product Vision:**
[One sentence that captures the aspirational future state]
```

**Template options:**

1. **Outcome-driven:** "A world where [target users] can [desired outcome] without [current pain]."
2. **Transformation:** "Transform how [target users] [activity] by [shift]."
3. **Democratization:** "Make [valuable capability] accessible to [currently underserved group]."

### Step 3: Write the Supporting Mission

```markdown
**Mission (1-3 year focus):**
[How your product specifically contributes to this vision — more concrete and actionable]
```

### Step 4: Validate

```markdown
**Vision Validation Checklist:**
- [ ] Can a new hire understand it in 10 seconds?
- [ ] Does it guide "should we build X?" decisions?
- [ ] Is it aspirational (not just describing what exists)?
- [ ] Would you be proud to put this on your careers page?
- [ ] Does it survive a "so what?" challenge?
```

---

## Examples

### ✅ Good Examples

| Company | Vision |
|---------|--------|
| Tesla | "Accelerate the world's transition to sustainable energy" |
| Stripe | "Increase the GDP of the internet" |
| Figma | "Make design accessible to everyone" |
| Notion | "Make toolmaking ubiquitous" |

**Why these work:** Customer-centric, aspirational, memorable, durable, no jargon.

### ❌ Bad Examples

| Vision | Problem |
|--------|---------|
| "Be the leading SaaS analytics platform" | Self-referential, not customer-centric |
| "Leverage AI to optimize workflows" | Technology-first, forgettable |
| "Build excellent software" | Could be anyone, says nothing |
| "Disrupt the $50B market" | About you, not the customer |

---

## Quality Rubric

| Dimension | 0 | 1 | 2 |
|-----------|---|---|---|
| **Customer Focus** | About your product | About your market | About the customer's world |
| **Aspirational** | Describes today | Slightly ahead | Inspiring future state |
| **Memorability** | 3+ sentences | One sentence but wordy | 10 words or fewer |
| **Durability** | Obsolete in a year | Good for 3 years | Valid for 5+ years |
| **Actionability** | No guidance on decisions | General direction | Clearly guides yes/no decisions |

---

## Common Pitfalls

### Pitfall 1: Vision as Feature Description

**Fix:** If your vision mentions specific features, zoom out. Features change; the destination shouldn't.

### Pitfall 2: Vision Without Mission

**Fix:** A vision without a mission is a poster, not a strategy. Always pair with a concrete 1-3 year mission.

---

## References

### Related Skills
- `skills/strategy/positioning-statement/SKILL.md` — Positioning operationalizes the vision
- `skills/strategy/okr-framework/SKILL.md` — OKRs translate vision into measurable goals
- `skills/strategy/north-star-metric/SKILL.md` — North star metric tracks progress toward vision

### External Frameworks
- Marty Cagan, *Inspired* (2017) — Product vision concepts
- Simon Sinek, *Start with Why* (2009) — Purpose-driven framing

---

**Skill type:** Component
**Domain:** Strategy & Vision