Mission / purpose
Why the organization or product effort exists at the broadest durable level. A product team may inherit this rather than own it.
Not a quarterly objective, feature list or delivery plan.
Product Management Foundations · Module 3 of 15
Product Vision and Strategy
Turn evidence into direction, without turning your roadmap into “strategy.”
You now have evidence about users and the market. The next challenge is deciding what future to pursue, where to focus, what not to do, and how to connect those choices to outcomes, bets, metrics and product work.
30 current learning unitsStrategic Layer DebuggerCoherence trace + two mini practicesReal lesson preview
The direct answer
Vision gives direction. Strategy makes choices.
A product vision describes a future worth moving toward. Product strategy turns that direction into choices about where to focus, which users, problems or advantages matter, what will not be pursued, and which assumptions make those choices plausible. Outcomes and metrics help observe progress; bets test ways to advance the strategy; the roadmap communicates current sequencing. None of those layers is a substitute for the others.
The chapter question
How do vision, strategy, outcomes, bets, metrics and roadmaps fit together, and how can I tell when my team has confused one layer for another?
Need the broad Product Strategy reference rather than this Foundations chapter? Use the Product Strategy topic.
You came from
Understanding Users and Markets
What evidence changes your assumptions?
You are here
Product Vision and Strategy
What direction and choices follow?
Next
Opportunity Discovery and Ideation
What opportunities could advance that direction?
Real CraftUp lesson
Why vision matters
Try the quiz questions taken directly from the published CraftUp lesson for this module.
Quick practiceThe guide continues below
Want another challenge? Practice another round.
Real CraftUp curriculum · no sign-up required
A compact strategy-coherence model
Separate the layers before you try to align them
Organizations use strategy vocabulary differently. Treat these labels as a practical way to separate durable purpose, desired future, choices, observable change, investment and execution, not as a universal hierarchy or rigid waterfall.
Product vision / future
A meaningful future state the product is trying to help create. It should give direction when choices compete.
Not a feature list, delivery commitment, metric target or mandatory fixed-horizon statement.
Strategic choice
A constrained choice about where and how to focus: target context, problem, approach, value model, advantage or deliberate exclusions.
Not a generic ambition such as “grow faster” or a framework filled in without a real trade-off.
Outcome / objective
An observable change that would indicate meaningful progress for users, the business or the system.
Not automatically the strategy. The strategy should explain why this outcome deserves focus and how value is expected to be created.
Bet / theme
A bounded area of investment believed to advance the strategy while important uncertainty remains.
Not proof that the approach will work. A bet can fail while the broader strategic direction remains sound.
Metric
A measurement used to observe progress, health, guardrails or trade-offs.
Not the strategy. A dashboard can show what changed without deciding what the team should choose next.
Roadmap
A communication of current intended sequencing, direction, bets or initiatives.
Not an immutable contract and not a substitute for the strategic rationale behind the sequence.
Tactic / initiative
A specific action or implementation approach used to advance a bet or outcome.
Not automatically a strategic choice. Tactics can change as the team learns.
A useful direction is iterative: evidence can change the vision, strategic choices can change the candidate bets, and results can reopen earlier assumptions. The model is for checking coherence, not enforcing a fixed sequence.
10× learning asset
Strategic Layer Debugger
Classify each statement before you read the explanation. Then ask what layer is missing and why the current wording may be strategically incoherent. The goal is reasoning, not memorizing vocabulary.
Statement 1
“Increase activation from X to Y.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Statement 2
“Launch a mobile app.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Statement 3
“Become the world's best collaboration platform.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Statement 4
“Focus on independent accounting firms that coordinate recurring client-close workflows, rather than generic SMB collaboration.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Statement 5
“Reduce month-end coordination failures.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Statement 6
“Launch the assistant in Q2.”
Choose a layer to reveal the reasoning. The exercise grades the decision logic, not terminology alone.
Coherence check
A polished plan can still be strategically empty
Run these questions across a vision slide, OKR, roadmap theme, metric target or initiative. If the answers do not connect, the problem may be a missing layer rather than weak wording.
- 1
What layer is this statement or artifact operating at?
- 2
What layer should logically precede it?
- 3
What choice does it constrain?
- 4
What evidence or assumptions support it?
- 5
What trade-off or non-goal follows from it?
- 6
What outcome or signal would show whether progress is happening?
- 7
What evidence would make the team reconsider the choice?
Worked example · explicitly hypothetical
Trace one direction from evidence to roadmap consequence
The example below uses a B2B workflow product for small accounting firms so every layer can be inspected without relying on a named company story.
Evidence
Suppose small accounting firms coordinate recurring client-close work across email and spreadsheets, status collection creates repeated manual effort, several roles participate, generic project tools feel broad for the workflow, and accuracy plus auditability matter. This is a hypothetical learning case, not claimed market research.
Weak “vision”
“Be the best AI project management tool for accountants.” The technology leads the statement, “best” is undefined, the future value is unclear, and the wording does not help resolve trade-offs.
Better future direction
“Accounting teams can complete recurring client-close coordination without chasing status across disconnected tools.” This is one possible future direction, not a universal vision formula.
Strategic choice
Focus first on small accounting firms with repeatable multi-client close workflows, and compete through structured recurring coordination plus client evidence capture rather than generic project-management breadth.
Non-goals
For the current period: generic software teams, a full accounting ledger, and a broad all-purpose collaboration suite. Explicit exclusions make the focus inspectable.
Outcome
More target teams complete recurring close workflows with less manual follow-up. This describes desired change without inventing a percentage.
Strategic bet
Invest in a reusable client-close workflow with status and evidence handoff. It is a bet because the team does not yet know whether the approach will materially improve the outcome.
Possible measures
Workflow completion, manual follow-up burden, repeated use and target-account retention could all be informative. None is declared the universal North Star Metric.
Roadmap consequence
Sequence bets that support recurring close coordination ahead of generic chat, unrelated AI features or broad custom project templates unless new evidence changes the reasoning.
Reversal evidence
Reconsider the strategy if target users do not repeatedly experience the problem, the workflow value fails to materialize, another segment shows materially stronger fit, or constraints make the chosen approach untenable.
Mini practice · strategy or wish list?
Which plan actually constrains decisions?
Plan A
- Launch AI.
- Redesign onboarding.
- Add integrations.
- Build a mobile app.
- Improve analytics.
What strategic choice can you infer?
Possibly none. This is a list of outputs or bets without a shared target, rationale, trade-off, non-goal or theory of value creation.
Plan B
- Target a specific high-friction workflow.
- Explain why the context matters now.
- Choose a differentiated approach.
- Name current non-goals.
- State the supporting assumptions and evidence.
- Define the desired outcome.
Why is this more strategic?
It creates boundaries. Teams can use the choices to reject plausible alternatives, select bets and explain why a local tactic belongs or does not belong.
Outcomes, metrics and OKRs
Measurement observes strategy; it does not create it
Outputs describe what the team ships or does. Outcomes describe observable change. Metrics help observe progress, health or trade-offs. OKRs can express objectives and measurable results after direction is sufficiently clear. None automatically tells the team which strategic choice to make.
A North Star Metric can be useful in some contexts, but there is no universal requirement that every product strategy has exactly one. When metric selection itself becomes the job, use the North Star Metric Finder.
Strategy revision
Stable direction does not mean immutable choices
- Retain
- when evidence still supports the assumptions and progress remains plausible.
- Adjust bets
- when the direction still looks sound but one approach fails.
- Revise strategy
- when material assumptions or context change enough that the current choices no longer look coherent.
- Revisit vision
- when the desired future itself no longer reflects reality or purpose.
Technology changes assumptions, not the need for strategy
Treat AI as a strategic input, not a strategy substitute
AI can change capability cost, user expectations, build-versus-buy choices, differentiation, data and privacy constraints, competitive dynamics and product interaction models. If that changes an assumption underneath the strategy, revisit the assumption. It does not remove the need for a coherent user problem, explicit choices, trade-offs or evidence.
Common strategic category errors
Diagnose the missing question instead of polishing the slide
Vision as slogan
Example: “Be the most loved platform.”
Better question: What meaningful future should become true, and how would that future help us recognize aligned versus misaligned choices?
Strategy as ambition
Example: “Grow faster.”
Better question: Where will we focus, how do we expect to create value, and what credible alternative are we choosing not to pursue?
Strategy as feature list
Example: “Launch AI, mobile, integrations and analytics.”
Better question: What shared problem, target context and strategic rationale make these initiatives belong together?
Goal as strategy
Example: “Increase retention.”
Better question: Why does retention deserve investment here, for whom, and which strategic choices are expected to change it?
Roadmap as strategy
Example: “Q1 onboarding, Q2 mobile, Q3 analytics.”
Better question: What choices and trade-offs explain why this sequence is the right current expression of the strategy?
Framework as strategy
Example: “The canvas is complete.”
Better question: Which real choice, non-goal, assumption and reversal condition did the framework make explicit?
Company goal as product strategy
Example: “Grow enterprise revenue.”
Better question: How are product choices expected to create sustainable user and business value or satisfy a material constraint?
Full curriculum
30 lessons, grouped by the strategic question they serve
The real lesson order remains unchanged. These phases add orientation without pretending that the first lesson titles are a procedural strategy framework.
Phase 1, Separate direction from execution
What layer are we actually discussing?
- 1Why vision matters
- 2Mission vs vision vs strategy vs tactics
- 3What makes a strong product vision
- 4Examples of great product visions
- 5How to craft your first product vision
- 6Vision vs roadmap: keeping direction while staying flexible
Phase 2, Connect direction to market and business context
What choices make the direction specific?
- 7Value proposition basics
- 8What is positioning and why it matters
- 9Aligning product strategy with company goals
- 10Strategic frameworks for PMs
Phase 3, Translate choices into outcomes and bets
How do we express progress without turning metrics into strategy?
- 11Understanding outcome-driven thinking
- 12What is a North Star Metric?
- 13OKRs for product teams
- 14Strategic themes and bets
- 15Balancing short-term vs long-term priorities
Phase 4, Adapt and communicate strategy
How does strategy survive organizational reality and new learning?
- 16When to pivot strategy
- 17How to communicate product vision to your team
- 18How to communicate product vision to executives
- 19Strategy in startups vs corporates
Phase 5, Defend coherent choices
What makes strategy more than a plan?
- 20Case: Netflix's strategy evolution
- 21What is competitive advantage?
- 22The role of user insight in strategy
- 23The danger of feature factories
- 24Tools for strategy documentation
Phase 6, Keep strategy alive
What evidence should cause the system to change?
- 25How AI changes product strategy
- 26Understanding vision-market fit
- 27What is strategic prioritization?
- 28Linking vision to roadmap
- 29Common strategy mistakes
- 30When great visions die
Use the specialist owner when the job changes
Learn the layers here; create and operate the artifacts elsewhere
Broad Product Strategy reference
Use the topic owner for broad concept exploration and practitioner reference beyond this beginner chapter.
Create the strategy artifact
Use the One-Pager when the job becomes writing target, choices, non-goals, rationale, assumptions and reversal conditions into one inspectable artifact.
Prioritize within the strategy
Once direction constrains the candidate set, use the prioritization owner to decide which current opportunity or bet deserves capacity.
Communicate bets and sequencing
Use the roadmap artifact after strategic direction is clear enough to explain current sequencing without pretending the roadmap is the strategy.
Strategy interview preparation remains a different hiring-format job. Deeper strategic choice under constraints belongs to the later Strategic Decision-Making for PMs chapter, while measurement depth belongs to Metrics, Analytics and Data Literacy.
Next learning step
Direction creates boundaries. Discovery searches inside them.
Strategy decides where and why to focus. The next chapter asks a different question: given this direction, where is the most important opportunity to improve the user's situation?
