product-strategy-session
Orchestrate positioning, discovery, and roadmap planning into a validated product strategy in 2-4 weeks.
- Guides teams through six structured phases: positioning and market context, problem framing and validation, solution exploration, prioritization and roadmap planning, stakeholder alignment, and execution planning
- Includes decision points after problem validation and solution exploration to adapt the workflow based on uncertainty; skip discovery or experiments if assumptions are already validated
- Orchestrates 15+ component and interactive skills (positioning workshop, problem framing canvas, opportunity solution tree, prioritization advisor, epic breakdown, and others) into a cohesive end-to-end process
- Designed for cross-functional participation (PM, design, engineering, leadership, sales, customer success) to build shared mental models and prevent solo PM exercises that lack team buy-in
Purpose
Guide product managers through a comprehensive product strategy session by orchestrating positioning, problem framing, customer discovery, and roadmap planning skills into a cohesive end-to-end process. Use this to move from vague strategic direction to concrete, validated product strategy with clear positioning, target customers, problem statements, and prioritized roadmap—ensuring alignment across stakeholders before committing to execution.
This is not a one-time workshop—it's a repeatable process for establishing or refreshing product strategy, typically spanning 2-4 weeks with multiple touchpoints.
Key Concepts
What is a Product Strategy Session?
A product strategy session is a structured, multi-phase process that takes a product from strategic ambiguity to validated direction. It orchestrates:
- Positioning & Market Context — Define who you serve, what problem you solve, and how you're differentiated
- Problem Discovery & Validation — Frame and validate customer problems through research
- Solution Exploration — Generate opportunity solutions and prioritize based on impact
- Roadmap Planning — Sequence epics and releases based on strategy
Why This Works
- Structured discovery: Prevents jumping to solutions before understanding problems
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1Kuser-story-mapping
Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.
1.1K