#product-management

Prioritize product features using RICE scoring. Methodology: 1. Reach (how many users affected per quarter). 2. Impact (how much it improves user experience, 0.25-3 scale). 3. Confidence (certainty in estimates, 0-100%). 4. Effort (person-months required). Calculate RICE score: (Reach × Impact × Confidence) / Effort. Rank features by score. Include qualitative factors (strategic fit, technical debt). Create prioritization matrix visualization. Involve cross-functional stakeholders in scoring.

Conduct comprehensive user research program. Process: 1. Define research objectives and key questions. 2. Create user interview guide with open-ended questions. 3. Conduct usability testing sessions with task scenarios. 4. Implement surveys for quantitative data collection. 5. Perform competitive analysis and market research. 6. Create user personas based on research findings. 7. Build empathy maps and customer journey maps. 8. Synthesize insights into actionable product recommendations. Include recruitment criteria and analysis templates.

Act as a Head of Product. I have a list of 20 potential features for our next quarterly roadmap. Our key business goals are to increase user retention and expand into a new market segment. Use a prioritization framework like RICE (Reach, Impact, Confidence, Effort) or MoSCoW (Must-have, Should-have, Could-have, Won't-have) to help me decide which features to focus on. Explain your reasoning.

Create a strategic product roadmap for the next 3 quarters. Framework: 1. Theme-based organization (not feature list). 2. Now/Next/Later timeline visualization. 3. Strategic initiatives aligned to company OKRs. 4. Customer impact and business value scoring. 5. Resource allocation and dependencies. 6. Success metrics for each initiative. Use tools like ProductPlan or Aha!. Balance innovation vs maintenance. Include stakeholder communication plan. Update monthly based on learnings.

Create a comprehensive PRD (Product Requirements Document) template. Sections: 1. Executive Summary (Problem, Solution, Success Metrics). 2. User Stories and Personas. 3. Functional Requirements (Must-have vs Nice-to-have). 4. Technical Constraints and Dependencies. 5. Success Criteria and KPIs. 6. Timeline and Milestones. 7. Open Questions and Risks. Use clear, unambiguous language. Include wireframes placeholders and acceptance criteria for each requirement.