# PM Frameworks — from PM Pulse

A working library of product management frameworks, curated and applied by Deep Mehtaji in the weekly PM Pulse newsletter. Each entry includes what it is, when to use it, and a real applied example.

---

## The Vertical Squeeze Matrix
**When to use:** Any time a new provider-facing platform, outcome-based payment model, or care-coordination tool launches in your market — before assuming it's "not a payer problem."

A 2×2: Axis 1 — who owns the direct member/provider relationship today (the Plan or a Third Party). Axis 2 — how the payment logic is structured (Traditional fee-for-service or Outcome-Aligned/Direct).

| Quadrant | Meaning |
|---|---|
| Plan-Owned + Traditional | Legacy Safe Zone — defensible today, but complacency risk |
| Plan-Owned + Outcome-Aligned | Compounding Advantage — hardest position to dislodge |
| Third-Party + Traditional | Slow Leak — a competitor is building adjacent tooling; time to react |
| Third-Party + Outcome-Aligned | Acute Exposure — a competitor owns both the relationship and the payment logic |

**Diagnostic questions:** (1) For each major product surface, which quadrant is it in today? (2) Which quadrant is it drifting toward over the next 12–18 months if nothing changes? (3) What's the one investment that would move your highest-usage surface toward Compounding Advantage?

> "The threat to your Medicare Advantage app isn't a better plan. It's a provider who no longer needs you to build the relationship."

---

## Taste as Compounding Moat (The Tony Fadell Rule)
**When to use:** Making 1.0 product decisions in a new category where data doesn't exist yet. When your data says "current users love X" but your instinct says the market is shifting.

Data tells you what your current users do. Taste tells you what the next generation of users will need before they can articulate it.

**The three-step taste practice:**
| Step | How to do it |
|---|---|
| Cross-domain absorption | 20% of one day/week with products outside your industry, adjacent (not competitor) categories |
| Opinion journaling | One sentence daily on why a product is compelling — before checking reviews |
| Opinion-first decisions | 1–2 decisions per sprint made on explicit taste rationale, documented before data analysis |

**Fadell's Three Generations Rule:** Design for the third-generation user, not the first adopter. First adopters forgive friction; third-generation users expect the category to be obvious and effortless.

**The Fadell Test:** "Would someone who has never seen this category before immediately understand why it's better?" If the answer requires explanation, your differentiation lives in the marketing deck, not the product.

> "When everyone can ship a product in a day, taste becomes the scarcest resource in technology." — Tony Fadell

---

## The AI Maturity Multiplier
**When to use:** Before any company-wide AI tool rollout or mandate. Whenever leadership treats "AI adoption %" as a success metric in itself.

AI doesn't equalize product orgs — it multiplies whatever maturity (or dysfunction) already exists in the operating model. High-maturity orgs compound their advantage; low-maturity orgs just fail faster.

**The diagnostic question:** Before scaling any AI rollout — is our operating model (decision rights, discovery cadence, feedback loops) something we'd want multiplied at 3x speed? If not, fix the model before you scale the tool.

> "AI is a multiplier, not an equalizer."

---

## The Regulatory Moat vs. Regulatory Trap Matrix
**When to use:** Evaluating a compliance-heavy feature build. Entering a regulated-adjacent market. Any time a teammate says "we need to comply with X" — ask which quadrant that compliance investment lands in.

|  | High Differentiating Value | Low Differentiating Value |
|---|---|---|
| **High Compliance Cost** | Regulatory Moat — certify early, own the space before the crowd arrives | Regulatory Trap — compliance is your ceiling, not your floor |
| **Low Compliance Cost** | First-Mover Gift — easy to comply + high value = unfair advantage window | Table Stakes — do it, don't pitch it |

**The diagnostic question:** "Is my moat in the standardized layer (Regulatory Trap) or in the intelligence above it (Regulatory Moat)?"

---

## The Market Contraction Playbook
**When to use:** When enrollment data, funding trends, or user data shows declining TAM, or when your growth plan assumes a market size that current data contradicts.

1. **Rebase your market model** — don't use projections from peak-year assumptions; model off current trajectory.
2. **Find the contrarian expander** — in every contracting market, one player makes the opposite bet. Study their product bets; they're solving the actual problem, not the growth-era problem.
3. **Shift from acquisition to retention intensity** — when new users are scarce, every existing one is irreplaceable. Redesign metrics around retention depth, not acquisition breadth.

> "In a growing market, the rising tide hides bad product decisions. In a contracting market, bad product decisions become the tide."

---

## Opportunity Solution Tree (OST)
**Source:** Teresa Torres, *Continuous Discovery Habits*
**When to use:** Any time you're starting discovery or feeling the urge to jump straight to solutions.

Forces you to separate what you want to achieve, from what problems exist, from what you might build. Map the opportunity space *before* any solutions appear — solutions live at the bottom, never the top.

**Pro tip:** If you can't draw the OST for your current initiative in 5 minutes, you don't understand the problem well enough yet.

---

## The Three Levels of PM Work
**Source:** Shreyas Doshi
**When to use:** Self-assessment, performance reviews, coaching junior PMs.

| Level | Description | Trap |
|---|---|---|
| Impact | Does this move the needle for users and the business? | Skipping this entirely |
| Execution | Are we shipping well, on time, with quality? | Getting stuck here |
| Optics | Do stakeholders know what we're doing and why? | Over-investing here |

Great PMs spend most energy at the Impact level. Average PMs get trapped at Execution and mistake Optics for strategy.

---

## The Decision Velocity Index (DVI)
**When to use:** When your team ships faster than customers can absorb, or you're reopening the same debates monthly.

| Input | Target |
|---|---|
| Decision Throughput (significant decisions/week) | 5+ |
| Decision Latency (days from "need to decide" to "decided") | Under 3 |
| Decision Override Rate (reopened within 4 weeks) | Under 15% |

Three artifacts that fix it (none are meetings): a Weekly Decision Log, a Dead-End Register, and an Async Pre-Mortem Template.

> "Stop trying to be a faster human. Build decision infrastructure instead."

---

*Curated from PM Pulse — a weekly newsletter on product management and digital health strategy by Deep Mehtaji. Subscribe on Substack.*