Karthik Kamalakannan
Karthik Kamalakannan Founder and CEO

10 ChatGPT prompts for product managers

Use these 10 ChatGPT prompts to speed up product strategy and decision-making.

Published February 18, 2023
Summarize with
ChatGPT
Claude
Gemini
10 ChatGPT prompts for product managers

If you're a product manager who hasn't tried throwing your toughest questions at ChatGPT yet, you're leaving a lot on the table. I've been experimenting with it for months now, and while it won't replace your judgment, it's genuinely useful for getting unstuck, pressure-testing your thinking, or just saving time on tasks that used to eat up entire afternoons.

Here's the thing though - ChatGPT is only as good as your prompts. Vague questions get vague answers. So I put together 10 prompts that actually produce useful output for product managers. They're specific enough to get real responses and flexible enough to adapt to your product.

10 ChatGPT prompts for product managers

  1. "I'm building [product type] for [audience]. Here are the top 5 feature requests from users: [list]. How would you prioritize these given a goal of [specific goal]?" - This beats the generic "how do I prioritize features?" prompt by a mile. Give ChatGPT context about your specific situation and the output gets dramatically better.

  2. "Here's feedback from 20 users about [feature]. Identify the top 3 themes and suggest which ones we should address first." - Paste in actual feedback. ChatGPT is surprisingly good at spotting patterns you might miss when you're too close to the data.

  3. "Review our product onboarding flow: [describe steps]. What accessibility issues or friction points might we be missing?" - Don't rely on this alone for accessibility audits, but it's a solid first-pass check that catches obvious gaps.

  4. "Our key metrics are [list metrics]. We saw [metric] drop by X% last month. What are the most likely causes and what data should I pull to diagnose the issue?" - Treat it as a brainstorming partner for root cause analysis. It won't know your product's internals, but it'll suggest angles you hadn't considered.

  5. "Users report that [specific workflow] feels confusing. Here's the current flow: [describe]. Suggest 3 ways to simplify it." - Give it the actual workflow details. Even a text description of the steps produces helpful suggestions for where to cut complexity.

  6. "I need to get buy-in from [stakeholder type] for [initiative]. What's the strongest business case I can make? What objections should I prepare for?" - Fantastic for prepping before a high-stakes meeting. ChatGPT often flags pushback you wouldn't have anticipated until you were already in the room.

  7. "Our product currently serves [current audience] but we want to expand to [new audience]. What are the biggest risks and what should we validate first?" - Useful for sanity-checking expansion plans. It'll usually flag obvious risks that are easy to overlook when you're excited about a new market.

  8. "Design an A/B test for [specific hypothesis]. What should the control and variant look like? What sample size do I need and how long should I run it?" - Saves the usual scramble through statistical significance calculators. Double-check the math, but the test design is usually sound.

  9. "I'm launching [feature] next month. Draft a launch plan covering pre-launch, launch day, and post-launch, focused on [goal: adoption/activation/retention]." - Specifying a single goal makes the plan much more useful than a generic "write me a launch strategy."

  10. "What's happening in [your industry/niche] right now that could affect our product roadmap in the next 6 months?" - Use this with the browsing feature turned on so it pulls recent trends and news. Without browsing, it's limited to training data and the output isn't nearly as useful.

Getting better results from these prompts

A few things I've picked up from using these regularly:

Context is everything. The more you tell ChatGPT about your product, your users, and your constraints, the better the output. "How do I prioritize features?" gives you a textbook answer. "Here are our 12 feature requests, our team is 4 engineers, and our goal this quarter is reducing churn" gives you something actionable.

Treat it like a junior analyst. The output is a starting point, never the final answer. It's solid at structuring your thinking and surfacing options, but your knowledge of your users and product is what makes the final call.

Iterate on prompts. If the first response isn't useful, tell it why. "That's too generic. Focus specifically on B2B SaaS with under 1000 users" usually gets you somewhere better.


Every voice heard.
Every feature shipped.

You're ready to ship. We're ready to help.
Start free, no credit card required.