product-architecture
Structure what you're building and why now. Use when organizing products into capability blocks, creating bet backlogs, building roadmaps, or writing solution briefs. Part of the Modern Product Operating Model collection.
YannickMaurice · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add yannickYamo/skills --skill product-architecture技能说明
name: product-architecture description: Structure what you're building and why now. Use when organizing products into capability blocks, creating bet backlogs, building roadmaps, or writing solution briefs. Part of the Modern Product Operating Model collection. author: YannickMaurice version: 1.0.0 tags: product-management, roadmap, backlog, solution-brief, product-architecture
Product Architecture System
"A roadmap is not a feature list. It's a sequence of bets on how to create value."
This skill covers the Product System — structuring what you're building and why now. It turns validated opportunities into bets, organizes work into capability blocks, and creates roadmaps that communicate strategy without false precision.
Part of: Modern Product Operating Model — a collection of composable product skills.
Related skills: product-strategy, product-discovery, product-delivery, ai-native-product, product-leadership
When to Use This Skill
Use this skill when:
- Organizing your product into capability blocks
- Converting discovery opportunities into prioritized bets
- Building or updating your roadmap
- Writing solution briefs before engineering commits
- Preparing for planning cycles (quarterly, annually)
- Communicating product direction to stakeholders
Cadence: Quarterly planning, ongoing refinement | Owner: PM with trio input
The Problem This Solves
Most teams have:
- Feature lists masquerading as roadmaps
- No clear connection between strategy and what gets built
- Solution briefs that are either too vague or too prescriptive
- Backlogs organized by urgency, not impact
The Product Architecture System creates a clear hierarchy: Strategy → Bets → Blocks → Features, with traceable connections at each level.
Philosophy
Core Beliefs
- Bets over features — We're not building features, we're placing bets on outcomes
- Roadmaps show direction, not dates — Commitments are for sprints, not quarters
- Problems before solutions — Every bet must connect to a validated opportunity
- Solution briefs over PRDs — Just enough spec to start, emergent detail through building
- Blocks organize complexity — Group capabilities by customer value, not technical architecture
What This Framework Rejects
- Feature factories (build what's requested, not what matters)
- Date-driven roadmaps (false precision creates false expectations)
- Disconnected backlogs (no traceability to strategy)
- Waterfall PRDs (200-page specs nobody reads)
- Tech-driven architecture (organizing by system, not customer)
Framework Components
1. Product Blocks & Features
What is a Block?
A block is a capability area that delivers distinct customer value. Blocks organize your product by what customers can accomplish, not by technical architecture.
Good Block Examples:
- "Onboarding" (helps users get started)
- "Reporting" (helps users understand performance)
- "Collaboration" (helps teams work together)
- "Integrations" (connects to existing workflows)
Bad Block Examples (Tech-Driven):
- "Backend services"
- "API layer"
- "Database module"
Block Portfolio View:
| Block | Owner | Maturity | Strategic Priority | Active Bets |
|---|---|---|---|---|
| Onboarding | [PM] | Growth | P1 | 2 |
| Reporting | [PM] | Mature | P2 | 1 |
| Collaboration | [PM] | New | P1 | 3 |
| Integrations | [PM] | Growth | P3 | 0 |
Block Maturity Stages:
| Stage | Definition | Focus |
|---|---|---|
| New | Unproven, high uncertainty | Find PMF within block |
| Growth | Validated, expanding | Scale and optimize |
| Mature | Stable, well-understood | Maintain, incremental improvements |
| Sunset | Declining value | Deprecate or replace |
Features Within Blocks:
Each block contains features. Features are the specific capabilities users interact with.
BLOCK: Reporting
├── Feature: Dashboard builder
├── Feature: Scheduled reports
├── Feature: Export to PDF
└── Feature: Custom metrics
0→1 Mode: One block, maybe two. Don't over-structure before you have PMF.
Scaling Mode: Multiple blocks with clear owners. Block health reviews quarterly.
2. The Bet Backlog
What is a Bet?
A bet is a time-boxed investment with a hypothesis, success metrics, and kill criteria. Unlike features, bets explicitly acknowledge uncertainty.
Bet Format:
BET: [Name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Hypothesis: We believe that [action] will result in [outcome]
Target metric: [Metric] from [baseline] to [target]
Timebox: [Duration]
Block: [Which block this belongs to]
Opportunity: [Link to validated opportunity in OST]
Kill criteria: [When we stop]
Scale criteria: [When we double down]
Effort: [T-shirt size]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Bet Categories:
| Category | Description | Example |
|---|---|---|
| Value creation | New capabilities that solve customer problems | New reporting feature |
| Growth | Acquisition, activation, expansion | Onboarding improvements |
| Platform | Infrastructure, scalability, efficiency | Performance optimization |
| Trust | Security, compliance, reliability | SOC 2 certification |
| Moat | Building defensibility | Proprietary data features |
Portfolio Balance:
| Category | Target Allocation | Rationale |
|---|---|---|
| Core (proven, incremental) | 70% | Keep the lights on, serve existing customers |
| Adjacent (related, moderate risk) | 20% | Expand to new use cases or segments |
| Transformational (new, high risk) | 10% | Explore future opportunities |
Bet Prioritization:
Use ICE, RICE, or simple compare-and-contrast:
| Bet | Impact | Confidence | Effort | Score | Priority |
|---|---|---|---|---|---|
| A | High |