--- title: "If Your Product Vision Cannot Rule Anything Out, It Is Not Doing Its Job" description: "A product vision should do more than describe an ambitious destination. It should constrain choices, expose the beliefs behind the strategy, and make clear which attractive opportunities do not belong." author: "Kody Everson" url: "https://theipp.org/insights/If-Your-Product-Vision-Cannot-Rule-Anything-Out-It-Is-Not-Doing-Its-Job" date: "2026-07-01T11:34:29.826Z" --- # If Your Product Vision Cannot Rule Anything Out, It Is Not Doing Its Job ## Summary A product vision should do more than describe an ambitious destination. It should constrain choices, expose the beliefs behind the strategy, and make clear which attractive opportunities do not belong. ## Main content The average product visions I see, “Become the leading platform for X.”, “Deliver seamless experiences for every customer.” These statements may be ambitious. They may be motivating. They may even describe something worth achieving. But they are rarely useful visions. Most are goals, aspirations, or promises written in elevated language. They describe an outcome the organisation hopes to reach, but offer little guidance about the future it is deliberately choosing or the alternatives it is willing to reject. That distinction matters because a goal and a vision do fundamentally different jobs. > A goal tells you what success looks like. A vision tells you what kind of future is worth building. A useful vision also makes clear that some otherwise attractive futures are not the future you have chosen. When teams confuse goals with vision, they create statements that inspire briefly but guide almost nothing. ## The Test a Product Vision Must Pass Ask one question: What does this vision help us rule out? A goal aggregates effort toward an outcome, whereas a vision discriminates between different directions that may all appear reasonable in isolation. “Grow active users to ten million” is a goal. It can be achieved through better products, aggressive notifications, acquisitions, geographic expansion, pricing changes, dark UX patterns, or incentives that attract low-value usage. The goal has no opinion about which path is right though, tt only measures whether the number is moved. A vision should have an opinion. Consider the difference between: "Grow the number of active buyers" and "Create a world where anyone can find and buy almost anything they need in one place." The first tells you what to increase. The second describes a future to build. That future creates direction. It favours breadth over curation, it directs blue sky thinking over control, holistic infrastructure over individual category optimisation, and convenience over exclusivity. It makes some opportunities more strategically coherent than others. A vision is useful because it helps an organisation choose between such futures before those choices can then appear as individual roadmap debates. This does not mean every vision must reject specific backlog items. Vision operates at a higher altitude than quarterly prioritisation. It should, however, rule out classes of direction. If almost any product, market, customer, or business model could fit beneath your vision, the statement is not providing direction. It is providing generic cover. ## Vision, Strategy, Bets and Goals Are Not the Same Thing Much of the confusion around product vision comes from asking one statement to perform several different jobs. A stronger strategic system consists of four unique components: - **Vision** describes the future you are choosing. - **Strategy** explains why you believe that future matters and why your organisation can create it. - **Bets** (or initiatives) are the specific paths you pursue to move toward that future. - **Goals** measure whether those bets are producing meaningful progress. For example: - The vision may be a future in which small businesses can manage their finances without specialist knowledge. - The strategic thesis may be that automation, embedded financial services, and real-time data will make this possible and that the company has exclusive access to the workflows required to deliver it. - The bets may include automated cash-flow forecasting, embedded lending, intelligent invoicing, and proactive tax preparation. - The goals may include adoption, retention, forecast accuracy, time saved, or reductions in financial administration. Each layer answers a different question. - **Vision:** What future are we trying to create? - **Strategy:** What must be true for us to create it? - **Bets:** Where will we act? - **Goals:** How will we know whether we are progressing? Clarity between these layers allows an organisation to learn and make mistakes without losing direction. A bet can fail while the vision remains sound. Several bets can fail while the strategic thesis remains credible. ## What a Useful Vision Must Contain A vision that genuinely shapes product decisions needs more than aspiration. Three characteristics separate a useful vision from one that is merely decorative. ### 1\. It describes a changed world, not a changed metric A vision should describe how a customer experience, market, organisation, or system will be meaningfully different because the product exists. “People can manage their money without thinking constantly about money” describes a changed world. “Increase customer deposits by forty per cent” describes a changed metric. The metric may be commercially important. It may even provide evidence that the company is moving toward its vision. But it is not the vision itself. Metrics expire. They are revised when targets are met, missed, or overtaken by new priorities. A vision should survive multiple planning cycles (or ideally for the life of the product or company) because it describes a longer-term direction rather than a temporary performance threshold. A simple test is to remove your company’s name and KPIs from the statement. Does it still describe a meaningful future? If not, you probably have a goal. ### 2\. It excludes plausible alternatives A useful vision does not merely say that the future should be better, easier, faster, or more empowering. Almost every organisation wants those things. It chooses a particular form of better. Consider a company providing management tools for independent contract professionals. Several futures might be attractive: - Become the cheapest administrative platform. - Become the most comprehensive business-management suite. - Become the trusted financial partner for self-employed workers. - Become a marketplace connecting professionals with customers. - Become the infrastructure layer used by other platforms. Each could support a successful business but they are not interchangeable. A real vision makes one direction more coherent than the others. It creates a basis for deciding which capabilities to build, which customers to prioritise, which partnerships to pursue, and which revenue opportunities to decline. This is what vague visions avoid. They are written to preserve optionality and secure agreement. Every executive can interpret the words in a way that supports their existing priorities. The result sounds aligned while leaving the underlying choices unresolved. A vision that accommodates every plausible strategy has not created alignment. It has postponed disagreement. ### 3\. It rests on beliefs that evidence can challenge The vision itself describes a desired future. The strategic thesis beneath it contains assumptions about why that future matters and how it might become possible. Those assumptions should be challengeable. You may believe that: - customer behaviour is moving in a particular direction; - a technology will become sufficiently capable or affordable; - regulation will open or close part of a market; - an underserved group will pay for a different experience; - your organisation has an advantage competitors cannot easily reproduce. These are not certainties. They are beliefs about the future. A serious product strategy makes them explicit and identifies what evidence would weaken them. This does not mean demanding proof before acting. Product vision necessarily involves uncertainty. The future cannot be validated in advance. But there is a difference between acting under uncertainty and constructing a statement that no possible evidence could challenge. If the organisation would continue pursuing the same vision under every imaginable market condition, the vision is not a strategic choice. ## How Weak Visions Fail in Practice A weak vision rarely produces a visible crisis. It tends to fail quietly through hundreds of individually reasonable decisions leading in the wrong direction. One team responds to a large customer request. Another pursues an acquisition opportunity. A third improves an underperforming funnel. A fourth builds a capability needed by a powerful stakeholder. Each decision can be justified. Each business case may be positive. Each initiative may improve a metric. Yet the product gradually becomes a collection of locally sensible features that do not add up to a coherent whole. The vision should provide an independent basis for choosing between these opportunities. Instead, prioritisation defaults to urgency, political influence, revenue proximity, or whichever stakeholder has prepared the strongest presentation. Discovery becomes equally fragmented. Teams investigate isolated customer problems without a shared view of the future they are trying to create. They generate insight, but the organisation lacks a clear basis for determining which insights matter strategically. Decision rights also deteriorate. Leaders often say they want empowered teams, but empowerment requires boundaries. Teams can only make consequential decisions independently when they understand the direction and the limits of acceptable action. A useful vision constrains the decision space enough to make delegation safe. Without that constraint, significant decisions return to senior leaders because teams cannot confidently determine whether an opportunity belongs. Leadership becomes the integration layer holding a portfolio together. The organisation may call this governance. Usually, it is compensation for unclear direction. ## How Vision Should Shape Daily Product Practice A vision that lives only in a deck is not yet functioning as a vision. It becomes real when it changes how decisions are made. ### Prioritisation Most prioritisation methods can rank opportunities by reach, impact, confidence, effort, revenue, risk, or customer value. They cannot determine whether an opportunity moves the organisation toward the future it has chosen. That is the role of vision and strategy. When two opportunities are commercially attractive, the answer should not always be to select the one with the higher value or prioritisation score. One may deepen the company’s strategic position while the other pulls the product toward a different business. A useful vision does not replace analysis. It gives the analysis direction. ### Decision rights A clear vision allows leaders to move decisions closer to the teams with the relevant information. Teams do not need approval for every choice when they understand: - the future the organisation is pursuing; - the customers and problems that matter most; - the strategic beliefs supporting that direction; - the boundaries they should not cross. This is why vision is not merely a communications artefact. It is part of the organisation’s operating system. Clear direction enables decentralised judgment whereas vague direction creates continued escalation. ### Outcome accountability Teams should be accountable for outcomes that connect to the longer-term direction, not merely for shipping features or moving isolated numbers. A metric can improve while the product moves away from its intended future. Engagement can rise because notifications became more aggressive. Revenue can grow because the company accepted bespoke work that weakens the platform. Conversion can improve because choice was reduced in a way that damages long-term trust. The vision provides the context required to distinguish progress from movement. A strong product system should allow leaders to trace a line from: - the vision; - to the strategic thesis; - to the current bets; - to team-level outcomes; - to the evidence being collected. When that line cannot be traced, the artefacts are operating independently. The vision is decoration, the strategy is narrative, the roadmap is negotiation, and the metrics are reporting activity rather than direction. ## Audit the Vision You Already Have Product leaders do not necessarily need another vision workshop. They need to ask harder questions of the existing vision. Start with these: ### What future are we choosing? Describe the change you want to create in the world, market, system, or customer experience. Do not describe your desired market position. Do not use a KPI. Do not default to words such as seamless, leading, innovative, trusted, or empowering unless they specify something meaningful. What will genuinely be different if you succeed? ### What attractive alternatives are we rejecting? A vision is a choice between plausible futures. Name the customers you will not prioritise, the business models you will not pursue, the capabilities you will not become known for, or the types of opportunity that may be valuable but do not belong to your direction. If leaders are unwilling to name anything the vision excludes, they have probably not made a strategic choice. ### What must be true for this direction to remain credible? Identify the beliefs beneath the vision. What do you believe about customers, technology, competition, regulation, distribution, economics, or organisational advantage? What evidence would strengthen those beliefs? What evidence would force you to reconsider them? ### Would the vision survive the failure of our current bets? A vision should not be a disguised description of one feature, channel, technology, or product mechanic. Current bets are possible paths, not the destination itself. If one failed experiment would make the vision irrelevant, the statement is probably too narrow. If no amount of failed experimentation or market evidence could ever challenge it, it is probably too vague. The right altitude is broad enough to permit learning but specific enough to create direction. ## Stop Asking Whether the Vision Is Inspiring The standard question in vision workshops is often: **Does this feel inspiring?** It is not a useless question. People are unlikely to commit to a future they find meaningless, but inspiration is an insufficient standard. A more valuable question is: **What will we do differently because this is our vision?** What will receive more investment? What will receive less? Which customer will take precedence when needs conflict? Which capability must become exceptional? Which attractive opportunities will we decline? Which decisions can now be delegated because the boundaries are clearer? If the vision changes none of these things, better wording will not fix it. The organisation does not have a communication problem. It has simply avoided making a choice. ## Conclusion The difference between a vision and a goal is not ambition, eloquence, or time horizon. It is function. A goal measures progress. A vision describes the future an organisation has chosen to create. Strategy explains why that future is worth pursuing and how the organisation might reach it. Bets test possible paths. Goals reveal whether those bets are producing progress. A useful vision does not prescribe every product decision. But it gives those decisions a direction. It makes some opportunities more coherent and others incompatible. It allows teams to act independently without allowing the product to become accidental. Most product visions fail because they are written to maximise agreement rather than force a choice. They promise a better future without specifying which better future the organisation actually means. The strongest visions are different. They describe a particular future, rest on beliefs that evidence can challenge, survive the failure of individual bets, and give teams permission to say no to work that does not belong. If your vision has never caused you to reject something attractive, it is not yet doing its job. ## Related pages - [Insights](https://theipp.org/insights.md) - [Product Profile](https://theipp.org/tools/product-profile.md) - [Standards](https://theipp.org/standards.md)