100 AI Prompts for Product Managers — Complete Guide

Generate 15 user interview questions to understand how [target user: e.g., 'small business owners'] currently manage [problem space: e.g., 'invoicing']. Follow the Jobs-to-be-Done framework. Include warm-up questions, behavioral questions about current workflow, frustration-probing questions, and avoid leading questions. Add follow-up probes for each question.

Synthesize the following user interview notes into key insights: [paste notes from 3-5 interviews]. Group findings into: core jobs to be done, main pain points ranked by frequency, current workarounds, unmet needs, and surprising discoveries. Identify patterns across participants and note where participants disagreed.

Create 3 detailed user personas for a [product type] targeting [market segment]. For each persona include: demographic profile, job role and context, primary goals and motivations, main frustrations with current solutions, technical proficiency, key behavioral patterns, and a 'day in the life' narrative. Base them on [describe research or market context].

Create a detailed customer journey map for [persona] trying to [accomplish goal] using [product/service]. For each stage (Awareness, Consideration, Onboarding, Regular Use, Retention/Churn), describe: what the user is doing, thinking, and feeling; touchpoints; pain points; and opportunities for improvement.

Write a product validation survey for [product idea description] targeting [audience]. Include: screening questions to qualify respondents, problem validation questions (does this pain exist?), solution validation questions (would they use/pay for this?), pricing sensitivity questions (Van Westendorp PSM), and a final NPS-style recommendation question. Limit to 10 questions.

Analyze the following 50 user feedback items from [channel: app store reviews, support tickets, NPS surveys]: [paste feedback]. Categorize by theme, identify the top 5 most frequently requested features, top 3 biggest pain points, and calculate sentiment distribution. Flag any critical issues mentioned more than 3 times.

Conduct a competitive analysis for [product] in the [market] space. Compare [competitor 1], [competitor 2], [competitor 3] across: core features, pricing model, target customer, key differentiators, known weaknesses (from reviews), and go-to-market approach. Identify the white space our product could own.

Help me write a crisp problem statement for the following product challenge: [describe the situation]. Use the format 'We have observed [observation] which leads to [impact]. How might we [action] for [users] so that [outcome]?' Then validate: is the problem statement specific, measurable, user-centric, and free of assumed solutions?

Design a concept testing protocol to evaluate [number] product concepts with [target users]. Include: screening criteria for participant recruitment, session structure (5-second test, think-aloud walkthrough, preference ranking), specific questions to ask for each concept, success criteria definition, and how to analyze and compare results.

I am building [product description] for [target users]. Help me identify the 10 riskiest assumptions underlying this product, ranked by: business risk (if wrong, kills the business) and validation difficulty. For each assumption, suggest the fastest and cheapest way to test it — before building anything.

Write a product vision statement for [product name] in the [market] space. Use the format: 'For [target customer] who [has this need], [product name] is a [product category] that [key benefit]. Unlike [alternative], our product [key differentiator].' Make it aspirational, memorable, and aligned with [company mission].

Help me prioritize the following features using the RICE framework: [list 10 features with brief descriptions]. For each feature, help me estimate: Reach (users/quarter), Impact (0.25-3x scale), Confidence (%), and Effort (person-months). Calculate RICE scores, rank them, and flag any features where my estimates seem inconsistent.

Write a 12-month product roadmap narrative for [product] divided into 3 themes: [theme 1], [theme 2], [theme 3]. For each quarter, describe the strategic bets, key deliverables, and expected outcomes in business terms (not feature lists). Include a 'why now' rationale for each phase and connect each theme to company OKRs: [list OKRs].

Help me apply the Kano model to categorize the following [N] features for [product]: [list features]. For each feature, suggest whether it is a: Basic (must-have), Performance (more is better), or Delight (unexpected wow) feature, with reasoning. Then recommend which to prioritize in each development phase.

Write quarterly OKRs for a product team responsible for [product area] with the strategic goal of [describe goal]. Create 3 Objectives, each with 3-4 Key Results. Ensure KRs are: outcome-focused (not output), measurable with specific numbers, ambitious but achievable (~70% confidence), and time-bound to the quarter.

Help me make a build vs buy vs partner decision for [capability needed]. We need it to: [list requirements]. Current team size: [N engineers], timeline: [X weeks], budget: [$Y]. Evaluate the top 3 options across: total cost of ownership, time-to-value, strategic fit, vendor risk, and long-term flexibility. Recommend with reasoning.

Define a go-to-market strategy for [product/feature] targeting [ICP]. Cover: positioning statement, key messages for each buyer persona, primary acquisition channels with rationale, pricing strategy and packaging, launch timeline with milestones, success metrics for the first [30/60/90] days, and internal enablement needs for sales/CS.

Help me define a North Star metric for [product] that serves [user segment] in the [market]. The metric should: directly correlate with customer value delivery, drive long-term revenue, be actionable by the product team, and be measurable weekly. Suggest 3 candidates, evaluate each, and decompose the recommended NSM into 3-5 input metrics.

Design a 90-minute prioritization workshop agenda for a cross-functional team of [N people] to align on Q[X] priorities from a backlog of [N] items. Include: icebreaker, context-setting, voting/scoring exercise, discussion format, tie-breaking protocol, and decision documentation template. The goal is to leave with an agreed top 10 list.

Write a 5-minute strategic narrative for [product area] to present to executives. Structure it as: current state (with data), the market opportunity, our strategic bet, what success looks like in 18 months (outcomes), what we need to get there (resources/decisions), and the key risks. Make it clear what decision or support you are asking for.

Write a Product Requirements Document for [feature name]. Include: problem statement, user personas affected, user stories (as [persona] I want to [action] so that [benefit]), acceptance criteria for each story, out-of-scope items, edge cases, success metrics, and dependencies. Target audience is the engineering and design team.

Write user stories with acceptance criteria for [feature: describe it]. Format each story as: 'As a [user type], I want to [action] so that [benefit].' Add Gherkin-style acceptance criteria (Given/When/Then) for each story. Cover the happy path, edge cases, and error states. Break down any story larger than [story point threshold].

Define success metrics for [feature name]. Identify: primary metric (the one number that proves this feature works), secondary metrics to monitor for side effects, guardrail metrics that must not degrade, how to measure baseline before launch, target values with rationale, and the measurement plan (tool, event names, query).

Write a detailed technical specification for [feature] intended for the engineering team. Include: functional requirements (numbered), non-functional requirements (performance, security, accessibility), API contract changes, data model changes, UI state machine, error handling requirements, analytics events to fire, and open questions for engineering.

Create a product decision log entry for the decision to [describe decision]. Include: decision date, decision owner, context and problem being solved, options considered with pros and cons, decision made and rationale, stakeholders consulted, expected outcomes, and review date to assess if the decision was correct.

Write an A/B test brief for testing [hypothesis about change to product]. Include: hypothesis statement, primary and secondary metrics, minimum detectable effect, required sample size calculation, targeting criteria, test duration, control and variant descriptions, success/failure criteria, and what you will do based on each outcome.

Identify all edge cases and failure modes for the following feature: [describe feature]. Consider: empty states, error states, permission variations, data boundary conditions, concurrent usage, slow network/offline behavior, accessibility edge cases, and internationalization issues. For each edge case, define the expected behavior.

Create a comprehensive launch checklist for [feature/product]. Include sections for: engineering readiness (tests, monitoring, rollback plan), design sign-off, legal/compliance review, data privacy assessment, customer support preparation (FAQs, training), sales/CS enablement, marketing materials, and post-launch monitoring schedule.

Define the API requirements for [feature] from a product perspective. For each API endpoint needed, specify: the business operation it supports, required input fields and validation rules, expected response data, error cases and user-facing messages, rate limiting requirements, and any backwards-compatibility constraints.

Write a deprecation plan for [feature/product/API]. Include: business rationale, affected user segments and count, migration path to replacement, communication timeline (notice period, reminder emails), sunset date, what happens to data after sunset, support policy during transition, and success criteria for the deprecation.

Write a product update email to [audience: company all-hands / investors / customers] covering the last [month/quarter]. Include: headline achievement, 3 key product milestones shipped, key metrics progress (with actual numbers: [list metrics]), what is coming next quarter, and a closing reflection on what you learned. Keep it under 400 words.

Write a response to the following internal stakeholder feature request that we cannot prioritize this quarter: [describe request and requester]. The response should: acknowledge the request positively, explain the prioritization rationale without blaming constraints, describe the alternative (if any), offer a clear path for reconsideration, and maintain the relationship.

Write an executive briefing document for a 20-minute roadmap review with the C-suite. Cover: strategic context (what problem we are solving for the business), Q[X] commitments and confidence level, key trade-offs made and why, the top 3 risks to the plan, what decisions or support you need from leadership, and the key metrics to watch.

Write a product retrospective for [quarter/period]. Structure it as: what we shipped (output), what moved (outcomes and metrics), what we learned (biggest surprises and insights), what did not work (honest assessment), what we are changing next period, and recognition of team contributions. Audience: team + leadership.

Write a product FAQ document for the sales team on [feature/product]. For each question, provide: a concise answer (2-3 sentences), a deeper explanation for complex follow-ups, competitive comparison points where relevant, and links to relevant demo assets. Include the top 10 questions customers ask sales about [feature/product].

Draft a response to the following customer escalation raised by our enterprise account [company name]: [describe the issue]. The response is from the product team to the account manager to share with the customer. Include: acknowledgment of the impact, what we know about the root cause, short-term workaround, long-term fix timeline, and executive sponsor name.

Write 5 product principles for [product name] that guide decision-making when the team faces trade-offs. Each principle should: articulate a value the team holds, be written as an active statement, include a 'not [anti-pattern]' clause for clarity, and have a real example of a decision this principle would guide. Principles should be distinct and occasionally in tension.

Write a message from the PM to the product team announcing a significant pivot from [old direction] to [new direction]. The message should: explain what changed and why (new evidence/insight), validate the work done so far (it was not wasted), describe the new direction clearly, acknowledge the emotional impact of change, and outline the immediate next steps.

Write a customer-facing release note for [feature name]. The note should: lead with the user benefit (not the technical implementation), explain how to access the feature, show a concrete use case with an example, list any limitations, and include a CTA. Tone: [friendly/professional/technical]. Max length: 150 words.

Define the contents of a product metrics dashboard for [product area]. Specify: top-level business metrics (revenue, retention, growth), product health metrics (activation rate, feature adoption, task completion), leading indicators that predict future outcomes, and operational metrics. For each metric, define the chart type, update frequency, and alerting threshold.

Design a user onboarding flow for [product] targeting [persona]. Define: the Aha Moment (first value experience), the minimum steps to reach it, what to defer to later, activation milestone definition, email/in-app nudge sequence for users who stall, and how to personalize the flow based on [user attributes collected at signup].

Help me analyze churn drivers for [product]. Our monthly churn rate is [X%]. Here is data on churned users: [describe behavioral patterns, survey data, exit interview themes]. Identify the top 3 churn causes, suggest leading indicators to detect at-risk users before they churn, and recommend 3 interventions to test.

Design a pricing strategy for [product] in the [market]. Current state: [describe current pricing or that it is new]. Analyze: value metric selection, packaging options (1-3 tiers), price point recommendations using value-based pricing and competitive benchmarks, freemium vs free trial decision, and expansion revenue mechanics (usage-based add-ons, seats, features).

Identify the key growth loops for [product]. For each loop, describe: the trigger, the action users take, the value created, how it brings in new users or drives re-engagement. Distinguish between acquisition loops, engagement loops, and monetization loops. Estimate which loop has the highest compounding potential.

Design a feature adoption campaign for [feature name] that has [X% adoption] despite being live for [Y months]. Target [user segment] who have not used it. Create: an in-app tooltip sequence, a 3-email drip campaign, a one-pager for the CS team, and a success metric (target adoption rate in [Z weeks]).

Design a retention analysis for [product]. Define: retention metric (Day 1/7/30 or weekly/monthly cohort retention), analysis by [acquisition channel, persona, plan type], healthy retention benchmarks for [product category], the specific retention curve shape to aim for (quick drop vs gradual), and interventions to test at each retention drop-off point.

Design a referral program for [product]. Define: referral trigger (when to ask), incentive structure for referrer and referee, referral mechanics (link, code, or direct invite), fraud prevention measures, tracking attribution across channels, landing page messaging, and success metrics. Include a phased rollout plan starting with power users.

Identify expansion revenue opportunities for [product] within the existing customer base. Current ARPU: [$X], NRR: [Y%]. Analyze: upsell opportunities (which customers are ready for a higher tier and why), cross-sell opportunities (adjacent products/add-ons), usage-based expansion triggers, and the expansion motion (self-serve vs CSM-led). Prioritize by revenue potential.

Define activation milestones for [product]. The Aha Moment hypothesis is: [describe what you think delivers first value]. Identify 3-5 specific in-product actions that correlate with long-term retention (use correlation with [30-day retention metric] as the criterion). Define a composite activation score and the threshold that predicts retention. Describe how to measure each milestone.

Write a win-loss analysis framework for [product] in competitive deals. Design: interview questions for won and lost customers (separate scripts), categories to score (product fit, pricing, sales experience, competition), how to aggregate results across [N] interviews, how to present findings to product and sales leadership, and a template for quarterly win-loss review.