Product Strategy Session

Skill Overview

Product Strategy Session is an end-to-end strategic workflow that guides product managers through “product positioning → problem validation → solution exploration → roadmap planning → executive alignment → execution” within 2–4 weeks, helping teams establish a validated direction before investing in development.

Use Cases

1. The team has a large backlog but lacks strategic direction, and leadership requires a credible product strategy before a review.
2. The team needs to progress from positioning and customer discovery to a roadmap that everyone genuinely supports, building alignment between execution teams and management on “what to do and why.”
3. A new product or major initiative is being launched; quarterly or annual planning is underway; a product is being repositioned; or a new product leader needs to align the strategy after taking over.

Core Features

1. Six-stage structured workflow orchestration: Positioning and market context, problem framing and validation, solution exploration, prioritization and roadmap planning, stakeholder alignment, and execution planning. Each stage clearly defines participants, duration, and deliverables, and orchestrates 15+ sub-skills, including positioning workshops, JTBD, problem framing canvases, Opportunity Solution Trees, and RICE prioritization.
2. Built-in decision points and validation loops: Decision points are included for both problem validation and solution testing. When customer evidence is insufficient, the workflow automatically inserts 5–10 customer discovery interviews or POC experiments to avoid committing resources to unvalidated problems and solutions. When uncertainty is low, these steps can be skipped to avoid following process for its own sake.
3. Cross-functional alignment and execution handoff: The workflow includes a strategy presentation for executives—with an optional Amazon Working Backwards–style fictional press release to help secure support—as well as Epic decomposition, user story writing, and initial sprint planning. This turns strategy directly into schedulable development work rather than leaving it at the documentation stage.

Frequently Asked Questions

How long does the complete process take?

The shortest path is 2 weeks when additional validation is skipped; the typical duration is 3 weeks, including one round of problem validation; and the longest is 4–6 weeks when customer interviews and solution experiments are included. Built-in decision points adjust the process based on uncertainty. It is still recommended to complete the process within 2–4 weeks to avoid analysis paralysis—“always working on strategy, never executing.”

Who should participate?

This is not an exercise for product managers alone. The positioning workshop requires participation from product, marketing, and sales. The problem framing canvas should include design, engineering leads, and customer success. Engineering leads should also jointly score solutions during solution exploration and prioritization. In particular, it is recommended to schedule the executive strategy presentation before kickoff—without executive sponsorship, it is difficult for a strategy to secure resources.

How is it different from an ordinary feature brainstorming session?

A strategy session first frames and validates the problem, then explores and prioritizes solutions. Positioning, problems, solutions, and the roadmap build progressively, with customer validation built into the process. Brainstorming sessions often jump straight to producing a feature list. This is not waterfall planning either—the process retains feedback loops and iteration. The final output is a validated direction and an executable roadmap, rather than a one-time, top-down list of features.