contextgo PM Product Strategy
Use this skill to move from broad ambition to a set of clear strategic choices.
What strategy means here
Product strategy is not a mission statement and not a backlog.
It is a coherent answer to:
- who we are serving
- which problem or outcome matters most
- where we will focus
- what we will not do
- how this should shape the roadmap
Use when
- A team has a broad initiative but weak strategic focus.
- Leadership wants direction, not yet a detailed execution plan.
- A roadmap exists, but the reasons behind it are muddy.
- A product is being repositioned for a new segment, market, or growth stage.
Do not use when
- The strategy is already explicit and validated.
- The request is a narrow tactical feature.
- The team only needs execution planning.
Strategy failures to avoid
- turning a feature list into "strategy"
- copying competitor moves without stating a deliberate choice
- claiming to serve everyone
- writing goals without tradeoffs or non-goals
- mixing long-term strategic direction with this quarter's implementation backlog
The strategy frame
Build the strategy through five lenses.
1. Market and customer
Clarify:
- target segment
- buying or usage context
- strongest unmet need
- why this segment matters now
If several segments are in play, force a primary target. Secondary targets are allowed, but only after the primary focus is explicit.
2. Strategic problem or opportunity
State the core problem in business and customer terms.
Good:
Mid-market operations teams cannot trust cross-channel reporting quickly enough to act during weekly planning, limiting adoption and expansion.
Bad:
We need better analytics.
3. Unique angle
Explain why this product should win or matter.
Possible angles:
- speed
- workflow depth
- distribution advantage
- ecosystem fit
- compliance or trust
- lower cost to value
If the angle is not differentiating, call that out instead of pretending there is one.
4. Core choices
A strategy must include explicit choices:
- where to invest
- where not to invest
- which customer behavior you want to change
- which metrics should move first
This is the most important section. If there are no tradeoffs, there is no strategy.
5. Roadmap direction
Strategy should shape the roadmap without collapsing into task sequencing.
Define:
- 2-4 strategic bets or themes
- why each exists
- what evidence supports it
- what would invalidate it
Workflow
Phase 1: Gather the frame
Collect:
- product description
- market context
- customer signals
- business goals
- current constraints
If gaps are large, mark the strategy as provisional.
Phase 2: State the strategic diagnosis
Summarize:
- current situation
- main customer problem
- why it matters commercially
- why now
This is the "what is really going on" section.
Phase 3: Define the strategic choices
Write the choices as commitments and exclusions.
Examples:
- prioritize admin trust and reporting speed over broad dashboard customization
- focus on mid-market operations leaders before enterprise procurement buyers
- invest in adoption and expansion before new top-of-funnel acquisition
Phase 4: Shape bets and signals
Turn choices into strategic bets.
Each bet should include:
- intended customer or business outcome
- leading indicator
- confidence level
- key assumption
Phase 5: Draw the boundary to execution
End with guidance for what should happen next:
- more discovery
- company research
- roadmap planning
- PRD drafting
Do not over-specify implementation inside the strategy artifact.
Output format
Return:
1. Strategic context
- product
- market
- target segment
- current pressure or opportunity
2. Strategic diagnosis
- core problem
- why it matters
- evidence strength
3. Strategic choices
- where to focus
- where not to focus
- major tradeoffs
4. Strategic bets
- bet
- outcome
- leading indicator
- assumption
- confidence
5. Roadmap direction
- now
- next
- later
6. Open questions
- the few issues that could still change strategy materially
Use together with
pm-company-researchwhen market or competitor context is still thinpm-opportunity-solution-treewhen strategy must branch into multiple opportunity spacespm-roadmap-planningwhen the strategy is ready to be sequenced into initiative-level planning