defining-product-vision

Create product vision statements using frameworks from 101 product leaders.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill defining-product-vision-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defining-product-vision
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/defining-product-vision
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill defining-product-vision-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often write vague taglines or feature lists instead of real visions, leaving teams without a shared long-term direction. This Skill helps you craft a concrete, testable product vision grounded in insights from 101 product leaders at companies like Notion, Airbnb, Canva, and the New York Times. ## Core Features & Use Cases - Vision vs. strategy clarification: Distinguish vision (long-term aspiration), strategy (how to win), and roadmap (what to build) so each artifact serves its purpose. - Framework-based guidance: Apply criteria from leaders like Ebi Atawodi (lofty, realistic, tech-agnostic, problem-grounded) and Ben Williams (describe the user's world, not your product). - Mistake detection: Flag vague taglines, feature lists masquerading as vision, and statements that mention the product instead of the user's future. - Use Case: A head of product drafting a company vision statement uses this Skill to pressure-test it against the four criteria, rewrite it to describe the user's world in 5-10 years, and align executives on the result. ## Quick Start Help me write a product vision statement for my company and critique my current draft against proven vision frameworks.

Frequently Asked Questions about defining-product-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product vision statement?

Describe the user's world 5-10 years in the future without mentioning your product or company. Prefix the statement with 'In the future...' and ensure it is lofty, realistic, tech-agnostic, and grounded in a clear problem.

What is the difference between product vision and product strategy?

Vision is the long-term aspirational state you aim to enable for users, while strategy is the set of choices about where to play and how to win. Strategy sits between the vision and the tactical roadmap, forcing resource allocation decisions.

Why do most product vision statements fail?

Most fail because they are vague taglines that teams cannot elaborate on, feature lists describing what will be built, or statements that mention the product instead of the user's future. A vision that doesn't change team behavior is not useful.

How can I test if my vision statement is specific enough?

Ask whether a team member could make a good decision using only the vision as a guide, and whether you can elaborate on it in concrete terms. If executives cannot explain what the statement means in practice, it is a tagline, not a vision.

When should I use a prototype instead of a written vision document?

Use visual artifacts like mock-ups and prototypes when abstract documents fail to align stakeholders. Concrete visual forms help teams communicate and internalize the future state more effectively than text alone.