AI Prompts for ChatGPT for Product Managers

Help me write a crisp product problem statement. Context: [DESCRIBE THE USER SEGMENT, THE SITUATION THEY ARE IN, AND THE PAIN OR UNMET NEED]. The problem statement should: identify the specific user, describe the situation in which the problem occurs, articulate the pain or friction in one sentence, and explain the business impact of not solving it. Format as a single paragraph and as a "How might we" question. Avoid solution language in the problem statement.

I have completed [X] user interviews and [Y] survey responses. Here are the key themes I observed: [PASTE OR DESCRIBE THEMES]. Help me synthesize this into: (1) a Jobs-to-be-Done statement for the primary user, (2) a list of the top 3 unmet needs ranked by frequency and intensity, (3) the key insight that should guide our product direction, and (4) 3 open questions that need further research before we can design a solution. Keep each section concise and actionable.

Help me structure a competitive analysis for [PRODUCT/FEATURE AREA]. My direct competitors are [LIST]. My indirect competitors are [LIST]. For each competitor, I want to evaluate: core value proposition, primary user segment, key features and differentiators, pricing model, and known weaknesses. After the comparison table, write a 150-word "Competitive Gap Analysis" identifying the underserved segment or missing capability my product could own. Format the comparison as a table.

Write a testable product hypothesis for this idea: [DESCRIBE THE FEATURE OR PRODUCT CHANGE]. Structure it using the format: "We believe that [DOING X] for [USER SEGMENT] will result in [OUTCOME], as measured by [METRIC]. We will know we are right when [SPECIFIC, MEASURABLE SIGNAL]." Then generate 2 alternative hypotheses I should also consider testing. Explain what assumption each hypothesis is testing and what would invalidate it.

Help me write an opportunity sizing section for a product proposal. Here is my data: [TOTAL ADDRESSABLE MARKET, SERVICEABLE ADDRESSABLE MARKET, CURRENT PRODUCT USAGE DATA, RELEVANT INDUSTRY STATS]. Translate this data into a compelling 200-word narrative that makes the business case for investing in this area. Show the path from current state to the long-term opportunity without overstating certainty. Write for a VP or C-suite audience who will push back on weak assumptions.

Write a PRD for [FEATURE NAME]. Background: [DESCRIBE WHY WE ARE BUILDING THIS, WHAT PROBLEM IT SOLVES, AND WHAT WE HAVE ALREADY LEARNED FROM DISCOVERY]. Target user: [DESCRIBE]. Success metrics: [LIST 2-3 METRICS]. In scope: [LIST]. Out of scope: [LIST]. Write the following sections: Problem Statement, Goals and Non-Goals, User Stories (5-7 stories in "As a [USER], I want to [ACTION] so that [OUTCOME]" format), Functional Requirements (numbered list), Non-Functional Requirements, and Open Questions. Keep each section sharp and avoid padding.

Write a complete user story with acceptance criteria for: [DESCRIBE THE FEATURE OR FUNCTIONALITY IN PLAIN LANGUAGE]. Format: User Story ("As a [PERSONA], I want to [ACTION] so that [BENEFIT]"), Acceptance Criteria (Given/When/Then format, 4-6 scenarios covering the happy path, edge cases, and error states), and Definition of Done (checklist of quality and non-functional requirements). Make the acceptance criteria specific enough that an engineer and QA can test them without asking follow-up questions.

I am building [DESCRIBE THE FEATURE]. The primary happy path is: [DESCRIBE USER FLOW]. Generate a comprehensive list of edge cases and failure scenarios I need to account for in the spec. Organize by category: user input edge cases, system/network failure scenarios, permission and access edge cases, data edge cases, and concurrency or race condition scenarios. For each edge case, note the expected behavior the product should exhibit.

Help me draft the API requirements section of a PRD for [FEATURE]. The feature requires [DESCRIBE DATA NEEDS AND USER ACTIONS]. For each API endpoint we need, specify: method (GET/POST/PUT/DELETE), endpoint path pattern, request parameters and body, response structure, error codes and messages, authentication requirements, and rate limiting needs. Also note any dependencies on third-party APIs or existing internal services.

My team needs to cut scope for [FEATURE] due to [TIME CONSTRAINT/RESOURCE CONSTRAINT]. Here is the full feature list: [PASTE FEATURE LIST OR USER STORIES]. Help me apply a MoSCoW prioritization (Must Have, Should Have, Could Have, Won't Have this time). For each item, reason through: impact on core user value, technical dependency order, implementation complexity, and business risk of deferring. Produce a recommended cut list with a one-sentence justification for each item I am deferring.

Help me score these backlog items using the RICE framework (Reach, Impact, Confidence, Effort). Here are my items: [LIST 5-10 ITEMS WITH A BRIEF DESCRIPTION EACH]. For each item, suggest a score for Reach (how many users affected per quarter), Impact (0.25 to 3 scale), Confidence (10%-100%), and Effort (person-months). Calculate the RICE score for each and rank the list. Flag any items where my confidence score should be lower because I lack data, and suggest what I would need to validate them.

Help me structure a Now/Next/Later product roadmap for [PRODUCT AREA]. Now = current sprint/quarter, Next = next quarter, Later = 6-12 months. Here are the initiatives I am considering: [LIST INITIATIVES WITH BRIEF DESCRIPTIONS]. Assign each to the appropriate horizon based on: strategic priority, technical readiness, customer demand signals, and dependency order. For each initiative, write a one-sentence "why now/next/later" justification. Format as a roadmap table.

A stakeholder is pushing me to add [FEATURE/SCOPE] to the roadmap this quarter. My reasons for not prioritizing it are: [LIST YOUR REASONS]. Write a professional, non-defensive response I can use in a meeting or email that: acknowledges their input and the business case for the feature, explains the current prioritization logic and what it would displace, offers a concrete alternative (deferral to next quarter, partial scope, data-first approach), and closes with alignment on how we will make the decision. Keep it collaborative, not defensive.

Draft product OKRs for next quarter for [PRODUCT AREA OR TEAM]. Our strategic focus is [DESCRIBE]. Key inputs: [DESCRIBE COMPANY OBJECTIVES, USER RESEARCH THEMES, AND BUSINESS METRICS YOU NEED TO MOVE]. Write 1 Objective and 3 Key Results. The Objective should be inspirational and direction-setting. Each Key Result should be: measurable with a specific number, achievable but stretching, outcome-focused (not activity-focused), and tied to a metric we already track or can begin tracking. Also note the leading indicator for each KR.

Help me map dependencies for this initiative: [DESCRIBE THE PRODUCT INITIATIVE]. Teams involved: [LIST: ENGINEERING, DESIGN, DATA, MARKETING, LEGAL, ETC.]. For each dependency, identify: what needs to be delivered, which team owns it, what the critical path sequence is, and what the risk is if this dependency is late. Output a dependency table and a short narrative summary of the highest-risk dependencies I should flag in my roadmap presentation.

Write an internal launch announcement for [FEATURE NAME] going live on [DATE]. Audience: [COMPANY-WIDE/SALES TEAM/SUPPORT TEAM]. Include: what we built and why (one paragraph), the user problem it solves, key things the team needs to know (how to access, what's changed, any known limitations), a link to documentation, and who to contact with questions. Keep it energetic and specific, under 300 words. This should make the team proud of what we shipped.

Write user-facing release notes for this product update: [DESCRIBE WHAT CHANGED]. For each change, write: a one-line headline, a 2-3 sentence description of what changed and why it's better for the user, and if applicable, a note about any migration or action required. Organize into sections: New Features, Improvements, Bug Fixes. Write at a product-literate user level. Avoid engineering jargon. Keep the tone helpful and direct.

Help me write a blameless postmortem for a product incident: [DESCRIBE WHAT HAPPENED, WHEN, DURATION, USER IMPACT]. Structure: Timeline of events (bullet points with timestamps), Root Cause Analysis (use 5 Whys to find the systemic cause, not a person), Impact Assessment (users affected, revenue impact, trust impact), Immediate Actions Taken, Long-Term Remediation Plan (3-5 specific action items with owners and due dates), and Lessons Learned. Write in a blameless, factual tone focused on systems and processes, not individuals.

Write a one-page executive status update for [INITIATIVE NAME] to be shared with [VP/C-SUITE/BOARD]. Current status: [ON TRACK/AT RISK/BLOCKED]. Key updates: [DESCRIBE PROGRESS, DECISIONS MADE, CHANGES TO PLAN]. Format: Status (green/yellow/red with one-sentence reason), Summary (3 bullets on progress this period), Key Decisions Needed (if any), Risks and Mitigations (2-3 items), and Next Milestones with dates. Write with the directness and brevity executives expect. No filler sentences.

Write an A/B test plan for testing [HYPOTHESIS ABOUT THE FEATURE OR CHANGE]. Include: Test Name, Hypothesis (in "If we change X, then Y will happen because Z" format), Control (current state), Variant(s) (what we are changing), Primary Metric (what we are trying to move), Guardrail Metrics (what we must not break), Target Sample Size and Statistical Power, Minimum Detectable Effect, Estimated Run Time, and Rollout Plan. Flag any data or instrumentation dependencies we need in place before the test can run.