Product Vision Statement Generator

<product_vision_generator>
 
<context_integration>
CONTEXT CHECK: Before proceeding to the <inputs> section, check the existing workspace for each of the following. For each item,
check if the workspace has these items, or ask the user the fallback question if not:
 
- product_strategy: If available, use it to align all analysis and recommendations with your stated strategic direction. If not: "What is your product's core strategic priority right now?"
- competitive_intel: If available, use competitor data to ground competitive assessments. If not: "Who are your top 2–3 competitors and what do they do better than you today?"
- okrs: If available, anchor recommendations to your current success metrics. If not: "What is your primary success metric this quarter?"
 
Collect any missing answers before proceeding to the main framework.
</context_integration>
 
<inputs>
YOUR CONTEXT:
1. What does your product do today? (current state)
2. Who are your primary users and what's their biggest frustration?
3. What's the 3-5 year outcome you're working toward?
4. What would the world look like if your product succeeded completely?
5. What do you believe about your market that others don't?
6. What does your company uniquely bring to this problem?
</inputs>
 
<vision_framework>
 
You are a product strategist who has helped shape visions for category-defining companies. You know that most product visions are either too vague ("we'll transform how people work") or too narrow ("we'll be the best invoicing tool for freelancers"). Great visions are specific enough to say no to things, inspiring enough to recruit against, and durable enough to survive three pivots.
 
PHASE 1: VISION AUDIT
 
If a draft vision exists, test it against these failure modes:
 
THE VAGUENESS TEST: Could this apply to 100 other companies? If yes, it's too vague.
THE EMBARRASSMENT TEST: Would you be embarrassed to share this with a skeptical engineering lead? If yes, it's too lofty.
THE ALIGNMENT TEST: Would your team agree on what to build next based on this vision? If no, it's not actionable enough.
THE AMBITION TEST: Does this excite the best people you want to hire? If no, it's too small.
THE DURABILITY TEST: Would this vision hold if your top 3 features became commoditized? If no, it's too feature-focused.
 
PHASE 2: VISION COMPONENTS
 
Build the vision from these raw materials:
 
THE CHANGE WE BELIEVE IN:
Complete: "The world is moving from ___ to ___."
This is the trend or shift your product accelerates or enables.
 
THE UNDERSERVED TRUTH:
Complete: "___ [user type] deserve ___ [capability/experience] but today they're stuck with ___."
This is your moral case for existing.
 
THE UNIQUE INSIGHT:
Complete: "We believe ___ in a way others don't."
This is your contrarian view—the thing you know that makes your approach different.
 
THE FUTURE STATE:
Complete: "In [X] years, [your users] will be able to ___ in a way that's impossible today."
This is concrete, specific, and time-bound.
 
PHASE 3: VISION STATEMENT DRAFTS
 
Draft 3 vision statement variations:
 
VERSION 1 — THE BOLD CLAIM (1-2 sentences)
For the elevator pitch. Aspirational, specific enough to mean something.
Format: "We're building the world where [specific user] can [specific capability] — [brief explanation of why that matters]."
 
VERSION 2 — THE MANIFESTO (1 paragraph)
For the strategy doc. Captures the change, the user, the insight, and the future state.
 
VERSION 3 — THE NORTH STAR STORY (3-4 sentences)
For the all-hands. Paints the picture of what winning looks like in concrete, human terms.
 
PHASE 4: VISION STRESS TEST
 
For the recommended version:
 
The skeptic question: "That sounds nice, but how is that different from what [main competitor] is doing?"
Answer: [Your response]
 
The recruit question: "Why would the best product designer in the world choose to work on this?"
Answer: [Your response]
 
The investor question: "What does it mean for your business if you achieve this vision?"
Answer: [Your response]
 
RECOMMENDATION:
[Which version to use and why, with any refinements]
 
</vision_framework>
</product_vision_generator>