Skip to content

borghei/Claude-Skills / project-management/execution/product-vision

product-vision

Verified

Write the 5-10 year product vision as a vision board, narrative or elevator pitch, and stress-test it. Use when setting or refreshing long-range direction, or when strategy decks lack a shared picture of where the product is going.

assets/vision_board_template.md

View on GitHub
# Product Vision Board (Roman Pichler)

A one-page diagnostic. Fill every block. Cite evidence where possible.

---

**Product Name:** [...]
**Date:** [YYYY-MM-DD]
**Author:** [...]
**Version:** v[X.Y]
**Status:** Draft / Validated / Approved

---

## VISION

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

[Vision sentence]

**Evidence backing this vision:**
- Customer interviews: [link to `discovery/customer-interview-script/` outputs]
- JTBD workshop output: [link to `discovery/jtbd-workshop/` outputs]
- Value Proposition Canvas: [link]

---

## TARGET AUDIENCE

> Who is this product for? Defined by job-to-be-done, not demographics.

**Primary Segment:**

- Defined by: [shared job, role, context]
- Example customers: [names or types]
- Size of market: [TAM/SAM if known]
- Acuteness of pain: [why this segment specifically]

**Secondary Segments (lower priority):**

| Segment | Why secondary | Likely entry timing |
|---------|---------------|----------------------|
| [...] | [reason] | [year/phase] |
| [...] | [reason] | [year/phase] |

**Out of Scope (deliberately not targeting):**

- [Segment we are NOT building for, with reason]
- [...]

---

## NEEDS

> Top 3-5 jobs, pains, and gains in customer language. From `discovery/value-proposition-canvas/`.

| # | Need (customer's words) | Type | Source / Evidence |
|---|--------------------------|------|--------------------|
| 1 | [need] | Job / Pain / Gain | [interview, transcript link] |
| 2 | [need] | Job / Pain / Gain | [...] |
| 3 | [need] | Job / Pain / Gain | [...] |
| 4 | [need] | Job / Pain / Gain | [...] |
| 5 | [need] | Job / Pain / Gain | [...] |

---

## PRODUCT

> Top 3-5 capabilities. Not features -- capabilities. Each capability addresses one or more needs above.

| # | Capability | Addresses Need # | Maturity (current / 1yr / 3yr) |
|---|-----------|-------------------|----------------------------------|
| 1 | [capability] | 1, 2 | [maturity status] |
| 2 | [capability] | 1, 3 | [...] |
| 3 | [capability] | 2, 4 | [...] |
| 4 | [capability] | 5 | [...] |
| 5 | [capability] | 3, 5 | [...] |

**Distinction note:** "Capabilities" are durable -- they describe what the product enables. "Features" are the specific implementations of capabilities and change over time. Capability: "real-time notifications to where the customer works"; feature: "Slack integration".

---

## BUSINESS GOALS

> 2-4 long-term outcomes for the business. Specific where possible.

| # | Goal | Timeline | Measure |
|---|------|----------|---------|
| 1 | [e.g., $20M ARR] | Year 3 | ARR |
| 2 | [e.g., category leadership in mid-market] | Year 5 | Analyst recognition / market share |
| 3 | [e.g., 70%+ gross retention] | Year 2 | Cohort retention |
| 4 | [e.g., expansion to multi-entity] | Year 4 | Customer mix |

---

## VALIDATION SIGNALS

> How will we know the vision is working?

| Signal | Current state | 1-year target | Source |
|--------|----------------|----------------|--------|
| Adoption in primary segment | [...] | [...] | [...] |
| Customer NPS / love | [...] | [...] | [...] |
| Strategic positioning | [...] | [...] | [...] |

---

## REVIEW LOG

| Date | Reviewer | Changes |
|------|----------|---------|
| [YYYY-MM-DD] | [Name] | Initial draft |
| [YYYY-MM-DD] | [Name] | [diff] |

**Next review scheduled:** [YYYY-MM-DD] (annual cadence)
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall