product-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
Security Assessment
About product-strategy-session
A workflow skill that guides product managers through an end-to-end product strategy session, orchestrating positioning, problem framing, customer discovery, and roadmap planning into one cohesive process. It is designed to move a product from vague strategic direction to a concrete, validated strategy with clear positioning, target customers, problem statements, and a prioritized roadmap, aligning stakeholders before execution. The process is framed not as a one-time workshop but as a repeatable practice for establishing or refreshing strategy, typically spanning two to four weeks with multiple touchpoints.
Work runs across six phases. Phase 1 covers positioning and market context via a positioning workshop, proto-personas, and jobs-to-be-done mapping. Phase 2 handles problem framing and validation with a problem framing canvas and a formal problem statement, plus optional customer journey mapping. Phase 3 explores solutions through an opportunity solution tree (or a Lean UX canvas alternative), epic hypotheses, and optional user story mapping. Phase 4 addresses prioritization and roadmap planning. Each phase names the component or interactive sub-skill to use, suggested participants, durations, and outputs, and includes decision points that route to additional discovery interviews when customer context or problem validation is insufficient, adding roughly a week each.
When run as a guided conversation, it defers to a workshop-facilitation skill as the interaction protocol, which governs the session heads-up and entry modes, one-question turns, progress labels, pause and resume behavior, and numbered recommendations; this file itself owns the workflow sequence and domain outputs and wins on conflicts. Use it when launching a new product or major initiative, during annual or quarterly planning, when repositioning, or when onboarding product leaders. It is explicitly not for cases where strategy is already validated, for tactical feature additions, or without executive sponsorship. A template.md provides the full fill-in structure.
FAQ
How long does a strategy session take?
It is a repeatable process rather than a single workshop, typically spanning two to four weeks with multiple touchpoints, and the phases are laid out across Week 1 and Week 2.
What are the phases of the workflow?
It orchestrates six phases including positioning and market context, problem framing and validation, solution exploration, and prioritization and roadmap planning, each with named sub-skills, participants, durations, and outputs.
When should this workflow NOT be used?
Avoid it when strategy is already clear and validated, for tactical feature additions with no strategic shift, or when you lack executive sponsorship, because the strategy will not stick.
What happens if the problem is not validated at a decision point?
The decision points route you to run customer discovery interviews using the discovery-interview-prep skill, validating with five to ten customers and iterating the problem statement, at a time impact of about one week.
How are guided conversations facilitated?
When run as a guided conversation it uses the workshop-facilitation skill as the interaction protocol for entry modes, one-question turns, progress labels, and pause and resume, while this file defines the workflow sequence and wins on conflicts.
Install product-strategy-session
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
deanpeters/product-manager-skills