product-vision

What this skill does

# Product Vision Expert

## Overview

The Product Vision is the narrative that sits above the north-star metric. It is the answer to "where are we going and why" -- the story that aligns engineers, designers, marketers, executives, and customers around a single point on the horizon. Without a vision, teams optimize local metrics; with a vision, teams optimize toward a shared destination.

A vision is *not* a mission statement, *not* a strategy, *not* a roadmap. A mission says why the company exists. A strategy says how the company will win. A roadmap says what will ship next quarter. A vision says where the product will be in 5-10 years -- specific enough to inspire engineering decisions today, ambitious enough to outlast any current technology or market condition.

This skill produces the Product Vision document across four canonical formats: Roman Pichler's **Product Vision Board** (one-page diagnostic), Geoffrey Moore's **elevator pitch** (single-sentence positioning from *Crossing the Chasm*), Andy Raskin's **strategic narrative** (5-act story arc used by Salesforce, Drift, Andreessen-backed companies), and Marty Cagan's **10-year horizon** (long-form Cagan-style vision narrative). It also provides a review checklist for testing whether a vision actually works.

### When to Use

- **New product launch.** You are starting a new product and need to articulate the destination before committing engineering quarters.
- **Major pivot.** The team's direction has shifted and the old vision no longer fits. Reset.
- **Strategy reset.** Annual or pre-funding-round refresh of the long-term direction.
- **Stakeholder misalignment.** Engineering, design, and exec teams are pulling in different directions. A re-articulated vision often surfaces the disagreement.
- **Hiring at scale.** You need a vision compelling enough that prospective hires can decide whether to join. Vague visions repel strong talent.

## Vision vs. Mission vs. Strategy vs. Roadmap

| Layer | Question Answered | Time Horizon | Example |
|-------|---------------------|---------------|---------|
| **Mission** | Why does the company exist? | Indefinite | "Bring the best user experience to its customers through innovative hardware, software, and services." (Apple) |
| **Vision** | Where is the product going in 5-10 years? | 5-10 years | "Every finance team closes the books in under 2 days with zero manual reconciliation." |
| **Strategy** | How will we win? | 2-3 years | "Land in mid-market B2B SaaS via the Stripe ecosystem, expand to ERP integrations, eventually serve enterprise." |
| **Roadmap** | What ships next? | 1 quarter to 1 year | "Q3: Xero integration. Q4: Audit log export. Q1: Multi-entity reconciliation." |

Confusing the layers is the most common vision failure. A "vision" that says "launch SSO in Q4" is a roadmap item. A "vision" that says "we exist to empower finance teams" is a mission statement.

The Product Vision lives in the second row -- specific enough to direct engineering choices today, abstract enough to outlast any single feature.

## Framework 1: Roman Pichler's Product Vision Board

The Product Vision Board is a one-page canvas with five blocks. It is the fastest way to draft a working vision before committing to a longer narrative.

```
+--------------------------------------------------------------+
| VISION                                                       |
| One sentence: the destination in 5-10 years                  |
+--------------------------------------------------------------+
| TARGET AUDIENCE  | NEEDS         | PRODUCT        | BUSINESS  |
| Who is this for? | What jobs and | What is the    | GOALS     |
|                  | pains does it | product (3-5   | How does  |
|                  | address?      | key features)? | it create |
|                  |               |                | value for |
|                  |               |                | us?       |
+--------------------------------------------------------------+
```

**Vision** (the single sentence at the top):

Format: "Help [target audience] [verb] [outcome] so that [bigger outcome]."

Example: "Help finance teams close the books in under 2 days with zero manual reconciliation so that finance becomes a strategic function rather than a clerical bottleneck."

**Target Audience:**

- Primary segment(s) by job-to-be-done, not demographics
- The most acute version of the pain (not "everyone in finance" -- "finance leads at 100-500 person B2B SaaS who close monthly")

**Needs:**

- Top 3-5 jobs, pains, gains from the Customer Profile (`discovery/value-proposition-canvas/`)
- The needs are the customer's, not the product's

**Product:**

- Top 3-5 capabilities (not features -- capabilities)
- Each capability addresses one or more needs

**Business Goals:**

- How the product creates value for the company
- 2-4 long-term goals (ARR target, market position, strategic moat)

## Framework 2: Geoffrey Moore's Elevator Pitch

From *Crossing the Chasm*. A single-sentence positioning statement that forces specificity.

```text
For [target customer]
who [statement of need or opportunity],
[product name] is a [product category]
that [statement of key benefit -- compelling reason to buy].
Unlike [primary competitive alternative],
our product [statement of primary differentiation].
```

Example:

> "For finance teams at 100-500 person B2B SaaS companies who lose 11 hours per close to manual reconciliation, Reconcile is a payment-data reconciliation platform that delivers a 2-day close with full audit traceability. Unlike spreadsheet-based reconciliation, Reconcile produces an audit-ready trail automatically and scales to 100K transactions per close."

**Use this format when:** You need a position statement for marketing, sales, board decks, or hiring conversations. The elevator pitch is the vision *compressed* -- if you cannot write the pitch, the vision is not yet sharp.

## Framework 3: Andy Raskin's Strategic Narrative

Andy Raskin's narrative framework (used by Salesforce, Drift, Yammer, Zuora) structures the vision as a 5-act story. The form is borrowed from screenwriting; the effect is that the audience identifies with the customer as protagonist and the product as the tool that helps them win.

**The 5 acts:**

1. **Name the undeniable change in the world.** A shift that everyone in the audience recognizes is real. ("Finance is being asked to be strategic, but spends 60% of its time on manual reconciliation.")
2. **Show the winners and losers of that change.** Who is benefiting? Who is being left behind? ("Finance teams who automate are seen as strategic partners. Teams stuck on spreadsheets are seen as cost centers.")
3. **Tease the promised land.** A future state that resonates emotionally. ("Imagine a finance function that closes in 2 days and spends 60% of its time on forward-looking analysis.")
4. **Identify the obstacles to the promised land.** Why is it hard to get there? ("Existing tools assume you have one payment processor. Reality: most companies have 3-7. No tool reconciles across them.")
5. **Position your product as the magic gift that overcomes the obstacles.** ("Reconcile unifies reconciliation across every payment processor, GL, and ERP -- so finance teams can finally make the leap.")

**Use this format when:** You need a vision narrative for sales pitches, board meetings, all-hands talks, or fundraising. The Raskin narrative is *emotional* in a way the Pichler board is not.

## Framework 4: Cagan's 10-Year Horizon

Marty Cagan (*Inspired*, *Empowered*) argues that a product vision should look 10 years into the future, not 1-3. The 10-year horizon does three things:

1. **Forces abstraction from current technology.** What you build in 10 years cannot rely on today's stack assumptions.
2. **Outlasts strategy cycles.** Strategy shifts every 2-3 years; vision endures.
3. **Aligns hiring and architecture.** A 10-year vision shapes who you hire and how you build.

**Cagan's vision