Promptea.
ESEN

AI prompts for product managers: PRDs, user research, and prioritization

Copy-paste prompt templates for the recurring PM workflows that AI handles well: writing specs, synthesizing research, and structuring prioritization decisions.

← Back to guides
Where AI saves PMs the most time
  • First-draft specs: a well-structured PRD template takes 30 minutes to fill instead of 3 hours to start from scratch.
  • User interview synthesis: summarizing 10 interviews into themes, evidence, and gaps is mechanical work — AI handles it well when you give it structure.
  • Prioritization frameworks: scoring features against RICE, ICE, or a custom rubric is faster when AI fills in the reasoning for each criterion.
  • Stakeholder communication: translating technical scope into executive summaries or customer-facing notes is a common AI strength.
  • Competitive landscape: summarizing how competitors address a specific problem saves hours of tab-switching (especially with a web-grounded model).
How to get reliable output for PM work
  • Always give the model the business context: who the user is, what the product does, and what constraint matters most (time, scope, resources).
  • Paste raw material in: interview notes, support tickets, data snippets. The model synthesizes better when it has real input rather than invented scenarios.
  • Ask for structure before prose: 'Give me the 5 themes first, then I'll tell you which to expand.' Reviewing structure is faster than reviewing paragraphs.
  • Specify the audience: a PRD for engineers needs different depth than a one-pager for the CEO. Name the reader.
  • Use the model to stress-test: 'Play devil's advocate. What are the strongest objections to this prioritization?' Surfaces gaps before the team meeting.
Templates
Lean PRD first draft
Write a lean PRD first draft for this feature.

Feature: [what it does in one sentence]
User problem: [the pain point it solves, from the user's perspective]
Target user: [who specifically — role, context, or user segment]
Business goal: [the metric this is expected to move, and by roughly how much]
Scope constraints: [what is explicitly out of scope for v1]
Key open questions: [2–3 things that need answers before build]

Output format:
## Problem
## Proposed solution (2–3 sentences)
## User stories (3–5, as "As a [user], I want [action] so that [outcome]")
## Success criteria (measurable, not aspirational)
## Out of scope
## Open questions

Keep it under 600 words. This is a first draft for team alignment, not a final spec.
Opens on home with the prompt prefilled.
Open in Promptea
User interview synthesis
Synthesize the following user interview notes into structured findings.

Interview notes:
"""
[paste raw notes from 3–10 interviews here]
"""

Output:
1. Top 5 themes — each with:
   - Theme name (3–5 words)
   - 1-sentence description
   - 2–3 direct quotes or paraphrases that support it
   - Which user segment mentioned it most

2. Top 3 unmet needs (things users said they wish existed or complained about most)

3. Gaps — what important questions remain unanswered by these interviews?

Constraints:
- Only include themes supported by at least 2 different users.
- Do not invent quotes or add outside assumptions.
- Flag anything where the evidence is thin (only 1 user mentioned it).
Opens on home with the prompt prefilled.
Open in Promptea
FAQ
Can AI replace user research?
No. AI synthesizes information you give it; it cannot observe behavior, pick up on tone, notice what users avoid saying, or ask follow-up questions in the moment. Where AI genuinely saves time is after the research: transcribing, synthesizing across interviews, grouping themes, and drafting summaries. The judgment about which themes matter for your product and which user quotes reveal something real versus situational still needs a PM who understands the context.
How do I get AI to write a PRD in our internal format?
Paste a real example from your team (anonymized or with sensitive details replaced) and say: 'Use exactly this structure and heading format for the new PRD I'm about to describe.' One well-chosen example is more effective than a detailed description of your format — the model infers section order, tone, depth, and terminology from the example. Keep the example short enough that the new content dominates the context.