25+ ChatGPT Prompts for SaaS Product Managers to Ship Faster
As a SaaS product manager, you're juggling roadmaps, user stories, and stakeholder updates. These expert-crafted ChatGPT prompts for product managers are designed to slash your documentation time. From drafting precise acceptance criteria to writing compelling release notes, use these AI prompts to focus on strategy, not syntax.
Quickly create detailed user personas based on target market data to inform product decisions.
Act as a senior product manager. Based on the following user research data, generate 3 distinct user personas for our SaaS product, which is a [PRODUCT DESCRIPTION]. Each persona should include a name, role, goals, frustrations, and a brief bio. Raw user data: [RAW USER RESEARCH DATA].
Competitive Analysis Summary
Summarize key features, pricing, and weaknesses of competing SaaS products to identify market gaps.
Provide a competitive analysis summary in a markdown table. Compare our product, [YOUR PRODUCT NAME], with these 3 competitors: [COMPETITOR A], [COMPETITOR B], [COMPETITOR C]. The columns should be: Feature, [YOUR PRODUCT NAME], [COMPETITOR A], [COMPETITOR B], [COMPETITOR C], and Market Opportunity. For the 'Feature' column, focus on [KEY FEATURE CATEGORIES, e.g., 'real-time collaboration', 'API integrations', 'reporting dashboards'].
Problem Statement Framing
Refine a user problem into a clear, actionable problem statement using a structured format.
Help me frame a problem statement for a new feature. The user is a [USER PERSONA]. The problem they face is [CORE PROBLEM]. The impact of this problem is [IMPACT OF PROBLEM]. Structure the output as: 'User,' 'Problem,' 'Impact,' and a final 'Problem Statement.'
Brainstorm 'How Might We' Questions
Generate creative 'How Might We' questions to spark ideation for a specific product challenge.
Generate 10 'How Might We' (HMW) questions to brainstorm solutions for the following problem: [SPECIFIC PROBLEM, e.g., 'Users find our onboarding process too long and confusing, leading to high drop-off rates after signup.']. The questions should be optimistic and open-ended.
Write a Gherkin-Style User Story
Convert a feature idea into a well-structured user story with the 'As a, I want, so that' format.
Write a user story in the Gherkin format ('As a [TYPE OF USER], I want [AN ACTION], so that [A BENEFIT]'). The feature is [FEATURE IDEA, e.g., 'the ability to export reports as a PDF']. The user is a [TYPE OF USER, e.g., 'finance analyst']. The benefit is [BENEFIT TO USER, e.g., 'to easily share financial performance with stakeholders who don't have access to our platform.'].
Deconstruct Epic into User Stories
Break down a large feature epic into smaller, manageable user stories for sprint planning.
I have a product epic: '[EPIC TITLE, e.g., 'Implement a new user notification center']'. Break this epic down into at least 5 smaller, independent user stories. Each story should follow the 'As a user, I want...' format and represent a distinct piece of functionality, such as viewing notifications, marking as read, receiving email digests, and managing notification settings.
Identify Edge Cases for a Feature
Brainstorm potential edge cases and error states for a new user story to ensure robust development.
Consider the following user story: 'As a user, I want to invite a team member to my project by entering their email address.' Brainstorm a list of potential edge cases, error states, and boundary conditions that developers should consider. Include scenarios like invalid email formats, inviting an existing user, invitation expiry, and network errors.
Generate Acceptance Criteria
Create a comprehensive list of acceptance criteria for a user story using the Gherkin 'Given/When/Then' format.
Generate a list of acceptance criteria for this user story: 'As a user, I want to reset my password so that I can regain access to my account if I forget it.' Use the Gherkin format (Given, When, Then) and cover the success path, invalid email entry, and expired token scenarios.
Draft a PRD Outline
Generate a structured outline for a Product Requirements Document (PRD) for a new feature.
Create a comprehensive PRD outline for a new feature called '[FEATURE NAME, e.g., 'Two-Factor Authentication']'. The outline should include sections for: 1. Introduction & Problem Statement, 2. Goals & Success Metrics, 3. User Personas & Stories, 4. Functional Requirements, 5. User Flow & Design, 6. Non-Functional Requirements (e.g., security, performance), 7. Future Considerations.
Translate Technical Concepts Simply
Explain a complex technical concept in simple terms for a non-technical audience, like sales or marketing.
Explain the concept of '[TECHNICAL CONCEPT, e.g., 'single sign-on (SSO) using SAML']' to a non-technical audience. Use an analogy and focus on the user benefits, such as improved security and convenience, rather than the technical implementation details. The goal is to help our sales team explain this feature to potential customers.
RICE Score Analysis
Analyze a feature idea using the RICE framework to help with prioritization discussions.
Help me conduct a RICE score analysis for the feature: '[FEATURE DESCRIPTION, e.g., 'Adding a dark mode to our web app']'. Provide a reasoned estimate for each component: Reach (e.g., '100% of our 5,000 daily active users'), Impact (on a scale of 0.25-3), Confidence (in percent), and Effort (in person-months). Then, calculate the final RICE score and provide a brief justification.
Draft a Quarterly Roadmap Theme
Articulate a clear, compelling theme for an upcoming product roadmap quarter to align the team.
Our company goal for Q3 is to [COMPANY GOAL, e.g., 'reduce customer churn by 10%']. Our key user persona is the [TARGET PERSONA, e.g., 'power user administrator']. Draft 3 potential, inspiring roadmap themes for the product team that align with this goal. For each theme, provide a one-sentence description.
Write a Stakeholder Update Email
Draft a clear and concise project status update email for stakeholders, using a structured format.
Draft a weekly stakeholder update email for the '[PROJECT NAME]' project. The status is currently [CURRENT STATUS AND REASON, e.g., 'Yellow' because of a delay in API development]. The email should have three sections: 1. Summary (a one-sentence overview), 2. What We Accomplished This Week (bullet points), 3. Blockers & Next Steps. Keep the tone professional and proactive.
Draft Internal Release Notes
Write internal release notes for sales and support teams, focusing on benefits and key changes.
Write internal release notes for our new feature: '[FEATURE NAME, e.g., 'Advanced Reporting Dashboard']'. The audience is our Sales and Customer Support teams. The notes should include: 1. What's New? (a brief summary), 2. Why It Matters (customer benefits and selling points), 3. How It Works (key steps for users), 4. Potential Customer Questions (with answers).
Create Public Release Notes
Generate user-facing release notes for a new feature launch, highlighting the value and benefits.
Write public-facing release notes for our new '[FEATURE NAME]' feature. The tone should be friendly and benefit-oriented. Start with a catchy title. Explain what the feature is and why it will make the user's life better. Include a link to the help documentation and a call-to-action to try it out. The feature allows users to [KEY FUNCTIONALITY, e.g., 'integrate their calendars to see all meetings in one place.'].
Prepare for a Sprint Review
Create a script or talking points for presenting a completed feature at a sprint review.
Generate a script for a 5-minute presentation at our upcoming sprint review. The feature to present is '[FEATURE NAME, e.g., 'CSV Data Import']'. The script should cover: 1. The user problem we solved. 2. A brief demo walkthrough of the feature's happy path. 3. The business impact or value delivered. 4. A thank you to the development team.
Generate User Interview Questions
Create a set of open-ended questions for a user interview about a new or existing feature.
I need to conduct user interviews to get feedback on our new feature, '[FEATURE NAME]'. The goal is to understand if it's solving the intended problem and identify any usability issues. Generate 10 open-ended interview questions that avoid leading the user. Start with broad questions about their workflow and then narrow down to the specific feature.
Summarize User Feedback
Analyze and summarize key themes from a batch of user feedback or survey results.
I have the following user feedback from a recent survey about our [PRODUCT AREA, e.g., 'mobile app']. Please analyze it and summarize the top 3 positive themes and top 3 areas for improvement. Present the output in bullet points with a brief explanation for each. Feedback: [RAW USER FEEDBACK DATA].
Refine User Story with Job Story Framework
Rewrite a user story using the 'Jobs to Be Done' framework for better context on user motivation.
Convert the following user story into the 'Jobs to Be Done' (JTBD) framework. User Story: 'As a project manager, I want to receive a daily summary email, so that I can stay updated on project progress.' The JTBD format is: 'When [situation], I want to [motivation], so I can [expected outcome].'
Write API Endpoint Requirements
Outline the requirements for a new API endpoint from a product perspective for the engineering team.
Draft the product requirements for a new API endpoint. The endpoint should allow users to [API ENDPOINT ACTION, e.g., 'retrieve a list of their projects']. Specify the required request parameters (e.g., 'user_id'), the expected data in the response (e.g., 'project_id, project_name, creation_date'), and any necessary filtering or pagination logic (e.g., 'limit results to 50 per page').
Draft a Roadmap Initiative Note
Write a concise summary of a new roadmap initiative, including the problem, hypothesis, and goals.
Write a one-page summary for a new roadmap initiative called '[INITIATIVE NAME, e.g., 'Improving Team Collaboration']'. The document should clearly state: 1. The Problem: What user or business problem are we solving? 2. The Hypothesis: What do we believe is the solution? (e.g., 'We believe that by adding in-app commenting, we will increase user engagement.') 3. Key Goals/Metrics: How will we measure success? (e.g., 'Increase daily comments per user by 15%').
Feature Prioritization Arguments
Generate arguments for and against prioritizing a specific feature to prepare for roadmap discussions.
I need to prepare for a roadmap prioritization meeting. The feature being debated is '[FEATURE NAME, e.g., 'Offline Mode for the mobile app']'. Generate a list of 3 strong arguments FOR prioritizing it now and 3 strong arguments AGAINST prioritizing it now (e.g., opportunity cost, technical complexity).
Draft a Feature Deprecation Notice
Write a clear and empathetic communication plan for deprecating an old feature.
Draft an announcement to users about the deprecation of our '[OLD FEATURE NAME]' feature, which will be removed on [DEPRECATION DATE]. The announcement should: 1. Clearly state what is happening and when. 2. Explain why we are making this change (e.g., 'to focus on improving our new [NEW FEATURE NAME]'). 3. Provide a clear migration path or alternative for users. 4. Show empathy for users who may be disrupted.
Value Proposition Canvas
Draft a value proposition canvas for a new feature or product to align on customer value.
Fill out a Value Proposition Canvas for our new feature: '[FEATURE NAME]'. The target customer segment is '[CUSTOMER SEGMENT]'. On the customer side, list their key 'Jobs to be Done,' 'Pains,' and 'Gains.' On the product side, list the 'Products & Services' (our feature), 'Pain Relievers,' and 'Gain Creators' that correspond to the customer profile.
Create a User Flow Logic Table
Describe a user flow in a logical, step-by-step table format for developers and designers.
Create a user flow logic table for the '[USER FLOW NAME, e.g., 'New User Signup']' process. The table should have three columns: 'Step Number,' 'User Action,' and 'System Response/UI Change.' Detail the flow from the moment the user clicks 'Sign Up' to when they land on the dashboard, including email verification.
Draft A/B Test Hypothesis
Formulate a clear hypothesis for an A/B test to improve a key metric.
I want to run an A/B test on our pricing page. The goal is to increase the conversion rate from visitor to trial signup. The proposed change is [PROPOSED CHANGE, e.g., 'changing the CTA button text from "Sign Up" to "Start My Free Trial"']. Formulate a clear A/B test hypothesis using the format: 'By [making this change], we believe it will cause [this effect] for [this user segment], because [this reason]. We will measure this by [this metric].'
Success Metrics Brainstorm
Brainstorm primary and secondary success metrics for a new feature launch.
We are launching a new feature: '[FEATURE NAME, e.g., 'In-app chat for support']'. Brainstorm a list of success metrics to track its performance. Categorize them into two groups: 1. Primary Metrics (e.g., adoption rate, reduction in support tickets) and 2. Secondary/Guardrail Metrics (e.g., impact on app performance, user satisfaction score).
Turn these prompts into a reusable workspace
Save your favourite prompts once, reuse them with Alt+P, keep a live Table of Contents of long chats, and export conversations when you're done.
