Product Prompts

Design a rigorous A/B test for product optimization. Process: 1. Define hypothesis (changing X will increase Y by Z%). 2. Choose primary and secondary metrics. 3. Calculate required sample size for statistical power. 4. Determine test duration (minimum 1 week, 2 business cycles). 5. Randomize users (50/50 split). 6. Implement tracking and QA. 7. Monitor for novelty effects and external factors. Analyze results with statistical significance testing. Document learnings. Iterate based on insights.

Apply Jobs-to-be-Done framework for product strategy. Structure: 1. Identify the 'job' customers are hiring your product for. 2. Map functional, emotional, and social dimensions. 3. Understand the 'struggling moment' that triggers the job. 4. Analyze competing solutions (including non-consumption). 5. Define success criteria from customer perspective. 6. Uncover unmet needs and innovation opportunities. Conduct switch interviews to understand why customers switched to/from your product. Use insights to guide product development.

Comprehensive product launch checklist across teams. Categories: 1. Product (feature complete, tested, documented). 2. Engineering (deployed, monitored, rollback plan). 3. Design (UI polished, onboarding flow). 4. Marketing (landing page, blog post, email campaign). 5. Sales (pitch deck, demo, pricing). 6. Support (help docs, FAQs, training). 7. Legal (terms updated, compliance). Timeline: 4 weeks pre-launch to 2 weeks post-launch. Assign owners and deadlines. Track in project management tool.

Create a detailed competitive feature comparison. Matrix structure: 1. List 5-7 key competitors (rows). 2. Define 15-20 critical features (columns). 3. Score each: ✓ (has), ✗ (missing), ⚠ (partial). 4. Add pricing tier for each feature. 5. Highlight your product's unique features. 6. Identify feature gaps and opportunities. Use color coding for visual clarity. Include market positioning insights. Update quarterly. Use for product strategy and sales enablement.

Build a comprehensive product metrics dashboard. Key metrics: 1. Acquisition (signups, activation rate). 2. Engagement (DAU/MAU, feature adoption). 3. Retention (cohort analysis, churn rate). 4. Revenue (MRR, ARPU, LTV). 5. Referral (viral coefficient, NPS). Use AARRR (Pirate Metrics) framework. Create separate views for different stakeholders. Include trend lines and targets. Set up automated alerts for anomalies. Use tools like Mixpanel, Amplitude, or custom SQL dashboards.

Design a comprehensive user research interview protocol. Structure: 1. Introduction and rapport building (5 min). 2. Background questions (user context, current workflow). 3. Behavioral questions (tell me about a time...). 4. Pain point exploration (what frustrates you?). 5. Solution validation (prototype feedback). 6. Wrap-up and thank you. Use open-ended questions. Avoid leading questions. Practice active listening. Record with permission. Aim for 30-45 min interviews. Synthesize findings into insights and themes.

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.

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.

Facilitate a user story mapping session for product planning. Process: 1. Define user personas and their goals. 2. Map user activities (horizontal backbone). 3. Break down activities into tasks (vertical stories). 4. Prioritize stories into releases (MVP, V2, V3). 5. Identify dependencies and risks. 6. Estimate effort and value. Use collaborative tools (Miro, Mural). Output: visual story map with clear release plan. Include acceptance criteria for each story. Align team on product vision and roadmap.