Product Management AI Prompts for PMs (2026)

Senior product managers spend upwards of 15 hours each week generating documentation, structuring requirements, and synthesizing cross-functional feedback. Modern engineering workflows require concise problem definitions, testable acceptance criteria, and quantitative prioritization models before a single line of production code is written. Applying structured ai prompts for product managers transforms unstructured stakeholder notes into validated technical specifications while preserving engineering rigor.

Key Takeaways

• The 4-part prompt framework (Role, Context, Task, Format) reduces PRD drafting cycles by up to 80% while standardizing engineering requirements.
• Frontier reasoning models like Claude Sonnet 5 and GPT-5.6 Sol provide multi-factor synthesis across complex Kano, RICE, and Jobs-to-be-Done frameworks.
• Connecting customer feedback transcripts directly into structured prompt templates saves product teams an average of 5 to 9 hours weekly on administrative overhead.
• Enforcing strict edge-case detection and acceptance criteria in prompt outputs prevents expensive architectural rewrites during development sprints.

Structured product management ai prompts provide operational scaffolds rather than automated shortcuts. Senior PMs leverage these templates to enforce thoroughness, align cross-functional teams, and evaluate trade-offs systematically across discovery, delivery, and post-launch reviews. For an end-to-end lifecycle playbook, explore our 30 AI prompts for product managers covering discovery through post-launch review.

Why AI-Powered Product Management Works

Product management has always been document-intensive. A single product launch can require PRDs, user stories, OKRs, competitive analysis, user personas, journey maps, and countless other artifacts. Mastering ai product management allows technical leaders to eliminate repetitive drafting and spend more time on customer discovery.

Structured prompts change this fundamentally. The same product frameworks that senior PMs spend years mastering (Jobs-to-be-Done, Kano Model, RICE scoring) can be systematically applied using well-crafted prompts. Using dedicated prd ai prompts accelerates drafting while standardizing specifications across agile teams. Formulating quarterly goals with okr ai prompts aligns engineering milestones with revenue targets.

Quantitative engineering research underscores this efficiency shift. When teams implement structured contextual prompting, technical specifications achieve 40% to 60% reductions in documentation cycles while improving feature clarity and cross-functional alignment. Industry standards documented in the Anthropic Prompt Engineering Documentation demonstrate that explicit role definition and formatted output schemas dramatically reduce hallucinations in downstream technical outputs.

What makes these prompts different from generic AI requests is specificity. Every prompt below defines the role the AI should play, the framework to apply, the constraints to follow, and the output format required. For a broader view of how AI transforms business workflows, explore our guide on AI prompts for business analysts.

Strategic Planning Prompts

These prompts help you think through product strategy, positioning, and go-to-market planning.

1. Product Vision Generator

Purpose: Create compelling, actionable product visions that align teams and guide decision-making.

Use case: Annual planning, strategy offsites, board presentations

# Role
Chief Product Officer with experience at B2B SaaS companies

# Objective
Create a compelling product vision that inspires teams, aligns stakeholders, and provides a north star for product decisions over a 3-5 year horizon.

# Context
A product vision answers "what world are we building?" It should be ambitious enough to attract talent, specific enough to guide decisions, and differentiated enough to matter. The best visions are remembered, not just read.

# Output Format

### Vision Statement
[A single, memorable sentence capturing the future state]

### Strategic Pillars
| Pillar | Description | Why It Matters |
|--------|-------------|----------------|
| Pillar 1 | | |
| Pillar 2 | | |

### 3-Year Roadmap Themes
| Year | Theme | Key Initiatives | Success Metrics |
|------|-------|-----------------|-----------------|
| Year 1 | | | |
| Year 2 | | | |

### Competitive Differentiation
- How this vision differentiates from competitors
- Sustainable advantages we're building
- Unique capabilities required

## User Input
[PASTE YOUR CONTEXT]
- Current product state
- Market opportunities identified
- Competitive landscape
- Company mission and values
- Target customer segments
- Technology trends relevant

Customize it: Make it personal, your vision should reflect genuine organizational values, not generic platitudes.

2. Lean Canvas Generator

Purpose: Translate product ideas into testable business models using the Lean Canvas framework.

Use case: New product exploration, startup planning, pitch preparation

# Role
Product Strategist and Startup Advisor

# Objective
Create a comprehensive Lean Canvas that captures your business model, identifies risks early, and provides a framework for iteration.

# Context
The Lean Canvas (Ash Maurya) adapts Business Model Canvas for startups, focused on problems, solutions, unique value propositions, and unfair advantages. It's designed to be completed in 20 minutes and updated continuously.

# Output Format

### 1. Problem
- Top 3 problems identified
- How customers currently solve these problems
- Pain intensity for each problem

### 2. Customer Segments
- Target customer profile
- Early adopters characteristics
- Personas to validate with

### 3. Unique Value Proposition
- Clear statement of value
- Analogy or metaphor for non-experts
- Visual tagline if applicable

### 4. Solution
- Top 3 features to build
- What's NOT in scope initially
- MVP definition

### 5. Channels
- Acquisition channels to test
- Distribution strategy
- Partnership opportunities

### 6. Revenue Streams
- Revenue model
- Pricing strategy
- Unit economics overview

### 7. Cost Structure
- Key costs to track
- Fixed vs. variable
- Economies of scale path

### 8. Key Metrics
- One metric that matters (OMTM)
- Supporting metrics
- Targets for each

### 9. Unfair Advantage
- Sustainable barriers to entry
- Network effects
- Proprietary assets

## User Input
[PASTE YOUR PRODUCT IDEA]
- Problem you're solving
- Target customers
- Proposed solution
- Any existing validation

Customize it: Focus on what you don’t know, use the canvas to identify assumptions to test.

3. Market Sizing Calculator

Purpose: Quantify market opportunity using top-down and bottom-up approaches.

Use case: Investment analysis, strategic planning, board presentations

# Role
Market Analyst and Strategy Consultant

# Objective
Calculate Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) with transparent methodology.

# Context
Market sizing requires both top-down (industry data) and bottom-up (specific customers) approaches. The best analyses triangulate multiple methods and clearly document assumptions.

# Output Format

### 1. Top-Down Analysis
| Source | Market Size | Methodology | Year |
|--------|-------------|-------------|------|
| Industry report 1 | | | |
| Industry report 2 | | | |
| Analyst estimate | | | |

### 2. Bottom-Up Analysis
| Segment | Customers | Price/Unit | Revenue |
|---------|-----------|------------|---------|
| Segment 1 | | | |
| Segment 2 | | | |

### 3. Market Sizing Summary
| Market | Size | Notes |
|--------|------|-------|
| TAM | | Top-down composite |
| SAM | | Serviceable portion |
| SOM | | Realistic 5-year capture |

### 4. Growth Projections
| Year | SAM | SOM | Growth Rate |
|------|-----|-----|-------------|
| Year 1 | | | |
| Year 2 | | | |

### 5. Methodology Notes
- Data sources used
- Assumptions made
- Limitations acknowledged

## User Input
[PASTE YOUR MARKET DATA]
- Industry and segment
- Pricing model
- Target geography
- Competitor landscape
- Available research

Customize it: Document every assumption, market sizing is only useful if others can evaluate your methodology.

4. SWOT Analysis Assistant

Purpose: Conduct structured SWOT analysis to inform product strategy decisions.

Use case: Strategy planning, competitive review, portfolio analysis

# Role
Senior Product Strategist

# Objective
Conduct comprehensive SWOT analysis for the product, identifying strategic implications and actionable recommendations.

# Context
SWOT (Strengths, Weaknesses, Opportunities, Threats) provides a framework for understanding strategic position. The key is moving beyond lists to strategic implications.

# Output Format

### 1. Strengths
| Strength | Evidence | Sustainability | Strategic Implication |
|----------|----------|----------------|----------------------|
| | | | |

### 2. Weaknesses
| Weakness | Evidence | Impact | Mitigation Approach |
|----------|----------|--------|---------------------|
| | | | |

### 3. Opportunities
| Opportunity | Market Evidence | Timeframe | Capture Requirements |
|-------------|-----------------|-----------|---------------------|
| | | | |

### 4. Threats
| Threat | Likelihood | Impact | Response Strategy |
|--------|------------|--------|-------------------|
| | | | |

### 5. Strategic Implications
- Priority strengths to leverage
- Critical weaknesses to address
- Opportunities to pursue first
- Threats to mitigate

### 6. Action Recommendations
| Action | Addresses | Timeline | Success Metrics |
|--------|-----------|----------|-----------------|
| | | | |

## User Input
[PASTE YOUR ANALYSIS CONTEXT]
- Product and features
- Competitive position
- Market dynamics
- Customer feedback themes

Customize it: Focus on actionable insights, SWOT without recommendations is just an exercise.

5. Strategy Canvas Creator

Purpose: Visualize competitive positioning and identify blue ocean opportunities.

Use case: Competitive analysis, innovation planning, feature prioritization

# Role
Competitive Strategy Analyst

# Objective
Create a strategy canvas comparing your product against competitors across key buying factors to identify differentiation opportunities.

# Context
The Strategy Canvas (Blue Ocean Strategy) visualizes how products compete across factors that matter to customers. The goal is finding uncontested market space by eliminating, reducing, raising, and creating factors.

# Output Format

### 1. Key Buying Factors
| Factor | Why It Matters | Customer Priority |
|--------|----------------|-------------------|
| | | |

### 2. Strategy Canvas Visualization
| Factor | Your Product | Competitor A | Competitor B | Industry Avg |
|--------|--------------|--------------|--------------|--------------|
| Factor 1 | | | | |
| Factor 2 | | | | |

### 3. ERRC Grid Analysis

#### Eliminate
- Factors the industry takes for granted but don't add value

#### Reduce
- Factors below industry standard that can be reduced

#### Raise
- Factors above industry standard that can be raised

#### Create
- entirely new factors the industry has never offered

### 4. Differentiation Opportunities
- Unique positioning identified
- Blue ocean moves suggested
- Risk assessment

## User Input
[PASTE YOUR COMPETITIVE DATA]
- Key competitors
- Buying factors relevant to your market
- Your current positioning
- Customer feedback on priorities

Customize it: Include factors customers care about, not just features you have.

6. Build vs. Buy Advisor

Purpose: Structure build vs. buy decisions with clear criteria and recommendations.

Use case: Technology decisions, feature planning, vendor selection

# Role
Technical Product Manager with M&A experience

# Objective
Provide structured analysis for build vs. buy decisions, evaluating total cost, strategic value, and implementation risks.

# Context
Build vs. buy decisions have long-term implications. The right choice depends on strategic differentiation, total cost of ownership, time-to-market, and organizational capabilities.

# Output Format

### 1. Requirements Definition
| Requirement | Must Have | Should Have | Nice to Have |
|-------------|-----------|-------------|--------------|
| | | | |

### 2. Build Analysis
| Factor | Assessment | Cost/Impact |
|--------|------------|-------------|
| Development effort | | |
| Time to value | | |
| Ongoing maintenance | | |
| Required expertise | | |

### 3. Buy Analysis
| Factor | Assessment | Cost/Impact |
|--------|------------|-------------|
| License/maintenance | | |
| Implementation | | |
| Customization needs | | |
| Vendor stability | | |

### 4. Comparative Analysis
| Factor | Weight | Build Score | Buy Score | Notes |
|--------|--------|-------------|-----------|-------|
| Cost | | | | |
| Time | | | | |
| Strategic | | | | |
| Risk | | | | |

### 5. Recommendation
| Option | Score | Rationale | Risk Mitigation |
|--------|-------|-----------|-----------------|
| Build | | | |
| Buy | | | |

### 6. Implementation Considerations
- Integration requirements
- Migration path
- Fallback options

## User Input
[PASTE YOUR DECISION CONTEXT]
- Capability under consideration
- Available solutions
- Internal capabilities
- Timeline constraints
- Budget parameters

Customize it: Consider indirect costs, maintenance, training, and integration often exceed initial costs.

User Research Prompts

These prompts support user research, from planning interviews to analyzing feedback.

7. User Persona Architect

Purpose: Create data-driven user personas that inform product decisions.

Use case: Feature prioritization, marketing alignment, team communication

# Role
UX Researcher and Customer Insights Lead

# Objective
Create comprehensive user personas based on research data, behavioral patterns, and customer segments.

# Context
Personas should be based on evidence, not assumptions. The best personas capture goals, behaviors, and contexts, not just demographics.

# Output Format

### Persona Overview
| Element | Details |
|---------|---------|
| Name | Representative name |
| Role | Job title/function |
| Industry | Sector |
| Company size | Segment |
| Age range | Approximate |

### Demographics
- Background and experience
- Decision-making authority
- Technical sophistication

### Goals & Motivations
| Goal | Importance | Current Solution |
|------|------------|------------------|
| | | |

### Behaviors & Habits
- How they research solutions
- Evaluation criteria
- Purchase process
- Usage patterns

### Pain Points
| Pain | Severity | Current Workaround |
|------|----------|-------------------|
| | | |

### Quote
[Representative quote capturing their perspective]

### How to Reach
- Preferred channels
- Content they consume
- Communities they participate in

## User Input
[PASTE YOUR RESEARCH DATA]
- Customer interview summaries
- Support ticket themes
- Usage data patterns
- Sales team insights

Customize it: Validate personas with actual customers, the best feedback comes from people who match your personas.

8. Empathy Map Generator

Purpose: Build empathy maps to understand users at a deeper level.

Use case: User research synthesis, design thinking workshops, persona development

# Role
UX Design Lead and Customer Research Specialist

# Objective
Create comprehensive empathy maps that capture user thoughts, feelings, and contexts beyond surface-level understanding.

# Context
Empathy maps (XPLANE) go beyond personas to capture what users say, think, do, and feel. They help teams develop genuine user understanding.

# Output Format

### User Context
- Who this user is
- When they use the product
- Where they're located

### Saying
- Direct quotes from user research
- Keywords and phrases used
- Questions they ask

### Thinking
- What users think but may not say
- Concerns and doubts
- Aspirations and hopes

### Doing
- Behaviors observed
- Actions taken
- Workarounds discovered

### Feeling
- Emotions expressed
- Frustrations identified
- Delights discovered

### Pains
| Pain | Evidence | Impact |
|------|----------|--------|
| | | |

### Gains
| Gain | Evidence | Value |
|------|----------|-------|
| | | |

### Key Insights
- Surprising discoveries
- Design implications
- Research gaps to fill

## User Input
[PASTE YOUR RESEARCH NOTES]
- Customer interview transcripts
- Observation notes
- Support interaction summaries
- Survey results

Customize it: Include quotes verbatim, language patterns reveal more than summaries.

9. User Story Writer

Purpose: Convert requirements into well-structured user stories with clear acceptance criteria.

Use case: Sprint planning, development handoffs, backlog grooming

# Role
Agile Product Coach and Technical Writer

# Objective
Write clear, actionable user stories with specific acceptance criteria that enable development teams to build the right thing.

# Context
User stories follow the format: "As a [persona], I want [action], so that [benefit]." Good stories are small enough to deliver in a sprint and clear enough that developers don't need to ask clarifying questions.

# Output Format

### User Story Template
As a [persona],
I want to [action/feature],
So that [benefit/outcome].

### Acceptance Criteria
| Criteria | Given | When | Then |
|----------|-------|------|------|
| Primary flow | | | |
| Secondary flow | | | |
| Error handling | | | |
| Edge case | | | |

### Story Points Estimate
| Component | Complexity | Estimate |
|-----------|------------|----------|
| Core functionality | | |
| Error handling | | |
| Testing | | |
| **Total** | | |

### Dependencies
- Technical dependencies
- Cross-team dependencies
- External dependencies

### Related Artifacts
- Design links
- PRD sections
- Test cases

## User Input
[PASTE YOUR REQUIREMENTS]
- Feature or functionality description
- Target user persona
- Business outcomes expected
- Existing constraints
- Technical context

Customize it: Keep stories small, anything over 8 story points likely needs decomposition.

10. Interview Script Generator

Purpose: Create interview guides for user research and customer discovery.

Use case: User research, customer development, feedback collection

# Role
User Research Lead and Customer Development Specialist

# Objective
Design comprehensive interview guides that uncover user needs, pain points, and behaviors while building rapport with participants.

# Context
Good interviews balance structure with flexibility. The guide provides a framework, but skilled interviewers follow threads and adapt.

# Output Format

### Interview Overview
- Purpose of research
- Target participants
- Duration
- Key research questions

### Pre-Interview
| Element | Details |
|---------|---------|
| Screening criteria | |
| Scheduling template | |
| Consent script | |

### Opening (5 minutes)
- Welcome and purpose
- Confidentiality commitment
- Permission to record

### Warm-up (5 minutes)
| Question | Purpose |
|----------|---------|
| | |

### Core Questions (30 minutes)
| Question | Follow-up | Listen For |
|----------|-----------|------------|
| | | |
| | | |

### Scenario Probes (15 minutes)
| Scenario | Questions | Hypothesis |
|----------|-----------|------------|
| | | |

### Wrap-up (5 minutes)
- Key takeaways summary
- Additional comments
- Next steps and thank you

### Post-Interview
- Synthesis template
- Insights capture format
- Participant incentive process

## User Input
[PASTE YOUR RESEARCH GOALS]
- Research objectives
- Target user segments
- Key hypotheses to test
- Prior interview insights

Customize it: Pilot the script, first interviews always reveal questions that need refinement.

11. JTBD Analyzer

Purpose: Apply Jobs-to-be-Done framework to understand why customers hire your product.

Use case: Innovation planning, competitive analysis, churn prevention

# Role
Jobs-to-be-Done Researcher and Innovation Consultant

# Objective
Conduct comprehensive Jobs-to-be-Done analysis to understand the functional, emotional, and social jobs customers hire your product to do.

# Context
Jobs-to-be-Done (Tony Ulwick) focuses on progress customers want to make, not products or features. Understanding jobs reveals opportunities for innovation that customer feedback alone misses.

# Output Format

### Job Statement
**Job:** [Verb] [object] [context]

### Job Steps
| Step | Description | Importance |
|------|-------------|------------|
| 1. | | |
| 2. | | |

### Functional Jobs
| Job | Importance | Satisfaction | Opportunity |
|-----|------------|--------------|-------------|
| | | | |

### Emotional Jobs
| Job | Evidence | Impact on Loyalty |
|-----|----------|-------------------|
| | | |

### Social Jobs
| Job | Context | Social Drivers |
|-----|---------|----------------|
| | | |

### Outcome Statements
| Job | Desired Outcome | Current Solution |
|-----|-----------------|------------------|
| | | |

### Innovation Opportunities
- Underserved outcomes
- Overlooked jobs
- New contexts

## User Input
[PASTE YOUR CUSTOMER DATA]
- Customer interview transcripts
- Usage patterns observed
- Support ticket themes
- Competitor analysis

Customize it: Focus on outcomes, not features, the job is what customers accomplish, not what you build.

12. Survey Question Designer

Purpose: Design effective surveys that generate actionable customer feedback.

Use case: NPS surveys, feature research, customer satisfaction

# Role
Research Methodologist and Survey Designer

# Objective
Create survey instruments that yield high response rates and actionable insights while minimizing bias and respondent fatigue.

# Context
Good surveys balance completeness with brevity. Every question should inform a decision; remove questions that don't pass this test.

# Output Format

### Survey Overview
- Purpose
- Target respondents
- Target sample size
- Expected duration

### Screening Questions
| Question | Response Options | Logic |
|----------|-----------------|-------|
| | | |

### Core Questions
| Question | Type | Scale/Labels | Purpose |
|----------|------|--------------|---------|
| | | | |

### Demographics
| Question | Options | Notes |
|----------|---------|-------|
| | | |

### Open-Ended Questions
| Question | Purpose | Max Responses |
|----------|---------|---------------|
| | | |

### Survey Flow
1. [Question flow with logic]
2. [Branching rules]
3. [Skip patterns]

### Response Validation
- Attention checks
- Speed filters
- Quality indicators

## User Input
[PASTE YOUR RESEARCH OBJECTIVES]
- Decisions to inform
- Key hypotheses
- Target audience
- Available distribution channels

Customize it: Test surveys internally first, bias often hides in assumptions about how questions will be interpreted.

Planning & Prioritization Prompts

These prompts help you plan product work and prioritize what to build next.

13. OKR Drafter

Purpose: Create quarterly objectives and key results aligned with product strategy.

Use case: Quarterly planning, team alignment, performance tracking

# Role
Product Goal-Setting Specialist

# Objective
Create quarterly Objectives and Key Results that are ambitious, measurable, and aligned with organizational strategy.

# Context
OKRs (Objectives and Key Results) should be ambitious (70% achievement is a good quarter) and outcome-focused. The best OKRs inspire teams while providing clear accountability.

# Output Format

### Quarterly OKRs

#### Objective 1: [Inspiring Title]
**Theme:** {THEME}
**Why this matters:** {RATIONALE}

| Key Result | Target | Baseline | Owner |
|------------|--------|----------|-------|
| KR 1: | | | |
| KR 2: | | | |
| KR 3: | | | |

#### Objective 2: [Inspiring Title]
**Theme:** {THEME}
**Why this matters:** {RATIONALE}

| Key Result | Target | Baseline | Owner |
|------------|--------|----------|-------|
| KR 1: | | | |

#### Objective 3: [Inspiring Title]
**Theme:** {THEME}
**Why this matters:** {RATIONALE}

| Key Result | Target | Baseline | Owner |
|------------|--------|----------|-------|
| KR 1: | | | |

### Scoring Guide
| Score | Meaning | Color |
|-------|---------|-------|
| 100% | Fully achieved | Green |
| 70-99% | Mostly achieved | Yellow |
| 0-69% | Not achieved | Red |

### Timeline
| Milestone | Date | Status |
|-----------|------|--------|
| Kickoff | | ☐ |
| Check-in 1 | | ☐ |
| Check-in 2 | | ☐ |
| Retro | | ☐ |

## User Input
[PASTE YOUR PLANNING CONTEXT]
- Quarter and year
- Product area
- Current state assessment
- Goal state vision
- Strategic focus areas
- Historical performance

Customize it: Make objectives qualitative and KRs quantitative, this distinction is critical.

14. RICE Score Helper

Purpose: Apply RICE prioritization framework to score and rank feature requests.

Use case: Backlog prioritization, roadmap planning, stakeholder alignment

# Role
Product Prioritization Specialist

# Objective
Apply the RICE framework (Reach, Impact, Confidence, Effort) to score features objectively and enable data-driven prioritization.

# Context
RICE provides a numerical score for comparison: RICE = (Reach × Impact × Confidence) / Effort. The framework reduces politics and focuses decisions on expected value.

# Output Format

### Feature Scoring Template
| Feature | Reach | Impact | Confidence | Effort | RICE Score |
|---------|-------|--------|------------|--------|------------|
| Feature A | | | | | |
| Feature B | | | | | |

### Scoring Criteria Guide

#### Reach
| Scale | Definition | Example |
|-------|------------|---------|
| 100 | 100% of users | Core feature change |
| 75 | Majority | Major UI change |
| 50 | Many | Feature for common use case |
| 25 | Some | Feature for minority |
| 10 | Few | Niche feature |

#### Impact
| Scale | Definition | Example |
|-------|------------|---------|
| 3 | Massive | Transforms product value |
| 2 | High | Significantly improves experience |
| 1 | Medium | Noticeable improvement |
| 0.5 | Low | Minor improvement |
| 0.25 | Tiny | Negligible impact |

#### Confidence
| Scale | Definition |
|-------|------------|
| 100% | High confidence in data |
| 80% | Good data, some assumptions |
| 50% | Limited data, educated guesses |

#### Effort
| Scale | Definition | Months |
|-------|------------|--------|
| 12 | Large investment | 3+ months |
| 6 | Medium investment | 1-3 months |
| 3 | Small investment | 2-4 weeks |
| 1 | Minimal effort | <2 weeks |

### Prioritization Results
| Rank | Feature | RICE Score | Recommendation |
|------|---------|------------|----------------|
| 1 | | | |
| 2 | | | |

## User Input
[PASTE YOUR FEATURE LIST]
- Features or initiatives to score
- Current user base metrics
- Historical impact data
- Engineering estimates

Customize it: Calibrate scoring with your team, definitions of “Impact” vary by organization.

15. Kano Classifier

Purpose: Apply Kano Model to classify features by customer satisfaction impact.

Use case: Feature prioritization, customer research, roadmap planning

# Role
Customer Research Analyst and Product Strategist

# Objective
Classify features using the Kano Model to understand how different types of features impact customer satisfaction.

# Context
The Kano Model (Noriaki Kano) categorizes features into Basic, Performance, and Delighter categories. Understanding this helps prioritize investments for maximum satisfaction impact.

# Output Format

### Feature Assessment

#### Feature: [Name]
**Category:** Basic/Performance/Delighter

**Evaluation Questions:**
| Question | Response | Scoring |
|----------|----------|---------|
| Functional: How would you feel if this feature was present? | | |
| Dysfunctional: How would you feel if this feature was absent? | | |

**Kano Analysis:**
| Satisfaction if Present | Satisfaction if Absent | Category |
|------------------------|----------------------|----------|
| Like | Neutral | Attractive |
| Like | Dislike | One-Dimensional |
| Neutral | Dislike | Basic |
| Neutral | Neutral | Indifferent |

**Impact Assessment:**
| Dimension | Score | Notes |
|-----------|-------|-------|
| Customer Satisfaction | | |
| Differentiation | | |
| Competitive Necessity | | |

### Portfolio Summary
| Category | Count | % | Priority |
|----------|-------|---|----------|
| Basic | | | Must-have |
| Performance | | | Should-have |
| Delighter | | | Nice-to-have |

### Recommendations
- Basic features to maintain
- Performance features to optimize
- Delighters to innovate

## User Input
[PASTE YOUR FEATURE DATA]
- Features to classify
- Customer feedback themes
- Competitive analysis
- Market research

Customize it: Validate with customer research, Kano requires understanding actual customer reactions.

16. Moscow Sorter

Purpose: Apply MoSCoW prioritization to categorize features by importance.

Use case: Release planning, stakeholder alignment, MVP definition

# Role
Agile Product Coach and Release Planner

# Objective
Apply MoSCoW prioritization to categorize features and create clear scope definitions for releases.

# Context
MoSCoW (Must, Should, Could, Won't) provides a simple framework for prioritization. The key is discipline in categorization, everything can't be a Must.

# Output Format

### Feature Assessment

| Feature | Current Category | Proposed Category | Rationale |
|---------|-----------------|-------------------|-----------|
| | | | |

### Final Prioritization

#### Must Have
[Features that are non-negotiable]
- Criteria: Essential for release
- Rationale: [Why each is essential]

#### Should Have
[Important but not essential]
- Criteria: Significant impact if included
- Rationale: [Why each matters]

#### Could Have
[Nice to have if time permits]
- Criteria: Low impact or easy to add later
- Rationale: [Why each is deferrable]

#### Won't Have (This Time)
[Consciously de-scoped]
- Criteria: Out of scope or better later
- Rationale: [Why not now]
- Alternative: [When/if to revisit]

### MVP Definition
| Inclusion | Feature | Justification |
|-----------|---------|---------------|
| Yes/No | | |

### Scope Boundary
- What's included
- What's explicitly excluded
- Known scope risks

## User Input
[PASTE YOUR FEATURE BACKLOG]
- All features under consideration
- Dependencies and constraints
- Stakeholder priorities
- Resource constraints

Customize it: Challenge every Must, too many “must-haves” indicate unclear priorities.

17. KPI Success Metric Selector

Purpose: Define appropriate success metrics for product initiatives.

Use case: Goal setting, experiment design, performance tracking

# Role
Product Analytics Lead

# Objective
Define appropriate KPIs and success metrics for product initiatives that enable meaningful measurement and informed decision-making.

# Context
Good metrics are actionable, laggable (or leading appropriately), and connected to business outcomes. Vanity metrics that don't inform decisions should be avoided.

# Output Format

### Initiative Overview
- Product/feature
- Business objective
- Time horizon

### North Star Metric
| Element | Details |
|---------|---------|
| Primary metric | |
| Definition | |
| Current baseline | |
| Target | |
| Why this metric | |

### Secondary Metrics
| Metric | Type | Purpose | Target |
|--------|------|---------|--------|
| | Leading/Lagging | | |

### Counter Metrics (Risks)
| Metric | Risk | Mitigation |
|--------|------|------------|
| | | |

### Measurement Plan
| Data Source | Collection Method | Frequency |
|-------------|-------------------|-----------|
| | | |

### Analysis Cadence
| Review | Timing | Owner |
|--------|--------|-------|
| Daily standup | | |
| Weekly review | | |
| Monthly retro | | |

## User Input
[PASTE YOUR INITIATIVE]
- Product or feature
- Business outcomes expected
- Available data sources
- Historical baselines

Customize it: Start with outcomes, not metrics, work backward from what success looks like.

18. Trend Spotter

Purpose: Identify and analyze emerging trends relevant to your product strategy.

Use case: Strategic planning, innovation pipelines, competitive intelligence

# Role
Technology Trend Analyst and Innovation Strategist

# Objective
Scan the landscape for emerging trends and assess their relevance and timing for your product strategy.

# Context
Trend spotting requires balancing hype against real impact. The goal is identifying trends at the right time, not too early (before they materialize) and not too late (after competitors have moved).

# Output Format

### Trend Assessment Matrix
| Trend | Relevance Score | Time to Impact | Confidence |
|-------|----------------|----------------|------------|
| | | | |

### Trend Deep Dives

#### Trend: [Name]
**Category:** Technology/Market/Regulatory/Social

**Description:**
- What the trend is
- Why it's happening
- Evidence supporting it

**Impact Assessment:**
| Dimension | Impact | Rationale |
|-----------|--------|-----------|
| Product | | |
| Business Model | | |
| Competition | | |
| Customer Needs | | |

**Timing:**
- When it becomes relevant
- Warning signs to watch
- Decision points

**Recommended Response:**
- Monitor
- Experiment
- Plan
- Execute

## User Input
[PASTE YOUR STRATEGIC CONTEXT]
- Industry and market
- Product category
- Technology landscape
- Competitive position

Customize it: Track trends over time, hype cycles reveal patterns in adoption timing.

Documentation Prompts

These prompts help you create the documents that product teams need to ship.

19. PRD Generator

Purpose: Write comprehensive Product Requirements Documents that engineering can execute.

Use case: Development handoffs, stakeholder alignment, scope definition

# Role
Product Requirements Specialist

# Objective
Write comprehensive Product Requirements Documents that provide clear scope definition, business context, and actionable specifications for engineering teams.

# Context
Good PRDs balance completeness with readability. They answer "what" and "why" while leaving "how" to engineering. The best PRDs enable developers to make good decisions without constant clarification.

# Output Format

### PRD Template

# PRODUCT REQUIREMENTS DOCUMENT

## 1. Overview
| Field | Value |
|-------|-------|
| Title | |
| Status | Draft |
| Owner | |
| Target Release | |
| PR Version | 1.0 |

## 2. Problem Statement
**The Problem:**
[Clear problem description]

**Who It Affects:**
[User segments affected]

**Impact:**
[Cost of not solving]

**Evidence:**
[Data supporting the problem]

## 3. Goals & Success Metrics
**Primary Goal:**
[What success looks like]

**Success Metrics:**
| Metric | Baseline | Target |
|--------|----------|--------|
| | | |

## 4. User Stories
| ID | User Story | Acceptance Criteria |
|----|------------|---------------------|
| US-1 | | |
| US-2 | | |

## 5. Requirements
| ID | Description | Priority | Status |
|----|-------------|----------|--------|
| REQ-1 | | Must/Should/Could | |
| REQ-2 | | | |

## 6. Design
[Links to Figma, designs, flows]

## 7. Technical Considerations
[Architecture, data, integrations]

## 8. Dependencies
- [Dependency 1]
- [Dependency 2]

## 9. Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| | | |

## 10. Timeline
| Milestone | Date | Status |
|-----------|------|--------|
| Design complete | | |
| Dev start | | |
| QA complete | | |
| Launch | | |

## User Input
[PASTE YOUR PRODUCT CONTEXT]
- Feature or product description
- Problem being solved
- Target users
- Success criteria
- Available constraints

Customize it: Focus on outcomes, not solutions, let engineering innovate on implementation.

20. Elevator Pitch Refiner

Purpose: Distill product value into compelling, memorable pitches.

Use case: Investor presentations, stakeholder updates, hallway conversations

# Role
Brand Strategist and Pitch Coach

# Objective
Transform product descriptions into compelling elevator pitches that capture attention and communicate value in 30-60 seconds.

# Context
An elevator pitch should be memorable, specific, and compelling. It answers: "What do you do?" in a way that makes people want to learn more.

# Output Format

### Pitch Options

#### Option 1: [Approach]
For [target customer],
Who [problem or need],
[Product name] is a [category]
That [key benefit].
Unlike [competitor/alternative],
Our product [key differentiation].

#### Option 2: [Approach]
[Story-based hook]

#### Option 3: [Approach]
[Question-based hook]

### Pitch Components

#### Target Customer
[Who this appeals to]

#### Core Problem
[What pain you're addressing]

#### Solution Summary
[What you offer]

#### Key Benefit
[Primary value delivered]

#### Differentiation
[Why you're different]

### Delivery Tips
- Emphasis points
- Common questions to anticipate
- Follow-up hooks

## User Input
[PASTE YOUR PRODUCT INFO]
- What you build
- Who it's for
- Key value proposition
- Competitive advantages
- Common misconceptions

Customize it: Test pitches with strangers, the best pitch works for people who don’t know your space.

21. Value Proposition Designer

Purpose: Craft compelling value propositions that align with target segments.

Use case: Marketing alignment, sales enablement, positioning

# Role
Brand Strategist and Marketing Consultant

# Objective
Create value propositions that clearly communicate customer benefits and differentiate from alternatives.

# Context
Value propositions should answer: "Why should I buy from you?" They focus on customer benefits, not features, and specifically address what makes your solution better.

# Output Format

### Value Proposition Canvas

#### Customer Profile
**Jobs:**
- [Functional job]
- [Emotional job]
- [Social job]

**Pains:**
- [Pain 1]
- [Pain 2]

**Gains:**
- [Gain 1]
- [Gain 2]

#### Value Map
**Products & Services:**
- [Your offerings]

**Pain Relievers:**
- [How you address pains]

**Gain Creators:**
- [How you create gains]

### Value Proposition Statements

#### For [Segment 1]
[Segment description]

**Value Proposition:**
[Clear statement of value]

**Key Benefits:**
- [Benefit 1]
- [Benefit 2]

**Proof Points:**
- [Evidence 1]
- [Evidence 2]

#### For [Segment 2]
[Repeat structure]

### Differentiation
| Dimension | Us | Competitor A | Competitor B |
|-----------|----|--------------|--------------|
| Benefit 1 | | | |
| Benefit 2 | | | |

## User Input
[PASTE YOUR POSITIONING]
- Target segments
- Product features
- Customer benefits
- Competitive alternatives
- Proof points available

Customize it: Focus on customer language, not features you have, but outcomes they want.

22. Release Notes Writer

Purpose: Create release notes that inform and delight users.

Use case: Product launches, update communications, changelog management

# Role
Technical Writer and Customer Communications Lead

# Objective
Write release notes that clearly communicate what's new, why it matters, and how to get started, without overwhelming users.

# Context
Good release notes inform without overwhelming. They help users understand what's changed and why they should care, providing clear paths to value.

# Output Format

### Release Notes Template

# Release: [Version] - [Title]

**Release Date:** [Date]
**Theme:** [One-line summary]

## What's New

### Major Features
[Headline feature]
- Description: [What it does]
- Why it matters: [Customer benefit]
- Get started: [Link or brief instructions]

### Enhancements
[Improvement 1]
- Description and benefit

### Bug Fixes
- [Fix 1] - [Brief description]

## Additional Resources
- Documentation link
- Video walkthrough
- Feedback form

## Release Notes Format

### For New Features
## [Feature Name]
**What:** [Brief description]
**Why:** [Customer problem solved]
**How:** [Quick start steps]

**Screenshots:** [Links]

**Learn more:** [Documentation link]

### For Updates
## Improved [Feature]
**What's changed:** [Description]
**Why:** [Reason for change]
**Impact:** [User benefit]

### For Bug Fixes
## Fixed: [Issue Title]
**Problem:** [Brief description]
**Solution:** [What was done]
**Reported by:** [Community, customer, or internal]

## User Input
[PASTE YOUR RELEASE INFO]
- Version and date
- New features and improvements
- Bug fixes
- Deprecations
- Known issues

Customize it: Write from the user’s perspective, focus on what they can do, not what you built.

Specialized Analysis Prompts

These prompts support specific product management activities.

23. Churn Analysis Assistant

Purpose: Analyze churn signals and identify at-risk customers.

Use case: Retention planning, customer success, product improvement

# Role
Customer Retention Analyst

# Objective
Analyze churn indicators and provide actionable recommendations for retention.

# Context
Churn prevention requires understanding both quantitative signals and qualitative reasons. The goal is identifying at-risk customers early enough to intervene.

# Output Format

### Churn Signal Analysis

#### Behavioral Indicators
| Signal | Data Source | Threshold | Action |
|--------|-------------|-----------|--------|
| | | | |

#### Engagement Scorecard
| Dimension | Score | Trend | Concern Level |
|-----------|-------|-------|---------------|
| Usage frequency | | | |
| Feature adoption | | | |
| Support tickets | | | |
| Payment changes | | | |

### At-Risk Customer Profile
| Indicator | Evidence | Risk Level |
|-----------|----------|------------|
| | | High/Med/Low |

### Churn Reason Taxonomy
| Reason Category | Frequency | Prevention Options |
|-----------------|-----------|-------------------|
| | | |

### Retention Recommendations
| Customer Segment | Intervention | Expected Impact |
|------------------|--------------|-----------------|
| | | |

## User Input
[PASTE YOUR CHURN DATA]
- Churned customer patterns
- At-risk signals identified
- Retention initiatives tried
- Customer success resources

Customize it: Combine quantitative and qualitative data, patterns in support tickets often reveal churn reasons.

24. Competitor Feature Matrix

Purpose: Create structured competitive feature comparisons.

Use case: Competitive analysis, sales enablement, roadmap planning

# Role
Competitive Intelligence Analyst

# Objective
Build comprehensive competitive feature matrices that inform positioning and roadmap decisions.

# Context
Competitor analysis should inform, not dictate, product strategy. The goal is understanding gaps and opportunities, not just copying competitors.

# Output Format

### Feature Comparison Matrix
| Feature | Your Product | Competitor A | Competitor B | Winner |
|---------|--------------|--------------|--------------|--------|
| Feature 1 | | | | |
| Feature 2 | | | | |

### Deep Dive Analysis

#### Competitor: [Name]
**Strengths:**
- [Strength 1]
- [Strength 2]

**Weaknesses:**
- [Weakness 1]
- [Weakness 2]

**Recent Moves:**
- [Move 1] - [Implication]
- [Move 2] - [Implication]

### Gaps & Opportunities
| Gap | Competitor | Your Advantage | Action |
|-----|------------|----------------|--------|
| | | | |

### Win/Loss Analysis Summary
| Factor | Our Win Rate | Competitor Win Rate |
|--------|--------------|---------------------|
| | | |

## User Input
[PASTE YOUR COMPETITIVE DATA]
- Competitors to analyze
- Feature sets
- Recent competitive intelligence
- Win/loss data

Customize it: Focus on customer-mentioned factors, what sales teams hear matters most.

25. Churn Prevention Message

Purpose: Create personalized retention messages for at-risk customers.

Use case: Customer success, proactive outreach, retention campaigns

# Role
Customer Retention and Communications Specialist

# Objective
Generate personalized retention messages that address specific customer concerns while reinforcing value and building connection.

# Context
Churn prevention requires empathy and action. Messages should acknowledge concerns, reinforce value, and provide clear paths forward.

# Output Format

### Message Framework

#### Subject Line Options
- [Option 1 - Personalized]
- [Option 2 - Value-focused]
- [Option 3 - Relationship-based]

#### Message Template

Hi [Customer Name],

[EMPATHETIC OPENING - Acknowledge their situation]

I noticed [specific observation about their usage/engagement], and I wanted to reach out personally.

[VALUE REINFORCEMENT - Remind them of key benefits]

[SPECIFIC OFFER - Address likely concerns]

[ASK - Invite response]

[CLOSING - Appreciation and next steps]

Best,
[Account Manager Name]

### Message Variations

#### For Price Concerns
**Focus:** ROI and value
**Key points:**
- Total cost of switching
- Value delivered to date
- Flexible options available

#### For Usage Concerns
**Focus:** Getting started
**Key points:**
- Quick wins available
- Resources to help
- Personal assistance offer

#### For Feature Concerns
**Focus:** Product roadmap
**Key points:**
- Planned improvements
- Workarounds available
- Feedback channel

## User Input
[PASTE CUSTOMER CONTEXT]
- Customer name and history
- Engagement patterns
- Likely churn reason
- Available retention offers

Customize it: Personalize beyond the template, at-risk customers can tell when they receive form messages.

26. Event Tracking Planner

Purpose: Design event tracking strategies for product analytics.

Use case: Analytics implementation, measurement planning, data infrastructure

# Role
Product Analytics Architect

# Objective
Design comprehensive event tracking plans that enable meaningful product analysis and informed decision-making.

# Context
Good event tracking requires upfront planning. The goal is capturing user behavior data that informs decisions, not just collecting everything possible.

# Output Format

### Event Taxonomy

#### User Actions
| Event | Description | Properties | Trigger |
|-------|-------------|------------|---------|
| | | | |

#### System Events
| Event | Description | Properties | Source |
|-------|-------------|------------|--------|
| | | | |

### Event Definitions

#### [Event Name]
**Category:** User Action/System Event/Error

**Description:**
[What this event captures]

**Properties:**
| Property | Type | Required | Description |
|----------|------|----------|-------------|
| | | | |

**Trigger:**
[When this event fires]

**Use Cases:**
- [How this data will be used]

### Naming Conventions
| Category | Pattern | Example |
|----------|---------|---------|
| User actions | verb_noun | view_page |
| System events | system_noun | user_created |
| Errors | error_type | payment_failed |

### Quality Checklist
- [ ] Events documented before implementation
- [ ] Properties follow naming conventions
- [ ] Triggers are consistent
- [ ] Privacy requirements met
- [ ] Test coverage planned

## User Input
[PASTE YOUR ANALYTICS NEEDS]
- Key metrics to track
- User actions of interest
- Available tools
- Privacy constraints

Customize it: Start with decisions, not events, plan what you need to know before planning how to track it.

27. Feature Edge Case Brainstormer

Purpose: Identify edge cases and failure modes before development.

Use case: QA planning, PRD refinement, risk mitigation

# Role
QA Lead and Risk Analyst

# Objective
Brainstorm edge cases, failure modes, and boundary conditions to improve feature quality and reduce production issues.

# Context
Edge cases are where bugs hide. Proactively identifying them improves PRDs, speeds development, and reduces production incidents.

# Output Format

### Feature Overview
[One-sentence description]

### Happy Path
1. [Primary user flow]
2. [Expected outcome]

### Edge Cases by Category

#### Input Validation
| Edge Case | Expected Behavior | Priority |
|-----------|-------------------|----------|
| Empty input | | |
| Maximum length | | |
| Special characters | | |
| Invalid format | | |

#### State Variations
| Edge Case | Expected Behavior | Priority |
|-----------|-------------------|----------|
| No prior data | | |
| Concurrent users | | |
| Session timeout | | |
| Network interruption | | |

#### Error Scenarios
| Edge Case | Expected Behavior | Priority |
|-----------|-------------------|----------|
| API failure | | |
| Permission denied | | |
| Rate limiting | | |
| Service unavailable | | |

#### Boundary Conditions
| Edge Case | Expected Behavior | Priority |
|-----------|-------------------|----------|
| First/last items | | |
| Zero values | | |
| Maximum values | | |
| Time boundaries | | |

### Testing Recommendations
| Test Type | Coverage | Tools |
|-----------|----------|-------|
| | | |

### Known Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| | | | |

## User Input
[PASTE YOUR FEATURE]
- Feature description
- User flows
- Technical architecture
- Known risky areas

Customize it: Involve QA early, quality minds catch different edge cases than development minds.

Quick Reference: All Product Management Prompts

#	Prompt	Purpose	Use Case
1	Product Vision Generator	Create inspiring visions	Strategy planning
2	Lean Canvas Generator	Model business concepts	Startup planning
3	Market Sizing Calculator	Quantify opportunities	Investment analysis
4	SWOT Analysis Assistant	Strategic positioning	Competitive review
5	Strategy Canvas Creator	Visualize competition	Innovation planning
6	Build vs. Buy Advisor	Technology decisions	Procurement planning
7	User Persona Architect	Build data-driven personas	Team alignment
8	Empathy Map Generator	Deep user understanding	Research synthesis
9	User Story Writer	Create development-ready stories	Sprint planning
10	Interview Script Generator	Design research interviews	User research
11	JTBD Analyzer	Understand customer jobs	Innovation discovery
12	Survey Question Designer	Build effective surveys	Feedback collection
13	OKR Drafter	Create quarterly goals	Team alignment
14	RICE Score Helper	Prioritize objectively	Backlog management
15	Kano Classifier	Classify feature impact	Prioritization
16	MoSCoW Sorter	Categorize by importance	Scope definition
17	KPI Success Metric Selector	Define success measures	Goal setting
18	Trend Spotter	Identify emerging trends	Strategic planning
19	PRD Generator	Write requirements docs	Development handoffs
20	Elevator Pitch Refiner	Distill value propositions	Stakeholder comms
21	Value Proposition Designer	Craft value statements	Marketing alignment
22	Release Notes Writer	Communicate changes	Launch communications
23	Churn Analysis Assistant	Identify at-risk customers	Retention planning
24	Competitor Feature Matrix	Compare competitive features	Analysis
25	Churn Prevention Message	Create retention outreach	Customer success
26	Event Tracking Planner	Design analytics strategy	Measurement planning
27	Edge Case Brainstormer	Identify failure modes	Quality assurance

Common Mistakes (And How to Avoid Them)

Mistake #1: Vague User Stories

What it looks like:

“As a user, I want better search so I can find things.”

The fix:

“As a marketing manager, I want to filter search results by campaign date range and status, so I can quickly locate specific campaign assets during audits.”

Why it fails: Vague stories create vague requirements. Specificity enables development.

Mistake #2: Feature-Focused OKRs

What it looks like:

“KR: Launch feature X by Q2”

The fix:

“KR: Achieve 25% of daily active users adopting feature X, driving a 5% increase in core retention metrics.”

Why it fails: Feature launches are outputs; outcomes are what matter.

Mistake #3: Ignoring Edge Cases

What it looks like:

Building only the happy path

The fix:

Using the Edge Case Brainstormer to identify failure modes before coding begins

Why it fails: Edge cases are where real users live.

Implementing AI Prompts in Your Product Workflow

Integrating AI prompts into daily product operations requires structured team habits and clear governance. Teams achieve the greatest leverage when standardizing prompt libraries across Notion, Jira, and collaborative workspaces like Claude Projects or the OpenAI Python developer repository.

To scale these templates effectively, teams establish a centralized prompt repository reviewed during sprint retrospectives. Pairing procedural product specifications with operational routines from our operations AI prompts bridges the gap between high-level strategy and technical execution. Documenting evaluation standards from the GPT-4 Technical Report on arXiv ensures that prompt outputs maintain consistent qualitative benchmarks across distributed engineering teams.

Frequently Asked Questions

How do product managers balance AI prompts with product judgment?

Product managers use AI prompts to accelerate analytical structure, edge-case discovery, and draft formatting. Final decisions regarding strategic alignment, customer empathy, and roadmap prioritization remain strictly with human product leadership.

What are the best AI models for product management workflows?

Frontier models such as Claude Sonnet 5 and GPT-5.6 Sol offer superior multi-turn reasoning for complex frameworks like Kano and RICE scoring. Smaller edge models often omit edge cases in nuanced multi-variable feature dependencies.

How should product teams handle sensitive customer data in AI prompts?

Teams must sanitize proprietary customer data by stripping personally identifiable information before prompting commercial language models. Enterprise agreements with zero-data-retention guarantees or self-hosted models provide necessary compliance for sensitive user interview logs.

How do structured prompts improve cross-functional alignment with engineering?

Structured prompts generate explicit user stories, testable acceptance criteria, and documented constraints that engineers can translate immediately into technical tasks. This rigorous format eliminates ambiguity and minimizes rework across development cycles.