Notre avis

Assiste les chefs de produit dans la rédaction de PRD, la priorisation de fonctionnalités (RICE), l'analyse de métriques et la communication avec les parties prenantes.

Points forts

Fournit des cadres structurés (RICE, PRD, grille de décision Go/No-Go)
Analyse les retours utilisateurs et en extrait des thèmes et citations
Aide à la rédaction de communications adaptées aux différents publics

Limites

Nécessite des données textuelles de qualité pour être efficace
Ne remplace pas l'intuition terrain ou les entretiens réels
Les scores RICE restent subjectifs (dépendent des inputs fournis)

Quand l'utiliser

Utilisez cette compétence pour structurer vos réflexions produit, rédiger des documents cadres ou prioriser des fonctionnalités à l'aide de méthodologies éprouvées.

Quand l'éviter

Évitez de l'utiliser pour des décisions nécessitant une connaissance approfondie non documentée ou pour remplacer des tests utilisateurs réels.

Exemples

Prioritize features with RICE

I have these features: 1) Dark mode - Reach: 50k users/week, Impact: high (2), Confidence: 80%, Effort: 2 person-months. 2) In-app search - Reach: 20k/week, Impact: medium (1), Confidence: 90%, Effort: 3 person-months. Calculate RICE scores and recommend priority order.

Write a PRD for a new feature

Write a PRD for a notification center in a project management app. The problem is users miss updates. Success metric: 20% increase in daily active users within 30 days. Include user stories, acceptance criteria, edge cases, and out-of-scope items.

Analyze user interview transcript

Here are three user interview quotes about our analytics dashboard: 'I can't find the export button', 'The charts take too long to load', 'I wish I could filter by date range'. Synthesize the top pain points, group by theme, and suggest two opportunity areas with supporting quotes.

name: product-manager description: Product management: PRDs, RICE prioritization, metrics allowed-tools: Read, Write, Grep

Product Manager

Assists with core product management workflows including research synthesis, requirement documentation, feature prioritization, and strategic communication.

When to Use

Analyzing user interviews, surveys, or feedback
Writing or reviewing PRDs and product requirements
Prioritizing features or roadmap items
Preparing stakeholder updates or presentations
Interpreting product metrics and analytics
Conducting competitive analysis

Instructions

User Research Analysis

When analyzing user research:

Read the provided transcripts, feedback, or survey data
Identify the top 3-5 pain points with supporting quotes
Group insights by themes (not by individual users)
Prioritize by frequency AND impact
Suggest 2-3 actionable opportunity areas
Include specific quotes to support each finding

Feature Prioritization

When prioritizing features, use the RICE framework:

Reach: How many users impacted per time period?
Impact: Confidence score (0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive)
Confidence: Data quality (0-100%)
Effort: Person-months required
RICE Score = (Reach × Impact × Confidence) / Effort

Present results in a table with reasoning for each score.

PRD Writing

When creating or reviewing PRDs, ensure these sections:

Problem Statement: Clear user problem with evidence
Success Metrics: Quantifiable measures (not "improve UX")
User Stories: Format: "As a [user], I want [action] so that [benefit]"
Acceptance Criteria: Testable, specific conditions
Edge Cases: Error states, boundary conditions, empty states
Out of Scope: What we're explicitly NOT building

Flag any missing or unclear sections.

Stakeholder Communication

When drafting communications:

Lead with impact/outcome, not features
Match tone to audience (C-level: business impact; Eng: technical details)
Use specific metrics, not vague terms like "better" or "improved"
Include next steps with owners and timelines
Be transparent about blockers/challenges

Metrics Analysis

When analyzing metrics:

Calculate key ratios (DAU/MAU, retention cohorts, conversion rates)
Identify trends (week-over-week, month-over-month)
Flag anomalies requiring investigation
Distinguish between correlation and causation
Provide 2-3 actionable recommendations

Quick Reference

Problem Validation Checklist:

[ ] Problem clearly articulated?
[ ] Validated with real users (not assumptions)?
[ ] Frequent/painful enough to solve?
[ ] Users will pay/engage more if solved?
[ ] Technically feasible within constraints?

Go/No-Go Decision Criteria:

Strategic alignment with company vision?
Solves a validated user problem?
Moves key metrics meaningfully?
Team can build and maintain it?
Strengthens competitive differentiation?

Guidelines

Focus on outcomes (metrics moved) over outputs (features shipped)
Validate assumptions with data before building
Write testable, specific requirements (avoid "intuitive" or "easy to use")
Consider edge cases: errors, empty states, loading states
Question vanity metrics (prioritize engagement over page views)
Be explicit about trade-offs in prioritization decisions

Automatic Triggers:

User pastes interview transcripts or feedback
User asks to prioritize features or compare options
User mentions "PRD", "product requirements", or "user stories"
User shares metrics data or analytics
User requests stakeholder updates or presentations

Gestionnaire de Produit

Recommandé pour