100+ ChatGPT Prompts for Product Managers: From Strategy to Execution (2026)

Product managers are the connective tissue of product organizations — writing specs, analyzing data, communicating with stakeholders, and making strategic decisions. ChatGPT serves as an always-available thinking partner that can draft PRDs, generate user stories, analyze competitors, structure roadmaps, and help you think through complex product decisions.

These prompts follow the product management workflow from discovery through delivery and iteration.

Discovery and Research Prompts

User Research

Create a user interview guide for researching [problem/feature/opportunity]. Include:
- Screening criteria to find the right participants
- Warm-up questions (2-3)
- Core questions exploring the problem space (8-10)
- Questions about current workarounds and alternatives (3-4)
- Questions to validate potential solutions (3-4)
- Closing questions and next steps

Requirements:
- Open-ended questions (no leading or yes/no questions)
- Follow-up probes for each core question
- Organized from general to specific
- Estimated interview duration: [30/45/60] minutes

I conducted [number] user interviews about [topic]. Here are the key quotes and observations:
[paste notes or quotes]

Help me synthesize these into:
1. Key themes (grouped findings)
2. User needs (stated and unstated)
3. Pain points ranked by frequency and severity
4. Opportunities for our product
5. Quotes that best illustrate each theme
6. Recommended next steps for research or action

Competitor Analysis

Create a competitive analysis framework for our product [product name] in the [market/category]. Competitors: [list 3-5 competitors]

Analyze across these dimensions:
| Dimension | Our Product | Competitor A | Competitor B | Competitor C |
|-----------|------------|-------------|-------------|-------------|
| Target audience | | | | |
| Core value prop | | | | |
| Key features | | | | |
| Pricing model | | | | |
| Strengths | | | | |
| Weaknesses | | | | |
| Market positioning | | | | |
| Recent launches | | | | |

I'll fill in the specifics — create the analysis structure and suggest 5 additional dimensions relevant to [our market].

Analyze [competitor product]'s recent [feature launch / pricing change / strategy shift]. Based on what's publicly available:
1. What are they trying to achieve?
2. Who does this target?
3. How does this affect our competitive position?
4. What should we consider in response?
5. What can we learn from their approach?
Keep the analysis objective and actionable.

Market Sizing

Help me estimate the market size for [product/feature] using both top-down and bottom-up approaches.

Known data points:
- [Available market data]
- [Customer segment sizes]
- [Pricing benchmarks]

Calculate:
1. TAM (Total Addressable Market)
2. SAM (Serviceable Addressable Market)
3. SOM (Serviceable Obtainable Market)
Show your assumptions and methodology for each. Identify the most uncertain assumptions.

Strategy and Planning Prompts

Product Strategy

Help me develop a product strategy framework for [product] over the next [timeframe]. Context:
- Company mission: [mission]
- Current product state: [description]
- Key metrics: [current performance]
- Market trends: [relevant trends]
- Competitive landscape: [brief overview]

Structure the strategy as:
1. Vision: Where we're heading (2-3 years)
2. Strategic pillars: 3-4 focus areas
3. Goals per pillar: Measurable outcomes
4. Key bets: Assumptions we're making
5. What we're NOT doing: Strategic trade-offs
6. Success metrics: How we'll know it's working

I'm deciding between these strategic options for [product area]:
Option A: [describe]
Option B: [describe]
Option C: [describe]

Create a decision matrix evaluating each option across:
- Impact on key metric: [metric]
- Engineering effort (T-shirt size)
- Time to value
- Risk level
- Strategic alignment
- Revenue potential
- Customer demand signal

Help me think through the trade-offs and make a recommendation.

Roadmapping

Help me build a quarterly product roadmap. Here are the candidate initiatives:
[List 10-15 potential projects with brief descriptions]

For each initiative, help me assess:
- Impact: How much does this move our key metric?
- Confidence: How sure are we about the impact?
- Effort: Engineering weeks needed
- Dependencies: What needs to happen first?

Then create a recommended roadmap using RICE scoring:
- Now (this quarter): Top 3-4 items
- Next (next quarter): Items to prepare for
- Later: Backlog for future consideration
- Won't do: Items to explicitly deprioritize (with reasoning)

OKRs

Write OKRs (Objectives and Key Results) for [product/team] for [quarter/year]. Context:
- Company objectives: [list]
- Team focus: [area]
- Current challenges: [issues to address]

Create 3 objectives with 3-4 key results each. Each key result should be:
- Measurable (specific number or percentage)
- Ambitious but achievable
- Time-bound to the [quarter]
- Within our team's control or strong influence
Include current baselines where applicable.

Product Requirements Prompts

PRDs

Write a Product Requirements Document (PRD) for [feature/product]. Include:

## Overview
- Problem statement (what user problem are we solving?)
- Goal and success metrics
- Target users

## Context
- User research insights
- Business justification
- Competitive context

## Requirements
### Functional Requirements
- User stories with acceptance criteria
- Edge cases and error states
- Business rules

### Non-Functional Requirements
- Performance expectations
- Security considerations
- Accessibility requirements
- Scalability needs

## Design
- Key user flows (describe, not mockup)
- Information architecture
- States and transitions

## Technical Considerations
- Integration points
- Data requirements
- Migration needs (if applicable)

## Launch Plan
- Rollout strategy (beta → GA)
- Feature flags
- Success metrics and monitoring

## Open Questions
- Decisions still needed
- Assumptions to validate

Use this context: [provide relevant background]

User Stories

Write user stories for [feature]. Use the format:
"As a [user type], I want to [action], so that [benefit]"

Create:
- 5-8 user stories covering the core functionality
- 3-4 edge case stories
- 2-3 admin/operational stories
- Acceptance criteria for each story (3-5 criteria per story using Given/When/Then format)
- Story point estimate range (S/M/L)
- Dependencies between stories

Priority order them using MoSCoW (Must have, Should have, Could have, Won't have this time).

I have this high-level feature request: "[feature description]"
Break it down into:
1. Epic description
2. User stories (with acceptance criteria)
3. Technical tasks per story
4. Suggested sprint allocation (which stories go together)
5. MVP scope vs. full scope
6. Metrics to track post-launch

Stakeholder Communication

Executive Updates

Write a monthly product update for leadership. Data:
- Key metrics: [list metrics with current values and trends]
- Shipped this month: [features/improvements]
- In progress: [current work]
- Upcoming: [next month priorities]
- Blockers/risks: [issues]

Format:
- TL;DR (3 bullet points, 1 sentence each)
- Metrics dashboard (table format)
- Highlights (what went well)
- Lowlights (what didn't, and what we're doing about it)
- Asks (decisions or resources needed)

Keep it under 1 page. Data-driven, not opinion-driven.

Help me prepare for a product review meeting with [executives/board]. Topic: [subject].

Create:
1. Opening statement (30 seconds — frame the problem and opportunity)
2. Key data points to present (5 most compelling)
3. Recommended path forward (with reasoning)
4. Anticipated questions and prepared answers (5 questions)
5. Ask/decision needed from the audience
6. One-page summary leave-behind

Engineering Communication

Write a technical specification overview for engineering based on this PRD:
[paste PRD or key requirements]

Translate the product requirements into:
- System behavior descriptions (not implementation — let engineering decide how)
- API contract expectations (inputs, outputs, error states)
- Data model requirements
- Integration points and contracts
- Performance requirements (latency, throughput, availability)
- Edge cases and expected behavior for each

Write in a way that gives engineering clear requirements without prescribing the solution.

Go-to-Market

Create a go-to-market brief for launching [feature/product]. Include:
1. Launch summary (what we're launching and why it matters)
2. Target audience (who cares most)
3. Key messaging (elevator pitch, value props, proof points)
4. Sales enablement (talking points, objection handling)
5. Marketing channels and tactics
6. Support preparation (FAQ, known issues)
7. Success metrics (what does a successful launch look like?)
8. Timeline and key dates

Analytics and Metrics

Help me define a metrics framework for [feature/product]. Create:

Primary Metric (North Star):
- Metric name and definition
- Why this metric matters
- How to measure it
- Target value and timeline

Supporting Metrics:
- 3-4 metrics that explain changes in the primary metric
- Leading indicators (predict future primary metric changes)
- Guardrail metrics (things that shouldn't get worse)
- Input metrics (things we directly control)

For each metric: name, definition, data source, target, measurement frequency.

Our [metric] dropped by [percentage] this [week/month]. Help me structure a root cause analysis:
1. Possible causes (brainstorm 8-10 hypotheses)
2. Data to check for each hypothesis
3. Priority order for investigation (most likely first)
4. Questions to ask the data team
5. Framework for the postmortem if needed

FAQ

Can ChatGPT write production-ready PRDs?

ChatGPT produces excellent first drafts that capture the right structure and content. You’ll need to add specific user research findings, technical constraints from your engineering team, and business context that only you know. Expect to spend 30% of the time refining vs. 100% writing from scratch.

How do I use ChatGPT for prioritization?

Share your initiative list with ChatGPT and ask it to apply frameworks like RICE, ICE, or a weighted scorecard. ChatGPT can structure the analysis, but you’ll need to provide the input scores based on your knowledge of the business, users, and technical complexity.

Can ChatGPT replace product research?

No. ChatGPT can help structure research plans, synthesize findings, and generate hypotheses, but it cannot conduct user interviews, observe behavior, or provide real user insights. It’s a research amplifier, not a replacement for talking to users.

How accurate is ChatGPT’s market analysis?

ChatGPT provides useful frameworks and general industry knowledge, but may not reflect the most current market data or your specific competitive landscape. Use it for structure and initial hypotheses, then validate with current sources, industry reports, and your own market intelligence.

Should I share ChatGPT outputs directly with my team?

Always customize AI outputs before sharing. Add your unique context, validate the assumptions, and ensure the content reflects your actual strategy and priorities. Generic AI output without your expertise added will be obvious and less effective.

Conclusion

These prompts cover the full product management workflow from discovery through delivery. The highest-value prompts for most PMs are PRD generation, user story creation, and stakeholder communication — areas where ChatGPT saves the most time while maintaining quality.

Start by using ChatGPT for your next PRD or executive update. Build on the output with your domain expertise, user research, and business context. Over time, you’ll develop a library of customized prompts that match your team’s specific templates and workflows.