The Hook

**TL;DR:** A backlog is not a product strategy. A roadmap is not a vision. If your product process is a list of features ranked by whoever shouted loudest, Product-Manager will help you rebuild it around customer problems, business outcomes, and evidence-based prioritization.

The product management crisis in software isn't a tools crisis. It's a thinking crisis. Most product processes produce the illusion of progress: sprint velocity, roadmap burndown, ticket throughput. These metrics measure output. Product management's job is to move outcomes — revenue, retention, engagement, efficiency. Product-Manager forces that distinction into every decision.

The 10-Second Pitch

• **Opportunity assessment framework** — Score opportunities on value, confidence, and effort
• **Jobs-to-be-done discovery** — Structured customer interview templates around JTBD framework
• **KPI decomposition** — Translate company-level OKRs into product-level metrics and experiments
• **Prioritization matrix** — RICE, ICE, or custom scoring with documented assumptions
• **Experiment design** — A/B test or qualitative validation before building anything irreversible
• **Stakeholder alignment toolkit** — RACI matrices, decision logs, and communication templates

Setup Directions

Step 1 — Define Your Product Strategy

product_strategy:

horizon: 12_months

target_outcomes:

• metric: monthly_active_users

baseline: 50000

goal: 120000

leading_indicators: [activation_rate, weekly_retention, referral_rate]

• metric: revenue_per_user

baseline: 12.50,

goal: 18.00

leading_indicators: [upgrade_conversion, feature_adoption_rate]

strategic_bets:

• bet: enterprise_expansion

hypothesis: Enterprise accounts will drive 3x revenue per user

confidence: 0.6

evidence: [customer_interviews, competitor_analysis, pricing_test]

• bet: mobile_experience

hypothesis: Mobile users convert at lower rates due to friction

confidence: 0.7

evidence: [funnel_analysis, session_recordings, survey_data]

Step 2 — Run Opportunity Assessment

Use product-manager to score our current feature backlog against our Q2 OKRs. Apply the RICE framework: Reach (users affected), Impact (metric lift per user), Confidence (how sure are we), Effort (person-weeks). Rank the top 10 opportunities and explain the tradeoffs for each. Present the analysis before any prioritization decisions.

Step 3 — Design an Experiment

product-manager experiment design \

--opportunity ./opportunities/referral-program.yaml \

--metric conversion_rate \

--minimum_detectable_effect 0.10 \

--confidence_level 0.95 \

--output ./experiments/referral-program-design.md

Outputs: hypothesis, control/treatment split, sample size, duration, success criteria

Step 4 — Review Weekly Product Metrics

Use product-manager to produce a weekly product metrics review for our dashboard at ./metrics/dashboard.json. Highlight: (1) which metrics are moving, (2) which are within expected variance vs. statistically significant changes, (3) which product bets are showing early signals. Flag anything that needs immediate attention.

Pros / Cons

Verdict

Product management is the bridge between what engineers build and why it matters to the business. Without that bridge, you get either engineering-led output (technically impressive, commercially irrelevant) or business-led output (feature overload, technical debt, user neglect). Product-Manager gives that bridge a structural foundation.

**Rating: Essential for product-led organizations. Valuable for any team where the cost of building the wrong thing is high.**