AI Prompts for Product Managers and POs

"Write the "Goals, Non-Goals, and Success Metrics" section of a PRD for a new "Multi-User Workspaces" feature in a B2B design tool. Include at least 3 clear business goals, 2 explicitly stated non-goals (what we are deliberately NOT building in V1), and 4 measurable KPIs (Key Performance Indicators) with hypothetical baseline and target metrics. Ensure the metrics map directly back to the stated goals."

"Take the following high-level feature request: "Users need to be able to export their analytics dashboard to PDF." Break this down into 3-4 distinct Agile user stories using the "As a [type of user], I want [an action] so that [a benefit]" format. For each user story, write 4-5 rigorous Acceptance Criteria following the Given/When/Then BDD (Behavior-Driven Development) format, ensuring edge cases (like empty states or massive data sets) are covered."

"Analyze the following raw notes from 5 customer churn interviews. Identify the top 3 core themes driving churn. For each theme: provide a 1-sentence summary, list the verbatim quotes that support it, rate the severity (High/Medium/Low), and propose one immediate tactical product improvement and one long-term strategic shift to address it. Sample notes: [Insert Notes Here]. (Use a hypothetical B2B SaaS tool with complaints about slow reporting, confusing pricing, and missing integrations)."

"Translate these technical Jira tickets into engaging, customer-facing release notes for our monthly newsletter. Tickets: 1) Refactored auth flow to use JWT rotation (fixes random logouts), 2) Added index to messages table (improves search speed by 40%), 3) Implemented dark mode toggle in nav bar, 4) Deprecated legacy v1 API endpoints. Structure the notes with a catchy hook, group the updates logically (e.g., "New Features", "Performance Boosts"), and explain the actual user value for each change, completely hiding the technical jargon."

"Perform a teardown of how Slack handles "Threaded Conversations" versus how Microsoft Teams handles them. Analyze the UX choices, discoverability, notification management, and mobile experience for both. Conclude with a list of 3 things Slack does better, 3 things Teams does better, and 1 specific "white space" opportunity where a new competitor could build a superior threading experience that neither current product offers."

"Evaluate the following 3 proposed features using the RICE (Reach, Impact, Confidence, Effort) prioritization framework. 1) Mobile App Redesign, 2) SOC2 Compliance Certification, 3) Slack Integration. Assign plausible hypothetical numbers for Reach (users affected per quarter), Impact (1-3 scale), Confidence (percentage), and Effort (person-months) for each. Show the math for the final RICE score for each feature, rank them, and explain why the winner should be prioritized next quarter despite any trade-offs."

"Create a comprehensive Go-To-Market (GTM) launch checklist for a major "V2.0" platform overhaul. Divide the checklist by department: Product, Engineering, Product Marketing, Sales, and Customer Success. Include specific tasks for T-minus 30 days, T-minus 14 days, Launch Day, and T-plus 7 days. Ensure critical cross-functional dependencies are highlighted (e.g., Sales enablement materials MUST be ready before Sales training at T-14)."

"I am designing a "Seamless Checkout" feature for an e-commerce app where users can buy an item with one click using saved payment data. Brainstorm 10 critical edge cases, failure states, or unhappy paths we must design for. Cover scenarios involving network failures, expired cards, inventory stockouts during the millisecond of purchase, concurrent logins, and fraud detection flags. For each edge case, suggest the ideal user-facing error state or fallback behavior."

"Draft a bi-weekly executive update email regarding the delayed "Enterprise SSO" project. The project is currently 2 weeks behind schedule due to unexpected technical debt in the legacy user database. The tone must be strictly objective, taking accountability without being overly apologetic. Format the email using the "Watermelon Status" framework: what is Green (on track), what is Yellow (at risk), and what is Red (blocked/delayed). Include the specific mitigation plan and the new revised launch date."

"Draft a script for a 30-minute user discovery interview regarding a potential new feature: "AI-Assisted Email Drafting" in a CRM tool. Write 8 open-ended questions designed to uncover their actual past behavior and pain points, strictly avoiding leading questions, yes/no questions, or asking them to predict their future behavior. Include an introductory script setting the stage, and provide 3 specific follow-up probing questions (e.g., the "5 Whys" technique) to use when they give a superficial answer."