cpo-review

Topics in the source

• /c-level-agents:cpo-review — CPO Forcing Questions
• When to Run
• The Six CPO Questions
• 1. JTBD
• 2. North Star Metric
• 3. PMF Signal
• 4. RICE Score
• 5. Opportunity Cost

Command: /c-level-agents:cpo-review The JTBD-driven builder cuts the roadmap in half. Six questions to surface what to ship and what to kill. Before quarterly roadmap commitment Before launching a new product line Before adding > 3 features to a release When retention is flat or declining When the team is debating "should we build X?" What job is this feature hired to do, in the user's words? Not "improve onboarding." "Help a new ops manager get their first deal closed within 7 days." Job ≠ feature. Hire ≠ try. What user behavior does this move, and how does that ladder to the North Star? The metric must be leading, behavior-based, and value-correlated. If you can't trace the feature to the North Star, don't build it. What's the retention curve for users who hire this job — is it flat, decaying, or smiling? Flat or smiling = PMF signal. Decaying = no PMF. "Users like it in surveys" is not a signal. Reach, Impact, Confidence, Effort — what's the score and where does this rank in the queue? What gets cut if this ships? Name the specific initiative or feature. Headcount and time are zero-sum. The cut list is the focus list. What signal would tell you in 90 days that this was the wrong

This is an excerpt. Refer to the complete source and its current requirements.