Category 1: Product Strategy & Vision
1. The “Working Backwards” Press Release (Amazon Method)
Act as a seasoned product strategist at a FAANG company. I am developing a new product, [Product Name], which is a [brief, one-sentence description, e.g., an AI-powered meal planning app for busy families]. Draft a "working backwards" Press Release for its launch, dated one year in the future. The press release must be compelling, customer-centric, and clearly articulate the problem it solves, the solution, and the primary benefits. Follow this with a detailed FAQ section that anticipates and answers tough questions from both customers (e.g., 'How is this different from [Competitor A]?') and internal executives (e.g., 'What is the projected impact on our core business?').
2. Strategic Moat and Defensibility Analysis
You are a business strategy analyst. I am the PM for [Product Name], which operates in the [Market/Industry, e.g., B2B SaaS for cybersecurity]. My key competitors are [Competitor A], [Competitor B], and [Competitor C]. Analyze the competitive landscape and generate a strategic moat analysis in a markdown table. Evaluate my product and each competitor based on the following defensibility types: Network Effects, Switching Costs, Economies of Scale, Brand, and Counter-Positioning. For each, rate the strength from 1-5 and provide a concise justification. Conclude with a summary of my product's most significant competitive vulnerability and a strategic recommendation to strengthen its moat.
3. Cascading OKR (Objectives and Key Results) Formulation
Act as a product leadership coach. Our company's top-level objective for the next quarter is: '[Company Objective, e.g., Increase market share in the enterprise segment]'. My product is [Product Name]. Help me cascade this into a powerful Product Objective and 3-4 ambitious, measurable Key Results for my team. The Product Objective should clearly state how my product will contribute to the company goal. The Key Results must be quantifiable outcomes, not outputs (e.g., 'Increase enterprise user activation rate by 15%' is a KR; 'Ship feature X' is not). Explain the rationale behind each proposed KR.
4. Market Opportunity Sizing with TAM, SAM, SOM
You are a market research analyst. I am exploring a new feature initiative for [Product Name] targeting the [new user segment or problem area, e.g., freelance graphic designers who need better collaboration tools]. Conduct a high-level market sizing analysis. Define and estimate the Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM). Clearly state your assumptions for each calculation. Provide the output in a structured format and conclude with a recommendation on whether the market size justifies a significant product investment.
5. “Product Principles” Generation for Decision Making
Act as a VP of Product. My team is building [Product Name], and we often struggle with making consistent trade-off decisions between [dilemma 1, e.g., speed vs. quality] and [dilemma 2, e.g., user experience simplicity vs. feature power]. Generate a list of 5-7 opinionated and memorable Product Principles for our team. Each principle should be a clear, concise statement that serves as a tie-breaker in decision-making. For each principle, provide a short "What it means" and "What it doesn't mean" section to add clarity. For example, a principle could be "Simplicity is the highest form of sophistication."
Category 2: User Research & Customer Empathy
6. Jobs-to-be-Done (JTBD) Interview Script Generator
You are a senior user researcher specializing in the Jobs-to-be-Done framework. I need to conduct customer interviews to understand why users hire our product, [Product Name]. Generate a 10-question interview script designed to uncover the user's "job," including the functional, social, and emotional dimensions. The questions should be open-ended, non-leading, and focused on past behaviors rather than future intentions. Include probing follow-up questions for each primary question to dig deeper into their struggles, motivations, and the "push" and "pull" factors that led to their purchase decision.
7. Persona “Red Team” Challenge
Act as a skeptical product critic. Below is my primary user persona for [Product Name]. Your task is to "Red Team" it. Aggressively challenge the assumptions, biases, and potential blind spots in this persona. Identify where the persona is likely an oversimplification. Pose 5-7 difficult questions that would force me to validate or reconsider my understanding of the user. Conclude with three suggestions for research activities to make this persona more robust and grounded in reality.
[Paste your User Persona description here]
8. Synthesis of Raw User Feedback into Actionable Insights
You are an AI research synthesizer. I have a collection of raw user feedback about [Product/Feature Name] from various sources (support tickets, app store reviews, survey responses). Your task is to process this raw data, identify the top 5 recurring themes, and categorize them as either 'Pain Points,' 'Feature Requests,' or 'Positive Feedback.' For each theme, provide a representative user quote, estimate its frequency (low, medium, high), and formulate a concise, actionable "How might we..." statement that my team can use for brainstorming solutions.
[Paste up to 2-3 pages of raw, anonymized user feedback here]
9. Empathy Map for a Negative User Journey
Act as a UX designer. I need to build deeper empathy for a frustrating user experience within my product, [Product Name]. The specific journey is: [Describe the negative journey, e.g., 'A new user trying to set up their first project template but failing because the UI is confusing']. Create a detailed Empathy Map for a user going through this specific negative journey. Fill out the four quadrants: Says, Thinks, Feels, and Does. Be specific and use emotive language. Conclude with a list of 3 key 'Pains' and 3 potential 'Gains' (opportunities for improvement) derived directly from the map.
10. “Five Whys” Root Cause Analysis on a User Behavior
You are a data-driven Product Manager. We've observed a troubling metric in our analytics for [Product Name]: [State the specific metric and the negative trend, e.g., '75% of users drop off during the onboarding process at the 'invite-a-teammate' step']. Apply the "Five Whys" root cause analysis technique to drill down from this surface-level data point to a potential root cause. Formulate each "Why?" as a question, and then provide a plausible, hypothetical answer that leads to the next question. Present this as a chain of 5 questions and answers, ending with a testable hypothesis about the fundamental problem to solve.
Category 3: Prioritization & Roadmapping
11. RICE Score Prioritization Simulation
Act as a Lead Product Manager facilitating a prioritization meeting. I have a list of potential features to build. For each feature, I've provided a brief description. Your task is to lead me through a RICE scoring exercise. For each feature, ask me clarifying questions to estimate the Reach, Impact, Confidence, and Effort. Then, calculate the RICE score and present the final prioritized list in a markdown table. Force me to justify my assumptions for each component of the score.
Here are the features:
- Feature A: [Description]
- Feature B: [Description]
- Feature C: [Description]
12. Kano Model Feature Classification
You are an expert in the Kano Model of customer satisfaction. Analyze the following list of features for my product, [Product Name]. Classify each feature into one of the three main Kano categories: 'Basic Expectations' (must-haves), 'Performance Payoffs' (more is better), and 'Delighters' (exciters). For each classification, provide a brief rationale explaining why it fits that category from a user's perspective. Finally, explain the strategic implication of this analysis for my product roadmap (e.g., 'We must invest in all Basic Expectations before focusing on Delighters').
Feature List:
1. [Feature X]
2. [Feature Y]
3. [Feature Z]
13. Stakeholder-Centric Roadmap Narrative
Act as a master communicator and storyteller. I need to present my product roadmap for the next two quarters to different audiences. Take my list of planned epics and features and weave them into three distinct, compelling narratives, each tailored for a specific audience:
1. **For the Executive Team:** Focus on business outcomes, strategic alignment, and competitive advantage.
2. **For the Engineering Team:** Focus on the technical challenges, user problems we're solving, and the 'why' behind the sequencing.
3. **For the Sales & Marketing Team:** Focus on customer benefits, market differentiation, and key messaging points they can use.
My planned epics are: [List 3-5 major epics or features, e.g., 'Q1: User Profile Redesign', 'Q1: Integration with Slack', 'Q2: New Analytics Dashboard'].
14. Opportunity Solution Tree Brainstorm
You are a product discovery coach who champions the Opportunity Solution Tree framework. My desired outcome for the next quarter is: '[State a clear, measurable outcome, e.g., 'Increase user retention by 10% for our mobile app'].' Guide me in building an Opportunity Solution Tree. Start by brainstorming at least four distinct user-centric 'Opportunities' (unmet needs or pain points) that could lead to this outcome. For the top-voted opportunity, generate three different 'Solutions' (feature ideas). Finally, for one of those solutions, suggest two 'Experiments' we could run to test the idea quickly. Structure your output clearly in a tree format.
15. Cost of Delay Prioritization Argument
Act as a product leader skilled in quantitative decision-making. I have two critical initiatives competing for the same limited engineering resources, but we can only do one next quarter.
- Initiative A: [Description of initiative A, e.g., 'A new feature that our biggest enterprise customer is demanding'].
- Initiative B: [Description of initiative B, e.g., 'A major refactor to reduce technical debt and improve site performance'].
Frame this prioritization decision using the 'Cost of Delay' framework. For each initiative, create a short, persuasive argument outlining the potential cost of delaying it for one quarter, considering factors like user value, revenue impact, and operational efficiency. Conclude with a recommendation, justifying it based on minimizing the overall Cost of Delay.
Category 4: Execution & Stakeholder Management
16. Gherkin-Style User Story & Acceptance Criteria Generation
You are an expert Agile Product Owner. I need to write a user story for my development team. The goal is to [describe the feature's goal, e.g., allow users to reset their password via email].
1. Write a classic user story in the format: "As a [user type], I want to [action], so that [benefit]."
2. Generate a comprehensive set of at least 5-7 Acceptance Criteria (AC) for this story.
3. Write the most critical ACs in the Gherkin syntax: `Given [context], When [action], Then [outcome]`. This will ensure they are unambiguous and testable.
17. “Pre-Mortem” Risk Analysis and Mitigation Plan
Act as a seasoned program manager. My team is about to kick off a complex project: [Project Description, e.g., 'Migrating our entire user database to a new service provider']. Conduct a "pre-mortem" analysis. Imagine it is six months from now and the project has failed spectacularly. Brainstorm and list at least 10 potential reasons for this failure, covering technical, product, communication, and dependency risks. Then, for the top 3 most likely risks, create a proactive mitigation plan with specific, actionable steps we can take *today* to prevent them from happening.
18. Stakeholder Communication Matrix
You are a senior product manager skilled in stakeholder management. I am leading the launch of [Feature Name]. My key stakeholders are: Engineering Lead, Head of Sales, Director of Customer Support, VP of Marketing, and the CTO. Create a Stakeholder Communication Matrix in a markdown table. The columns should be: 'Stakeholder', 'What They Care About', 'Key Message for Them', 'Communication Method' (e.g., Slack, email, meeting), and 'Frequency'. Fill this out to create a clear communication plan that ensures everyone stays informed and aligned without being overwhelmed.
19. Drafting a “Decision Log” Entry
Act as a meticulous Product Owner who values clear documentation. We just made a critical product decision: [Describe the decision, e.g., 'We decided to use a third-party payment provider (Stripe) instead of building our own from scratch']. Draft a clear, concise "Decision Log" entry for our internal documentation. It must include:
- **Decision:** The final decision made.
- **Date:** Today's date.
- **Status:** Decided.
- **Context:** Brief background on the problem.
- **Options Considered:** List the alternatives (e.g., 1. Build in-house, 2. Use Stripe, 3. Use Adyen).
- **Rationale for Decision:** The specific reasons we chose this option (e.g., speed to market, security compliance, developer experience).
- **Expected Impact:** What this decision enables or changes.
20. Technical Debt Negotiation Script
Act as a product director coaching a PM on how to negotiate with their engineering counterpart. My Engineering Lead wants to dedicate the next entire sprint (2 weeks) to paying down technical debt in our [specific part of the codebase]. I need to push for shipping [Feature X] which has a hard external deadline. Draft a conversational script for me to use in this discussion. The script should:
1. Acknowledge and validate the engineer's concerns about tech debt.
2. Clearly articulate the business impact and urgency of Feature X.
3. Propose a specific compromise (e.g., 'Can we allocate 20% of the next 3 sprints to this debt? Or can we dedicate one full sprint after this deadline passes?').
4. Focus on collaborative problem-solving rather than conflict.
Category 5: Go-to-Market & Post-Launch Analysis
21. Tiered Launch Communication Plan
You are a Go-to-Market specialist. We are launching a new feature, [Feature Name], on [Launch Date]. Create a tiered internal communication plan to ensure the right people know the right information at the right time. Define three tiers of features (e.g., Tier 1: Major strategic launch, Tier 2: Significant improvement, Tier 3: Minor enhancement) and assume this is a Tier 2 launch. Outline the communication plan for different audiences (Leadership, Sales, Customer Support, All Company) detailing the timing, channel, and key message for each.
22. A/B Test Hypothesis and Metrics Definition
Act as a data scientist specializing in product experimentation. I want to run an A/B test to improve [a specific metric, e.g., sign-up conversion rate on our homepage]. The proposed change is [describe the change, e.g., 'changing the primary call-to-action button from 'Learn More' to 'Get Started Free' '].
1. Formulate a strong, structured hypothesis using the format: "Because we observe [data/insight], we believe that [change] for [user segment] will result in [impact]. We will know we are right when we see [primary success metric] change by [expected %] with statistical significance."
2. Define the Primary Metric to track.
3. List at least two Guardrail Metrics (metrics to watch to ensure we're not causing unintended harm, e.g., account deletion rate).
23. “Feature Onboarding” Teardown and Improvement Plan
You are a growth product manager. I want you to analyze the user onboarding flow for a popular product, [choose a well-known app like Slack, Notion, or Duolingo]. Perform a teardown of its first-time user experience (FTUE) for a key feature.
1. Map out the key steps in the onboarding journey for that feature.
2. Identify one "Aha!" moment the flow is designed to create.
3. Pinpoint two areas of friction or potential confusion.
4. Based on this analysis, propose three specific, actionable recommendations for how I could improve the onboarding for my own product's [Feature Name].
24. Feature Sunset/Deprecation Communication Plan
Act as a senior PM who has to make a tough decision. We have decided to sunset a legacy feature, [Feature Name], because of low usage and high maintenance costs. The feature will be removed from the product in 60 days. Draft a clear, empathetic, and direct communication plan. This must include:
1. An email template to send to the small cohort of active users of the feature.
2. A brief in-app notification message.
3. Talking points for the Customer Support team on how to handle user complaints.
The communication must explain the 'why' behind the decision, acknowledge the inconvenience, and where possible, suggest an alternative workflow.
25. Launch Retrospective (Post-Mortem) Facilitation Agenda
You are an Agile coach facilitating a retrospective (post-mortem) after a recent product launch. Create a detailed agenda for a 60-minute meeting. The goal is a blameless retrospective that generates actionable improvements for the next launch. The agenda should include specific timings, key questions to ask the team, and activities for each section. Structure it around these three parts:
1. **What went well?** (Celebrate successes)
2. **What could have gone better?** (Identify challenges)
3. **What will we commit to improving next time?** (Define concrete action items with owners)
