Prompts for Work

15 AI Prompts to Supercharge Your Product Management Workflow

October 6, 2025

Product Management is a discipline of relentless context-switching. One moment you're deep in user data, the next you're defining a long-term strategy, and minutes later you're refining a user story with engineering. The cognitive load is immense, and the risk of getting bogged down in documentation and administrative tasks is high, stealing time away from the deep strategic thinking that drives real product innovation. Imagine having a co-pilot to help you structure your thoughts, generate first drafts, and analyze feedback. AI tools like ChatGPT are exactly that. By leveraging the right prompts, you can offload the rote work and amplify your strategic impact. This guide offers 15 essential prompts designed to serve as your product management toolkit, covering every phase of the product development lifecycle.

Phase 1: Discovery & Strategy

Before a single line of code is written, you need a deep understanding of your users, your market, and your vision. These prompts help you build a solid strategic foundation.

1. The Detailed User Persona Creator

Building without a clear user in mind leads to products that serve no one well. This prompt helps you create rich, detailed user personas that serve as a north star for your entire team, fostering empathy and user-centric decision-making.

Act as a Senior UX Researcher. Create 2-3 detailed user personas for a product that [briefly describe your product]. The target audience is [describe your target audience]. For each persona, create a profile including:
- **Name and Photo Descriptor:**
- **Demographics:** (Age, Location, Occupation, Income)
- **Goals:** (What are they trying to achieve in relation to your product?)
- **Pain Points & Frustrations:** (What challenges do they face that your product can solve?)
- **Motivations:** (What drives their decisions? e.g., 'Wants to save time', 'Needs to look professional').
- **A brief narrative/bio:** (A short paragraph describing a day in their life).
    

2. The Competitive Analysis Framework

Understanding the competitive landscape is crucial for differentiation and identifying market gaps. This prompt uses a classic SWOT framework to provide a structured analysis of your competitors' positioning.

Act as a Product Strategist. Conduct a competitive analysis for my product, [Your product name or description]. Our main competitors are [Competitor 1], [Competitor 2], and [Competitor 3].

For each competitor, create a SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) in a markdown table. After the tables, provide a summary of key strategic insights and potential differentiation opportunities for my product.
    

3. The Product Vision and Mission Statement Generator

A compelling vision statement inspires your team and aligns stakeholders. It's the 'why' behind your product. This prompt helps you distill your product's purpose into a powerful and memorable statement.

Act as a Product Leader. I need help crafting a vision and mission for a new product. 

- **Product:** [Describe the product, what it does, and who it's for].
- **Problem it solves:** [Describe the core customer problem].
- **Desired future state:** [Describe the ideal world/outcome the product creates].

Based on this, generate:
1.  **A Product Vision Statement:** An aspirational, long-term statement about the future you are trying to create.
2.  **A Product Mission Statement:** A more concrete, present-day statement about how you will achieve that vision.
    

4. The Strategic Product Roadmap Themes

A good roadmap is more than a list of features; it's a statement of strategic intent. This prompt helps you brainstorm high-level themes that connect your team's work to broader business objectives.

Act as a Head of Product. My company's strategic goals for the next [timeframe, e.g., 6 months] are:
1. [Goal 1, e.g., Increase user retention by 15%]
2. [Goal 2, e.g., Expand into the enterprise market]
3. [Goal 3, e.g., Improve operational efficiency]

For my product, a [product description], brainstorm 2-3 potential product roadmap 'themes' or 'initiatives' for each of these goals. A theme is a high-level user problem to solve, not a specific feature. For each theme, provide a brief description of the user problem and how solving it supports the company goal.
    

Phase 2: Planning & Definition

With a strategy in place, it's time to translate it into actionable plans. These prompts streamline the creation of core product documents and help you make tough prioritization calls.

5. The User Story and Acceptance Criteria Writer

Clear user stories are the building blocks of development, ensuring the engineering team knows what to build and why. This prompt generates well-formed stories and crucial acceptance criteria to prevent ambiguity.

Synergy Tip: Use the goals and pain points from the User Persona prompt (#1) as direct input here to write highly empathetic and relevant user stories.

Act as an Agile Product Owner. I need to write user stories for a new feature. 

**Feature:** [Describe the feature, e.g., 'A user profile page'].
**User Persona:** [Describe the primary user, e.g., 'A new user named Jane who wants to customize her experience'].

Generate 3-5 user stories related to this feature. Each story must follow the format: 'As a [persona], I want to [action], so that [benefit].'

For each user story, also write 3-5 clear and testable Acceptance Criteria using the 'Given-When-Then' format.
    

6. The Feature Prioritization Assistant (RICE)

Not all features are created equal. Prioritization is a PM's most critical and difficult job. This prompt acts as a sounding board, applying the RICE framework to help you make objective, data-informed decisions.

Act as a Senior Product Manager. I need help prioritizing a list of potential features using the RICE scoring model (Reach, Impact, Confidence, Effort). 

**My features are:**
- Feature A: [Description]
- Feature B: [Description]
- Feature C: [Description]

For each feature, walk me through the RICE scoring. Ask me clarifying questions to estimate each variable (e.g., 'For Reach, how many users would this feature affect in a typical month?'). Then, present the final scores and a recommended prioritization order in a markdown table.
    

7. The Product Requirements Document (PRD) Outliner

A good PRD is the single source of truth for a feature. Starting with a blank page is intimidating. This prompt generates a comprehensive PRD template, ensuring you don't miss any critical sections.

Act as a Principal Product Manager. Generate a comprehensive outline for a Product Requirements Document (PRD) for a new feature. The outline should be detailed and serve as a template for me to fill in.

Include the following major sections, with bullet points for key content within each section:
1.  **Overview** (Problem Statement, Vision, Goals/Objectives, KPIs)
2.  **User Personas & Stories**
3.  **Features & Functionality** (Detailed breakdown of requirements)
4.  **Design & UX Requirements** (Mockups, user flow)
5.  **Technical Requirements** (Dependencies, constraints)
6.  **Future Work & Out of Scope**
7.  **Go-to-Market Plan**
    

8. The North Star Metric Brainstormer

Your North Star Metric (NSM) is the one metric that best captures the core value your product delivers to customers. This prompt helps you brainstorm potential NSMs to align your team around a single, crucial goal.

Act as a Growth Product Manager. I need to define a North Star Metric (NSM) for my product.

- **Product:** [e.g., A B2B project management tool, a meditation app, an e-commerce marketplace]
- **Core Value Proposition:** [e.g., 'Helps teams complete projects faster', 'Helps users reduce stress', 'Helps buyers find unique goods']

Brainstorm 3-5 potential North Star Metrics for this product. For each potential NSM, explain:
- Why it reflects the core value delivered to users.
- How it ties to long-term business success (e.g., revenue).
- A potential downside or risk of focusing too heavily on it.
    

Phase 3: Execution & Launch

As your product comes to life, the focus shifts to testing, communication, and a successful launch. These prompts help you prepare for market entry and continuous improvement.

9. The A/B Test Hypothesis Generator

Data-driven iteration is key to growth. A good A/B test starts with a strong hypothesis. This prompt helps you brainstorm meaningful test ideas aimed at improving a specific user behavior or metric.

Act as a Conversion Rate Optimization (CRO) Specialist. I want to improve a key metric for my product.

- **Page/Screen:** [e.g., The signup page, the checkout flow, the main dashboard]
- **Metric to Improve:** [e.g., Conversion rate, user engagement, average order value]

Generate 3-5 A/B test ideas to improve this metric. For each idea, formulate a clear hypothesis using the format: 'By [making this change], we believe [this user group] will [do this desired action], because [this reason]. We will measure this by [this specific metric].'
    

10. The User-Friendly Release Notes Writer

Release notes are a crucial touchpoint with your users, but they're often dry and technical. This prompt helps you draft clear, concise, and benefit-oriented release notes that get users excited about what's new.

Act as a Product Marketing Manager. I need to write release notes for our latest product update. The tone should be user-friendly, clear, and focused on benefits.

**New Features/Fixes:**
- [Feature 1: Briefly describe the technical change]
- [Feature 2: Briefly describe the technical change]
- [Bug Fix: Briefly describe the fix]

Draft the release notes. For each item, give it a clear heading and explain the user benefit (the 'so what?') rather than just the technical change. Start with a friendly opening and end with a call to action (e.g., 'Let us know what you think!').
    

11. The Go-to-Market (GTM) Strategy Outliner

A great product with a poor launch strategy will fail. This prompt provides a comprehensive checklist and outline for your GTM plan, ensuring all cross-functional teams (marketing, sales, support) are aligned.

Act as a Product Marketing Manager. Create a go-to-market (GTM) strategy outline for the launch of a new product: [Product Name/Description]. 

Generate a checklist or outline covering these key areas:
1.  **Target Audience & Positioning:** (Who are we selling to? What is our key message?)
2.  **Launch Goals:** (What are the specific success metrics? e.g., sign-ups, revenue).
3.  **Pricing & Packaging:**
4.  **Marketing & Communications Plan:** (Channels, timeline, content).
5.  **Sales Enablement:** (Training materials, talking points for the sales team).
6.  **Customer Support Readiness:** (FAQs, support staff training).
7.  **Launch Timeline:** (Key milestones and dates).
    

Phase 4: Iteration & Growth

The launch is just the beginning. The final set of prompts helps you analyze user feedback, make data-driven decisions about existing features, and understand why users leave.

12. The User Feedback Categorizer

Raw user feedback from support tickets, app reviews, and surveys is a goldmine of insight, but it's messy. This prompt acts as an initial analysis engine, grouping unstructured feedback into actionable themes.

Act as a Product Analyst. I have a collection of raw, unstructured user feedback. Your task is to perform a thematic analysis. Read the feedback below and categorize each piece of feedback into one of the following buckets: 'Bug Report', 'Feature Request', 'Usability Issue', 'Pricing/Billing', or 'General Praise'.

After categorizing, provide a summary of the top 3 most common themes.

**User Feedback:**
"""
[Paste up to 10-15 pieces of raw user feedback here. For example: 'The app crashes when I upload a photo.', 'I wish I could export to PDF.', 'The save button is hard to find.']
"""
    

13. The 'Kill, Keep, or Improve' Feature Analyst

Not every feature is a winner. Deciding what to do with a low-usage feature is tough. This prompt provides a structured framework to help you make a data-informed decision to either sunset, maintain, or reinvest in a feature.

Act as a data-driven Product Manager. I need to decide what to do with an underperforming feature in my product.

- **Feature:** [Feature Name and brief description]
- **Usage Data:** [e.g., 'Used by only 2% of monthly active users']
- **Original Goal:** [e.g., 'To increase user engagement']
- **Maintenance Cost:** [e.g., 'High, it has many dependencies']

Provide a structured analysis to help me decide whether to 'Kill' (remove), 'Keep' (maintain as-is), or 'Improve' (reinvest in) this feature. Walk me through key questions I should answer, such as the impact on the users who DO use it, the strategic alignment, and the opportunity cost of improving it vs. building something new.
    

14. The Customer Churn Survey Designer

Understanding why customers churn is critical for improving retention. This prompt helps you design a short, effective survey to send to users who have canceled, aiming to uncover the root causes.

Act as a UX Researcher specializing in retention. Design a short, effective churn survey to understand why users are canceling their subscription to my [Product Type, e.g., 'SaaS Project Management Tool'].

The survey should:
1.  Start with a multiple-choice question to categorize the main reason for leaving (e.g., 'It's too expensive', 'I'm not using it enough', 'I switched to another product', 'It's missing a feature I need').
2.  If they select 'switched to another product', ask a follow-up: 'Which product did you switch to?'.
3.  If they select 'missing a feature', ask a follow-up: 'What feature was that?'.
4.  End with one open-ended question: 'Is there anything we could have done to keep you as a customer?'.

Keep the survey brief to maximize the response rate.
    

15. The 'Working Backwards' Press Release

Inspired by Amazon, the practice of writing a press release for a feature before you build it forces you to focus on the customer benefit. This prompt helps you draft that future-state press release to clarify your thinking and build excitement.

Act as a visionary Product Manager using Amazon's 'Working Backwards' method. I have an idea for a new feature or product: [Describe the product/feature idea].

Your task is to write a future-state internal press release, dated one year from today, announcing the successful launch of this product. The press release should be one page long and include:
- **Headline:** A compelling, customer-benefit-oriented title.
- **Sub-Headline:** Summarizes the announcement.
- **Dateline:** City, State, and future date.
- **Introduction:** Briefly introduces the product and its main benefit.
- **Problem & Solution:** Clearly describes the customer problem and how this product solves it.
- **Quote from a Leader:** An inspiring quote from a fictional team leader.
- **Customer Quote:** A quote from a fictional happy customer.
- **Call to Action:** How customers can get started.
    

From Idea to PRD: A Product Planning Workflow

See how you can chain these prompts together for a seamless workflow:

  1. Begin your discovery process with prompt #1 to create detailed User Personas for your target audience.
  2. With your personas in mind, use prompt #5 to brainstorm a backlog of empathetic User Stories.
  3. Take your list of potential stories and features to prompt #6 to apply the RICE framework and prioritize what to build next.
  4. Once you have a high-priority feature, use prompt #7 to instantly generate a comprehensive PRD outline, giving you a structured document ready to be filled in.

Conclusion

These 15 prompts are not about replacing the critical thinking, creativity, and customer empathy that define great product management. Instead, they are about augmenting those skills. They act as a catalyst for your ideas, a structure for your documents, and a framework for your analysis. By integrating them into your workflow, you can reduce the time spent on mundane tasks and maximize the time spent on what truly matters: talking to users and building products they love. Start experimenting, adapt them to your needs, and unlock a new level of productivity and strategic focus.