Product Strategy Session

What Is This?

Overview

Product Strategy Session is a structured skill for running end-to-end product strategy work across three interconnected disciplines: positioning, discovery, and roadmap planning. It orchestrates multiple product management sub-skills into a single cohesive process, guiding teams from vague strategic intent to concrete, validated direction. Rather than treating positioning, problem framing, and roadmap planning as separate activities, this skill treats them as a unified workflow where each phase informs the next.

The skill is designed for situations where a team is about to commit significant engineering or design resources but lacks validated strategic alignment. It surfaces assumptions early, structures customer discovery around real problems, and produces a roadmap grounded in evidence rather than opinion. The output is not just a document but a shared understanding of why the product exists, who it serves, and what to build next.

This skill draws from the deanpeters/Product-Manager-Skills source and is intended to be used with AI-assisted product management workflows. It works best when facilitated through a structured prompt session that walks participants through each phase sequentially.

Who Should Use This

• Product managers preparing for a quarterly planning cycle who need to align stakeholders before committing to a roadmap
• Startup founders validating a new product direction before investing in development
• Product leads onboarding a new team who need to establish shared context quickly
• Growth teams evaluating whether to expand into a new market segment or customer persona
• Consultants running product audits for clients who need a structured discovery framework
• Senior engineers or technical leads who are stepping into product ownership roles for the first time

Why Use It?

Problems It Solves

• Teams often start building before validating whether the problem is real or the positioning is differentiated, leading to wasted cycles
• Roadmap planning sessions frequently lack a shared problem statement, causing misalignment between engineering, design, and business stakeholders
• Customer discovery is often skipped or done informally, leaving strategic decisions based on assumptions rather than evidence
• Positioning work is treated as a marketing task rather than a strategic foundation, disconnecting it from what actually gets built
• Without a structured session format, strategy conversations drift and rarely produce actionable outputs

Core Highlights

• Covers the full strategy arc from positioning through discovery to roadmap in one session
• Structures problem framing before solution exploration to prevent premature commitment
• Integrates customer discovery as a required input, not an optional step
• Produces a validated roadmap with explicit assumptions and evidence
• Supports async and synchronous facilitation modes
• Works with AI prompt chaining to automate session scaffolding
• Reduces time from strategic ambiguity to execution-ready direction
• Applicable across B2B, B2C, and internal product contexts

How to Use It?

Basic Usage

To invoke this skill in an AI-assisted workflow, use a structured prompt that initializes the session with context about the product, the team, and the current strategic question.

/run product-strategy-session
  product: "B2B invoicing tool for freelancers"
  stage: "post-MVP, pre-Series A"
  question: "Should we expand to small teams or deepen solo freelancer features?"
  discovery_data: "12 user interviews, 3 churn surveys"

The session will then walk through positioning review, problem framing, discovery synthesis, and roadmap prioritization in sequence.

Specific Scenarios

Scenario 1: Pre-planning alignment. A product team is entering quarterly planning with three competing priorities. Run the session to surface the core strategic question, align on the target customer segment, and produce a prioritized problem list before any roadmap items are written.

Scenario 2: New product validation. A founder has a product hypothesis but no customer data. Use the discovery phase of the session to generate interview guides, synthesize findings, and validate or invalidate the core assumption before writing a single line of code.

Real-World Examples

A SaaS team used this session to discover that their assumed primary persona (solo developers) was not the buyer, and that team leads were the actual decision-makers. This shifted their positioning and roadmap within a single two-hour session.

A consulting team used the skill to run a product audit for a client, producing a structured findings report and a 90-day roadmap recommendation in one facilitated workshop.

Important Notes

Requirements

• At least one product manager or product owner must be present to provide context and validate outputs
• Some existing customer data or market context is needed to make discovery synthesis meaningful
• The team should have a defined strategic question before starting the session
• Access to an AI assistant capable of multi-turn prompt chaining is required for automated facilitation