cpo-advisor

What this skill does

# CPO Advisor

Strategic product leadership. Vision, portfolio, PMF, org design, and metrics. Not for feature-level work -- for the decisions that determine what gets built, why, and by whom.

## Keywords

CPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, jobs to be done, JTBD, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects, product-led growth, PLG, feature adoption, time to value, activation rate

---

## The CPO Owns Three Things

Everything else is delegation.

| Ownership | What It Means | Key Question |
|-----------|--------------|--------------|
| Portfolio | Which products exist, which get investment, which get killed | "If we could only fund 2 of our 4 products, which 2?" |
| Vision | Where the product goes in 3-5 years and why customers care | "What does the world look like if we succeed?" |
| Organization | The team structure that can execute the vision | "Can this org ship the next 12 months of strategy?" |

---

## Product-Market Fit Assessment

### PMF Scoring Matrix

| Dimension | Weight | Score 1-3 (Weak) | Score 4-6 (Emerging) | Score 7-10 (Strong) |
|-----------|--------|-----------------|---------------------|---------------------|
| Retention | 30% | D30 < 15% (consumer) or < 40% (B2B) | D30 15-30% / 40-60% | D30 > 30% / > 60% |
| Engagement | 25% | DAU/MAU < 15% | DAU/MAU 15-35% | DAU/MAU > 35% |
| Satisfaction | 25% | Sean Ellis < 25% "very disappointed" | 25-40% | > 40% |
| Growth | 20% | No organic growth | Some organic, mostly paid | > 50% organic |

### PMF Decision Tree

```
START: "Do we have PMF?"
  |
  v
[Check retention curve shape]
  |
  +-- Declining to zero --> NO PMF. Stop building. Talk to users.
  |
  +-- Declining but flattening --> EMERGING. Find the segment where it's flat.
  |
  +-- Flat or smiling --> [Check Sean Ellis score]
                          |
                          +-- < 25% "very disappointed" --> Weak PMF. Product is nice, not essential.
                          |
                          +-- 25-40% --> Moderate PMF. Find and double down on power users.
                          |
                          +-- > 40% --> [Check organic growth]
                                        |
                                        +-- < 30% organic --> PMF exists but distribution is weak.
                                        +-- > 30% organic --> STRONG PMF. Scale.
```

### Post-PMF Traps

| Trap | Description | Prevention |
|------|-------------|------------|
| Feature creep | Adding features for new segments dilutes core value | Maintain a "jobs" focus, not feature focus |
| Premature scaling | Scaling sales/marketing before retention proves sustainable | Prove 3+ cohorts retain before scaling spend |
| Metric vanity | Celebrating signups while ignoring retention | North star must be a retention/engagement metric |
| Founder departure from product | CEO stops talking to customers post-PMF | Monthly customer conversations are permanent |
| Platform too early | Building platform capabilities before core is solid | Platform only after 3+ products need shared infra |

---

## Portfolio Management

### Investment Posture Framework

Every product gets exactly one posture. "Wait and see" is a decision to lose share.

| Posture | Signal | Resource Allocation | Review Cadence |
|---------|--------|-------------------|----------------|
| **Invest** | High growth, strong/improving retention, clear PMF | Full team, aggressive roadmap, dedicated marketing | Monthly |
| **Maintain** | Stable revenue, slow growth, good margins | Bug fixes, incremental improvement, minimal new features | Quarterly |
| **Harvest** | Declining growth, still profitable, no recovery path | Minimal investment, maximize cash extraction | Quarterly |
| **Kill** | Declining, negative margins, no recovery evidence | Set sunset date, migration plan, team reallocation | Immediate |

### Portfolio Health Scorecard

| Metric | Healthy | Unhealthy |
|--------|---------|-----------|
| % revenue from "Invest" products | > 60% | < 40% |
| % engineering on "Kill" candidates | < 10% | > 20% |
| Number of products without clear posture | 0 | > 1 |
| Portfolio D30 retention (weighted) | Improving QoQ | Declining QoQ |
| # of "question marks" > 2 quarters | 0 | > 2 |

### Portfolio Review Process

```
Quarterly Portfolio Review (Half-day workshop)

Step 1: Data Preparation (pre-meeting)
  - Revenue, growth rate, retention, margin per product
  - Engineering investment % per product
  - Customer satisfaction per product

Step 2: BCG Classification
  - Plot each product on Growth Rate (Y) vs Market Share (X)
  - Stars: high growth, high share --> Invest
  - Cash Cows: low growth, high share --> Maintain/Harvest
  - Question Marks: high growth, low share --> Invest or Kill (decide now)
  - Dogs: low growth, low share --> Kill

Step 3: Investment Allocation
  - Align engineering capacity to posture
  - Reallocate from Kill/Harvest to Invest
  - Set clear milestones for Question Marks (90-day decision point)

Step 4: Communication
  - Share portfolio decisions with all product teams
  - Update roadmaps to reflect postures
  - Communicate sunset plans for Kill products
```

---

## North Star Metric Framework

### Selection Criteria

The north star metric must satisfy ALL of these:

| Criterion | Test |
|-----------|------|
| Measures customer value | Does improvement mean customers got more value? |
| Leading indicator | Does it predict future revenue? |
| Actionable | Can product teams influence it? |
| Single number | Can you state it as one metric? |
| Non-gameable | Is it hard to improve without genuinely helping customers? |

### North Star by Business Model

| Model | North Star | Why It Works |
|-------|-----------|-------------|
| B2B SaaS | Weekly active accounts using core feature | Combines adoption + engagement + stickiness |
| Consumer social | Daily content creators | Creators drive consumer engagement |
| Marketplace | Successful transactions per week | Both sides active = healthy marketplace |
| PLG | Accounts reaching activation within 14 days | Activation predicts retention |
| Data/Analytics | Queries per active user per week | Usage intensity = value received |
| Fintech | Monthly active transactors | Transaction activity = core value |
| E-commerce | Repeat purchase rate (90-day) | Retention is everything in commerce |

### Metrics Hierarchy

```
North Star Metric (1, owned by CPO)
  |
  +-- Leading Indicator 1 (owned by PM Team A)
  |     e.g., Activation rate within 7 days
  |
  +-- Leading Indicator 2 (owned by PM Team B)
  |     e.g., Feature X adoption rate
  |
  +-- Leading Indicator 3 (owned by PM Team C)
  |     e.g., D7 retention rate
  |
  +-- Guard Rail Metrics (owned by CPO)
        e.g., NPS, support ticket volume, revenue per user
```

---

## Product Organization Design

### Team Topology Selection

| Topology | When to Use | Optimal Size | Communication |
|----------|------------|-------------|---------------|
| Stream-aligned | Default. Teams own end-to-end customer journey. | 5-9 people | Low cross-team dependency |
| Platform | Shared infrastructure multiple streams need | 4-8 people | API-first, self-service |
| Enabling | Temporary teams to upskill stream teams | 2-4 people | Coaching mode, time-limited |
| Complicated subsystem | Deep specialist domain (ML, payments) | 3-6 people | Provides service to streams |

### Product Team Ratios

| Company Size | PM : Engineers | PM : Designer | Total Product Team |
|-------------|---------------|---------------|-------------------|
| 10-30 | 1:4-6 | 1:1 | 1 PM, 1 Designer, 4-6 Eng |
| 30-80 | 1:5-8 | 1:1-2 | 2-4 PMs, 2-3 Designers |
| 80-200 | 1:6-10 | 1:1-2 | 5-10 PMs, 4-6 Designers |
| 200+ | 1:8-12 | 1:2 | 10+ PMs