Top 250+ AI Prompts Every Product Owner Should Bookmark

Mastering AI prompts allows Product Owners to automate routine tasks, draft precise user stories, and streamline agile ceremonies. The best results come from structured frameworks that provide clear context, define the persona, and specify the exact format of the output.  

In this blog, we’ll explore 250+ AI prompts every product owner should bookmark, organized across major product management categories including Agile planning, roadmapping, analytics, product discovery, customer research, AI workflows, product launches, stakeholder communication, and more. 

 

How to Use This Guide 

The prompts are organized into 20 categories. You don't need to read it start to finish jump to the section you need right now. Each prompt is designed to be copy-paste ready with minor customization. 

For best results, open every AI session with a context block like this: 

"I'm a product owner at [company type]. We build [product description] for [target audience]. Our current strategic focus is [focus area]. Keep this context in mind for all my prompts in this session." 

That single setup message will improve every output that follows. 

1. User Research and Discovery 

1. "Generate 15 open-ended interview questions for [target user persona] about their experience with [problem area]. Avoid leading questions. Include follow-up probes for each." 

2. "I conducted user interviews and here are my notes: [paste notes]. Synthesize the top 5 themes. For each theme, summarize the core user need, a representative quote style, and the product implication." 

3. "Write a discussion guide for a 45-minute user research session exploring how [target user] currently handles [job to be done]. Include a warm-up, core exploration section, concept reaction section, and closing." 

4. "Analyze this survey data: [paste data]. Identify patterns, outliers, and the 3 most actionable insights for our product team." 

5. "Create a user empathy map for [persona]. Include what they think and feel, what they hear, what they see, what they say and do, their pains, and their gains. Base it on this context: [paste context]." 

6. "I have these 30 user feedback items: [paste]. Group them by theme, rank themes by frequency, and flag any that suggest urgent product risk." 

7. "Write 5 hypothesis statements for user research in the format: 'We believe [user type] experiences [problem] because [assumption]. We will know this is true when [signal].'" 

8. "Generate a screener survey for recruiting research participants who are [target user description]. Include 6–8 qualifying questions." 

9. "Summarize this customer support transcript into the underlying user need: [paste transcript]. Separate the surface request from the root problem." 

10. "Create a jobs-to-be-done framework for [product area]. List the functional job, emotional job, and social job for [primary user persona]." 

11. "Write a research synthesis document from these three interview summaries: [paste]. Highlight agreements, contradictions, and open questions." 

12. "Generate 10 diary study prompts for participants tracking their experience with [product or workflow] over two weeks." 

13. "I'm planning a contextual inquiry session with [user type]. Write an observation guide covering what to look for, what to ask, and how to document findings." 

14. "Transform this raw NPS feedback into categorized themes: [paste NPS comments]. Flag comments that suggest churn risk." 

15. "Write a research question hierarchy for discovering why [user segment] stops using our product after [time period]." 

2. Persona Development 

16. "Create a detailed user persona for [describe user based on research]. Include: demographics, goals, frustrations, behaviors, tools they use, and a day-in-the-life summary." 

17. "I have three user segments: [A], [B], [C]. Write a persona for each. Then write a comparison table showing where their needs overlap and where they conflict." 

18. "Update this existing persona with new information from recent interviews: [paste persona] + [paste new findings]." 

19. "Write a persona narrative a first-person day-in-the-life story for [persona name]. Make it emotionally realistic, not a list of attributes." 

20. "Create an anti-persona a description of who our product is NOT for based on this context: [paste product description and target user]." 

21. "Generate a jobs-to-be-done persona card for [user type]. Format it as: the job they're trying to do, the obstacles in their way, the emotions involved, and what success looks like to them." 

22. "We have these behavioral segments from our analytics: [describe segments]. Write a persona for each segment that a designer could use to make decisions." 

23. "Review these three personas we've created: [paste]. Identify where they overlap too much to be useful and suggest how to differentiate them." 

3. Problem Definition and Framing 

24. "Reframe this feature request as a user problem statement: '[paste request].' Use the format: [User] needs a way to [goal] because [context/constraint]." 

25. "Write a problem statement for a product opportunity in [product area]. Make it specific, user-centered, and free of solution language." 

26. "Generate 10 'How Might We' questions from this problem context: [paste context]. Range from incremental to bold." 

27. "Analyze this problem statement for weaknesses: [paste]. Is it too broad? Too narrow? Solution-biased? Suggest an improved version." 

28. "Write a problem brief for this opportunity: [describe]. Include: who has the problem, how often, what the current workaround is, and what solving it would unlock." 

29. "Given these user pain points: [paste], identify which represent genuine product opportunities vs. one-off complaints vs. table stakes expectations." 

30. "Translate this business goal into a user problem: 'We need to increase retention by 15%.' What problems do users experience that, if solved, would drive that outcome?" 

31. "Write a problem hypothesis using this format: 'We believe [user type] struggles with [problem] in [context], which causes [consequence]. We think the root cause is [assumption].'" 

4. Ideation and Feature Definition 

32. "Generate 15 solution ideas for this user problem: [paste problem]. Include obvious ideas, unexpected ideas, and at least two that are 10x different from current solutions." 

33. "Run a SCAMPER ideation exercise for [feature or product]. Suggest: Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse ideas." 

34. "Write a feature brief for [feature name]. Include: the problem it solves, proposed solution, user flow summary, success metrics, out of scope items, and open questions." 

35. "Generate three different versions of [feature concept] a minimal version, a standard version, and a premium version with different scope and value trade-offs." 

36. "We're considering building [feature]. Write a pre-mortem: what are the ten ways this could fail, and what would we need to do to prevent each?" 

37. "List 10 features that [competitor or product type] doesn't offer that could differentiate us in [market]." 

38. "For this problem: [paste], generate one feature idea each for: (a) reducing friction, (b) increasing value, (c) building habit, (d) reducing cognitive load." 

39. "Write a feature concept one-pager for [feature] that a non-technical stakeholder could read in 2 minutes and understand." 

40. "Generate jobs-to-be-done inspired feature ideas for [product area]. For each, specify which job it helps the user complete." 

41. "Review this feature idea: [paste]. What are the strongest arguments for and against building it? What information would make the case clearer?" 

5. User Story Writing 

42. "Write a user story for [feature/functionality] in the format: As a [persona], I want [goal], so that [benefit]. Include 5 acceptance criteria in Given/When/Then format." 

43. "This user story is too large to deliver in one sprint: [paste story]. Break it into 4–5 smaller stories, each independently valuable." 

44. "Add edge case and error state user stories to this core story: [paste story]. Cover empty states, permission errors, and network failures." 

45. "Rewrite this user story to be more testable: [paste story]. Make every acceptance criterion something a QA engineer can verify without ambiguity." 

46. "Generate the full set of user stories for [feature area], organized by user role: [list roles]. Cover happy paths, edge cases, and admin actions." 

47. "Translate this technical requirement into a user-centered story: '[paste technical spec].' Focus on user value, not implementation." 

48. "Write user stories for a [feature] that needs to work for three different personas: [A], [B], [C]. Note where the same story serves all three and where they diverge." 

49. "Review this set of user stories: [paste]. Identify: stories that are too vague, stories missing acceptance criteria, dependencies between stories, and sequencing recommendations." 

50. "Write a developer-facing user story for [API or technical feature]. Use the persona 'As a developer integrating with our platform...' and include technical acceptance criteria." 

51. "Generate user stories for the onboarding flow of [product]. Cover: first login, setup steps, first value moment, and help/support access." 

52. "Write user stories for the permission and role management of [product feature]. Cover: admin, standard user, and read-only roles." 

53. "Create user stories for an accessibility-compliant version of [feature]. Reference WCAG 2.1 AA criteria where relevant." 

54. "Take this epic description and write a full story map: [paste epic]. List backbone activities across the top and user stories under each." 

55. "Write the 'definition of done' for user stories in [product area]. Include criteria for design, development, testing, documentation, and analytics." 

6. Product Roadmapping 

56. "Organize these features into a Now / Next / Later roadmap: [paste list]. Explain the reasoning for any non-obvious placements." 

57. "Write a roadmap narrative for our Q3 plan: [paste roadmap items]. Explain the strategic logic for an executive audience in 3 paragraphs." 

58. "Review this roadmap: [paste]. Identify: gaps in coverage, over-commitment risks, missing dependencies, and items that belong in a different horizon." 

59. "Create a one-page roadmap summary for [product] including: vision statement, three strategic themes, quarterly deliverables, and one deliberate 'not doing' item." 

60. "Generate a product roadmap for [product type] for a 12-month period. Organize it into themes rather than features. Include quarterly milestones." 

61. "Write the OKR-to-roadmap alignment story for this quarter: [paste OKRs and roadmap]. Show how each roadmap theme connects to a specific key result." 

62. "Play devil's advocate on this roadmap: [paste]. What are the strongest three arguments against this sequence? What are we missing?" 

63. "Write a roadmap FAQ document the 10 most common questions stakeholders ask about our roadmap and clear, honest answers to each." 

64. "Translate this customer-facing roadmap into an internal delivery roadmap with dependencies, milestones, and owner placeholders." 

65. "Generate a rolling 90-day roadmap for [product area] based on these priorities: [paste]. Include confidence levels for each item. 

7. Prioritization Frameworks 

66. "Apply RICE scoring to these features: [paste list]. Use placeholders where data is missing and flag which estimates need validation." 

67. "Apply the MoSCoW framework to this backlog for MVP: [paste list]. Explain your reasoning for each classification." 

68. "Compare these two roadmap bets: [Option A] vs [Option B]. Walk through trade-offs across: user impact, strategic fit, reversibility, effort, and opportunity cost." 

69. "Create a value vs. effort matrix for these features: [paste list]. Place each in a quadrant: quick wins, big bets, fill-ins, or avoid." 

70. "Write a prioritization brief for [feature]. Include: estimated reach, impact on key metric, confidence in estimate, effort required, and recommendation." 

71. "We have unlimited ideas and limited quarters. Write a framework for how we should decide what makes it onto the roadmap. Base it on our strategy: [paste strategy]." 

72. "Generate a set of prioritization questions our team should answer before any feature gets added to the roadmap." 

73. "Review our current top 10 priorities: [paste]. Suggest re-sequencing with a rationale. Assume we have one cross-functional team for 12 weeks." 

74. "Apply the Kano model to these features: [paste list]. Classify each as: Basic need, Performance feature, or Delighter." 

75. "Write a decision memo for choosing between [Option A] and [Option B]. Structure it as: context, options, analysis, recommendation, and risks." 

8. Backlog Management 

76. "Review this sprint backlog: [paste]. Flag: stories that are too large, missing dependencies, unclear acceptance criteria, and sequencing issues." 

77. "Write a backlog grooming agenda for a 90-minute session covering [focus areas]. Include timings and facilitation notes." 

78. "Generate 10 questions a product owner should ask before accepting a story into the sprint." 

79. "Clean up this backlog item title and description to be clear, user-centered, and actionable: [paste]." 

80. "Identify which items in this backlog are duplicates or near-duplicates: [paste list]. Suggest consolidations." 

81. "Write a set of backlog hygiene rules for our team. Include: what qualifies for the backlog, how items are sized, how they're archived, and how often they're reviewed." 

82. "Generate a template for backlog items in our product that includes: title format, description structure, acceptance criteria format, and required metadata fields." 

83. "We have 60 items in our backlog. Help me create a triage process to reduce it to the 20 most important items this quarter." 

9. Sprint Planning and Ceremonies 

84. "Write a sprint goal for a team working on [feature area] this sprint. Make it outcome-focused, not task-focused." 

85. "Generate a sprint retrospective agenda for a team that recently had [describe challenge  e.g., scope creep, missed deadlines, communication gaps]." 

86. "Write 10 retrospective prompts that go deeper than 'what went well / what didn't.' Focus on process, team dynamics, and learning." 

87. "Create a sprint review presentation outline for stakeholders covering: what we built, demo structure, metrics update, and what's next." 

88. "Generate a definition of done checklist for [product type]. Include criteria for: code, design, testing, documentation, and analytics." 

89. "Write a sprint planning facilitation guide for a 2-hour session. Include: pre-work, capacity planning step, story review step, and commitment check." 

90. "Generate questions to ask during sprint planning to catch risks before the sprint starts." 

91. "Write a team working agreement for a product squad. Cover: communication norms, decision-making, meeting expectations, and how to handle blockers." 

10. Stakeholder Management and Communication 

92. "Write a stakeholder update email for [project/feature] covering: what we shipped, what we learned, what's next, and what we need from them." 

93. "A stakeholder is pushing to add [feature] to the roadmap. We've decided not to. Write a diplomatic response that explains our reasoning without creating conflict." 

94. "Create a RACI matrix for the product launch of [feature]. Roles involved: [list roles]." 

95. "Write a pre-read document for a roadmap review meeting with senior leadership. Include: strategic context, current roadmap summary, key decisions needed, and open questions." 

96. "Generate 10 questions to ask a new stakeholder in a first 1:1 to understand their priorities, constraints, and definition of success." 

97. "Write a stakeholder communication plan for [product initiative]. Include: audience, frequency, format, owner, and key messages for each segment." 

98. "Draft a response to this stakeholder escalation: [paste message]. Be empathetic, clear about constraints, and propose a path forward." 

99. "Write a product update for a monthly all-hands. Cover: wins, learnings, upcoming milestones, and one metric we're proud of. Tone: transparent and energizing." 

100. "Create a FAQ document for [product launch or change] answering the 10 questions stakeholders are most likely to ask." 

101. "Write talking points for a difficult stakeholder conversation where we need to say no to a high-priority request without damaging the relationship." 

11. Product Strategy 

102. "Write a product vision statement for [product] that is inspiring, memorable, and specific enough to guide decisions. Generate three versions with different angles." 

103. "Develop a product strategy one-pager for [product area]. Include: market context, target customer, strategic bets, success metrics, and what we're not doing." 

104. "Write a north star metric recommendation for [product]. Explain why it captures the core value delivered to users and how it connects to business outcomes." 

105. "Generate 5 strategic themes for [product] for the next 12 months based on this context: [paste market/user/business context]." 

106. "Write a product positioning statement for [product] using the format: For [target customer] who [need], [product name] is a [category] that [key benefit]. Unlike [alternative], we [differentiator]." 

107. "Analyze our product strategy against this competitive landscape: [paste competitors and positioning]. Where are we vulnerable? Where is there white space?" 

108. "Write a build vs. buy vs. partner analysis framework for [capability]. What criteria should we use to decide?" 

109. "Draft a product strategy narrative that connects our 3-year vision to our 12-month roadmap to this quarter's OKRs." 

110. "Generate a set of strategic bets for [product] high-conviction investments where we're willing to be wrong but the upside justifies the risk." 

111. "Write a 'strategy on a page' document for our product team. Make it clear enough that any team member could use it to make a daily prioritization decision." 

12. Competitive Analysis 

112. "Create a competitive analysis framework for [product category]. What dimensions should we evaluate competitors on?" 

113. "Write a competitive positioning map for [product]. Compare us to [Competitor A], [Competitor B], [Competitor C] on dimensions of [criteria]." 

114. "Analyze this competitor's product page: [paste URL or content]. What is their positioning, who are they targeting, and what messaging angles are they using?" 

115. "Write a battle card for competing against [competitor] in sales conversations. Include: their strengths, their weaknesses, our counter-narrative, and landmine questions to ask." 

116. "Generate a win/loss analysis framework for [product]. What questions should we ask customers who chose us or chose a competitor?" 

117. "Write a competitor monitoring plan. What signals should we track weekly to stay ahead of [competitor]'s product moves?" 

118. "Summarize the key product differences between [our product] and [competitor] in plain language a salesperson could use in a conversation." 

119. "Identify the gaps in this competitive landscape: [paste]. What problems exist that no current solution addresses well?" 

13. Metrics and Analytics 

120. "Write an OKR set for [product team] for Q[X]. Include 2–3 objectives and 3–4 key results each. Make key results measurable and time-bound." 

121. "Generate a metrics framework for [product feature]. Include: primary success metric, secondary metrics, guardrail metrics, and leading indicators." 

122. "Write a data requirements document for [feature]. What events should we track, what properties should each event have, and what dashboards do we need?" 

123. "Analyze these product metrics: [paste]. What's performing well, what's underperforming, what are the likely causes, and what would you investigate next?" 

124. "Generate a product health scorecard template. Include: retention metrics, engagement metrics, acquisition metrics, and revenue metrics with benchmark guidance." 

125. "Write a hypothesis for an A/B test on [element]. Include: what we're testing, why we think it will work, what metric we're measuring, and what sample size we need." 

126. "Design an experiment to validate this assumption: [paste assumption]. Include: method, success criteria, timeline, and risk of false positive." 

127. "Write the analytics spec for [feature]. What do we need to measure to know if this feature is successful, and how do we define success?" 

128. "Generate 10 product questions our team should be able to answer with data, but currently can't. Use this context: [paste product description]." 

129. "Translate these business metrics into user behavior metrics: [paste business KPIs]. What user actions would move each needle?" 

130. "Write a post-launch measurement plan for [feature]. Include: what we measure, when we measure it, who reviews it, and what triggers a response." 

14. Go-to-Market and Launch 

131. "Write a go-to-market plan for [feature or product]. Include: target segment, key message, launch channels, launch timeline, and success metrics." 

132. "Create a product launch checklist for [product type]. Cover: pre-launch, launch day, and post-launch activities across product, marketing, sales, and support." 

133. "Write a press release for the launch of [product/feature]. Include: headline, dateline, opening paragraph, product description, quote from founder, and boilerplate." 

134. "Generate three different launch narratives for [product] one for a tech audience, one for a business buyer, and one for a general consumer." 

135. "Write a sales enablement one-pager for [feature]. Include: what it does, who benefits, key differentiators, common objections, and suggested talking points." 

136. "Create a launch communication plan covering: internal announcement, customer announcement, partner communication, and public announcement with timing and format for each." 

137. "Write a beta program brief for [feature]. Include: goals, participant criteria, feedback collection method, timeline, and success criteria." 

138. "Generate a soft launch vs. full launch trade-off analysis for [product/feature]. What are the risks and benefits of each approach?" 

139. "Write a product FAQ for the launch of [feature]. Cover the 10 questions customers are most likely to ask." 

140. "Create a launch retrospective template to run after [product launch]. What should we evaluate and how?" 

15. Product Copy and Content 

141. "Write five landing page headline options for [product]. Vary the angle: outcome, speed, simplicity, trust, and problem." 

142. "Write onboarding tooltip copy for [feature]. Each tooltip should be under 20 words and answer: what this is and why it matters." 

143. "Generate empty state copy for [product screen]. Include a headline, a short description, and a CTA. Make it helpful, not just decorative." 

144. "Write error message copy for these five error states in [product]: [list states]. Make each message clear, human, and actionable." 

145. "Create a product changelog entry for [feature]. Write in plain language for a user audience, not a technical one. Under 100 words." 

146. "Write microcopy for the following UI elements in [product]: [list buttons, labels, placeholders, confirmation messages]." 

147. "Generate three email subject line options for a feature announcement to existing users. Include: a curiosity angle, a benefit angle, and a direct angle." 

148. "Write a help center article for [feature]. Cover: what it is, how to use it, common questions, and where to get help." 

149. "Create in-app notification copy for [user action or milestone]. Keep it under 50 words and make it feel like a human wrote it." 

150. "Write a product update blog post for [release]. Include: what changed, why we made the change, how to use it, and what's coming next." 

16. Design and UX Collaboration 

151. "Write a design brief for [feature]. Include: user problem, key user flows, edge cases to design for, constraints, and success criteria." 

152. "Generate 10 UX research questions we should answer before designing [feature]." 

153. "Review this user flow: [paste or describe]. Identify friction points, missing steps, and edge cases not covered." 

154. "Write usability test tasks for [feature]. Create 5 tasks a participant could complete to evaluate whether the design is intuitive." 

155. "Generate accessibility requirements for [feature] based on WCAG 2.1 AA. List what the design and development team need to implement." 

156. "Write the content requirements for the [screen or flow] in [product]. What copy, labels, microcopy, and help text does the designer need to spec?" 

157. "Critique this wireframe description from a UX perspective: [paste description]. What might confuse users? What's missing?" 

158. "Write a design system contribution brief for [new component]. Include: use cases, variants needed, states, and behavior specs." 

159. "Generate interview questions for a UX portfolio review focused on product thinking and cross-functional collaboration." 

160. "Write a design review agenda for [feature]. What should we evaluate, who should attend, and what decisions need to be made?" 

17. Engineering Collaboration 

161. "Translate this product requirement into a technical requirements document outline: [paste PRD section]. Flag areas where engineering decisions are needed." 

162. "Write a set of clarifying questions a product owner should answer before engineering can estimate [feature]." 

163. "Generate a technical spike definition for [area of uncertainty]. Include: what we're trying to learn, timebox, and what a successful outcome looks like." 

164. "Write a migration plan communication for [technical change] that explains the user impact without technical jargon." 

165. "Create a dependency mapping template for [feature]. What needs to be built first, what can be built in parallel, and what is blocked by external teams?" 

166. "Write a product-engineering escalation framework. How should conflicts between product scope and technical constraints be handled?" 

167. "Generate a set of engineering team agreements for how product and engineering collaborate during sprint planning, mid-sprint, and retrospectives." 

168. "Write the API documentation outline for [feature] from a product perspective what does a developer integrating this need to know?" 

169. "Create a technical debt briefing for non-technical stakeholders explaining why [area of debt] needs investment and what the user impact is if we don't address it." 

170. "Write questions a product owner should ask in a technical architecture review for [feature]." 

18. Artificial Intelligence and AI Features 

171. "Write a product requirements document for an AI-powered [feature type] in [product]. Include: user problem, proposed AI behavior, training data requirements, evaluation criteria, and edge case handling." 

172. "Generate 10 ways AI could enhance [existing product feature]. For each, describe the user benefit and the data required." 

173. "Write a responsible AI checklist for [AI feature]. Cover: bias risk, transparency, user control, data privacy, and failure modes." 

174. "Create a product spec for an AI recommendation feature. Include: inputs, outputs, user control options, explanation requirements, and feedback loop." 

175. "Write user stories for an LLM-powered [feature]. Include stories for: successful output, poor output, user correction, and output feedback." 

176. "Generate an evaluation framework for [AI feature]. What metrics determine whether the AI is performing well from a user perspective?" 

177. "Write the explainability requirements for [AI feature]. What does the user need to understand about how the AI made its decision?" 

178. "Create a data labeling brief for training [AI feature]. What examples does the model need, how should they be labeled, and what edge cases should be included?" 

179. "Write a rollout plan for [AI feature] that includes a limited pilot phase, feedback collection, and criteria for full release." 

180. "Generate a product FAQ for [AI feature] that honestly addresses: how it works, what it can't do, how we protect data, and what happens when it's wrong." 

19. Customer Success and Retention 

181. "Write a customer onboarding sequence for [product]. Include: welcome email, activation prompt, first value moment email, and 14-day check-in." 

182. "Generate churn risk signals for [product]. What user behaviors in the first 30 days predict whether someone will stay or leave?" 

183. "Write a customer health score framework for [product]. What events, behaviors, and usage patterns indicate a healthy vs. at-risk account?" 

184. "Create a win-back email sequence for churned users of [product]. Include: 3 emails with different angles new features, social proof, and direct offer." 

185. "Generate 10 NPS follow-up questions to ask users who gave a score of 6 or below." 

186. "Write an in-app survey for users who haven't returned after their first session. Keep it to 3 questions maximum." 

187. "Write a customer success playbook for [segment] at the 30/60/90-day marks. What should CS do, say, and share at each milestone?" 

188. "Generate a feature adoption campaign for [underused feature]. Include: in-app message, email, and tooltip copy." 

189. "Write a renewal conversation guide for a B2B product. What should a CS manager cover in a renewal call 60 days before contract end?" 

190. "Create a customer feedback loop process. How do we collect feedback, route it to product, act on it, and close the loop with customers?" 

20. Career, Hiring, and Team Development 

191. "Write a job description for a Senior Product Manager at [company type] focused on [product area]. Include: responsibilities, requirements, nice-to-haves, and team context." 

192. "Generate a PM interview scorecard for evaluating [specific competency e.g., prioritization, stakeholder management, data fluency]." 

193. "Write a 30/60/90-day onboarding plan for a new Product Manager joining [team type]." 

194. "Create a PM career progression framework from Associate PM to Director level. Define key competencies and expectations at each level." 

195. "Write a product manager performance review template. Include: goal evaluation, competency assessment, strengths, development areas, and next steps." 

196. "Generate a set of PM interview questions that go deeper than surface answers for [competency area]." 

197. "Write a team charter for a new product squad. Include: mission, ways of working, decision rights, and success metrics." 

198. "Generate a skills gap analysis template for a product team. What competencies should we assess, how do we rate them, and how do we close gaps?" 

199. "Write a product manager development plan for someone looking to grow from PM to Senior PM in 12 months." 

200. "Create an interview take-home challenge for PM candidates at [company type]. Include: brief, deliverables, time expectation, and evaluation criteria." 

BONUS: 50+ Situation-Specific Prompts 

When you're stuck 

201. "I'm trying to make a decision about [topic] and I'm stuck between [Option A] and [Option B]. Ask me 5 clarifying questions that would help me decide." 

202. "I can't articulate why [feature] matters. Help me find the user value by asking me questions about the problem it solves." 

203. "I need to say no to [request] in a way that's honest but doesn't damage the relationship. Help me structure my response." 

204. "My team is misaligned on [issue]. What are the most common underlying causes of this type of disagreement, and what facilitation approaches might help?" 

205. "I've been going in circles on [decision]. Summarize the decision, the options, the key trade-offs, and what information would break the tie." 

When you're preparing for a meeting 

206. "Write a pre-read for a product strategy meeting covering: context, current state, key questions to resolve, and desired outcomes." 

207. "Generate an agenda for a 60-minute product critique session. Include timings, facilitation approach, and decision format." 

208. "Write a meeting prep checklist for a quarterly business review where product is presenting results and next quarter plan." 

209. "Prepare me for a tough question I'm likely to get in [meeting type]. Question: '[paste question].' Draft a clear, honest answer." 

210. "Write a one-page briefing on [topic] that a VP-level executive would read in 3 minutes before a product review." 

When you're writing documents 

211. "Write a PRD outline for [feature]. Include all standard sections and note which require input from engineering, design, or data." 

212. "Review this PRD section: [paste]. Identify: missing information, ambiguous requirements, and questions engineering will ask." 

213. "Write the executive summary for this product document: [paste document]." 

214. "Convert this PRD into a JIRA epic with sub-stories. Use the information in [paste] to create a complete set of tickets." 

215. "Write a risk register for [product initiative]. Include: risk description, likelihood, impact, mitigation strategy, and owner." 

When you're working with data 

216. "Write a data analysis brief for [question]. Include: what we're trying to understand, what data we need, how we'll analyze it, and how we'll act on findings." 

217. "Translate this analytics dashboard: [paste metrics]. What's the story in plain English?" 

218. "Generate a set of cohort analysis questions for [product]. What user cohorts should we track and what behavior differences should we look for?" 

219. "Write a funnel analysis brief for [user flow]. What drop-off points should we examine and what hypotheses might explain the drop-off at each stage?" 

220. "I have these A/B test results: [paste]. Interpret them. Is the result significant? What should we do next?" 

When you're thinking about the market 

221. "Write a market sizing estimate for [product/feature]. Use TAM / SAM / SOM framework. Use reasonable assumptions and show your work." 

222. "Generate a SWOT analysis for [product] in [market]. Be specific and evidence-based, not generic." 

223. "Write a Porter's Five Forces analysis for [industry/market]. What does it mean for our product strategy?" 

224. "Generate a market trend brief for [industry]. What are the 3–5 most important shifts over the next 2 years and what do they mean for us?" 

225. "Identify the jobs-to-be-done that no current solution in [market] adequately addresses." 

When you're managing up 

226. "Write a product scorecard I can share with my CEO monthly. Include: north star metric, 3 supporting metrics, key wins, key risks, and 30-day focus." 

227. "Help me structure a difficult conversation with my VP about why [initiative] is behind schedule. What should I cover and how should I frame it?" 

228. "Write a proposal for increasing product team headcount. Include: current capacity, gaps, impact of the gap, proposed hire, and expected ROI." 

229. "Generate talking points for a board update on product progress. Cover: what we shipped, what we learned, what we're building next, and where we need help." 

230. "I need to push back on a directive from leadership. Help me write a response that challenges the decision constructively while showing I understand the business context." 

When you're learning 

231. "Explain [product concept] as if I'm a PM who knows the basics but has never applied it. Give a real example from a product I'd know." 

232. "Create a learning plan for a PM who wants to improve at [skill area] over 90 days. Include: resources, exercises, and ways to practice on the job." 

233. "Write a case study analysis framework for studying [competitor product]. What should a PM look for and what questions should they ask?" 

234. "Generate a book club discussion guide for [product/business book]. Include 8 questions that connect the concepts to our real product challenges." 

235. "What are the most common mistakes PMs make when [specific situation e.g., writing OKRs, running discovery, launching features]? How do I avoid them?" 

When you're thinking about the future 

236. "Write a 3-year product vision narrative for [product]. Make it ambitious but grounded. Include where users are today, where they'll be in 3 years, and how we get them there." 

237. "Generate a set of product bets for [market] based on emerging trends in [technology area]. For each, describe the bet, the upside, and the risk." 

238. "Write a scenario planning brief for [product]. Describe three futures optimistic, expected, and pessimistic and what our roadmap should look like in each." 

239. "Identify the technology or market shifts that could make [our current product approach] obsolete in 3–5 years. What should we be watching?" 

240. "Write a product moonshot brief a version of [product] that is 10x better for users than what we have today. What would need to be true for it to exist?" 

When you're wrapping up 

241. "Write a project retrospective for [initiative]. Cover: what we set out to do, what we achieved, what we learned, and what we'd do differently." 

242. "Create a knowledge transfer document for [product area] that a new PM could read to get up to speed in one hour." 

243. "Write a celebration post for the team after [launch or milestone]. Keep it genuine, specific, and motivating." 

244. "Generate a lessons learned report for [project]. Format it for sharing with the broader product organization." 

245. "Write a personal PM performance reflection for Q[X]. Evaluate: what I did well, where I grew, where I underperformed, and my focus for next quarter." 

Power combos multi-step prompts 

246. "First, summarize the key user problem from this feedback: [paste]. Then write a user story for it. Then generate 3 acceptance criteria. Do this in sequence." 

247. "Read this feature request from a stakeholder: [paste]. First, translate it into a user problem. Then generate three possible solutions. Then recommend one and explain why." 

248. "Take this rough roadmap: [paste]. First, identify the strategic theme that connects these items. Then write a one-paragraph narrative. Then suggest one item to cut and explain why." 

249. "Here are our top 5 user pain points: [paste]. For each, write: the problem statement, one feature idea, and one metric that would tell us if we solved it." 

250. "Review this sprint plan: [paste]. Identify the riskiest assumption in it. Write a one-week experiment we could run to validate or invalidate that assumption before committing." 

Learning through the upGrad KnowledgeHut Agile Management Course can help you understand how to apply Agile methodologies effectively in real-world project management scenarios. 

Conclusion 

AI prompts are becoming one of the most valuable productivity assets for modern product owners. By using well-structured prompts, product managers can accelerate Agile planning, improve documentation quality, automate repetitive workflows, generate strategic insights, analyze customer behavior, and scale product operations more efficiently. 

Contact our upGrad KnowledgeHut experts for personalized guidance on choosing the right course, career path, and certification to achieve your goals.