The 9 Sections of the Product Strategy Canvas: A Complete Framework Guide
The Product Strategy Canvas is a nine-section strategic framework defined in the phuryn/pm-skills repository that guides product teams from aspirational vision to competitive defensibility through structured sections covering market segments, value propositions, trade-offs, metrics, growth, capabilities, and moats.
The Product Strategy Canvas provides a systematic approach to defining, positioning, and scaling products. According to the source code in phuryn/pm-skills, this framework is implemented as a core skill that walks product managers through nine sequential decisions. Each section builds upon the previous to ensure strategic coherence, starting with high-level vision and ending with specific defensibility mechanisms.
What is the Product Strategy Canvas?
The Product Strategy Canvas is a concise planning tool that captures all critical strategic decisions required to bring a product to market. As defined in pm-product-strategy/skills/product-strategy/SKILL.md, the framework organizes strategy into nine interconnected sections that progress logically from purpose to protection. This structure ensures that product teams explicitly define not only what they will build and for whom, but also what they will explicitly avoid and how they will sustain competitive advantage.
The 9 Sections of the Product Strategy Canvas
The canonical definition in pm-product-strategy/skills/product-strategy/SKILL.md divides the canvas into nine specific sections. Each section addresses a distinct strategic dimension, with line references indicating their precise location in the source documentation.
1. Vision
Vision captures the aspirational purpose of your product—the impact you intend to create, the values you stand for, and the high-level goal you are working toward. According to lines 26-30 of the skill file, this section establishes the north star that aligns all subsequent strategic decisions.
2. Market Segments
Market Segments defines the specific customer problems (jobs-to-be-done) you are solving, the outcomes those customers desire, and the rationale for prioritizing one segment over others. This section, detailed in lines 31-36, ensures you are targeting the right users with the right pain points.
3. Relative Costs
Relative Costs positions your product on the cost spectrum compared to competitors. As outlined in lines 37-41, you must determine whether you are pursuing low-cost leadership (e.g., Southwest Airlines) or premium value positioning (e.g., Starbucks).
4. Value Proposition
Value Proposition articulates the current pain experienced by each target segment, how your product resolves it, the post-solution state customers will achieve, and the alternatives they currently use. Lines 42-48 specify that this section bridges customer problems with your specific solution.
5. Trade-offs
Trade-offs explicitly states what you will not do—which features, markets, or initiatives remain out of scope. According to lines 49-53, documenting these "no's" sharpens strategic focus and prevents resource dilution across too many priorities.
6. Key Metrics
Key Metrics identifies the North Star Metric that drives overall business success and the One Metric That Matters (OMTM) you will optimize for the current quarter. This dual-metric approach, defined in lines 54-57, balances long-term vision with immediate execution.
7. Growth
Growth outlines your growth model (sales-led versus product-led), primary acquisition channels, scaling approach, and unit-economics considerations. Lines 58-63 specify that this section translates strategy into executable growth mechanics.
8. Capabilities
Capabilities inventories the competencies, resources, and partnerships required to execute the strategy. Lines 64-68 detail that this section explicitly defines what you will build in-house versus outsource, ensuring organizational readiness aligns with strategic ambitions.
9. Can't/Won't (Defensibility)
Can't/Won't (Defensibility) establishes the barriers that protect your product from copycats. As detailed in lines 69-73, this includes network effects, switching costs, intellectual property, or other strategic moats that make your position sustainable.
How to Generate the Product Strategy Canvas
The phuryn/pm-skills repository provides a command-line interface to generate the canvas interactively. The /strategy command, documented in pm-product-strategy/commands/strategy.md, produces a completed canvas populated across all nine sections.
To generate a full product strategy document from your terminal, use:
# Generate a full product-strategy document (all 9 sections) interactively
pm-skills /strategy "Create a strategy for a new AI-driven note-taking app."
Alternatively, you can supply a structured JSON payload for programmatic integration:
{
"command": "product-strategy",
"arguments": {
"productDescription": "AI-powered note-taking app for students",
"marketContext": "High competition, low-cost incumbents, premium productivity tools",
"companyResources": "Small dev team, $500k seed funding"
}
}
Running either method produces a completed canvas where each of the nine sections is populated according to the provided inputs, creating a coherent strategic roadmap from vision to defensibility.
Summary
- The Product Strategy Canvas is defined in
pm-product-strategy/skills/product-strategy/SKILL.mdas a nine-section framework for product planning. - Vision establishes aspirational purpose, while Market Segments identifies target customers and their jobs-to-be-done.
- Relative Costs positions you against competitors, and Value Proposition articulates how you solve specific pain points.
- Trade-offs explicitly defines what the product will not do, sharpening strategic focus.
- Key Metrics pairs long-term North Star indicators with quarterly OMTM execution targets.
- Growth models acquisition channels and scaling, Capabilities defines build versus buy decisions, and Can't/Won't establishes defensible moats.
- The
pm-skills /strategycommand generates the complete canvas interactively via the CLI.
Frequently Asked Questions
What is the difference between the North Star Metric and OMTM in the Product Strategy Canvas?
The North Star Metric represents the single measurement that best captures the core value your product delivers to customers, driving long-term success. The One Metric That Matters (OMTM) is the specific metric you will optimize for the current quarter to make immediate progress toward that North Star. According to the source in pm-product-strategy/skills/product-strategy/SKILL.md (lines 54-57), this dual approach balances strategic vision with tactical focus.
How does the Trade-offs section improve product strategy?
The Trade-offs section forces explicit decisions about what the product will not do, preventing scope creep and resource fragmentation. By documenting which features, markets, or initiatives remain out of scope (as specified in lines 49-53), teams create a "sharp edge" to their strategy that clarifies positioning and prevents dilution across too many opportunities.
Where is the canonical definition of the Product Strategy Canvas located?
The canonical definition resides in pm-product-strategy/skills/product-strategy/SKILL.md within the phuryn/pm-skills repository. This file contains the detailed descriptions of all nine sections, including line-specific references for Vision (lines 26-30), Market Segments (lines 31-36), and the remaining strategic components through line 73.
Can the Product Strategy Canvas be used for non-software products?
Yes. While the phuryn/pm-skills repository implements the canvas within a product management toolkit, the nine sections—covering vision, market segmentation, cost positioning, value proposition, and defensibility—apply to any product or service requiring strategic positioning. The framework's structure is domain-agnostic, though the CLI tooling is optimized for software product workflows.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →