As a Product Manager, you’re always looking for an edge – a better way to understand your users, craft compelling strategies, or communicate your vision more effectively. You’ve probably heard about ChatGPT, and maybe you’ve even dabbled with it. But are you unlocking its full potential to supercharge your PM tasks?
The secret isn’t just using ChatGPT; it’s guiding it with precision. The quality of its output is directly tied to the quality of your input. That’s where this guide steps in.
We’ve curated a comprehensive collection of prompts specifically for Product Managers. They’re practical templates you can use immediately to tackle real-world product challenges. With clear placeholders [in_brackets]
, you can tailor each prompt to your unique situation, transforming ChatGPT from a curious novelty into a powerful productivity partner.
If you’re ready to move beyond basic queries and tap into a new level of efficiency and insight for your product work, you’re in the right place. Let’s explore how to make ChatGPT work harder for you.
Remember these general tips for all prompts:
- Provide Context: The more background you give, the better the output.
- Be Specific: Vague questions lead to vague answers.
- Iterate: Ask follow-up questions to refine the results.
- Define the Persona (Optional but helpful): “Act as an experienced Product Manager specializing in [e.g., B2B SaaS, e-commerce, mobile gaming].”
- Specify Format (Optional): “Provide the answer in bullet points,” “Create a table,” “Write this as a draft email.”
I. User & Market Understanding
- Persona Development:
Create[Number]
detailed customer personas for[product name]
targeting[target market segment]
. Based on this data:[provide key demographics behaviors needs pain points and goals]
. Each persona should include: a name, background, goals, pain points/frustrations, motivations, tech savviness, and how[product name]
helps them solve[specific problem]
. - User Interview Questions:
Suggest[Number]
open-ended interview questions to uncover unmet needs and pain points of[target user segment]
regarding[problem area or task]
for our[product category, e.g., project management tool]
. - Job-to-be-Done (JTBD) Framing:
Help me frame the Job-to-be-Done for users of[product type or competitor product]
. What is the primary ‘job’[target audience]
is ‘hiring’ this product to do, considering their situation when they encounter[specific problem]
and their desired outcome[desired functional and emotional outcome]
? - Market & Trend Analysis:
Analyze current market trends in the[industry/sector]
relevant to[product type or problem domain]
. Identify the top[Number]
trends, their potential impact on products like[our product name or category]
, and suggest[Number]
opportunities for innovation. - Emerging Technology Assessment:
Provide a summary of emerging technologies like[specific technology 1]
and[specific technology 2]
and their potential applications or threats to[our product/industry]
. - Detailed Competitive Comparison:
Compare[our product name]
with[competitor product 1]
and[competitor product 2]
focusing on: key features, target audience, pricing, unique selling propositions, user experience, and marketing strategies. Identify[our product name]
‘s key differentiators and[Number]
areas for improvement. - Competitive Feature Gap Analysis:
Identify[Number]
key features that[Competitor A name]
offers for their[competitor product name]
which our[our product name]
currently lacks, and explain the potential impact on[target user segment]
. - TAM/SAM/SOM Estimation Brainstorm:
Suggest data sources and a methodology to estimate the Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for a[new product concept]
targeting[specific user segment]
in the[geographic region]
market solving[problem to be solved]
.
II. Product Strategy & Vision
- Product Vision Statement:
Help draft a compelling product vision statement for a[product type or description, e.g., mobile app for local volunteering]
that aims to solve[core user problem]
for[target audience]
. It should be inspiring, long-term, and guide future development. - Product Mission Statement:
Generate[Number]
mission statement options for[product name]
that clearly articulate its purpose, what it does, who it serves, and its unique value in the present. - Value Proposition Crafting:
Help me craft a clear value proposition for[product/feature name]
. It should articulate the unique benefit for[target customer segment]
, how it solves[customer pain point]
, and why it’s better than[alternative solutions or competitors]
. - SWOT Analysis:
Conduct a SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) for our[product/service name]
given its current state ([brief product description and maturity]
) in the[market name]
market, considering competitors like[competitor 1 name]
and[competitor 2 name]
, and key internal factors like[internal factor 1]
and external factors like[external factor 1]
. - Strategic Pillar Identification:
Based on our company goal of[company goal, e.g., increasing market share by X%]
and product vision[product vision statement]
, suggest[Number]
strategic pillars for our[product name]
for the next[timeframe, e.g., 12-18 months]
. - Business Model Canvas (BMC) Elements:
For a[product idea, e.g., subscription box for artisanal coffee]
, help me brainstorm key elements for the Business Model Canvas, specifically for: Value Propositions, Customer Segments, Channels, Customer Relationships, Key Activities, Key Resources, Key Partners, Cost Structure, and Revenue Streams. - “How Might We” Questions for Strategy:
Generate[Number]
‘How Might We’ questions to explore strategic opportunities for[product name]
to address[challenge or opportunity, e.g., user churn]
for[target user segment]
.
III. Ideation & Validation
- New Product Concept Brainstorming:
Generate[Number]
innovative product concepts that leverage[specific technology/trend, e.g., AI, sustainability]
to solve[specific customer problem]
for[target demographic]
in the[industry name]
sector. - Feature Brainstorming for Existing Product:
Suggest[Number]
unique feature ideas for[existing product name]
that could enhance[specific user experience aspect, e.g., user engagement, efficiency]
for[target user segment]
based on[observed pain point or need or user feedback theme]
. - Idea Validation & Feedback Simulation:
Evaluate the product/feature concept:[describe product/feature concept including key functionalities and target audience]
. Simulate potential positive and negative user reactions, provide feedback on its viability, list[Number]
potential challenges, and highlight its unique selling points. - Pros & Cons Evaluation:
What are the potential pros and cons of introducing a feature like[describe feature]
into our[product name]
for[target audience]
? - Minimum Viable Product (MVP) Definition:
For a new product concept[product concept description]
aimed at solving[core problem]
for[early adopter segment]
, what are the absolute core features needed for an MVP to test our primary hypothesis:[key hypothesis to test]
?
IV. Planning & Roadmapping
- Roadmap Development:
Outline a[timeframe, e.g., 6-month, 1-year]
product roadmap for[product name]
. Include key strategic themes (e.g.,[Theme 1]
,[Theme 2]
), major features/initiatives under each, target outcomes/metrics for each, and potential dependencies. Our primary business goals for this period are[goal 1]
and[goal 2]
. - Milestone Identification:
Identify key milestones for the development and launch of[product name or major feature]
from concept to post-launch, focusing on[specific area like market entry or feature set completion]
. - Epic Definition & Breakdown:
Define an Epic for[new major feature, e.g., 'User Profile Management']
in[product name]
. Describe its overall goal and benefits. Then, break this epic down into[Number]
smaller, actionable user stories with clear acceptance criteria. - User Story Writing:
Write[Number]
user stories for the feature[feature name]
which allows[target user type]
to[achieve a goal]
so that[reason/benefit]
. Include[Number]
acceptance criteria for each. - Acceptance Criteria Generation:
Given the user story: ‘As a[user type]
, I want to[action]
, so that[benefit]
‘, list[Number]
potential acceptance criteria that would confirm this story is successfully implemented. - PRD/Specification Outline:
Create a comprehensive outline for a Product Requirements Document (PRD) or feature specification for a new feature:[feature name]
for[product name]
. Include sections for: Introduction (Problem, Proposed Solution), Goals & Objectives, Success Metrics, Target Audience, User Stories/Requirements, Design Considerations, Technical Considerations, Release Plan, Future Iterations, and Out of Scope. - Understanding Prioritization Frameworks:
Explain how to use the[RICE/MoSCoW/Value vs Effort]
prioritization framework. What are the key components of this framework, and what questions should I ask the team to effectively score features like[Feature A description]
and[Feature B description]
for[product name]
? - Prioritization Framework Application:
I have the following features:- Feature A:
[Description of Feature A]
, Estimated Effort:[e.g., High/Medium/Low or Story Points]
, Potential Impact/Value:[e.g., High/Medium/Low or Revenue Projection or Strategic Alignment Score]
- Feature B:
[Description of Feature B]
, Estimated Effort:[...]
, Potential Impact/Value:[...]
- Feature C:
[Description of Feature C]
, Estimated Effort:[...]
, Potential Impact/Value:[...]
Help me prioritize these features for
[product name]
using the[RICE/ICE/MoSCoW/Value vs Effort]
framework. Show the scoring and explain the resulting order. - Feature A:
V. Design & Development Support
- User Flow Design:
Describe a detailed user flow for a[user persona name or type]
trying to achieve[specific goal, e.g., 'complete a purchase of X item']
using[product name]
. List all steps, decision points, and potential error states. - User Scenario Generation:
Generate[Number]
user scenarios for the[specific feature]
of[product name]
, detailing the user’s context ([e.g., on mobile, commuting]
), motivation ([e.g., needs to quickly find X]
), and expected outcome after using the feature. - A/B Test Design & Hypothesis:
Help design an A/B test for[product name]
to compare[Variation A description, e.g., 'current homepage design']
with[Variation B description, e.g., 'new homepage design with a prominent CTA for X']
. What is a clear hypothesis? What key metrics (e.g., conversion rate, click-through rate, bounce rate) should we track? Who is the target segment for this test, and what is the recommended duration? - UI/UX Copy & Microcopy:
Generate UI text components (e.g., button labels for[action 1]
and[action 2]
, menu items for[section A]
and[section B]
, tooltips for[complex element]
, empty state messages for[empty state scenario]
, error messages for[error scenario]
) for the[specific screen/flow, e.g., 'user registration process']
of[product name]
. The product is designed for[target audience]
to achieve[user goal]
. The tone should be[desired tone, e.g., friendly and encouraging, professional and concise]
.
VI. Go-to-Market & Launch
- Go-to-Market Strategy Outline:
Outline a go-to-market strategy for the launch of[new product or feature name]
targeting[target audience segment]
. Include sections for: Product Readiness, Key Messaging Themes ([Theme 1]
,[Theme 2]
), Recommended Marketing Channels (e.g.,[channel 1]
,[channel 2]
), Pre-launch Activities, Launch Activities, Post-launch Engagement Tactics, Sales Enablement Plan, and Customer Support Plan. - Product Descriptions & Marketing Copy:
Craft[Number]
compelling product description options for[product name]
, a[product category or type]
. Key features are:[feature 1 with benefit]
,[feature 2 with benefit]
. The target audience is[target audience description]
, and the unique benefit it offers is[unique benefit statement]
. The desired tone is[tone, e.g., exciting, trustworthy, simple]
. - Crafting Release Notes:
Draft engaging release notes for version[version number]
of[product name]
. Highlight the key new features:[Feature A name and brief benefit]
,[Feature B name and brief benefit]
, major improvements like[Improvement 1 description]
, and important bug fixes:[Bug fix 1 description]
. The tone should be[desired tone, e.g., enthusiastic and user-focused]
and include a call to action:[CTA, e.g., 'Try it out now!']
. - Press Release Draft:
Draft a press release announcing the launch of[product name or significant feature]
. Highlight its key features:[feature 1]
,[feature 2]
; unique benefits:[benefit 1]
; target audience:[target audience]
; and availability:[date/platform]
. Include a compelling headline, a brief company overview, and a quote from[spokesperson title and name, e.g., CEO, Jane Doe]
. - Social Media Launch Announcement:
Compose an engaging social media post for[platform, e.g., LinkedIn, Twitter, Instagram]
announcing the new[feature/product name]
. Emphasize[key benefit for users]
for[target audience]
. Include relevant hashtags like[#hashtag1]
,[#hashtag2]
, an image/video suggestion:[image description]
, and a clear call to action:[CTA, e.g., 'Learn more here: [link]']
.
- Effectively take your product to market with strategies developed using our Prompts for Marketing.
VII. Post-Launch, Measurement & Iteration
- Defining Success Metrics/KPIs:
For the new feature[feature name]
(or product[product name]
) which aims to achieve[primary goal of feature/product, e.g., increase user engagement]
, identify[Number]
Key Performance Indicators (KPIs) to track its success. Our overarching business goals are[business goal 1]
and[business goal 2]
. For each KPI, explain why it’s important, suggest how it could be measured, and define a target. - User Feedback Analysis & Synthesis:
Analyze the following user feedback for[product name or feature]
from[source, e.g., survey responses batch 1, app store reviews for May, support tickets about X]
:[Paste or summarize feedback snippet 1]
[Paste or summarize feedback snippet 2]
[Paste or summarize feedback snippet 3 (add more as needed)]
Identify the top
[Number]
key themes, common pain points, notable feature requests, and overall sentiment. Suggest[Number]
actionable product improvements based on this analysis. - Product Performance Data Analysis:
Given the following performance data for[product name or feature]
for the period[time period, e.g., last quarter]
:[Metric 1 name e.g., Daily Active Users]: [Metric 1 value and trend e.g., 10,000 down 5% WoW]
[Metric 2 name e.g., Conversion Rate for X]: [Metric 2 value and trend]
[Metric 3 name e.g., Churn Rate]: [Metric 3 value and trend]
Analyze these trends, identify potential causes for
[specific observation e.g., the drop in DAU or increase in churn]
, and suggest[Number]
areas for further investigation or A/B testing. - Customer Survey Design:
Design a customer satisfaction (CSAT) / Net Promoter Score (NPS) / feature-specific survey for[product name]
to gather feedback on[specific feature or experience, e.g., the new onboarding process or overall usability]
. Include[Number]
questions, mixing formats like[Likert scale for satisfaction]
,[multiple-choice for feature usage]
, and[open-ended for qualitative feedback]
. The primary goal is to understand[primary learning objective e.g., why users are dropping off during onboarding]
.
VIII. Stakeholder Communication & Product Operations
- Stakeholder Update Email Draft:
Draft an update email to[stakeholder group e.g., Engineering Lead, Marketing Manager, Head of Sales, Leadership Team]
about the progress of[project/feature/product name]
. Key points to cover:- Recent achievements:
[Milestone achieved 1, Key decision made 1]
- Current status & outlook:
[e.g., On track for X release, Slightly delayed due to Y with new ETA]
- Key risks/blockers & mitigation:
[Risk 1 description and mitigation plan]
- Next steps for the coming
[time period e.g., week/sprint]
:[Action item 1, Action item 2]
- Expected impact on business goal:
[e.g., This will help us achieve X% increase in Y metric]
- Request for support (if any):
[Specific ask from stakeholder]
- Recent achievements:
- Explaining Technical Concepts Simply:
Explain the concept of[technical concept, e.g., API rate limiting / microservices architecture / machine learning model training / data encryption at rest]
in simple, non-technical terms for a[non-technical audience, e.g., sales team, CEO, or marketing department]
and why it’s relevant or beneficial for our[product name or company strategy]
. - Preparing for a Difficult Conversation:
I need to communicate to[stakeholder name or team or customer group]
that[difficult news, e.g., a feature release will be delayed by X weeks / we are sunsetting X feature / a recent outage impacted Y]
. Help me structure the key talking points for this conversation, focusing on transparency, empathy, clear reasons, impact, and proposed next steps or solutions. - FAQ Section Generation:
Generate an FAQ section for[product name or specific feature]
covering common questions about[topic 1 e.g., account setup and login]
,[topic 2 e.g., using feature X and its settings]
, and[topic 3 e.g., troubleshooting common issue Y and billing queries]
. - User Guide Creation:
Create a step-by-step user guide for the[specific feature or task e.g., 'setting up your first project']
in[product name]
. This guide is for users who are[specific user characteristic e.g., new to the platform or non-technical]
. Include screenshots placeholders like[Screenshot of Step 1]
where appropriate. - Risk Assessment & Mitigation Plan:
Identify[Number]
potential risks for the upcoming launch/development of[product/feature name]
. For each risk, describe it, assess its potential impact (High/Medium/Low) and likelihood (High/Medium/Low), and suggest a potential mitigation strategy. Consider risks related to[technology e.g., scalability]
,[market adoption e.g., low uptake]
,[resource constraints e.g., developer availability]
, and[timeline slippage]
. - Meeting Agenda Draft:
Draft an agenda for a[duration e.g., 1-hour]
[meeting type e.g., product team sync / sprint planning / feature kick-off]
about[meeting topic e.g., planning for Q3 roadmap for product X]
. Key objectives for this meeting are[objective 1 e.g., align on priorities]
and[objective 2 e.g., identify dependencies]
. Include time allocations for each agenda item, required attendees:[attendee 1, attendee 2]
, and any pre-reading:[document link 1]
.
- These prompts are a great tool for any business leader. For more, see our best Prompts for Entrepreneurs.
- A key part of product management is briefing your team effectively. Empower your creative counterparts by sharing these expert Prompts for Designers to ensure you’re both speaking the same language from the start.
- To truly understand your users, you need to go beyond metrics and analyze their feedback from interviews and surveys. For this, check our Prompts for Qualitative Data Analysis.