ChatGPT Prompts for Product Managers

You are a senior product manager at a B2B SaaS company with 10 years of experience writing PRDs that engineering teams actually read and use as a source of truth.

I need a PRD for a "Smart Notifications" feature for our project management tool. Context: Our current notification system sends every event to every user who has access to the project — teams are turning off all notifications because of noise, and then missing critical updates. The goal of Smart Notifications is to let users set preferences by event type and urgency, with an AI-suggested default profile based on their role.

Write a complete PRD that includes:
- Problem statement (1 paragraph, grounded in user pain)
- Goals and non-goals (what this release does and explicitly does not solve)
- User personas affected (at minimum: the project owner, a contributor, an executive stakeholder)
- Functional requirements (organized by must-have / should-have / won't-have-v1)
- Success metrics with baselines: notification opt-out rate (current: 62%), weekly active users on notification settings, and support tickets mentioning "missed update" (current: ~40/week)
- Edge cases and open questions that engineering needs answered before building
- Out-of-scope items for this version

Format as a proper PRD document with headings. Write for an audience of engineers and designers who will build from this doc.

You are a product manager experienced in writing user stories that work for agile sprint planning — specific enough that engineers can estimate and QA can write test cases, but not so prescriptive that they constrain implementation.

Feature context: We're adding a "Guest Checkout" option to our e-commerce platform. Currently, all customers must create an account to complete a purchase. Stakeholder goal: reduce checkout abandonment (currently at 74%, industry average is 68%). Technical constraint: guest orders must still capture email for order confirmation and return initiation; marketing team must not receive guest emails for campaign lists without explicit opt-in.

Write user stories for the following flows:
1. Guest initiates checkout without logging in
2. Guest receives order confirmation email
3. Guest initiates a return
4. Guest is offered (but not forced to) create an account post-purchase

For each story:
- Write in standard format: "As a [persona], I want to [action] so that [outcome]"
- Include 3–5 acceptance criteria per story using Given/When/Then format
- Flag any story where there's ambiguity that needs a product decision before engineering can proceed

Do not write implementation details — these are product stories, not technical tickets.

You are a product strategy consultant who helps teams cut through opinion-based roadmap debates by applying structured prioritization frameworks. You're especially good at forcing teams to make their assumptions explicit.

I have 6 features competing for Q3 roadmap slots and my team can realistically ship 3 of them. Here is each feature with rough estimates:

1. Bulk export to CSV — Reach: 800 users/quarter, Impact: medium (2), Confidence: 90%, Effort: 2 weeks
2. Slack integration — Reach: 1,200 users/quarter, Impact: high (3), Confidence: 60%, Effort: 6 weeks
3. Mobile app (iOS) — Reach: 2,000 users/quarter, Impact: high (3), Confidence: 40%, Effort: 20 weeks
4. Custom dashboard widgets — Reach: 400 users/quarter, Impact: high (3), Confidence: 80%, Effort: 4 weeks
5. SSO / SAML support — Reach: 150 users/quarter (enterprise only), Impact: massive (4), Confidence: 95%, Effort: 3 weeks
6. In-app onboarding checklist — Reach: all new users (~300/quarter), Impact: medium (2), Confidence: 85%, Effort: 2 weeks

Calculate RICE scores for each feature (RICE = Reach × Impact × Confidence ÷ Effort). Then:
- Rank them by RICE score
- Identify the top 3 to ship in Q3
- Flag any where the assumptions feel shaky and should be pressure-tested before committing
- Note if any features have strategic reasons to include or exclude them that RICE doesn't capture

Show your math.

You are a product manager who is skilled at writing stakeholder communications that are honest about bad news without causing panic or eroding trust. You know that how you frame a delay matters as much as the delay itself.

I need to communicate a 3-week launch delay to executive stakeholders and our go-to-market team. Context: We were supposed to launch our new Reporting Suite on June 3rd. During final QA this week, we discovered a data accuracy issue in multi-currency reports — numbers are off by up to 8% in edge cases when a user has transactions in more than 3 currencies. We cannot ship a reporting product with incorrect numbers. New target date: June 24th. The engineering fix is scoped and underway.

Write a stakeholder update that:
- Opens with the key facts (what, when, why) in the first 2 sentences — no burying the lead
- Explains the issue in plain language without technical jargon, but without dumbing it down either
- Is clear about why we can't ship as-is (accuracy issue in a reporting product = trust problem)
- States the new date with confidence, not as a tentative estimate
- Outlines the 3 actions already in motion to resolve it
- Addresses the GTM impact: what campaigns or announcements need to shift
- Does not over-apologize or get defensive

Format: email to a distribution list of 12 executives and GTM leads. Subject line included.

You are a product strategist who has conducted competitive analyses for B2B SaaS products across categories including CRM, HR tech, project management, and fintech. You know that a useful competitive analysis identifies strategic patterns, not just feature checklists.

I'm building a competitive analysis for our time-tracking and invoicing tool (targeting 1–20 person service businesses: agencies, consultants, freelancers). Main competitors: Harvest, Toggl Track + Toggl Invoices, FreshBooks, and QuickBooks Time.

Create a competitive analysis framework that:
- Defines 5–7 dimensions to evaluate across (not just features — include positioning, pricing model, ideal customer profile, integration ecosystem, and at least one qualitative dimension like "ease of first invoice")
- Includes a scoring rubric for each dimension so the analysis is repeatable and not purely subjective
- Suggests primary research methods to validate assumptions (where to look: G2 reviews, Reddit threads, sales call recordings if available, churned customer interviews)
- Identifies the 2–3 strategic questions the analysis should answer, not just describe (e.g., "Where are competitors weakest with <10-person teams?" rather than "Who has the most integrations?")
- Flags which competitors are worth a deep dive vs. a lighter pass given our current stage

Deliver this as a framework and methodology document, not the analysis itself — I'll fill in the data.