Home
cd ../playbooks
Product ManagementAdvanced

Compounding PM Operating System

A persistent PM profile that learns your frameworks, vocabulary, and decision patterns across product cycles — comparing predictions to actuals so each cycle gets sharper than the last.

20 minutes
By Abhishek TiwariSource
#product-management#pm-frameworks#opportunity-evaluation#product-strategy#prediction-tracking#personalization#decision-log#product-discovery

Every product cycle you run with AI assistance starts from zero. The tool doesn't remember that your last three activation predictions were 20% optimistic, doesn't know your team calls it a 'north star' not a 'KPI', and has no idea you already tried this exact approach eighteen months ago and it flopped.

Who it's for: product managers who want their tools to learn their frameworks instead of re-explaining them every session, PM leads coaching a team toward consistent operating patterns, PMs who want a real prediction-accuracy track record instead of vibes-based retros, product teams building a shared institutional memory instead of losing it every time someone leaves, PMs tired of generic frameworks that ignore what actually worked for them before

Example

"Evaluate this opportunity: enterprise customers keep asking for SSO" → Because a similar past opportunity is in the profile, the system surfaces it directly: 'This resembles the 2024 SAML integration — that one hit 60% of predicted enterprise activation because we underestimated procurement friction. Key learning: budget 6 weeks for security review, not 2.' The current opportunity gets evaluated with that calibration built in, not from scratch

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

Or install from your terminal:
npx ccplaybooks add compounding-pm-operating-system
# Compounding PM Operating System

## Your Role

You are my product management operating system — not a set of one-shot templates, but a system that gets sharper with every product cycle. You learn how I work, remember what I've tried, and calibrate your suggestions against my actual track record instead of generic PM theory.

**The core principle**: each product cycle should make the next one easier, not harder. Two things compound over time — **artifacts** (specs, decisions, learnings) and **judgment** (prediction accuracy, bias awareness, calibration). Skip the compounding step and this is just PM templates with a chatbot attached. The compounding step is the entire point.

---

## The Full Loop

Get new playbooks like this one

One email a week with new Claude Code workflows. Free, like everything here.

No spam. Unsubscribe anytime.

README.md

What This Does

Most PM frameworks are static — the same opportunity template, the same prioritization matrix, every single time, with no memory of what you tried before or whether it worked. This is different: a pm-profile.yaml file that captures your actual frameworks, vocabulary, and decision history, and gets updated after every product cycle with real predictions-vs-actuals data.

The mechanism is simple but the effect compounds: by cycle 5, the system is suggesting activation thresholds calibrated from your last four projects instead of generic benchmarks. By cycle 10, it knows your estimation bias and corrects for it automatically, and flags when a new opportunity resembles a past failure before you commit resources to repeating it.


Quick Start

Step 1: Create a Project Folder

mkdir pm-operating-system && cd pm-operating-system

Step 2: Download the Template

Click Download above, then:

mv ~/Downloads/CLAUDE.md ./

Step 3: Build Your Profile

claude

Then say: "Let's set up my PM profile" — import existing docs, answer a short Q&A, or start minimal and let it build through usage.


The Full Loop

Observe → Opportunity → Solution → Spec → Review → Measure → Compound
   ↑                                                              │
   └──────────────────── learnings feed back ─────────────────────┘
Step What it produces
Opportunity A structured, evaluated opportunity doc — signal classified, problem framed as a How Might We, prioritized on impact/risk
Solution Multiple solution approaches, classified as Differentiator / Must-Match / Neutralizer
Spec Vision narrative, journey map, metrics framework, launch criteria
Review Prioritized findings (P1 blocking / P2 should-fix / P3 nice-to-have)
Measure Explicit, falsifiable predictions — not vague directional hopes
Compound Predictions compared to actuals, profile updated — the step that makes everything else worth doing

What Gets Personalized

Profile field Adapts
Frameworks (opportunity evaluation, solution classification, metrics hierarchy) How each step structures its output
Vocabulary Whether you call it a "north star," an "outcome metric," or a "KPI"
Thresholds Pre-filled targets calibrated from your actual project history
Project patterns Surfaced automatically when a new opportunity resembles a past one
Decision log Surfaced when a similar trade-off comes up again

Tips & Best Practices

  • Never skip Compound. It's explicitly framed in the source material as "the most important step" — everything before it is just PM templates with a chatbot attached. The compounding only happens if predictions get checked against reality and the profile gets updated.
  • Make predictions specific and falsifiable. "Adoption will improve" isn't a prediction the system can learn from. "35% activation within 7 days" is — it has a number that can be right or wrong.
  • Classify failures by type, not just outcome. The template distinguishes strategy failure (wrong market), opportunity failure (right market, wrong problem), prioritization failure (right problem, wrong solution), execution failure, and measurement failure — because the fix is different for each one.
  • Let it surface past patterns before you ask. When a new opportunity resembles something already in project_patterns, the system should say so proactively — that's the whole value of the memory existing.
  • Start minimal if you're not sure. A skeleton profile that fills in through actual usage beats an elaborate upfront setup you have to guess at before you've run a single cycle.

Limitations

  • The compounding value is genuinely cumulative — cycle 1 looks like any other PM template, and the differentiation only shows up after several real cycles have fed the profile
  • Works best with a git-tracked project where pm-profile.yaml and the docs/ output persist between sessions — it's designed around a durable file, not a one-off conversation
  • For a team, a shared team-profile.yaml layer requires deliberate promotion of individual learnings — insights don't automatically become team knowledge without an explicit sharing step
  • This playbook condenses the operating system's core loop and compounding mechanism; the source repository also ships dedicated judgment-training exercises (teardown practice, reaction simulation, bias checks) and standalone strategy/growth commands (segmentation, competitive differentiation, North Star metric design) worth exploring directly in the source if you want the full toolkit

$Related Playbooks

Product Management

Acquisition Channel Advisor

Evaluate acquisition channels using unit economics, customer quality, and scalability. Decide whether to scale, test, or kill each channel with finance-backed reasoning.

10 minutes
Intermediate
Product Management

SaaS Business Health Diagnostic

Diagnose SaaS business health across growth, retention, unit economics, and capital efficiency. Identify red flags by urgency and get a prioritized action plan with stage-specific benchmarks.

15 minutes
Advanced
Product Management

Context Engineering Advisor

Diagnose whether you're doing context stuffing (volume without intent) or context engineering (structure for attention). Build memory architecture, define context boundaries, and implement the Research → Plan → Reset → Implement cycle.

15 minutes
Advanced
Product Management

Director Readiness Advisor

Coach the PM-to-Director transition with 4 situational branches — preparing, interviewing, newly landed, or recalibrating — and deliver war-story-backed guidance calibrated to your specific stage.

10 minutes
Advanced
Product Management

Discovery Interview Prep

Design a customer discovery interview plan with the right methodology, questions, and bias guardrails — calibrated to your research goal, segment, and constraints via 4 adaptive questions.

15 minutes
Intermediate
Product Management

Discovery Process (End-to-End)

Run a complete 6-phase discovery cycle — frame, research, synthesize, generate, validate, decide — in 3-4 weeks. Orchestrates 10+ component skills for problem-to-validated-solution workflow.

30 minutes
Advanced
Product Management

AI-Shaped Readiness Advisor

Diagnose whether your product work is 'AI-first' (efficiency) or 'AI-shaped' (strategic transformation). Score 5 competencies, identify gaps, and get a priority action plan.

15 minutes
Advanced
Product Management

Altitude & Horizon Framework (PM → Director)

Understand the PM-to-Director transition through altitude (scope) and horizon (time). Diagnose which of four transition zones is creating friction and apply the Cascading Context Map when direction from above is vague.

10 minutes
Intermediate
Product Management

Customer Journey Map

Build a strategic customer journey map across Awareness → Consideration → Decision → Service → Loyalty — with actions, touchpoints, emotions, KPIs, business goals, and owning teams per stage.

20 minutes
Intermediate
Product Management

Customer Journey Mapping Workshop

Run a 5-question adaptive workshop to build a customer journey map — actor, scenario, phases, actions/emotions, and prioritized opportunities — that aligns cross-functional teams around real pain points.

15 minutes
Intermediate
Product Management

End-of-Life (EOL) Message

Write a clear, empathetic EOL announcement with customer-benefit rationale, explicit impact acknowledgment, transition support, and specific timeline — maintaining trust through product retirements.

10 minutes
Beginner
Product Management

Epic Breakdown Advisor (Humanizing Work)

Break epics into user stories using the Humanizing Work methodology — INVEST validation, 9 splitting patterns applied sequentially, and evaluation criteria that expose low-value work.

15 minutes
Intermediate

Browse all Product Management playbooks →