ChatGPT Prompts for Product Managers: 12 AI Templates for PRDs, Roadmaps & User Stories

You are a senior product manager at [company type]. Write a complete PRD for the
following feature:

Feature name: [feature name]
Product: [brief product description]
Problem being solved: [specific user problem]
Target users: [user segment]
Business goal: [specific business objective]

Structure the PRD with these sections:
- Executive Summary (2-3 sentences)
- Problem Statement (detailed, user-centered)
- 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 (performance, security, scalability)
- Success Metrics (3-5 measurable KPIs)
- Open Questions
- Timeline Considerations

Be specific and use concrete language. Avoid vague statements like "improve user experience."

You are a product manager working with an agile engineering team. Convert the following
raw feature idea into properly formatted user stories with detailed acceptance criteria:

Feature idea: [describe the feature in plain language]
User type: [primary user persona]
Platform: [web/mobile/API/etc.]

For each user story:
1. Write the story in proper format: "As a [user], I want [action] so that [outcome]"
2. Add a brief rationale (why this matters)
3. List 4-6 acceptance criteria in Given/When/Then format
4. Estimate story complexity (S/M/L/XL) with brief justification
5. Note any dependencies or risks

Generate 4-6 user stories that together represent the complete feature scope.

Help me build a quarterly product roadmap. Here's the context:

Product: [product name and brief description]
Current quarter goals: [top 3 business goals this quarter]
Engineering capacity: [approximate team size/velocity]
Key constraints: [technical debt/dependencies/resource limits]

Known initiatives (list everything we're considering):
- [Initiative 1]
- [Initiative 2]
- [Initiative 3]
(add more as needed)

Create a roadmap with:
1. Now / Next / Later prioritization framework applied to these initiatives
2. Rationale for each prioritization decision
3. Dependencies and sequencing notes
4. Risks and mitigation strategies for top 3 priorities
5. Suggested success metrics for each now/next initiative
6. One-paragraph executive summary suitable for sharing with leadership

Format as a structured document I can paste into a presentation.

Create a competitive analysis for [product/feature] against the following competitors:
- Competitor 1: [name]
- Competitor 2: [name]
- Competitor 3: [name]

Analyze each competitor across:
1. Core feature set (what they do)
2. Target customer segment
3. Pricing model
4. Key differentiators / unique value
5. Known weaknesses or gaps
6. Recent product moves (from your training data if relevant)

Then provide:
- A competitive positioning matrix (table format)
- Our relative strengths vs. this competitive set
- 3 opportunities we should act on based on competitive gaps
- 2 threats we should defend against

Format as a professional competitive analysis document I can share with stakeholders.

Create a go-to-market strategy outline for the following product launch:

Product: [product/feature name]
Target market: [primary customer segment]
Value proposition: [what makes this product uniquely valuable]
Launch date target: [timeframe]
Pricing model: [how we plan to charge]
Current channels: [how we currently reach customers]

Build a GTM outline covering:
1. Target segments and buyer personas (2-3 personas)
2. Positioning statement (formula: For [target customer] who [has this problem], [product name] is a [product category] that [key benefit]. Unlike [alternatives], we [differentiator].)
3. Launch phases (pre-launch, launch day, post-launch)
4. Channel strategy for each phase
5. Key messages for each audience
6. Launch success metrics
7. First 90-day customer acquisition plan

Write a user research interview script for the following study:

Research objective: [what we're trying to learn]
Participants: [user segment being interviewed]
Duration: [30/45/60 minutes]
Research stage: [discovery/validation/usability]

Include:
1. Introduction script (explain study purpose without biasing answers)
2. Warm-up questions (3-4 to build rapport)
3. Core research questions (8-10 open-ended questions)
4. Specific probes for each core question
5. Scenario tasks (if usability testing)
6. Closing questions (reactions, anything else to share)
7. Thank-you and next steps script

Important: Write questions in open-ended format, avoid leading questions, include
"Tell me more about that" and similar probing follow-ups throughout.

Help me prioritize the following features using an ICE scoring model
(Impact × Confidence ÷ Effort):

Product context: [brief description]
Strategic goals this quarter: [1-3 goals]

Feature backlog:
1. [Feature 1]
2. [Feature 2]
3. [Feature 3]
4. [Feature 4]
5. [Feature 5]

For each feature, provide:
- Impact score (1-10): Effect on key metrics if successful
- Confidence score (1-10): How confident we are impact estimate is accurate
- Effort score (1-10, where 10 = lowest effort): Engineering complexity
- ICE score (calculated)
- 1-sentence rationale for each score

Present as a prioritization table, sorted by ICE score, with a brief narrative
explaining the top 3 priorities and any nuances in the ranking.

Write a stakeholder status email for the following project:

Project: [project name]
Status: [On track / At risk / Delayed]
Audience: [Executive leadership / Engineering peers / Cross-functional partners]
Reporting period: [week/month]

Update content:
- Progress this period: [what was accomplished]
- Key decisions made: [important decisions and who made them]
- Current blockers: [issues needing help or awareness]
- Next period plan: [what we're working on next]
- Metrics update: [relevant numbers]

Write the email in professional but direct language. Lead with status (green/yellow/red)
and the most critical information. Keep it scannable with bullet points for progress
and blockers. Appropriate length: 200-300 words. Subject line included.

Help me write strong OKRs (Objectives and Key Results) for the following context:

Team: [team name]
Quarter: [Q_/Year]
Company goal we're supporting: [relevant company-level goal]
What our team is working on: [high-level initiatives]

Draft 2-3 Objectives with 3-4 Key Results each.

Requirements for strong OKRs:
- Objectives: Inspiring, qualitative, memorable direction-setting statements
- Key Results: Measurable, time-bound, ambitious but achievable (70% stretch target)
- Each KR should be a metric, not a task (measure outcomes not activities)
- Include current baseline where possible so progress can be measured

For each KR, also note:
- Data source (where we'd get this number)
- Current baseline (if you can estimate or I should provide)
- Definition of "done" / measurement methodology

Create a sprint retrospective facilitation guide for the following context:

Team size: [number] people
Sprint length: [1 or 2] weeks
Notable events this sprint: [key things that happened — incidents, launches, changes]
Team maturity: [new team/established team]
Previous retro themes: [recurring issues to address or celebrate]
Format: [in-person/remote/hybrid]

Include:
1. Opening activity (5 min) to create psychological safety
2. Data gathering activity (10 min) — What went well / what didn't / puzzles
3. Insight generation (15 min) — group themes, vote on priorities
4. Action item creation (10 min) — 2-3 specific, owned action items
5. Closing activity (5 min) — appreciation round or team health check
6. Facilitator tips for each section
7. Remote tool suggestions (if applicable)

Format as a step-by-step facilitator guide with timing and instructions.

Translate the following technical specification into business-friendly language
for a non-technical stakeholder audience:

Technical spec or description:
[paste technical description here]

Stakeholder audience: [executive / sales / customer / board]

Translate this into:
1. Plain-language explanation of what this is (2-3 sentences, no jargon)
2. Why it matters to the business (specific business impact)
3. What it enables us to do that we couldn't before
4. Any risks or tradeoffs in understandable terms
5. Timeline and what stakeholders should expect
6. FAQ — 3-5 questions this audience is likely to ask, with answers

Avoid all technical jargon. Use business and user outcome language throughout.

Write a product strategy one-pager for the following initiative:

Initiative: [initiative name]
Problem we're solving: [clear problem statement]
Target users: [specific user segment]
Our solution: [what we're building/changing]
Why now: [market timing, opportunity window, or strategic context]

Format as a compelling one-page strategy document with:

**Problem** (2-3 sentences): The specific, validated problem
**Opportunity** (2-3 sentences): Market size, current gap, why we're positioned to win
**Approach** (3-4 sentences): What we'll build and key strategic bets
**Success Metrics** (3-5 KPIs with targets): How we'll know it's working
**Risks** (bullet list): Top 3 risks and mitigation
**Timeline**: High-level milestone timeline in [months]
**Resources needed**: Team, budget, and dependencies

Write in persuasive, executive-ready language that makes the case for investment.