Product Strategy

What Is This?

Overview

Product strategy is the structured discipline of defining where a product is going, why it exists, and how it will succeed in the market. The Product Strategy Canvas is a nine-section framework that organizes this thinking into a coherent, actionable document. It covers vision, customer segments, cost structures, value propositions, trade-offs, success metrics, growth levers, core capabilities, and defensibility, giving product teams a complete picture of their strategic position.

This skill enables you to generate a comprehensive product strategy document by working through each canvas section systematically. Rather than producing disconnected strategy fragments, the canvas forces alignment between market opportunity, organizational capability, and measurable outcomes. The result is a strategy that can be communicated clearly to stakeholders, used to prioritize roadmap decisions, and revisited as market conditions change.

The nine-section structure prevents common strategy failures such as defining a vision without connecting it to customer needs, or identifying growth opportunities without acknowledging the trade-offs required to pursue them. Each section informs the others, creating a strategy that holds together under scrutiny.

Who Should Use This

• Product managers building a strategy for a new product or a major product pivot
• Startup founders who need to articulate product direction to investors and early team members
• Product leaders aligning multiple teams around a shared strategic direction
• Consultants and advisors helping clients define or refine their product positioning
• Senior engineers and technical leads who want to understand the strategic context behind roadmap decisions
• Business analysts translating market research into structured strategic recommendations

Why Use It?

Problems It Solves

• Fragmented strategy documents that address vision but ignore costs, or define segments but skip defensibility
• Misalignment between what a product team builds and what the business needs to sustain itself financially
• Inability to explain trade-offs clearly, leading to scope creep and conflicting priorities
• Lack of measurable success criteria, making it impossible to evaluate whether the strategy is working
• Growth plans that assume capability the organization does not yet have

Core Highlights

• Covers all nine strategic dimensions in a single structured output
• Forces explicit trade-off documentation, so decisions are visible and deliberate
• Connects customer value propositions directly to cost and revenue structures
• Includes defensibility analysis to assess competitive durability
• Produces a document suitable for executive review, team alignment, and investor communication
• Works for new products, existing products entering new markets, and products undergoing strategic repositioning
• Integrates growth levers with capability requirements to ensure feasibility

How to Use It?

Basic Usage

Invoke the skill by providing your product context. A minimal prompt looks like this:

Use product-strategy skill.
Product: B2B project management tool for remote engineering teams.
Stage: Early growth, 200 paying customers.
Goal: Define strategy for expanding into mid-market accounts.

The skill will generate all nine canvas sections based on the context you provide.

Specific Scenarios

Scenario 1: New Product Launch Provide the problem space, target customer, and any known constraints. The canvas will generate a vision statement, segment definitions, and an initial value proposition, then surface the trade-offs inherent in your launch approach.

Scenario 2: Strategic Repositioning Describe your current product, what is not working, and the new direction you are considering. The canvas will map the gap between your existing capabilities and what the new position requires.

Real-World Examples

A SaaS company moving from SMB to enterprise customers used the canvas to identify that their current pricing model, support capacity, and security certifications were all misaligned with enterprise requirements, producing a clear capability gap list before any engineering work began.

A consumer app team used the defensibility section to recognize that their only moat was brand familiarity, prompting investment in network effects and data advantages before a well-funded competitor entered the market.

When to Use It?

Use Cases

• Defining product direction for a new venture or product line
• Preparing for a board or investor strategy review
• Onboarding a new product leader who needs to understand current strategic positioning
• Evaluating whether to enter a new market segment
• Documenting strategy before a major architectural or pricing change
• Resolving disagreements between product, engineering, and business stakeholders about priorities
• Annual or quarterly strategic planning cycles

Important Notes

Requirements

• You should have at least a basic understanding of your target customer and the problem your product addresses
• Some knowledge of your cost structure or business model improves the quality of the financial sections
• Access to competitive landscape information strengthens the defensibility analysis