AI Prompts for Product Managers: Ship Better Products with AI

Create a 12-month product roadmap for [product]. Current market position: [position]. Key competitors: [competitors]. User feedback themes: [feedback]. Format as a table with quarter, initiative, rationale, success metrics, and dependencies. Include at least 3-4 initiatives per quarter balancing quick wins with strategic bets. Flag any high-risk dependencies or overlaps.

I have these feature requests for my [product type]: [list 8-10 features]. My key metrics are [metrics]. Our constraints are [team size, timeline, technical debt]. Create a prioritization matrix using RICE (Reach, Impact, Confidence, Effort). For each feature, assign scores 1-10, calculate priority score, and provide brief rationale. Highlight the top 3 features to build first.

Analyze the market opportunity for [product/feature] in [market/segment]. What are the TAM, SAM, and SOM? Who are the main competitors? What unmet needs exist? What is the pricing landscape? Provide a 300-word summary structured as: Market Size | Competition | Unmet Needs | Pricing Opportunity | Recommendation.

We are considering pivoting our product from [current focus] to [new focus]. Current traction: [metrics]. Proposed pivot rationale: [reason]. Evaluate this pivot across: Market Opportunity (TAM, growth), Competitive Landscape, Technical Feasibility, Team Capability, and Financial Impact. Highlight risks and mitigating strategies. Recommendation: go/no-go with reasoning.

Generate 15-20 interview questions to understand [user segment]'s experience with [problem area]. I want to explore: [key themes]. Current assumptions: [assumptions]. Format as: Introduction Question | Problem Area Questions (5-7) | Current Solution Questions (3-4) | Needs & Desires Questions (3-4) | Closing Questions (2-3). Include follow-up probes for each.

Here are excerpts from 8 user interviews about [topic]: [paste quotes]. Analyze these quotes and: Identify 5-7 common themes. For each theme, find 2-3 supporting quotes. Rate each theme by frequency and intensity (high/medium/low). Suggest 3-5 product implications. Present as a structured report with theme title, description, quote examples, frequency/intensity, and implications.

Create detailed personas for [product] based on: [research data/user segments]. For each persona (3-5 personas), include: Name & Title | Demographics | Goals & Motivations | Pain Points | Current Solutions | Barriers to Adoption | Success Metrics | Key Behaviors. Use data from interviews, surveys, and analytics. Make personas vivid and specific.

Map the user journey for [user segment] solving [problem] with [product]. Include stages: Awareness | Consideration | Decision | Onboarding | Active Use | Retention | Advocacy. For each stage, detail: Jobs to be done | Pain points | Emotions | Touchpoints | Key moments of truth. Identify 3-5 areas for improvement with specific recommendations.

Write a complete PRD for [feature/product]. Include: Overview (1-2 paragraphs) | Goals & Success Metrics (3-5 metrics) | User Problems & Jobs to Be Done | Use Cases (2-3) | Requirements (functional & non-functional) | Design Principles | Timeline & Dependencies | Go-to-Market Plan | Success Criteria. Base this on: [user research findings]. Keep it concise but thorough (1500-2000 words max).

Define success metrics for [feature]. Goal: [product goal]. User impact: [expected user benefit]. Business impact: [expected business outcome]. For each metric, provide: Name & Definition | Why it matters | How to measure | Target value | Baseline | Leading vs Lagging indicator. Include 5-7 metrics covering user behavior, business, and quality. Format as a table with these columns.

Document 5-7 detailed use cases for [feature]. For each use case: Title | Actor | Preconditions | Main Success Scenario (step-by-step) | Alternative Flows | Edge Cases | Error States. Also list 3-5 edge cases that might break the feature and how to handle them gracefully. Format for engineering clarity.

Evaluate the technical feasibility of [feature]. Technical constraints: [constraints]. Current architecture: [tech stack]. Estimate: Effort (eng time) | Complexity (1-5) | Technical Risk (1-5) | Dependencies | Potential blockers. Propose 2 technical approaches with pros/cons. Recommend which approach based on tradeoffs. Flag any architectural changes needed.

Create a 1-page executive summary for [initiative/product]. Audience: [stakeholders]. Must include: Problem & Opportunity | Proposed Solution | Expected Impact | Investment Required | Timeline | Key Risks & Mitigations | Recommendation. Use data and specifics. Write for clarity, not length. Format for a one-page slide.

Create tailored messaging for [decision/announcement] for these stakeholders: [list]. For each stakeholder, create: Key Message (1 sentence) | Context & Why It Matters | Impact on Them | Call to Action. Anticipate 2-3 questions or concerns each stakeholder might raise and draft thoughtful responses. Keep tone professional but personable.

Draft a product update announcement for [feature release]. Audience: [users/customers]. Must include: What's New | Why We Built It | How It Works (simple explanation) | How Users Benefit | Timeline for Rollout. Write 2 versions: technical (for power users) and non-technical (for general users). Use concrete examples.

Prepare for a conversation about [difficult topic: delayed feature, deprioritized request, resource constraint] with [stakeholder]. Help me: Anticipate their concerns | Draft my opening statement | Prepare 3-4 responses to likely objections | Propose solutions or alternatives | Plan follow-up actions. Make it constructive, empathetic, and solution-focused.