Product Management: ChatGPT Prompts for PMs

Help me frame this problem statement:
[Describe the situation — what users are experiencing, what we observe]

Structure the framing:
1. What is the core user problem? (one sentence)
2. Who experiences it? (be specific about the segment)
3. How do we know it's real? (evidence: data, interviews, support tickets)
4. What happens if we don't solve it? (quantify the cost of inaction)
5. What constraints shape the solution space? (tech, budget, timeline, policy)

Keep it tight — this should fit on one slide.

Help me size an opportunity for [product idea or feature].

Available data:
- TAM: [market size]. Our current market share: [X%].
- Monthly active users: [N]. Users expressing this need: [Y%].
- Average revenue per user: [$Z].
- Competitors who already solve this: [list].

Calculate:
1. The addressable market within our user base (users × percentage expressing need)
2. Revenue potential (low/medium/high scenarios)
3. What percentage of the opportunity we could realistically capture in 12 months
4. Opportunity cost — what are we NOT building if we build this?

Show your work. Flag assumptions explicitly.

Analyze [competitor name]'s [product/feature].

Strengths:
Weaknesses:
Pricing:
Target user:
Recent moves:

Based on this:
1. What is their strategy? (cost leader, differentiation, niche focus)
2. What user need are they solving better than anyone else?
3. Where are they vulnerable? (segment they ignore, workflow they skip, price sensitivity)
4. How should we position against them? (compete head-on, flank, ignore)
5. What could they do in the next 6 months that would threaten us?

Be honest — don't dismiss their strengths to make us feel better.

Write a first draft of a PRD for [feature or product].

Context:
- Problem: [one sentence]. Evidence: [data, user feedback].
- Target user: [persona]. Success metric: [what we'll measure].
- Constraints: [tech, timeline, dependencies].

Structure:
1. Problem statement and evidence (50 words)
2. Success criteria (measurable, with target values)
3. User stories (3-5, as "As a [user], I want [action] so that [outcome]")
4. Key flows (happy path + 2 error paths)
5. Out of scope (what we're explicitly NOT building)
6. Open questions (things we need to resolve before building)
7. Launch criteria (what must be true to ship)

Keep it under 800 words. No implementation details — that's the eng spec.

I have [N] features competing for the next quarter. Here they are:
[List each feature with estimated effort (S/M/L) and expected impact (H/M/L)]

Apply these prioritization frameworks and compare the results:
1. RICE (Reach × Impact × Confidence ÷ Effort) — score each feature
2. ICE (Impact × Confidence × Ease) — score each feature
3. Value vs Effort matrix — plot each feature

Identify:
- Where the frameworks agree (these are your top priorities)
- Where they disagree and why
- Which framework is most appropriate for our situation and why
- Features that rank low on all frameworks — should we kill them?

I need to get alignment from [describe stakeholders: engineering lead, design lead,
 exec, marketing] on [decision or roadmap].

Their likely concerns:
[For each stakeholder, list what they care about and what they're worried about]

Help me prepare:
1. A one-sentence positioning that addresses the decision from their perspective
2. Data or evidence they'll find compelling
3. What they'll ask that I'm not prepared for
4. A proposed compromise if they push back
5. The "no" I'm willing to accept and my fallback plan

Epic: [describe the feature or capability in 1-2 sentences].

Break this into user stories:
1. 5-8 stories covering the full user journey
2. Each story follows: "As a [persona], I want [action] so that [outcome]"
3. Order stories by dependency (what must be built first?)
4. Identify the "thin slice" — the smallest set of stories that deliver value
5. Flag stories that require design exploration before estimating

User story: [paste story].

Write acceptance criteria that:
1. Cover the happy path — what "done" looks like
2. Cover 3 edge cases — what happens when things go wrong
3. Are testable — a QA engineer could write a test from each criterion
4. Use given/when/then format
5. Include non-functional requirements (performance, accessibility, error handling)

Avoid implementation details. Focus on behavior, not how it's built.

I need to request a technical spike from the engineering team.

The decision we need to make: [describe the open question].
Context: [what we know, relevant systems, constraints].

Write a spike request that:
1. States the decision we need to make clearly
2. Lists what we already know vs what we need to learn
3. Suggests 2-3 investigation approaches
4. Specifies the output format (decision doc, prototype, performance numbers)
5. Estimates timebox (2 days? 1 week?)
6. Explains what happens if we get this wrong

Summarize this [product update/feature proposal/launch results] for an executive audience.

Full context: [paste detailed doc or notes].

The executive summary (200 words max):
1. What happened or what we're proposing (one sentence)
2. Why it matters to the business (one sentence)
3. Key numbers (2-3 metrics). Compare to target if relevant
4. What we need from them (decision, budget, awareness)
5. What's next

No detail they don't need. They can ask for depth if they want it.

We're launching [feature/product] to [audience].

Key details:
- What it does: [one sentence]. Problem it solves: [one sentence].
- Launch date: [date]. Availability: [all users/beta/paid tier].
- Known limitations: [list honestly].
- Links: [docs, announcement page, feedback channel].

Write:
1. Internal announcement for Slack (100 words)
2. External announcement for social media (2-3 platform-specific versions)
3. Customer-facing email (subject line + 150 word body)
4. FAQ page (5 questions users will actually ask)

Tone: [professional/playful/urgent/etc.].

Write a weekly status update for [project name].

This week:
- Accomplished: [list 3-5 items]
- Blocked: [list anything stuck, what's needed to unblock]
- Decisions made: [list]. Decisions needed: [list].

Next week:
- Priorities: [list 3-5 items]
- Risks: [list with mitigation]

Format as a concise bulleted list. Skip filler — if nothing is blocked, say "No blockers."