50 ChatGPT Prompts for Product Managers

Write a PRD for [feature name] that [solves what problem]. Include: Problem Statement (with user quotes if available), Goals and Non-Goals, User Stories, Functional Requirements, Non-Functional Requirements (performance, security, accessibility), Design Considerations, Technical Constraints, Success Metrics, and Open Questions.

Tip: Non-goals are as important as goals. Explicitly stating what you are NOT building prevents scope creep.

Create a one-page product brief for [initiative] to get executive buy-in. Cover: customer problem (with data), proposed solution (high level), business impact (revenue/retention/efficiency), effort estimate, key risks, and recommended next step. Persuasive and concise.

Tip: Executives approve initiatives that clearly connect customer problems to business outcomes.

Write acceptance criteria for [feature] using the Given-When-Then format. Cover: happy path (3 scenarios), edge cases (3), error states (3), and accessibility requirements (2). Each should be testable with a clear pass/fail.

Tip: Acceptance criteria written before development prevent the 'that is not what I meant' conversation during QA.

Draft a technical requirements document for integrating with [third-party API/service]. Cover: use case, data flow, authentication, rate limits, error handling, fallback behavior, data mapping, testing plan, and rollback strategy.

Tip: Integration specs should always define fallback behavior for when the third-party service is down.

Write 15 user stories for [feature/product] covering [user types]. Format: 'As a [persona], I want to [action] so that [benefit].' Prioritize by value and include acceptance criteria for the top 5. Group by epic.

Tip: The 'so that' clause is the most important part — it captures why the user cares, which informs design decisions.

Create a user interview script for understanding [problem space]. Include: warm-up questions (3), problem exploration (5), current solution questions (4), ideal state questions (3), and wrap-up. Add interviewer notes on probing techniques and what to listen for.

Tip: Never ask users what they want built. Instead, ask about their problems, workarounds, and what frustrates them.

Build a persona from this user research data: [paste interview notes or survey results]. Include: name, role, goals, frustrations, behaviors, tools used, a day-in-the-life narrative, and a quote that captures their core need. Based on patterns, not fiction.

Tip: Personas based on real research are strategic tools. Made-up personas are just creative writing exercises.

Write a Jobs-to-be-Done analysis for [product/feature]. Identify 5 jobs users hire this product to do. For each: the job statement, functional aspect, emotional aspect, social aspect, current alternatives, and what 'done well' looks like.

Tip: JTBD focuses on the progress users want to make, not their demographics. This shift in perspective reveals unexpected competitors.

Build a product roadmap for [product] for the next [3/6/12] months. Organize by: Now (committed), Next (planned), Later (exploratory). For each item: name, objective, key results, dependencies, and estimated effort (S/M/L). Include a 'not doing' list.

Tip: Roadmaps should communicate direction and priorities, not exact dates. Use time horizons, not deadlines.

Run a RICE prioritization on these feature requests: [list 5-8 features]. Score each on Reach, Impact, Confidence, and Effort. Show the calculation, rank them, and provide a recommended build order with rationale for any reordering.

Tip: RICE is a starting point for discussion, not a mathematical truth. Override the score when strategic context demands it.

We have [X] feature requests from customers, sales, and internal teams. Create a prioritization framework considering: strategic alignment, customer impact, revenue potential, technical complexity, and dependencies. Provide a scoring template and decision matrix.

Tip: The best prioritization frameworks are transparent. When stakeholders understand the criteria, they accept the outcome.

Write a 'what we are not building and why' document for [quarter/year]. List 5-7 commonly requested features or initiatives we are intentionally declining. For each: what was requested, why it is not a priority now, what we are doing instead, and when it might be reconsidered.

Tip: Saying no transparently builds more trust than saying maybe and never delivering.

Write a product update email for [audience: executives/sales team/engineering/customers]. Cover: what shipped this [week/sprint/month], key metrics impact, what is coming next, known issues, and how to provide feedback. Adapt tone and detail level for the audience.

Tip: Engineering wants technical details, sales wants customer-facing impact, executives want metrics — same update, different framing.

Prepare a stakeholder alignment document for [controversial product decision]. Present: the decision, the 3 alternatives considered, evaluation criteria, data supporting the decision, risks acknowledged, mitigation plan, and feedback process.

Tip: When a decision is controversial, documenting the alternatives you considered shows rigorous thinking even if people disagree.

Write a product launch communication plan. Audiences: internal (engineering, sales, support, executives), external (customers, prospects, press). For each: message, channel, timing, owner, and key talking points. Include a FAQ for support and sales.

Tip: Support and sales need launch information before customers do. Nothing kills launch momentum like a support team that cannot answer questions.

Write a product strategy document for [product]. Cover: vision (3-year), target market, customer problems we solve, competitive moat, business model, key bets (3-5 strategic hypotheses), how we win, and how we measure progress. One page, no fluff.

Tip: A product strategy should fit on one page. If it takes 20 pages, you do not have a strategy — you have a wish list.

Create a competitive analysis for [product] against [3 competitors]. For each: positioning, target customer, pricing, key strengths, key weaknesses, and recent strategic moves. Identify our defensible differentiation and areas of vulnerability.

Tip: Competitive analysis should inform your strategy, not drive it. Build for customer needs, not competitor feature lists.

Design a product-led growth (PLG) strategy for [product]. Cover: free tier design, activation metrics, time-to-value optimization, viral loops, expansion triggers, conversion points, and experimentation roadmap. Include benchmarks for each metric.

Tip: PLG requires the product to be the primary sales channel. Every friction point in the product is a conversion killer.

Write a product sunset plan for [feature/product] that still has [X] active users. Cover: user communication timeline, migration path, data export tools, support plan, sunset date, and internal decommissioning steps. Empathetic and practical.

Tip: How you sunset a product reveals your company's character. Give users time, tools, and genuine help migrating.