Defining a Strong Product Vision

A Good Vision Is Uncomfortable, a Bad Vision Is Forgettable

Product vision statements are the most written and least useful artifacts in product management. Every company has one. Almost none of them change behavior. They sit in strategy decks, get recited in all-hands meetings, and influence precisely zero daily decisions. The reason is not that vision statements are inherently useless. It is that most vision statements are written to be safe instead of true.

A good product vision should make at least some people in the room uncomfortable. It should describe a future that is ambitious enough to be uncertain, specific enough to guide decisions, and customer-focused enough to survive contact with reality. According to a study by Bain & Company, companies with clearly articulated and broadly understood strategies grow revenue 37% faster than those without. Yet a Gallup survey found that only 22% of employees strongly agree they understand their company's direction. The vision exists, but it does not land.

The Problem

Bad product visions share a pattern. They are either:

• Too vague to be actionable. "We empower people to do their best work" could describe any product in any category. It provides no guidance for what to build or what to say no to.
• Too tactical to be inspiring. "We will be the leading project management platform for mid-market companies" is a business goal, not a vision. It tells you where you want to be but not why it matters.
• Too consensus-driven to be distinctive. When a vision is workshopped by twenty people, it gets sanded down to something that offends nobody and inspires nobody.

The best product visions share different traits. They are grounded in a deep understanding of a customer problem. They describe a future state that does not yet exist. And they are specific enough that you can evaluate any proposed feature against them and get a clear signal.

How This Prompt Works

The Defining a Strong Product Vision prompt guides you through crafting a vision that meets four criteria:

• Lofty and inspiring enough to motivate the team through difficult quarters
• Realistic and attainable within a reasonable time horizon
• Constraint-free, describing the desired end state without prescribing the path
• Grounded in user problems, not technology capabilities or market positioning

You provide your product context, customer understanding, and strategic aspirations, and the prompt produces candidate vision statements with evaluation against each criterion.

When to Use It

• When founding or resetting the strategic direction of a product
• When your current vision no longer differentiates you from competitors
• When the team cannot articulate what the product is ultimately trying to achieve
• During leadership transitions when a new PM or CPO needs to establish direction

Common Pitfalls

• Confusing vision with mission. The mission is what you do today. The vision is what the world looks like when you succeed.
• Making the vision about your company instead of your customer. "We will be the market leader" is about you. "Every small business owner can focus on their craft instead of their accounting" is about the customer.
• Setting a vision once and never revisiting it. A good vision should be stable for years, but it should be re-evaluated annually to ensure it still reflects your best understanding of the customer and market.
• Treating vision-setting as a solo exercise. The PM or founder may author the vision, but it must be pressure-tested by the team who will execute it.

Sources

• Inspired by Marty Cagan covers how the best product leaders craft and communicate vision.
• Bain & Company: Strategy and Growth Research provides evidence that clear strategy accelerates growth.
• Product Talk: Product Vision Guide offers practical advice for crafting visions that are specific enough to be useful.