ChatGPT Prompts for Product Managers: PRDs, Roadmaps, User Stories

Published: July 2026 | 9 min read

Product managers sit at the intersection of users, business, and engineering. You translate customer needs into requirements, prioritize ruthlessly, and communicate across every team. AI can help you write PRDs, analyze feedback, plan roadmaps, and make prioritization decisions — if your prompts think like a PM who understands the difference between a feature and a benefit.

Product Planning & Strategy

1. Product Requirements Document (PRD)

Role: Senior product manager writing a PRD
Task: Create a PRD for [feature/product description].
Context: [Company, product, target user, current state]
PRD sections:
1. Title & Meta (feature name, author, status, date, stakeholders)
2. Problem Statement (what user problem are we solving? evidence?)
3. Target Users (persona, segment, size, current behavior)
4. Goals & Success Metrics (what outcomes? how measured? target values?)
5. Non-Goals (what are we explicitly NOT doing in this release?)
6. User Stories (3-5, with acceptance criteria)
7. Functional Requirements (detailed — what the system must do)
8. Non-Functional Requirements (performance, security, accessibility, scale)
9. Design & UX Considerations (key flows, edge cases, error states)
10. Technical Considerations (architecture, dependencies, constraints)
11. Timeline & Milestones (design review, dev start, QA, launch)
12. Risks & Mitigations (what could go wrong, how to handle)
13. Open Questions (what we still need to figure out)
14. Rollout Plan (feature flag? beta? phased? everyone?)
Format: PRD ready for engineering review.
Constraint: Every requirement must be testable. No "should be fast" — use "load in under 2 seconds."

2. Product Roadmap Generator

Role: Product strategy leader
Task: Create a [quarterly/annual] product roadmap for [product/area].
Inputs:
- Business objectives: [company goals for this period]
- User feedback themes: [top requests, complaints, churn reasons]
- Technical debt: [what needs addressing]
- Competitive landscape: [what competitors are doing]
- Team capacity: [engineering, design, PM headcount]
Roadmap structure:
1. Themes (2-3 strategic themes for the period)
2. Now / Next / Later (what we are building, what is coming, what is future)
3. For each initiative:
   - Name and description
   - Theme alignment (which strategic theme)
   - Expected outcome (metric we are moving)
   - Effort estimate (S/M/L/XL)
   - Dependencies
   - Target release window
4. What we are NOT doing (explicit non-priorities and why)
5. Risk factors (what could shift the roadmap)
6. Assumptions (what must be true for this roadmap)
Format: Roadmap document ready for leadership review and stakeholder communication.
Include: One-slide summary version (5 bullet points max).

3. Feature Prioritization Framework

Role: Product management strategist
Task: Help prioritize these features using a structured framework.
Features: [List with brief descriptions, estimated effort, user impact]
Frameworks to apply:
1. RICE Scoring:
   - Reach (how many users per quarter?)
   - Impact (1-3-5 scale: how much per user?)
   - Confidence (0-100%: how sure are we?)
   - Effort (person-months)
   - Score = (Reach x Impact x Confidence) / Effort
2. MoSCoW:
   - Must-have (non-negotiable for release)
   - Should-have (important but not blocking)
   - Could-have (nice to have if time allows)
   - Won't-have (explicitly excluded)
3. Kano Model:
   - Basic (expected, causes dissatisfaction if missing)
   - Performance (more is better)
   - Delight (unexpected, creates WOW)
For each feature:
1. RICE score (with breakdown)
2. MoSCoW category
3. Kano classification
4. Final recommendation (do now / next / later / no)
Output: Prioritized feature list with scoring rationale.
Format: Prioritization matrix ready for stakeholder review.

User Research & Feedback

4. User Interview Guide

Role: User research specialist
Task: Create a user interview guide for [research objective].
Research question: [What do we want to learn?]
Target persona: [Who are we interviewing? role, segment, behavior]
Interview structure (45-60 minutes):
1. Intro (2 min: purpose, consent, recording permission)
2. Warm-up (5 min: background, role, context)
3. Current behavior (10 min: how they do things now, pain points)
4. Problem exploration (15 min: deep dive on the specific problem)
5. Solution reaction (10 min: show concept/prototype, get reactions)
6. Trade-off discussion (10 min: what would they give up? what matters most?)
7. Wrap-up (3 min: anything else? thank you)
For each question:
1. Question (open-ended, non-leading)
2. Follow-up probes (if they give a short answer, what to ask next)
3. What we are looking for (what signal does this question provide?)
Rules:
- No leading questions (not "Do you like X?" but "Tell me about X")
- No hypothetical futures (not "Would you use X?" but "How do you currently...?")
- No yes/no questions (always ask "how" or "tell me about")
Format: Interview guide ready for a researcher to conduct.

5. Customer Feedback Analysis

Role: Product insights analyst
Task: Analyze customer feedback for [product/feature].
Feedback sources: [NPS comments, support tickets, app reviews, sales feedback, user interviews]
Volume: [approximate number of responses]
For each theme:
1. Theme description (what are they saying?)
2. Frequency (how many mentions, what % of total)
3. Sentiment (positive, negative, mixed)
4. User segment (which persona/type is saying this?)
5. Severity (how much does it affect satisfaction/churn?)
6. Underlying need (what do they actually want — not what they asked for)
7. Potential solution (product response to this feedback)
8. Priority (based on frequency x severity x alignment with strategy)
Output:
1. Top 10 feedback themes ranked by priority
2. Quick wins (can address in next sprint)
3. Strategic themes (need roadmap planning)
4. Contradictions (where different segments want opposite things)
5. "Don't do" list (feedback that would please few but hurt many)
Format: Feedback analysis report for the product team.

6. Competitive Analysis Template

Role: Product competitive intelligence analyst
Task: Create a competitive analysis for [product category].
Competitors: [List 3-5 direct competitors and 2-3 indirect]
For each competitor:
1. Company overview (size, funding, market position, target segment)
2. Product features (core features, unique capabilities, gaps)
3. Pricing (model, tiers, price points, discounts)
4. Strengths (what they do well — be honest)
5. Weaknesses (where they struggle — be specific)
6. User reviews (themes from G2, TrustRadius, app stores — what users say)
7. Recent moves (product launches, partnerships, acquisitions, pricing changes)
8. Threat level (how likely are they to take our customers?)
Comparison:
1. Feature matrix (us vs them — feature by feature)
2. Pricing comparison (apples to apples)
3. Positioning map (where do we sit relative to them?)
4. Differentiation (what can we claim that they cannot?)
Output:
1. Competitive landscape document
2. Our positioning recommendations (where should we differentiate?)
3. Threat response (what should we do about each threat?)
4. Opportunity gaps (where is nobody playing well?)
Format: Competitive analysis for PM and leadership review.

Execution & Communication

7. Sprint Backlog Grooming Assistant

Role: Agile product owner
Task: Help prepare the sprint backlog for grooming.
Current backlog: [List top stories with estimates, status, dependencies]
Sprint goal: [What is the sprint objective?]
Team velocity: [Story points per sprint]
For each story:
1. Is the acceptance criteria clear? (yes/no — what is missing?)
2. Are there dependencies? (what must be done first?)
3. Is the estimate realistic? (any unknowns that could blow it up?)
4. Is it ready for development? (INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable)
5. Any splitting needed? (stories too large for the sprint?)
Output:
1. Sprint-ready stories (can be committed to)
2. Stories needing refinement (what to discuss in grooming)
3. Stories blocked (what is blocking and who can unblock)
4. Recommended sprint commitment (point range based on velocity + capacity)
Format: Backlog grooming report for the PO to bring to the team.

8. Release Notes Generator

Role: Product marketing/PM writing release notes
Task: Write release notes for [version/release].
Changes: [List of features, fixes, improvements — with technical context]
Audience: [End users / admins / developers — which?]
Format:
1. Headline (1 sentence: what is the headline feature?)
2. Highlights (3-5 bullet points: what is new and why it matters)
3. New Features (detailed: what it does, how to use it, who benefits)
4. Improvements (what got better — in user terms, not technical terms)
5. Bug Fixes (only user-visible fixes, not internal cleanup)
6. Known Issues (any caveats? things to be aware of?)
7. Action Required (do users need to do anything? config change? migration?)
Rules:
- No technical jargon (unless developer audience)
- Focus on benefit, not implementation
- Link to docs/tutorials for each feature
- Include screenshots/mocks for visual features
Format: Ready-to-publish release notes.
Constraint: Keep under 500 words. Skim-friendly — bold headers, short paragraphs.

9. Stakeholder Update Email

Role: Product manager writing to stakeholders
Task: Write a stakeholder update for [project/initiative].
Context: [What is the project? What stage are we at?]
Stakeholders: [Who is receiving this? what do they care about?]
Format:
1. Subject line (descriptive, not clickbait)
2. TL;DR (1-2 sentences: current status and any decisions needed)
3. Progress (what we accomplished this period — bullet points)
4. Metrics (key numbers: are we on track? include before/after)
5. Risks/Issues (what is concerning, what we are doing about it)
6. Decisions Needed (what input do we need from stakeholders? by when?)
7. Next Steps (what is coming next, when)
8. Links (dashboard, doc, prototype — whatever is relevant)
Tone: Transparent, concise, no spin.
Constraint: Under 300 words. If they want more, link to details.

Strategy & Metrics

10. North Star Metric Framework

Role: Product strategy consultant
Task: Help define a North Star Metric for [product/company].
Product: [What it does, for whom, value proposition]
Current metrics: [What is tracked now? are they leading or lagging?]
Process:
1. Articulate the product value (what value do we deliver to users?)
2. Identify candidate metrics:
   - List 10-15 potential North Star metrics
   - For each: what does it measure? is it a leading indicator of growth?
   - Rate each: Specific, Measurable, Actionable, Leading, Understandable
3. Select the North Star (the one that best reflects value delivered)
4. Define the metric precisely:
   - Exact formula
   - Time window
   - Segments (does it apply to all users?)
   - What it excludes
5. Identify supporting metrics (input metrics that drive the North Star)
6. Create the metric tree (North Star -> 3-5 input metrics -> tactical metrics)
7. Anti-metrics (what should NOT go up as a result of optimizing the NSM?)
Output: North Star Metric framework document with definition, tree, and guardrails.
Format: Strategy document ready for leadership alignment.

11. Product Experiment Design

Role: Product experimentation specialist
Task: Design an experiment for [hypothesis].
Hypothesis: [If we [change], then [metric] will [increase/decrease] by [X%] because [reasoning]]
Experiment design:
1. Hypothesis (formal: change + outcome + rationale)
2. Primary metric (what we are measuring)
3. Secondary metrics (guardrails we need to watch)
4. Variants (Control vs Treatment — what is different?)
5. Sample size (how many users? based on what MDE?)
6. Duration (how long to run? why?)
7. Targeting (who is in the experiment? any exclusions?)
8. Randomization (user-level, session-level, account-level?)
9. Analysis plan (which test, significance level, segments to analyze)
10. Decision criteria (what result leads to ship? what leads to kill?)
11. Risks (what could go wrong? user impact, business impact?)
12. Rollback plan (if we ship and it is bad, how do we revert?)
Output: Experiment brief ready for engineering and analytics review.
Constraint: MDE must be realistic — if we need 100K users to detect a 0.1% change, reconsider.

12. Churn Analysis Plan

Role: Product retention analyst
Task: Create a churn analysis plan for [product].
Churn definition: [How is churn defined? when is a user "churned"?]
Current churn rate: [overall, by segment, trend]
Analysis plan:
1. Quantify the problem:
   - Churn rate by month, by segment, by cohort, by plan
   - Revenue at risk (annualized churn value)
   - Comparison to industry benchmark
2. Identify who churns:
   - Firmographic/segment patterns (which types churn more?)
   - Behavioral patterns (what did churned users do differently?)
   - Usage signals (declining usage before churn? when does it start?)
   - Tenure patterns (do newer users churn more?)
3. Why they churn (combine quantitative + qualitative):
   - Exit survey themes
   - Support ticket analysis before churn
   - Competitor mentions
   - Pricing/VALUE objections
4. Predictive model:
   - Features for churn prediction (usage, engagement, support, payment)
   - Model approach (logistic regression, gradient boosting, survival analysis)
   - Alert thresholds (when to flag an account at risk)
5. Retention strategy:
   - Quick wins (onboarding improvements, targeted outreach)
   - Product changes (what features would increase stickiness?)
   - Process changes (CSM engagement, early warning system)
   - Pricing experiments (annual vs monthly, value reinforcement)
Output: Churn analysis plan with recommended actions.
Format: Retention strategy document for PM and leadership.

Best Practices

For more PM and tech content, see our AI prompts for project managers and ChatGPT prompts for software developers.