Write a product vision statement with evidence

Visions That Ship Features, Not Wall Posters

Vague vision statements produce wall posters; specific ones produce decisions. Marty Cagan's product vision writing and Paul Graham's essay on doing great work both argue that visions must be specific enough that engineers can evaluate tradeoffs against them — "we help teams collaborate" is useless; "engineers in 50-500 person teams complete incident response 10x faster" is actionable.

How the Write a product vision statement with evidence Prompt Works

The prompt produces a 500-word vision with six sections including the future state, problem with evidence, solution capabilities, proof points, and explicit non-goals. The "decision the vision helps us make tomorrow" output is the usefulness test — if the vision doesn't help a prioritization call this week, it's poetry.

When to Use It

• The team cannot articulate the long-term product direction.
• A new leader is establishing product strategy from scratch.
• A board or investor is asking for the 3-year vision.
• A prioritization debate keeps stalling because the destination is unclear.
• A cross-functional team needs alignment on direction.

Common Pitfalls

• Abstract language. "Empower" and "transform" help nobody. Replace with specific customer behavior.
• No evidence. A vision without customer research is wishful thinking.
• No non-goals. Without explicit non-goals, every stakeholder reads their own pet project into the vision.

Sources

• Product Strategy Overview — Silicon Valley Product Group
• How to Do Great Work — Paul Graham
• Ten Principles of Product Teams — Silicon Valley Product Group
• The Product Strategy Stack — Reforge