PM Claude Prompt Library

Act as a UX researcher. I'm building [product] for [persona]. Generate 20 open-ended interview questions that uncover goals, frustrations, and workarounds. Avoid leading questions.

I just completed 10 user interviews. Here are my raw notes: [paste]. Synthesize key themes, recurring pain points, and surprising insights. Group by theme, not by user.

Create a user interview discussion guide for [product stage: discovery / validation / usability]. Include: warm-up, core questions, probes, and a wrap-up. Target: [persona].

I want to validate whether [assumption] is true for [persona]. Design a 30-minute interview script that will confirm or refute this, including follow-up probes.

Analyze this interview transcript and identify: (1) explicit needs, (2) implicit needs, (3) emotional triggers, (4) decision drivers. [Paste transcript]

I have 5 interview transcripts. Run an AI-assisted thematic analysis. Cluster quotes by theme, identify contradictions across users, and flag the most surprising finding.

Design a remote, async interview using a video tool for [persona] around [topic]. Include: the 5 prompts, instructions for participants, and how you'll analyze the responses.

Apply Jobs-to-be-Done to [product]. Identify the functional, emotional, and social jobs. Write 3 JTBD statements: 'When I [situation], I want to [motivation], so I can [outcome].'

Write 5 job stories using JTBD format for [product]. For each, suggest one feature that directly fulfills the job.

Map the job executor journey for [persona] trying to accomplish [goal]. Break into: before, during, after. Identify pain points and opportunities at each stage.

I'm about to build [feature]. List all assumptions I'm making about: user behavior, market demand, technical feasibility, business viability. Rank by risk.

For each assumption: [list], design a lightweight experiment (survey, prototype, A/B test, customer conversation) to validate within 2 weeks.

Using the 2x2 Assumption Map (certainty vs. risk), categorize: [list assumptions]. Tell me which to test first and the fastest validation method for each.

Help me size the market for [feature]. Use top-down TAM/SAM/SOM. I have this data: [paste]. Fill gaps with estimates and state assumptions.

I want to prioritize between [opportunity A] and [opportunity B]. Estimate revenue impact, user reach, and strategic value of each using a scoring framework.

Write an opportunity brief for [feature]. Include: problem statement, target segment, estimated reach, frequency of need, current alternatives, and why now.

Given these churn reasons from exit surveys: [paste], identify the top 3 product gaps driving churn and suggest one feature or fix for each.

Our 30-day churn is [X]% in [segment]. What are the most common product, onboarding, and value-delivery reasons for churn at this stage? Suggest a retention experiment for each.

Create 3 detailed user personas for [product]. Each should include: demographics, goals, frustrations, tools used, a day-in-the-life, and a quote capturing their mindset.

I have this user research data: [paste]. Derive a primary persona and an anti-persona (user we are NOT building for). Explain the trade-offs of this focus.

Analyze [competitor] from a product lens: core value prop, target user, key features, pricing, weaknesses, and how they position vs. [my product].

Create a competitive matrix comparing [my product] vs. [competitor 1], [competitor 2], [competitor 3] across: [dimensions]. Highlight our differentiated advantages.

Design a 10-question survey for [goal: NPS / feature validation / pain point discovery]. Include rating scales, multiple choice, and one open-ended question. Avoid survey bias.

I collected these survey results: [paste]. Identify the most meaningful findings, flag sample size risks, and recommend 3 product decisions based on the data.

Reframe this problem using 5 lenses: user, business, technical, ecosystem, and a 'how might we' lens. Problem: [describe].

Write a clear problem statement for [feature] using: 'We observed [observation]. This is a problem because [impact]. If we solve it, we expect [outcome].'

Plan a contextual inquiry session for [persona] doing [task]. Create an observation guide: what to watch for, in-context questions, and how to document findings.

Create a research plan for [initiative]. Include: objectives, methods, sample size, recruitment criteria, timeline, and how findings will influence product decisions.

Write a usability test script for [feature/prototype]. Include: intro script, 5 task scenarios, observation prompts, and a debrief questionnaire.

I ran a usability test with 8 participants. Summarize usability failures by severity (critical / major / minor) and suggest a fix for each critical issue. Notes: [paste].

Extract VoC insights from these [reviews / support tickets / NPS comments]: [paste]. Group into themes, assign sentiment scores, flag strong quotes for PRD use.

Design a Customer Advisory Board structure for [product]. Who to invite, how often to meet, what to discuss, and how feedback flows into the roadmap.

Plan a 2-week diary study for [persona] around [behavior]. Define: what participants log daily, the prompts you'll send, and how you'll analyze the data.

Design a concept test for [product idea]. What stimulus will you show users? What questions will you ask? How will you measure desirability, viability, and feasibility?

Design a lightweight research repository for my team. How should we tag, store, and surface past insights so they inform current decisions?

Conduct a secondary research brief on [market/topic]. Synthesize: market size, key trends, industry reports, competitor moves. Identify 3 strategic implications.

Create an empathy map for [persona] around [task/goal]. Fill in what they think, feel, say, do, hear, and see. Derive 3 product insights from the map.

Design a 2-week validation sprint for [idea]. What questions must we answer? What's the cheapest experiment per question? What's our go/no-go criteria?

Run a 5 Whys analysis for this user problem: [describe]. Get to the root cause and suggest a product solution addressing the root, not the symptom.

Identify 5 macro or industry trends relevant to [product]. For each: the signal, implication for our users, and the product opportunity it creates.

Design a win/loss analysis program. What deals to analyze, who to interview, what questions to ask, and how findings feed into product strategy.

Here are insights from multiple sources (interviews, surveys, analytics): [paste]. Triangulate to identify strongest signals. Flag where sources conflict.

What are the top 5 unmet needs in [market/category]? For each, describe the current workaround users rely on, and the product opportunity this represents.

Map the end-to-end customer journey for [persona] from awareness to advocacy. Identify moments of truth, emotional highs/lows, and the biggest product opportunity at each stage.

Design a continuous feedback loop for [product]. How do we collect, synthesize, and act on user feedback weekly without it becoming a feature-request firehose?

Score these features using RICE (Reach, Impact, Confidence, Effort): [list]. Reach = users/quarter, Impact = 0.25–3x, Confidence = %, Effort = person-weeks. Show reasoning.

I've scored these features with RICE but I'm skeptical. Critique my scoring, flag overconfidence or underestimated effort, and suggest revised scores.

Help me write Q[X] OKRs for [product/team] focused on [strategic theme]. Write 2 objectives with 3 key results each. Make KRs measurable, time-bound, and ambitious.

Review these OKRs: [paste]. Identify: (1) KRs that are outputs not outcomes, (2) KRs without clear measurement, (3) conflicts between objectives. Rewrite the weakest ones.

Map each item in my backlog to our OKRs: [paste backlog + OKRs]. Flag items that don't map to any OKR — candidates for cutting or deferring.

Build an OST for [goal]. Start from the desired outcome, branch into opportunities, then solutions, then experiments. Use this research: [paste].

I have this OST: [paste]. Challenge each branch. Are opportunities distinct? Are solutions addressing root causes? Are experiments testing the right assumptions?

Organize this backlog into a Now/Next/Later roadmap: [paste]. Now = this quarter, Next = next quarter, Later = future. Explain each placement.

Translate this technical backlog into business-outcome language for non-technical stakeholders for a Now/Next/Later roadmap: [paste backlog].

Evaluate whether to build, buy, or partner for [capability]. Consider: strategic importance, time-to-market, cost, maintenance, competitive differentiation.

Create a weighted scoring matrix for [capability]. Criteria: [list]. Score each option and recommend the best path.

Write a quarterly product brief for Q[X]. Include: strategic context, top 3 bets, success metrics, key risks, and what we're explicitly NOT doing.

I need to cut scope this quarter due to [reason]. Help me evaluate which features to defer using: OKR impact, user value, technical dependencies, stakeholder commitments.

Categorize this feature list using MoSCoW for [release milestone]: [list]. Explain why each is Must Have, Should Have, Could Have, or Won't Have.

Create a user story map for [user journey]. User activities across the top, tasks below, stories mapped to release layers (MVP, v1.1, v2).

Apply the Kano Model to these features: [list]. Classify each as Basic, Performance, or Delight. Use this to inform MVP scope.

Map dependencies for this roadmap: [paste]. Identify cross-team, technical pre-requisite, and external dependencies. Flag highest risk blockers.

Our company strategy is [paste]. Derive 3–4 product strategic themes aligned to company goals. Map our roadmap against these themes to identify gaps.

Write a 1-page roadmap narrative for [product] covering the next 3 quarters. Focus on 'why' not 'what'. Audience: mixed business/technical.

Help me write a product vision statement for [product]. Aspirational, user-centric, timebound (3–5 years), and differentiated from competitors.

Help me choose between [option A] and [option B] for our roadmap. Think through trade-offs across: user value, revenue impact, engineering effort, risk, strategic fit.

Our team has [X] engineers for Q[X] and [Y] initiatives. Help me allocate capacity across: new features, tech debt, bugs, experiments. Show trade-offs of different splits.

Convert this feature-level roadmap into a theme-based roadmap answering 'what problem are we solving?' at each stage: [paste].

Review this backlog: [paste]. Identify: (1) duplicates, (2) vague items, (3) items with no success metric, (4) solutions disguised as problems. Recommend what to delete or rewrite.

Map our 3 strategic themes for next year: [list]. For each: user problem, business goal, key initiatives, success metric.

Design a process for collecting roadmap input from sales, CS, and marketing without letting the loudest stakeholder win.

Make the case to leadership for allocating [X]% of capacity to tech debt reduction using business impact language.

Grade our previous quarter OKRs: [paste + results]. Use 0–1.0 grading. For misses below 0.7, diagnose: ambition, execution, or external factors.

Help me decide how to split our roadmap between core improvements and innovative new bets. What framework should I use, and how do I defend the innovation budget?

What metrics measure the health of my roadmapping process itself? Include: predictability, stakeholder satisfaction, discovery/delivery balance, and cycle time.

We have 200 feature requests. Design a process to: categorize them, identify themes, weight by customer value, and translate into roadmap items.

We're debating investing in [capability] as platform vs. product feature. Think through: reusability, API design, revenue model, engineering implications.

Design a release planning process for a team running 2-week sprints aiming for monthly releases. How do we plan, communicate, and execute releases without slowing down development?

Sales wants [feature A], CS wants [feature B], and Engineering says [feature C] is critical. Help me facilitate a structured prioritization session to resolve this conflict.

We have 18 months of 'promised' features that are still not delivered. Help me audit these promises, assess which to keep vs. renegotiate, and draft communication to stakeholders.

Design the annual product planning process. Timeline, inputs needed, who participates, output format, and how the annual plan connects to quarterly OKRs.

We have 4 products competing for engineering resources. Help me design a portfolio prioritization model that balances: strategic importance, revenue contribution, and growth potential.

At the end of Q[X], run a roadmap retrospective. What % of planned items shipped? What caused slippage? What do we change in our planning process next quarter?

Add a risk adjustment layer to this roadmap: [paste]. For each initiative, rate delivery risk and market risk. Suggest how risk should change prioritization order.

I have a roadmap review with [exec] next week. Help me prepare: what questions they will likely ask, how to defend my prioritization, and what trade-offs to pre-empt.

Write a PRD for [feature]. Include: problem statement, user stories, acceptance criteria, out-of-scope, success metrics, edge cases, and open questions.

Review this PRD: [paste]. Identify: missing edge cases, ambiguous requirements, missing acceptance criteria, undefined terms, and unvalidated assumptions.

Convert this PRD into a lightweight 1-pager for a quick win feature: [paste]. Trim to: problem, solution, success metric, key constraints. Max 500 words.

Write user stories for [feature] using: 'As a [persona], I want to [action] so that [benefit].' Include Given/When/Then acceptance criteria.

Break this epic into user stories: [paste]. Ensure each story is independently deliverable, testable, and fits in one sprint. Flag stories to split further.

Write edge case user stories for [feature]: error states, empty states, maximum limits, concurrent users, slow connections, and accessibility scenarios.

Create a pre-launch checklist for [feature]: product QA, analytics instrumentation, marketing readiness, support enablement, legal/compliance, rollback plan.

Write a go-to-market launch plan for [feature] targeting [persona]. Include: messaging, channels, launch sequence, success metrics, and 30/60/90 day post-launch plan.

Design a phased rollout for [feature]: internal testing, beta cohort criteria, rollout percentages, rollback triggers, and success gates at each phase.

We're launching [feature] in a phased rollout. What monitoring setup, alerts, and response playbooks should I have in place before we go live?

Generate a comprehensive list of edge cases for [feature] across: input validation, state transitions, concurrent actions, failure modes, and security.

Review these edge cases: [list]. Are any missing? Prioritize by likelihood and severity. Which are must-fix vs. nice-to-fix?

Facilitate a sprint retrospective using the 'Sailboat' format. I'll paste our sprint data: [data]. Anchor = obstacles, wind = what helped, rocks = risks, island = goal.

We finished a sprint with these outcomes: [results]. Write a concise retrospective: what went well, what to improve, and 3 specific action items for next sprint.

I'm reviewing this technical design: [paste]. As a PM, what questions should I ask engineering to ensure the solution fully addresses user needs and business requirements?

Design a feature flag strategy for [feature]: flag naming, targeting rules for beta users, metrics to monitor per flag state, and deprecation criteria.

Write detailed acceptance criteria for these user stories: [paste]. Use Given/When/Then format. Include happy path and sad path scenarios.

Design error state messaging for [feature]. For each error: [list], write the user-facing message, recovery action, and support fallback.

Design a first-time user onboarding flow for [product/feature]. Map each step, the user action required, value demonstrated, and success trigger to advance.

Our onboarding completion is [X]%. Analyze this flow: [paste] and identify the 3 most likely drop-off points. Suggest one experiment per drop-off point.

Write user-facing release notes for: [describe changes]. Tone: clear, positive, benefit-focused. Organize by: New, Improved, Fixed.

Write internal release notes for engineering/design for sprint [X]: shipped features, known issues, deprecated components, dependencies for next sprint.

Map dependencies for [initiative]: external APIs, internal services, cross-team work, data pipelines. For each: owner, risk level, mitigation if delayed.

Create a Definition of Done checklist for [team]. Include criteria for: code quality, testing, documentation, analytics, accessibility, security.

Help me triage this bug list: [paste]. Classify each by severity (P0–P3), estimate user impact, and recommend which to fix in this sprint vs. defer.

Design an A/B test for [hypothesis]. Include: control and variant, primary metric, guardrail metrics, minimum sample size estimate, and test duration.

Given these user needs: [paste], define the smallest MVP that validates our core hypothesis: [hypothesis]. What stays in, what gets cut, and why?

We launched [feature] [X] weeks ago. Metrics: [paste]. Did we hit success criteria? What did we learn? What next?

Design a design review process. What stages go through review? Who should be in each? What feedback is in scope vs. out of scope?

Write a blameless post-mortem for this incident: [describe]. Timeline, root cause, contributing factors, user impact, and 3 action items to prevent recurrence.

Design the notification strategy for [feature]. For each user action: whether to notify, channel (push/email/in-app), timing, copy, and opt-out mechanism.

Write copy and design direction for empty states in [product]: initial empty state, 'try it' empty state, and error empty state.

Review [feature] for data privacy. What user data is collected? Is it necessary? How is it stored? What consent is required? GDPR/CCPA implications?

Conduct an accessibility checklist for [feature]: keyboard navigation, screen reader support, color contrast, touch targets, WCAG 2.1 AA compliance.

We're launching in [new market]. What localization considerations for: copy, date/time formats, currency, RTL support, cultural sensitivity?

Write a rollback plan for [feature launch]. Define: rollback trigger conditions, the steps, communication plan, and how to preserve user data during rollback.

Help me plan sprint [X] given: team capacity [X points], carryover [paste], OKR priorities [paste]. Suggest which stories to include and flag risks.

Write a developer-facing changelog for API version [X.X]: breaking changes, new endpoints, deprecated fields, and migration guide.

How should I account for technical debt when writing a PRD? Add a section capturing: known constraints, shortcuts being taken, and future work they'll create.

I have conflicting requirements between [stakeholder A] and [stakeholder B]. Here's the context: [paste]. Help me identify the root cause and propose a resolution.

We have 47 old feature flags never cleaned up. Create a process for: auditing active flags, deciding which to deprecate, and removing them safely.

Help me write the product section of API documentation for [feature]. Explain: what the API does, primary use case, key parameters, and a sample request/response in plain English.

Write an engineering handoff document for [feature]. Include: product context, user stories, acceptance criteria, edge cases, analytics events, and open questions.

Write a QA test plan for [feature]. Include: test scope, test cases for the happy path, negative test cases, performance test criteria, and regression areas to watch.

Create a go-live day checklist for [feature launch]. What must I verify in the hour before launch, during launch, and in the first hour post-launch?

Help me define a North Star Metric for [product]. It should reflect long-term user value, be measurable weekly, and align the entire team. Give 3 candidates with trade-offs.

Our current NSM is [metric]. Stress-test it: could it be gamed? Does it capture full user value? Is it a vanity metric? Suggest improvements or alternatives.

Build a metrics framework for [product/feature] using Input → Output → Outcome structure. Define: leading indicators, lagging indicators, and guardrail metrics.

I ran an A/B test with these results: [paste]. Help me interpret: statistical significance, practical significance, segment breakdowns, and whether to ship, iterate, or kill the variant.

My A/B test improved [metric] but degraded [guardrail metric]. How should I think about this trade-off? What additional analysis would help me make the ship decision?

Analyze this conversion funnel: [paste]. Identify the biggest drop-off, hypothesize 3 causes, and suggest one experiment per cause.

Build a funnel analysis framework for [user flow]. Define each stage, conversion metric between stages, and target conversion rate benchmarks.

Design a product dashboard for [team/stakeholder]. Include: 5 key metrics, visualization type for each, update frequency, and who owns each metric.

Review this dashboard: [paste]. Is it telling a coherent story? Are any metrics redundant? What's missing? Redesign for [audience].

Walk me through how to do a cohort analysis for [product]. Define: cohort criteria, retention metric, time period, and how to interpret results.

Here is my cohort retention data: [paste]. Identify: (1) where retention breaks down, (2) which cohorts perform best and why, (3) what product changes might improve week 4 retention.

It's been 30 days since [feature] launched. Metrics: [paste]. Did we achieve success criteria? What do the numbers tell us? What next?

For each OKR: [paste], define: measurement method, data source, update cadence, and owner. Flag KRs that lack a clear data source.

Our [metric] dropped [X]% this week. Walk me through a structured investigation: what to check first, how to isolate the cause, when to escalate.

I have this product data: [paste]. Write a data story for executives: leads with the insight, supports with data, ends with a clear recommendation.

Write a metric definition document for [metric]: definition, formula, data source, update frequency, owner, target, and how to interpret deviations.

Distinguish leading and lagging indicators for [product goal]. For each leading indicator, explain how it predicts the lagging outcome and what action to take if it trends negative.

Build a 90-day experimentation roadmap for [product area]. Prioritize by: expected impact, speed to results, risk. Include: hypothesis, metric, duration, sample size.

Our 30-day retention is [X]%. Break down how to think about: (1) activation, (2) habit formation, (3) re-engagement. Suggest one measurement and one intervention per area.

Write a narrative for our quarterly KPI review: [paste data]. Explain performance, contextualize vs. benchmark, and identify root causes of misses.

Segment our users by [behavior/attribute]. For each segment: size, engagement pattern, value to business, and the most impactful product improvement we could make.

Feature [X] has [Y]% adoption 60 days post-launch. Diagnose: is this good? What are the most common reasons for low feature adoption, and which apply here?

Apply Google's HEART framework to [product/feature]. Define one metric per dimension (Happiness, Engagement, Adoption, Retention, Task Success) and identify data sources.

Design an early warning system for churn. What behavioral signals to monitor? At what threshold to trigger an intervention? What interventions to run?

Set up a growth accounting framework for [product]. Define: new, retained, resurrected, and churned users. How does each connect to growth rate?

Design an analytics event tracking plan for [feature]. List: event names, properties, triggers, and the product question each event answers.

Design a revenue analytics framework. Include: MRR, ARR, expansion MRR, churn MRR, net revenue retention, and LTV:CAC. Define each and identify data sources.

Help me calculate and segment LTV for [product]. What inputs do I need? How does LTV vary by channel, plan, or segment? What decisions does LTV drive?

Analyze Customer Acquisition Cost by channel: [paste]. Which channels are most efficient? Where are we over/under-investing? What's our payback period?

For [product], what are 3 predictions worth making? What data do we need, and how would predictions change our decisions?

Our team runs 2 experiments per quarter. How do I increase to 10+ per quarter? What process, tooling, and culture changes are required?

How do I build a data culture on my product team? Design a process: sharing metrics in standups, running data office hours, making dashboards accessible to non-analysts.

Help me think through attribution for [growth channel]. What model should I use (first/last/multi-touch)? How do I set it up, and what decisions will it inform?

Design a real-time monitoring plan for [feature launch]. What metrics need real-time dashboards? What are alert thresholds? Who gets notified and how fast?

Set up a competitive benchmarking framework. Which metrics to track vs. [competitors], where to get proxy data, and how to use this in planning?

Audit our current product metrics. Which metrics are being tracked but not used for decisions? Which decisions lack a metric? Where are we measuring the wrong things?

Design a product health score for [product]. What dimensions matter (engagement, retention, satisfaction, growth)? How do you weight them into a single score? How do you use it?

Define engagement metrics for [product]. What does 'engaged' mean for our users? What actions indicate high engagement? How do we measure depth vs. breadth of engagement?

We shipped [feature] 3 months ago. Design a retrospective impact measurement study to determine the actual causal impact on [business outcome] beyond what A/B testing could show.

Design a weekly metrics ritual for my PM team. What do we review every Monday, who leads it, what questions do we ask, and how do we turn it into action?

Write a weekly product update email for senior leadership. Tone: concise, results-oriented. Include: key wins, risks/blockers, key metrics, decisions needed.

Write a one-page executive summary for [initiative] to get C-suite approval: problem, proposed solution, expected ROI, key risks, the ask.

Stakeholders [A] and [B] disagree on [decision]. Map their underlying interests (not positions) and suggest a path to alignment.

I need buy-in from [team] for [initiative]. What are the most likely objections? For each, write a response addressing their core concern.

I need to influence [stakeholder] to prioritize [initiative] without direct authority. What influence strategies are most appropriate, and what should I avoid?

Write a persuasive one-pager for [stakeholder] to get support for [initiative]. Lead with what's in it for them, support with data, end with a specific ask.

Help me prepare for our quarterly business review. Structure: Q[X] performance vs. targets, key learnings, Q[X+1] priorities, resource requests. Data: [paste].

Write the narrative section of our QBR for [product]. Explain performance in context of market conditions, internal decisions, and strategic bets. Data: [paste].

Write a product one-pager for our sales team about [feature]: customer problem solved, key benefits, 3 objection-handling points, competitive differentiator.

A customer asked sales: [question]. Draft a clear, honest answer that addresses the question and highlights our strengths without overpromising.

Give me a STAR-format answer for: 'Tell me about a time you made a product decision with incomplete data.' My background: [paste].

I have a PM interview with [company] about their product [X]. Give me 5 likely product sense questions and coaching on how to approach each.

Coach me through a product design interview: 'Design a feature for [product] to improve retention.' Walk me through the ideal framework and strong vs. weak answers.

Write a roadmap communication for [internal / external] audience explaining why we're not building [highly-requested feature]. Honest, clear, trust-maintaining.

Write a kickoff memo for a cross-functional initiative involving [teams]. Cover: why, each team's role, timeline, decision rights, and success criteria.

Create a RACI matrix for [project]. Stakeholders: [list]. Decisions/activities: [list]. Identify ownership gaps or conflicts.

Map stakeholders for [initiative]: influence level, interest level, likely stance (champion / neutral / skeptic), and recommended engagement strategy.

Write an internal product announcement for [feature launch]. Audience: company-wide. Cover: what launched, why it matters, how to try it, and how to give feedback.

Write a concise escalation note to [executive] about [issue]: the situation, what I've tried, what I need from you, and my recommended path.

Engineering says [feature] will take [X] weeks. Help me structure a constructive conversation that explores scope reduction without damaging the relationship.

I disagree with a design decision on [feature]. How do I raise this constructively, using user data and product principles rather than personal preference?

Prepare a product section for a board meeting deck: product highlights, key metrics, strategic bets, risks, and what you need the board's guidance on.

A key customer is threatening to churn because [reason]. Write a response that acknowledges frustration, explains our roadmap stance, and proposes a retention path.

Design a structured feedback collection process for [initiative] from [stakeholder group]. What feedback you need, how to collect, how to synthesize, and how to close the loop.

Write a partner update for [external partner]: what we've built together, what's next on our joint roadmap, and how to escalate issues between teams.

Write a product section for an investor update: key product milestones, NPS or engagement data, what we learned this quarter, and what we're betting on next.

Write a monthly product team newsletter for the broader company: what we shipped, what we learned, a user story, and what's coming next.

Design a vendor evaluation process for [vendor/capability]: RFP questions, scoring criteria, reference check questions, and final recommendation format.

Write copy for a compliance-driven product change: explains the change, minimizes alarm, and clearly tells users what they need to do.

We're deprecating [feature] users rely on. Design a change management plan: communication timeline, migration support, user incentives, success metrics.

Design a healthy PM-Engineering working model. How should we collaborate on discovery, planning, sprint ceremonies, and retros? What are the clear ownership boundaries?

Two stakeholders are in open conflict about [decision] and it's blocking our team. What de-escalation techniques should I use, and how do I get to a resolution?

Design a Customer Advisory Council session about [topic]. What to share, what to ask, how to capture insights, and how to follow up.

I need to have a difficult conversation with [stakeholder] about [situation]. Help me prepare: what to say, how to open, handle defensiveness, and close constructively.

Design a strategic alignment meeting for [initiative] across [teams]. Agenda, pre-reads, decision-making approach, and how to document outcomes and next steps.

A stakeholder is pushing hard for [feature] I don't think should be prioritized. Help me write a response that is honest, data-backed, empathetic, and maintains the relationship.

Write an external product announcement for [feature/launch]. Audience: customers and press. Tone: confident, customer-centric. Include: the hook, the benefit, and the CTA.

We collected feedback from [stakeholder group] 3 months ago and made changes. Write a 'closing the loop' communication to let them know what changed based on their input.

Design a monthly executive product review. What to present, what format, what decisions to drive, and how to make it efficient for busy executives.

I need to communicate [complex product decision] to a non-technical executive audience. Help me reframe the data and logic as a compelling story they'll remember and act on.

Build a growth strategy for [product] targeting [lever: acquisition / activation / retention / revenue / referral]. Start from current baseline and define a 90-day plan.

Audit our growth funnel: [paste data]. Identify the single highest-leverage intervention at each stage and the experiment to test it.

Our activation rate is [X]%. What is the 'aha moment'? How quickly should users reach it? Design 3 experiments to improve activation by 20%.

Map the activation journey for [persona]. At each step: the friction point, the emotional state, and the single action that most predicts retention.

Design a retention loop for [product] using the Hook Model. Identify: trigger, action, reward, and investment.

Our D7 retention is [X]% and D30 is [Y]%. Benchmark vs. industry standards for [category]. Diagnose the gap and suggest 3 product interventions ordered by expected impact.

Assess the viral potential of [product]. Calculate our current K-factor if viral loops exist. Design one new viral loop and estimate its impact.

We're considering [monetization model] for [product]. Analyze: user impact, revenue potential, implementation complexity, risk to existing metrics. Go/no-go?

Design a pricing experiment for [product tier]: hypothesis, control, variant, primary metric, guardrail metrics, how long to run it.

Design a referral program for [product]: referral mechanic, incentive structure, trigger moments, success metrics.

Evaluate [product] for a PLG motion. What features support self-serve? What needs to change? What's the first PLG experiment to run?

Design a freemium strategy for [product]. What's free (enough value), what's paid (expansion triggers), how does free drive upgrades?

Identify 10 high-intent search topics for [product] where a free tool or content could attract our target user. Include: topic, estimated intent, content type, conversion path.

Generate 10 growth experiment ideas across acquisition, activation, and retention. For each: hypothesis, change, metric, risk level.

Analyze whether [product] has or can build network effects. What type? How do we design for it, and what's the cold start strategy?

Design a churn prevention playbook: early warning signals, automated interventions, manual outreach triggers, and win-back campaigns for churned users.

Our ARPU is [X]. Design 3 expansion revenue strategies (upsell / cross-sell / seat expansion) and estimate the incremental ARR potential of each.

We're expanding to [new market/segment]. Assess: market size, competitive landscape, product gaps, GTM approach, and recommended entry strategy.

Review this landing page copy: [paste]. Rewrite to improve conversion: sharpen value proposition, reduce friction, add a stronger CTA.

Segment users into: power, casual, dormant, at-risk. For each: the most impactful product or marketing action to take.

Write a GTM strategy for [feature/product]: target segment, messaging, channels, launch sequence, and 30/60/90 day success metrics.

Design a pricing research study using Van Westendorp's Price Sensitivity Meter: the 4 questions, how to analyze results, how to set price points.

We're expanding to [market]. Assess: local competitive landscape, pricing, localization requirements, recommended GTM approach.

Design an ecosystem/partner strategy for [product]. What types of partners (technology, channel, data) create the most value? How do we recruit and enable them?

Design the optimal growth team structure for [stage: seed/series A/series B+]. What roles are needed, how does growth interact with product, what's the operating cadence?

Analyze how to monetize different user cohorts differently. Which cohorts have highest WTP? What triggers upgrade? How do we sequence the monetization ask?

Design a community strategy that drives product growth. What type of community, what platform, what content, and how does community loop back into product?

Design a personalization strategy for [product]. What signals will we use, what experiences will be personalized, and how will we measure impact vs. the non-personalized baseline?

Build a growth model for [product]. Define: inputs (acquisition, activation, retention, churn), the compounding logic, and the lever with the highest sensitivity.

Design a lifecycle marketing strategy for [product]. Define: stages (lead, trial, active, at-risk, churned), trigger, message, and channel for each.

We serve both enterprise ([B2B segment]) and consumers ([B2C segment]). How should our growth strategy differ for each? Where do they share tactics and where do they diverge?

Design 3 onboarding experiments to improve activation by [X]%. Each should test a different hypothesis about where users are failing to reach their aha moment.

Redesign [feature] to create a stronger daily habit loop. What is the trigger? How do we shorten the path to action? What variable reward are we offering?

Design an in-product upsell experience for [product] that converts free users to paid. What's the trigger moment? The message? The offer? The friction-reduction steps?

A competitor recently lost users due to [event]. How do we design a campaign to capture those users? What's the message, landing experience, and onboarding path?

Design a win-back campaign for users churned in the last 90 days. What is the message, the offer, the channel, and the re-onboarding experience?

Our NPS is [X]. Analyze this NPS verbatim data: [paste]. Identify the top 3 detractor themes and design one product change to address each.

Design a monthly growth review meeting for [product]. What metrics to cover, what decisions to drive, how to distinguish signal from noise.

Review this pricing page: [paste/describe]. What psychological pricing principles are we missing? Rewrite the structure to improve upgrade conversion.

We acquire users from [list channels]. Design a channel attribution experiment to understand which channels produce the highest LTV users, not just the most users.

Write a 6-month product strategy memo for [product]: where we are, where we're going, the bets we're making, what we're not doing, and how we'll know if we're winning.

Challenge our current strategy: [paste]. What assumptions could be wrong? What competitive threats are we underestimating? What opportunities are we missing?

Write a job description for a [Senior PM / APM / GPM] role. Include: the charter, problems they'll own, required skills, and the interview process.

Design a 90-day onboarding plan for a new PM. Week-by-week: what to learn, who to meet, what to deliver by day 90.

I'm mentoring a junior PM who is struggling with [specific challenge]. Give me a coaching framework, 3 guiding questions, and a development activity.

A PM on my team received this 360 feedback: [paste]. Help me structure a growth conversation: what to acknowledge, what to challenge, what development plan to co-create.

Facilitate a team prioritization session for [list of initiatives]. What framework? How do I prevent HiPPO dynamics? Design the session agenda.

Write 5–7 product principles for [product/team] that guide daily decisions, resolve trade-offs, and reflect our user and business values.

Write a performance review for a PM with this evidence: [paste accomplishments + feedback]. What they achieved, how they worked, growth areas, recommended next steps.

Design a product culture ritual that builds: user empathy, data literacy, and cross-functional collaboration. Lightweight (< 1 hour/week) and sustainable.

Write a strategic narrative for [product] for a company all-hands. Connect: market opportunity, our unique position, what we're building, how every team contributes.

Map a career development plan for a PM going from [current level] to [next level]: skills to develop, experiences to seek, milestones in 12 months.

Design a feedback framework for my product team: how we give feedback on PRDs, designs, and strategies; frequency; format; psychological safety.

What product operations processes should a [stage: early-stage / scaling / enterprise] PM team have? Design a lightweight but effective operating cadence.

I need to communicate a major product pivot to my team. Write a message that: explains the why, acknowledges impact, reframes the opportunity, motivates action.

I'm a new PM joining [company/team]. Design my 30-60-90 day plan to: build relationships, earn trust, understand the product, and make an early visible impact.

Identify the top 5 product risks for [initiative] across: technical, market, execution, organizational. Rate likelihood and impact, and define mitigation.

Design an innovation process for [team]: from unstructured idea to validated bet. Include ideation, filtering, validation, and go/no-go criteria.

What are the 5 most common mistakes PMs make when writing PRDs? Give a before/after example for each and a self-review checklist.

I'm facing a high-stakes decision: [describe]. Walk me through a structured decision-making framework: information needed, trade-offs to weigh, how to make the call with confidence.

Write a product vision presentation for a company all-hands. Inspire, be specific enough to guide decisions, and connect individual work to the bigger picture.

Explain [technical concept: APIs / databases / ML models / microservices] in a way that helps me be a better PM — focus on product implications, not code.

Design a monthly product review meeting for [team]. What to cover, who attends, what materials to prepare in advance, how to make it actionable.

We want to integrate AI/ML into [feature]. Think through: the user problem it solves, data requirements, trust and transparency considerations, success metrics.

A competitor just launched [feature]. Walk me through: immediate assessment, stakeholder communication, product decision framework, and communication plan.

Design a continuous discovery cadence for my team. How often to talk to users, what questions to always ask, and how insights flow into the roadmap.

I'm transitioning from [role: engineering / design / marketing] to PM. What skills transfer? What gaps do I need to close? Design a 6-month self-development plan.

Review [feature/product] through an ethics lens. What potential harms to users, vulnerable populations, or society? How should we design to mitigate these risks?

Assess my team's health across: clarity of vision, quality of discovery, execution speed, cross-functional relationships, PM growth. Design a quarterly health check.

Design a full PM hiring process: job description, screening criteria, interview stages, case study design, debrief process, offer criteria.

I just joined as Head of Product. Design my 90-day plan: what to learn, who to meet, what to assess, what quick wins to pursue, and what NOT to change yet.

How do I build a culture of experimentation in a risk-averse organization? What mindset shifts, processes, and structural changes are needed?

Audit our current PM tool stack: [list tools]. Are we over/under-tooled? What gaps exist? What should we consolidate, add, or remove?

I manage a portfolio of [X] products. Design an operating model: how to allocate resources, run portfolio reviews, and make investment decisions across products.

Design a PM career ladder for [company]. Define levels from Associate PM to VP Product: competencies, scope of ownership, impact expected, promotion criteria.

How should PMs be using AI tools in their day-to-day work? Design a practical guide: best use cases, prompt patterns, and where NOT to rely on AI.

Design the annual strategic planning process for my product org. Timeline, inputs needed, sessions to run, output format, and how the plan gets socialized and tracked.

My team has poor documentation habits. Design a documentation framework: what to document, templates for each type, when to write it, and how to keep it current.

Design a product scorecard for [executive/board]. What 6–8 metrics tell the story of product health and momentum? How should they be visualized and updated?

I'm deciding whether to promote [PM] to [next level]. What evidence should I look for? Design a leveling rubric and evaluate their readiness based on this evidence: [paste].

How do I build psychological safety in my product team so that people share bad news early, challenge each other's ideas, and bring their best thinking?

Facilitate a team OKR-setting workshop for Q[X]. What's the agenda, the exercises to run, how do we avoid gaming KRs, and how do we get to consensus?

I disagree with a strategic decision my manager made about [product area]. How do I raise this constructively, make my case with evidence, and accept the outcome either way?

We have 3 PMs working on overlapping product areas. Design a collaboration model: how do we align on shared outcomes, resolve conflicts, and avoid duplicating work?

I'm building out my product org. Should I organize PMs by: feature area, user segment, product stage, or cross-functional mission? Design the optimal structure for [company stage].

My PM team is showing signs of burnout: [describe]. What are the root causes to investigate, and what structural and cultural changes would reduce burnout sustainably?

Our product org is being reorganized. Help me think through: how to communicate the change to my team, what to protect, and how to maintain momentum during the transition.

Help me write OKRs for my PM team itself — not for the product, but for the team: research quality, shipping velocity, stakeholder trust, and PM skill development.

Assess the maturity of our product organization across: strategy clarity, discovery quality, delivery predictability, and cross-functional collaboration. Design a 90-day improvement plan.

I just interviewed a PM candidate. Help me write a structured debrief: strengths, weaknesses, hiring recommendation, and the one thing that most influenced my decision.