AI Prompts for Product Managers: 11 Copy-Ready Templates

You are a product manager at [COMPANY] researching [PROBLEM AREA]. Here are notes or transcripts from [NUMBER] customer interviews:

[PASTE INTERVIEWS]

Group what customers said into themes. For each theme, count how many interviews mentioned it, quote two short lines word for word, and note any customer who said the opposite. Do not suggest solutions yet.

Format: a table with Theme, Interviews mentioning it, Quotes, Counterpoints.

Act as a product manager. From this research summary:

[PASTE SUMMARY]

Write a problem statement in the form: [USER TYPE] needs a way to [NEED] because [INSIGHT], and today they [CURRENT WORKAROUND]. Then list what evidence supports it, what evidence would disprove it, and the one metric that would show we solved it.

Format: the statement in bold, then three short bulleted sections.

You are a product manager planning interviews with [CUSTOMER TYPE] about [TOPIC]. We want to learn [LEARNING GOALS].

Write a 30-minute interview guide: a warm-up, questions about their past behavior (not hypotheticals), probes for specifics, and a wrap-up. Avoid leading questions and do not describe our planned feature.

Format: sections with timings and numbered questions.

You are a product manager writing a one-page product requirements doc for [FEATURE] at [COMPANY]. Inputs: problem [PROBLEM], users [USERS], goals [GOALS], constraints [CONSTRAINTS], what is out of scope [OUT OF SCOPE].

Write the PRD with: problem, goals and success metrics, user stories, requirements (must, should, could), out of scope, and open questions. Put anything I have not decided under Open questions rather than deciding it.

Format: headed sections, under 600 words.

Act as a product manager. Feature: [FEATURE DESCRIPTION]. Users: [USER TYPES].

Write user stories in the form "As a [user], I want [action], so that [benefit]", each with three to five acceptance criteria in Given, When, Then form. Include at least one story for an error or edge case.

Format: numbered stories, criteria indented under each.

You are a senior engineer and a QA lead reviewing this spec for [FEATURE]:

[PASTE SPEC]

List the questions the team will ask before building: unclear behavior, missing edge cases, permissions, empty states, errors, performance and data concerns. For each, quote the line it relates to.

Format: a table with Area, Question, Related line, Priority (Blocker, Important, Nice to know).

Act as a product manager prioritizing [NUMBER] ideas. For each idea I give reach, impact, confidence and effort:

[PASTE IDEAS WITH VALUES]

Calculate a RICE score (Reach x Impact x Confidence / Effort) for each, show the math, and rank them. Then point out any idea where the score looks driven by a single guessed value, so we can discuss it.

Format: a ranked table with all inputs and the score, then the flagged ideas.

You are a product manager. We decided to [DECISION] and not [ALTERNATIVE] this quarter because [REASONS AND EVIDENCE]. Stakeholders who wanted the alternative: [WHO AND WHY].

Write a short message that states the decision, the reasoning, what it means for the stakeholders who wanted the alternative and when we will revisit it: [REVIEW DATE].

Format: under 200 words, respectful and direct.

You are writing release notes for [PRODUCT] version [VERSION]. Here are the changes from the engineering changelog:

[PASTE CHANGELOG]

Rewrite them for customers: lead with what they can now do, group into New, Improved and Fixed, and skip internal-only changes. Do not promise anything that is not in the changelog.

Format: a short headline, then three headed lists, each item one sentence.

Act as a product manager preparing [FEATURE] for launch on [DATE]. Facts: who it is for [AUDIENCE], what it does [WHAT], limits [LIMITS], pricing or plan [PLAN], support contact [CONTACT].

Write a one-page brief for sales and support: what it is in one sentence, who should use it, how to explain it to a customer, known limits, and five likely customer questions with answers based on these facts.

Format: headed sections with a Q and A list at the end.

You are a product manager reviewing feedback on [FEATURE] two weeks after launch. Here are support tickets, survey comments and sales notes:

[PASTE FEEDBACK]

Sort the feedback into Bugs, Confusion, Missing capabilities and Praise, with a count and two quotes for each. Then list the three changes that would address the most feedback.

Format: a summary table, then the three changes.