ChatGPT Prompts for Product Managers

Write a complete Product Requirements Document (PRD) for the following feature or product:

Feature/Product name: [name]
Product context: [brief description of the product it belongs to, the company type, and the business model]
Problem being solved: [describe the user problem or business problem in 2-3 sentences]
Target user: [specific user persona — job title, context, and pain point]
Business objective: [what business metric does this improve? e.g., activation rate, retention, revenue]

Structure the PRD with these sections:

**1. Overview**: Problem statement, proposed solution, and why now (1 paragraph each)
**2. Goals and success metrics**: 3-5 measurable success criteria with baseline and target values
**3. Non-goals**: What this feature explicitly will NOT do (to prevent scope creep)
**4. User stories**: 5-8 user stories in "As a [user], I want [action] so that [outcome]" format
**5. Functional requirements**: Numbered list of what the feature must do
**6. Non-functional requirements**: Performance, security, accessibility requirements
**7. UX/Design considerations**: Key user flows and edge cases to address
**8. Technical considerations**: Known dependencies, API requirements, or architectural notes (leave placeholders for engineering to fill)
**9. Launch plan**: Phased rollout recommendation (MVP vs V1 vs V2)
**10. Open questions**: 3-5 questions that need answers before development begins
**11. Appendix**: Relevant research, data, or competitive examples

Target length: 800-1200 words. Write for both engineering and stakeholder audiences.

Write a complete set of user stories with acceptance criteria for the following feature:

Feature: [describe the feature]
Product: [product name and type]
Users involved: [list the user types who interact with this feature]
Business context: [why does this feature exist? What metric does it improve?]

For each user story:
1. **User story**: "As a [specific user persona], I want [specific action] so that [specific outcome]"
   - Be specific: don't write "As a user" — name the persona ("As a free-tier user who hasn't set up their profile")
   - The action should describe intent, not implementation
   - The outcome should describe a tangible benefit, not a feature

2. **Acceptance criteria** (Given/When/Then format):
   - Given [precondition]
   - When [action taken]
   - Then [expected result]
   - Include at least 3 criteria per story: the happy path, an edge case, and an error state

3. **Story points estimate**: Suggest a relative complexity estimate (1, 2, 3, 5, 8, 13) and explain the rationale in one sentence

4. **Dependencies**: Note any other stories or systems this depends on

Write [5-8] user stories covering: the primary happy path, [2-3] alternative flows, [1-2] error/edge cases, and [1] admin or internal user story (if applicable).

Help me prioritize the following product backlog items using the RICE scoring framework (Reach × Impact × Confidence ÷ Effort).

My product: [product name and brief description]
Current business priority: [e.g., improving activation rate, reducing churn, growing revenue]
Quarter timeframe: [Q1/Q2/Q3/Q4 YEAR]

Backlog items to score:
1. [Feature/initiative 1]: [one-line description]
2. [Feature/initiative 2]: [one-line description]
3. [Feature/initiative 3]: [one-line description]
4. [Feature/initiative 4]: [one-line description]
5. [Feature/initiative 5]: [one-line description]
6. [Feature/initiative 6]: [one-line description]

For each item, estimate and score:
- **Reach** (users impacted per quarter): Low/Med/High + estimated number
- **Impact** (effect on the target metric): Score 0.25 / 0.5 / 1 / 2 / 3
- **Confidence** (how certain are we): 50% / 80% / 100%
- **Effort** (person-weeks to ship): Estimate and note assumptions

Calculate the RICE score for each item and rank them.

After scoring:
1. Identify the top 3 "quick wins" (high RICE score, low effort)
2. Identify any item that ranks high in RICE but should still be delayed (strategic or technical reasons)
3. Flag items with low confidence scores that need more discovery before committing
4. Recommend a quarterly roadmap sequence based on the scores

Write a competitive analysis brief comparing [my product] to [competitor 1] and [competitor 2] in the [product category] market.

My product context:
- Product: [name and 1-sentence description]
- Target user: [who uses it]
- Key differentiators (our hypothesis): [list 2-3]
- Current weaknesses (be honest): [list 1-2]
- Business model: [pricing and monetization]

For each competitor, structure the analysis:

**[Competitor name]**
1. Overview: What they do, who they serve, estimated scale
2. Pricing model: How they charge, entry price, and enterprise tier
3. Core strengths: What they genuinely do better than us (be fair)
4. Core weaknesses: Where they fall short or receive complaints (use review site data framing: "Users frequently report...")
5. Target segment overlap: What % of their users also look at us?
6. Recent moves: Product launches, funding, acquisitions, or strategy shifts in the last 12 months
7. Our competitive response: How should we position against this competitor in sales conversations?

**Competitive matrix**: Create a comparison table with 8-10 features/criteria and indicate which product wins each (Competitor 1 / Competitor 2 / Us / Tie)

**Strategic implications**: 3 bullet points on what this analysis means for our roadmap and positioning

Help me write a set of OKRs (Objectives and Key Results) for a product team at [company type: startup / growth-stage / enterprise] working on [product type].

Company-level context:
- Company's top priority this quarter: [e.g., double ARR, launch in new market, reduce churn by 20%]
- Product team's charter: [what the product team is responsible for]
- Current key metrics baseline: [list 2-3 with current values]

Write 3 Objectives for the product team (one for each of these lenses):
1. A **customer-centric objective**: focused on user value and experience
2. A **business-results objective**: focused on revenue, growth, or efficiency metrics
3. A **team-capability objective**: focused on improving the team's speed, quality, or process

For each Objective:
- Write the Objective statement: aspirational, directional, memorable (1 sentence, no numbers)
- Write 3-4 Key Results: specific, measurable, time-bound outcomes (not activities)
  - Each KR should have a baseline value and a target value
  - Mix leading and lagging indicators (don't only use lagging metrics like revenue)
  - Include at least 1 "guardrail" KR that ensures you don't sacrifice one metric to hit another

After writing the OKRs:
- Flag any Key Results that are output-focused (what we ship) rather than outcome-focused (what changes for users/business) and suggest how to rewrite them
- Identify potential conflicts between the 3 Objectives

Write a sprint planning summary document for the upcoming [sprint number] sprint at [company/team name]. This document will be shared with stakeholders before the sprint starts.

Sprint context:
- Sprint duration: [1 week / 2 weeks]
- Sprint goal: [1-2 sentences — what's the single most important thing this sprint achieves?]
- Team size: [X engineers, X designers, X QA]
- Total capacity: [X story points or X person-days]

Stories committed to this sprint:
1. [Story title] — [X] points — [assigned to]
2. [Story title] — [X] points — [assigned to]
3. [Story title] — [X] points — [assigned to]
[continue list]

Write the sprint planning summary with these sections:
1. **Sprint goal**: One clear sentence describing the sprint's purpose
2. **Why this sprint**: How this sprint connects to quarterly OKRs or roadmap milestones
3. **Committed scope**: A structured table of stories with owner, points, and acceptance criteria link
4. **What we're NOT doing**: Stories that were deprioritized and why (to prevent stakeholder confusion)
5. **Risks and blockers**: Known dependencies or blockers that could affect delivery
6. **Definition of done**: The criteria a story must meet to be considered complete this sprint
7. **Demo plan**: What will be shown at the sprint review and who the audience is

Keep it under 400 words. This is a communication document, not a Jira export.

Create a user interview guide for a product discovery session about [problem or feature area]. The interviews will be [30 / 45 / 60] minutes long and conducted with [number] users who are [describe user profile: current users / churned users / prospective users / power users].

Research goals:
1. [Primary question you're trying to answer]
2. [Secondary question]
3. [What hypothesis you're testing or trying to invalidate]

Structure the interview guide:
**Intro script (2 minutes)**: What to say to open the session, set expectations, and get recording consent
**Warm-up questions (5 minutes)**: 3 questions to understand their role, context, and relationship to [problem domain]
**Core discovery questions (20-30 minutes)**: 8-10 questions that explore their current behavior, workarounds, and pain points — NOT their opinion on features. Use Jobs-to-be-Done framing ("Tell me about the last time you...") rather than feature validation ("Would you use X if we built it?")
**Concept test section (if applicable, 10-15 minutes)**: How to introduce a prototype or concept and the 3-4 questions to ask after showing it
**Closing questions (5 minutes)**: "Is there anything important about this topic I didn't ask?" + referral ask

For each question, include:
- The question text
- A follow-up probe ("Tell me more about that" / "What did you do when that happened?")
- What you're listening for (the signal that would validate or invalidate your hypothesis)

Write a stakeholder update email summarizing the product team's progress for [week/month/quarter]. This email goes to [audience: executive team / all-hands / investors / cross-functional partners].

Update context:
- Time period covered: [dates]
- Key milestones hit: [list 2-3 specific things shipped or achieved]
- Key milestones missed: [anything that slipped and why — be direct and honest]
- Metrics movement: [list 2-3 metrics with before/after values]
- What's next: [top 2-3 priorities for the coming period]
- Key decisions needed from stakeholders: [any blockers or approvals required]

Write the email with:
1. **Subject line**: Clear and specific — not "Product Update" but "[Month] Product Update: [headline achievement]"
2. **Opening sentence**: The single most important thing that happened this period (positive or negative)
3. **Progress section**: Structured bullet points on what shipped, what moved, and what changed
4. **Metrics section**: A mini table or clear before/after comparisons — no vanity metrics
5. **Upcoming section**: What's being worked on, with realistic timelines
6. **Ask section**: Any decisions, resources, or input needed from this audience
7. **Closing**: One sentence on overall momentum or trajectory

Length: 300-400 words maximum. Stakeholders don't read long emails. If something needs more context, offer to discuss it, don't explain it inline.

Write an internal feature launch announcement for [feature name] at [company name]. This announcement goes to [the entire company / engineering and product teams / customer-facing teams (sales, success, support)].

Feature details:
- What it does: [describe in plain language — no jargon]
- Who it's for: [user segment or customer type]
- Launch date: [date]
- Access: [all users / paid users / beta group / gated rollout]
- Key metrics we're tracking: [2-3 success metrics]
- How to access it: [URL, feature flag, navigation path]

Write the announcement with:
1. **Subject/Headline**: Punchy, specific, celebration-worthy
2. **TL;DR**: 2-3 sentences max — what launched, for whom, and what to do next
3. **What it does**: A plain-language description of the feature and the problem it solves
4. **Why it matters**: The business or user context — what does this enable?
5. **Who gets it**: Rollout details and timeline
6. **Demo/links**: Where to see it in action (Loom link placeholder, Figma link, or changelog URL)
7. **How to help**: What you need from this team — feedback, escalations, customer conversations
8. **Thanks**: Brief acknowledgment of the team that built it

Tone: energetic but precise. Avoid hype language ("game-changer," "revolutionary"). Let the feature speak for itself.

Perform a Jobs-to-be-Done (JTBD) analysis for [product or feature] targeting [user segment]. I'll use this analysis to improve positioning, prioritize features, and guide discovery interviews.

Product: [describe the product]
User segment: [describe who this user is — job title, context, goals]
Core use case: [what do users primarily use this for today?]

For this user segment, identify:

**Functional jobs** (3-5): What tasks are they literally trying to accomplish?
Format: "When [situation], I want to [motivation], so I can [expected outcome]"

**Emotional jobs** (3): How do they want to feel while doing or after completing the task?
Format: "When [situation], I want to feel [emotion]"

**Social jobs** (2-3): How do they want to be perceived by others as a result of using this?
Format: "When [situation], I want others to see me as [perception]"

For the top 2 functional jobs:
1. **Current solutions**: How are users solving this job today? (including manual workarounds, competitor tools, or doing nothing)
2. **Struggle moments**: When does the current solution fail them?
3. **Switching triggers**: What event or frustration would make them actively search for a better solution?
4. **Success criteria**: What does "job done perfectly" look like to them?

Also produce: A one-paragraph positioning statement using JTBD language for the marketing team.

Design a product metrics dashboard structure for a [product type] at a [startup / growth-stage / enterprise] company. The dashboard will be used by [product managers / executives / the whole company].

Business model: [SaaS / marketplace / consumer app / ecommerce / developer tool]
Current stage: [pre-PMF / post-PMF scaling / mature product]
Primary business goal this quarter: [specific goal]

Design the dashboard with these layers:

**North Star metric**: The single metric that best captures whether users are getting value from the product. Explain why this metric and not others.

**L1 — Health metrics** (always visible): 5-6 metrics that tell you if the product is working at a basic level. Include retention, activation, and usage frequency metrics relevant to the business model.

**L2 — Growth metrics**: 4-5 metrics that track acquisition and expansion. Include at least one leading indicator.

**L3 — Quality metrics**: 3-4 metrics for performance, reliability, and customer satisfaction (NPS, CSAT, bug rate, load time)

**L4 — Feature-level metrics**: How to track adoption of specific features — suggest a framework rather than specific metrics (which depend on features built)

For each metric:
- Name and definition
- How to calculate it
- Recommended target range or benchmark
- Warning threshold (when to escalate)
- Where to find or query this data (placeholder for your data stack)

Facilitate a post-launch retrospective for [feature or product name] which launched [X weeks/months] ago. This retrospective will be run with the product team including [PM, engineering lead, designer, data analyst].

Launch context:
- Feature: [brief description]
- Launch date: [date]
- Planned success metrics: [what you said you'd achieve]
- Actual results: [what actually happened — be specific with numbers]
- Unexpected outcomes (positive or negative): [anything that happened that wasn't predicted]

Structure the retrospective agenda:

**1. Data review (15 min)**: Present the metric outcomes — what moved, what didn't, by how much vs. target. Include a "what the data tells us" interpretation.

**2. What went well (10 min)**: Specific things that worked — in execution, communication, process, or outcomes. Tie each to a reusable lesson.

**3. What didn't go well (15 min)**: Specific things that failed or underperformed. Be direct. For each, identify whether it was a: Discovery gap / Execution gap / Communication gap / External factor

**4. Biggest learning (10 min)**: The single most important thing this launch taught the team about the product, the user, or the process.

**5. Action items (10 min)**: 3-5 specific, assigned, time-bound improvements for the next launch.

Write the full retrospective document in this structure, ready to share with the team before the session. Include facilitation notes (what to ask, how to draw out quiet team members, how to prevent blame).