Write a product vision statement with evidence
Storytelling
0 uses
Updated 4/17/2026
Description
Your product vision statement is vague poetry and the team can't ship against it. This writes a 3-year vision statement grounded in evidence — target customer, problem, solution shape, proof points — so engineers can evaluate tradeoffs against it.
Example Usage
You are writing a 3-year product vision for {{product_name}}. Our current product: {{current_product}}.
## Structure
### 1. The future state (1 paragraph)
In 3 years, {{target_customer}} will use {{product_name}} to {{core_outcome}}. The experience feels like {{experience_description}}. The outcome they walk away with is {{measurable_outcome}}.
### 2. The customer (2-3 sentences)
Who specifically this is for. Named persona, company size, trigger event for adoption.
### 3. The problem (1 paragraph)
Why today's solutions (including ours) fall short. Evidence: customer research, behavior data, alternatives they use.
### 4. The shape of our solution (1 paragraph)
The 3-4 capabilities that define our vision. Not features — capabilities customers will experience.
### 5. The proof points (bulleted)
How we'll know we're making progress:
- Metric 1 (growth)
- Metric 2 (engagement)
- Metric 3 (customer love)
- Metric 4 (competitive position)
### 6. What this vision is NOT
3 things we are explicitly not doing, with brief rationale.
## Output
1. Filled vision statement (~500 words total)
2. The 3 capabilities ranked by confidence level
3. The 1 proof point most likely to be challenged
4. The decision the vision helps us make tomorrowCustomize This Prompt
Customize Variables0/6
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources