| name | product-strategy-operator-playbook |
| description | A 5-phase procedural playbook to develop a product strategy and build organizational alignment. Use this when the team doesn't understand "the why" behind a roadmap, when resources are spread too thin, or when shifting a product from incremental improvements to a new growth trajectory. |
Product Strategy Operator Playbook
Product strategy sits between your mission/vision and your execution plan (roadmap). It is the act of forcing choices to deploy scarce resources for maximum impact. This playbook demystifies strategy, turning it from a "mystical gene" into a repeatable 8-12 week process that achieves "resonance" between your product and the market.
The Strategy Definition
A valid product strategy must include:
- Strategic Pillars: A handful of focus areas (ideally 3).
- Explicit Non-Focus: A list of areas you are intentionally ignoring.
- The Why: The logic and data justifying these choices.
Phase 1: Preparation (4 Weeks)
Gather inputs to ensure the strategy is defensible and grounded in reality.
1. Form the Strategy Working Group
Assemble a core team: PM (Lead), Engineering Lead, Design Lead, and Data Lead. This group collaboratively builds the strategy to ensure cross-functional buy-in from day one.
2. Aggregate Insights
Assign specific data-gathering tasks to the working group:
- Behavioral Insights: Meta-analysis of historical data, feature launches, and usage patterns.
- UXR Meta-Analysis: Synthesis of soft signals from research, customer service, and social channels.
- Leadership Interviews: Conduct "The Fruit Story" interviews. Ask leaders: "What does success/failure look like?", "What are your pet ideas?", and "What principles should we keep in mind?"
- Competitive Analysis: Map competitors and identify their "angles of investment" based on recent releases.
