Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Before & after
Same prompt, same agent — the only difference is the skill.
RICE is a solid prioritization framework—it looks at Reach, Impact, Confidence, and Effort. You'd score each feature on those dimensions, then divide impact by effort weighted by reach and confidence. It's pretty straightforward conceptually, but getting consistent scoring across your team takes some work. The challenge is getting people to actually agree on what the numbers mean. You'd probably want to do a workshop with your product team and maybe some key stakeholders.
PRODUCT PRIORITIZATION: RICE SCORING MATRIX FRAMEWORK BREAKDOWN RICE = (Reach × Impact × Confidence) / Effort Scoring scale: Reach (users/month), Impact (1-3 scale), Confidence (%, 0-100), Effort (person-weeks) FEATURE SCORECARD 1. NATIVE DARK MODE Reach: 3,200 monthly active users Impact: 2 (nice-to-have, improves UX) Confidence: 95% (low uncertainty) Effort: 6 weeks RICE Score: (3200 × 2 × 0.95) / 6 = 1,013 2. BULK EXPORT TO CSV Reach: 800 users Impact: 3 (high value for enterprise) Confidence: 85% (some UX questions) Effort: 3 weeks RICE Score: (800 × 3 × 0.85) / 3 = 680 3. MOBILE APP LAUNCH Reach: 12,000 users (all users on mobile) Impact: 2 (incremental, not core feature) Confidence: 70% (mobile adoption unknown) Effort: 22 weeks RICE Score: (12000 × 2 × 0.70) / 22 = 764 4. REAL-TIME NOTIFICATIONS Reach: 5,600 users Impact: 3 (critical for power users) Confidence: 80% (requires new infrastructure) Effort: 12 weeks RICE Score: (5600 × 3 × 0.80) / 12 = 1,120 5. API ACCESS FOR INTEGRATIONS Reach: 2,100 users Impact: 3 (unlocks integrations) Confidence: 90% Effort: 10 weeks RICE Score: (2100 × 3 × 0.90) / 10 = 567 6. CUSTOM REPORTING TEMPLATES Reach: 4,200 users Impact: 2 (good-to-have) Confidence: 85% Effort: 8 weeks RICE Score: (4200 × 2 × 0.85) / 8 = 893 RANKED BY RICE SCORE 1. Real-time notifications (1,120) → PRIORITY 1 2. Native dark mode (1,013) → PRIORITY 2 3. Custom reporting templates (893) → PRIORITY 3 4. Mobile app launch (764) → PRIORITY 4 (reconsider scope) 5. Bulk CSV export (680) → PRIORITY 5 6. API access (567) → PRIORITY 6 QUARTERLY ROADMAP (Q3 capacity: 28 weeks) Q3 Sprint 1 (weeks 1-12): • Real-time notifications (12 weeks) → COMPLETE Q3 Sprint 2 (weeks 13-28): • Dark mode (6 weeks) → COMPLETE • Custom reporting (8 weeks) → COMPLETE • Buffer (6 weeks) → Reserve for bugs + scope creep OPPORTUNITY COST ANALYSIS Mobile app scores lower than 4 individual features. Recommend: Descope to mobile web responsive instead (2 weeks, score 720). Full native app → backlog for Q4. KEY INSIGHTS → Real-time notifications and dark mode both essential → Mobile app is effort-heavy; web-responsive is better ROI → API access enables customer integrations (consider bundling with #1) → Revisit mobile reach assumption (may be underestimated)
About this skill
"We ship features nobody uses" can mean no discovery, no launch, or no measurement, and each needs a different fix. This skill traces your team's symptom to the stage of the product loop that is actually broken and commits to one fix first.
What it does
- Checks seven stages (outcomes, discovery, prioritization, specification, delivery, launch, measurement) against evidence
- Tells apart root causes that look alike, such as missing goals vs a bad scoring model
- Lints an opportunity solution tree and a continuous-discovery cadence
- Names the one fix to make first, with an owner and a check date
- Points to the specific workflow to run next
What you get
A loop health table with evidence, a root cause with confidence, one first fix, the next workflow, and what to defer.
Best for
Heads of product, new product leaders, and founders who know the product process is off but not where.
SKILL.md preview
---
name: product-practice-diagnostic
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.
Audience Panel Review for Drafts and Ideas
Simulates 3-5 real people from your audience to react to a draft before launch, with tagged evidence, ranked edits, and follow-up questions.