Best AI Prompts for Product Managers in 2026 (25 Copy-Paste Prompts)

**Prompt 1: PRD Writer** Use this when: you need to write a full Product Requirements Document and want a clean, structured first draft to work from. Write a Product Requirements Document (PRD) for the following feature. Feature name: [feature name — e.g., 'In-App Notification Center' / 'Bulk CSV Export' / 'Role-Based Permission System']. Product context: [describe your product, the current state of this area, and why this feature is being built now]. Target users: [who this feature is for — role, segment, use case]. Problem being solved: [what frustration or need this addresses — be specific]. Desired outcomes: [what success looks like — user behavior change, metric movement, business impact]. Known constraints: [technical, legal, timeline, or resource limits]. The PRD should include: (1) Overview — 1-paragraph summary of the feature and its business rationale, (2) Problem statement — the user pain in specific, observable terms, (3) Goals and success metrics — what we're trying to achieve and how we'll measure it, (4) Scope — what's in and explicitly what's out of scope for this version, (5) User stories — the primary flows in 'As a [user], I want to [action] so that [outcome]' format, (6) Functional requirements — specific system behaviors organized by user action, (7) Non-functional requirements — performance, security, accessibility, (8) Open questions — the decisions still to be made and who owns them, (9) Out of scope / future considerations. Format as a structured document with clear section headers. Why it works: PRDs written without structure get read inconsistently across engineering, design, and QA. A well-structured PRD with explicit scope and open questions prevents the mid-sprint alignment failures that cost teams weeks.

**Prompt 2: User Story Generator** Use this when: you have a feature or capability defined and need to break it down into well-formed user stories that engineering and design can work directly from. Generate a complete set of user stories for the following feature. Feature description: [describe what the feature does and the user need it addresses]. Primary user types: [list the different roles or personas who will use this feature]. For each user story: (1) Format as 'As a [specific user type], I want to [specific action], so that [specific outcome],' (2) Include an explicit acceptance criteria section with 3-5 specific, testable conditions that define 'done,' (3) Flag dependencies — other stories or systems this story depends on, (4) Estimate relative complexity as small / medium / large / extra-large with a one-sentence rationale. Organize stories by: (1) Happy path — the primary flow for the most common user, (2) Edge cases — non-standard but valid user behaviors the system must handle, (3) Error states — what happens when something goes wrong. Highlight the top 2-3 stories that are most critical to validate early. Why it works: User stories without explicit acceptance criteria are the leading cause of ambiguous delivery and QA gaps. Generating the full set — including edge cases and error states — upfront prevents the 'oh we didn't think of that' discoveries that appear in staging.

**Prompt 3: Acceptance Criteria Writer** Use this when: you have a user story or feature requirement and need to write tight, testable acceptance criteria that QA and engineering can use as a clear definition of done. Write detailed acceptance criteria for the following user story or feature requirement. Story / requirement: [paste the user story or requirement]. System context: [describe the relevant system state, user permissions, or pre-conditions]. For each acceptance criterion: (1) Write in Given/When/Then format — 'Given [precondition], When [action], Then [expected result],' (2) Be specific enough that a QA engineer could write a test case from it without asking a follow-up question, (3) Cover: happy path (expected behavior), edge cases (boundary conditions, unusual but valid inputs), error states (what happens when inputs are invalid or the system fails), and permissions (what different user roles can and cannot do). Group criteria by: primary flow, edge cases, error handling, and permissions. Flag any criteria that require a product decision to complete (mark as [OPEN QUESTION]). Why it works: Vague acceptance criteria produce vague testing. Given/When/Then format forces specificity at every condition and makes it impossible to ship a feature as 'done' without confirming the exact behaviors the PM intended.

**Prompt 4: Feature Specification** Use this when: engineering or design needs more technical detail than a PRD or user story provides — a precise description of how a feature should behave across all states, interactions, and system conditions. Write a detailed feature specification for the following capability. Feature: [name and brief description]. User-facing behavior: [describe what the user sees and can do — every interaction, every state, every response]. System behavior: [describe what the system does behind the scenes — data created, updated, or deleted; APIs called; calculations performed; state changes triggered]. States and transitions: [describe every state this feature can be in and how it transitions between states — e.g., empty state, loading state, error state, success state, disabled state]. Edge cases to handle: [list any non-standard conditions the spec must address]. Data and storage: [what data is created, where it's stored, how long it's retained, and who can access it]. Permissions: [which user roles can see and do what]. Dependencies: [other features, systems, or services this depends on]. Format as a technical spec document that an engineer could implement from without a follow-up meeting. Why it works: Feature specs that stop at 'the user can do X' leave engineers making product decisions during implementation — and those decisions are rarely reviewed. A complete spec that addresses every state and edge case eliminates the most common source of PM/engineering misalignment.

**Prompt 5: Edge Case Analysis** Use this when: you've defined a feature and want to systematically surface the edge cases, failure modes, and unusual scenarios that could produce unexpected behavior before engineering begins. Conduct a thorough edge case analysis for the following feature. Feature description: [describe the feature — what it does, who uses it, what inputs it accepts]. For each edge case category, identify the specific scenarios that could cause problems and describe the intended handling for each: (1) Input edge cases — empty inputs, null values, maximum length, special characters, invalid formats, (2) User state edge cases — users with no data, users with maximum data, users with incomplete profiles, users with multiple roles, (3) Permission edge cases — what happens when a user tries to take an action they don't have permission for, (4) Concurrency edge cases — what happens if two users act on the same data simultaneously, (5) Network/system edge cases — what happens if a downstream service is slow, returns an error, or is unavailable, (6) Time-based edge cases — what happens with time zones, daylight saving, leap years, long-running sessions, (7) Data integrity edge cases — what happens if referenced data is deleted, edited, or in an inconsistent state. For each edge case: describe the scenario → the risk if unhandled → the recommended handling. Flag any edge cases that require a product decision rather than an engineering fix. Why it works: Edge cases discovered in production cost 10x more to fix than edge cases caught before sprint. A systematic analysis — organized by category — surfaces the scenarios that assumption-based planning misses.

**Prompt 6: Exec Summary Writer** Use this when: you need to brief an executive or leadership team on a product decision, initiative status, or strategic recommendation — and want the message to land in under 3 minutes of reading time. Write an executive summary for the following. Topic / decision: [describe what you're briefing leadership on — e.g., 'the recommendation to delay Feature X by one sprint' / 'Q3 roadmap priorities' / 'the outcome of our user research on checkout friction']. Key context: [what the executive needs to know to understand the summary — assume they haven't been close to the detail]. Recommendation or key finding: [what you want them to take away or decide]. Supporting evidence: [the 2-3 strongest data points or rationale behind your recommendation]. What you need from them: [a decision, a budget approval, alignment, visibility]. The executive summary should include: (1) The headline — one sentence that states the conclusion or recommendation, (2) Context — 2-3 sentences of necessary background, (3) The recommendation / finding — stated directly with your level of confidence, (4) Supporting evidence — 3 bullets maximum, (5) The ask — what you need from this audience and by when. Total length: under 200 words. Lead with the conclusion. No buried lede. Why it works: Executives don't read for context — they read for signal. A summary that buries the recommendation in paragraph 4 gets ignored or acted on incorrectly. Leading with the conclusion and limiting supporting evidence to three points is the format that gets decisions made.

**Prompt 7: Sprint Review Update** Use this when: you need to communicate sprint outcomes to stakeholders — what shipped, what didn't, what moved, and what's coming next — in a format that builds confidence without requiring a live meeting. Write a sprint review update for [sprint number/name]. Audience: [who receives this — e.g., engineering leadership / the executive team / cross-functional stakeholders]. What shipped this sprint: [list the features, fixes, or deliverables completed]. What didn't ship (and why): [list items that didn't make it and the honest reason — deferred by choice, blocked, scope-expanded, or discovered to be more complex than estimated]. Key metrics or signals from what shipped: [any early data, user feedback, or signals from features that went live]. What's coming next sprint: [the current top priorities and why]. Known risks for the next sprint: [anything that could cause the same problems again]. Format as a scannable update — use section headers, bullet points, and plain language. Under 400 words. Tone: direct, transparent, confident. Avoid 'we tried our best' language. Why it works: Sprint reviews that only celebrate what shipped and avoid addressing what didn't erode stakeholder trust over time. A transparent, direct update — including honest explanations for misses — builds more confidence than an unbroken success narrative.

**Prompt 8: Roadmap Communication** Use this when: you need to share the product roadmap with stakeholders — internal teams, leadership, or customers — and want to communicate the 'why' behind priorities, not just the 'what.' Write a roadmap communication document for the following product area. Audience: [who this is for — internal team / executive leadership / customers / investors]. Roadmap timeframe: [now/next/later OR Q3/Q4/H1 next year — whatever framing you use]. Priorities: [list your current roadmap themes or specific initiatives, in priority order]. Rationale for priorities: [why these are the right things to build now — user research, business metrics, strategic direction, competitive pressure]. What's explicitly not on the roadmap (and why): [things that have been asked for but aren't prioritized — and the honest reason]. Format as: (1) A 2-paragraph framing section that explains the strategic context and how these priorities connect to the product vision, (2) A 'Now' section — what we're actively building and why it matters, (3) A 'Next' section — what's coming in the following cycle and the key dependency or milestone that unlocks it, (4) A 'Later / Exploring' section — areas we know matter but haven't scoped, (5) A 'Not now' section — specific requests that are off the roadmap with one-sentence rationale for each. Tone: transparent and confident. Avoid vague commitments. Why it works: Roadmaps communicated as lists of features get challenged on every item. Roadmaps communicated with explicit rationale for what's in and what's out build stakeholder trust and reduce the volume of roadmap lobbying over time.

**Prompt 9: Saying No to Feature Requests** Use this when: you need to decline a feature request — from a stakeholder, a customer, or an internal team — in a way that's clear, respectful, and doesn't create resentment or the expectation that you'll revisit the decision. Help me write a response declining the following feature request. The request: [describe the feature request — what was asked for, who asked, and in what context]. Why we're not building it: [the honest reason — not the priority right now, not aligned with the product strategy, technically too expensive, too narrow a use case, overlaps with a different planned feature]. What I want to preserve: [the relationship, the stakeholder's sense of being heard, their willingness to continue sharing feedback]. The response should: (1) Acknowledge the underlying need — what problem the requester is trying to solve, (2) Explain the decision clearly — not vaguely or apologetically, (3) Provide the real reason if shareable, or the appropriate level of context if not, (4) Offer an alternative if one exists — a workaround, a different feature in progress, or a timeline for reconsideration, (5) Close in a way that keeps the feedback loop open without creating false hope. Format as an email reply, under 200 words. Tone: direct, respectful, confident. Why it works: Feature request declines that are vague ('that's on our radar!') or over-apologetic train stakeholders to keep pushing. A clear, confident no that acknowledges the underlying need and explains the reasoning produces fewer follow-ups and maintains more trust than a soft non-answer.

**Prompt 10: Cross-Functional Alignment Brief** Use this when: you're kicking off work that requires alignment across multiple teams — engineering, design, marketing, sales, legal — and want to establish shared context and clear ownership before the work begins. Create a cross-functional alignment brief for [initiative name]. Context: [describe the initiative — what it is, why it matters now, the timeline]. Teams involved: [list each team and their role in the initiative — e.g., engineering (building), design (UX and visual), marketing (launch), legal (compliance review), sales (enablement)]. Key decisions already made: [what is locked]. Open decisions: [what still needs to be decided, and by whom]. The brief should include: (1) Initiative summary — one paragraph on what we're doing, why, and by when, (2) Goals — what success looks like in measurable terms, (3) Roles and responsibilities — who owns what, who needs to be consulted, who needs to be informed (RACI format), (4) Timeline and milestones — key dates and dependencies between teams, (5) Open questions — decisions that need to be made before work can proceed, with owners, (6) Communication plan — how often teams will sync and how status will be shared. Format as a one-page working document that each team can use as a source of truth throughout the initiative. Why it works: Cross-functional work fails most often in the first two weeks — not because teams can't execute, but because alignment was assumed rather than built. A shared brief that makes ownership and open questions explicit before work begins prevents the mid-initiative realignments that cost the most time.

**Prompt 11: Interview Question Generator** Use this when: you're preparing for a round of user interviews and want a set of questions that will surface the most relevant insights — without leading the witness or getting surface-level answers. Generate a set of user interview questions for the following research goal. Research goal: [what you're trying to learn — e.g., 'understand why users abandon checkout before completing payment' / 'explore how data analysts currently manage their reporting workflow' / 'identify the biggest friction points in the onboarding experience for new admins']. Target user: [describe who you'll be interviewing — role, company type, experience level, any relevant behavioral segments]. What we already know or believe: [your current hypotheses — so questions can challenge rather than confirm them]. Format the questions in three sections: (1) Warm-up questions (3-4) — low-stakes questions about background and context that build rapport, (2) Core discovery questions (8-10) — open-ended, behavior-focused questions that get at the research goal without leading the respondent; avoid questions with a yes/no answer; ask about what people do, not what they think they would do, (3) Closing questions (2-3) — 'What else should I know?'-style questions that surface what you didn't know to ask. After each question, add a brief note on what insight it's designed to surface and any common follow-up probes. Why it works: Interview questions written the night before an interview tend to be either too leading (confirming what you already believe) or too open (producing tangents instead of insight). A structured set designed to challenge hypotheses and focus on behavior produces research that changes your thinking.

**Prompt 12: Research Synthesis** Use this when: you've completed a round of user interviews, usability tests, or observations and have raw notes you need to turn into actionable insights — fast. Help me synthesize the following user research findings. Research method: [interviews / usability testing / contextual inquiry / diary study]. Number of participants: [how many]. Raw notes or key observations: [paste your notes, verbatim quotes, or behavioral observations — as rough as you have them]. Research goal (what we were trying to learn): [restate your research question]. Synthesis should produce: (1) Top 3-5 themes — patterns that appeared consistently across participants, with supporting evidence (direct quotes or observed behaviors, not your interpretations), (2) Key insights — what the themes tell us that we didn't know before, stated as insight statements ('Users don't [X], they actually [Y]'), (3) Surprises — findings that contradicted our hypotheses, (4) Gaps — what we still don't know after this round of research, (5) Recommended next steps — the most important product or research actions implied by these findings. Format as a structured synthesis document that could be shared with the broader product team. Why it works: Research synthesis done in your head produces findings shaped by confirmation bias. A structured synthesis that separates evidence from interpretation — and explicitly surfaces surprises and gaps — produces more reliable, more useful insights.

**Prompt 13: Survey Question Writer** Use this when: you need to write a survey — for a product feedback flow, a post-onboarding NPS survey, a feature satisfaction check, or a market research study — and want questions that will produce valid, actionable data. Write survey questions for the following research goal. Survey goal: [what you're trying to measure — e.g., 'satisfaction with the new reporting feature' / 'likelihood to recommend after 90 days' / 'most important features for a new segment of potential users']. Audience: [who will complete the survey — existing users / churned users / prospects / a specific segment]. Distribution method: [in-app / email / embedded / link]. Target completion time: [how long the survey can be — 2 min / 5 min]. For each question: (1) Write the question and any necessary framing, (2) Specify the question type (Likert scale / multiple choice / ranking / open text / NPS), (3) Note what the response is designed to measure and how the data will be used, (4) Flag any common survey question pitfalls this question avoids (double-barreled, leading, jargon). Include a survey flow recommendation: question order, any skip logic, and a closing open-text question. Max questions: [your limit]. Optimize for completion rate and data quality over comprehensiveness. Why it works: Surveys written quickly tend to ask too many questions, use leading language, and conflate multiple measures in single items. A structured, question-by-question approach with explicit measurement intent produces data you can actually act on.

**Prompt 14: Customer Feedback Theme Analysis** Use this when: you have a batch of qualitative customer feedback — from NPS surveys, support tickets, reviews, interviews, or sales calls — and need to surface the main themes and prioritize what they mean for the product. Analyze the following customer feedback and surface the main themes. Feedback source: [describe where this came from — e.g., 'open-text responses from our Q2 NPS survey' / 'support ticket descriptions from the past 30 days' / 'sales call notes from accounts that churned']. Number of items: [how many feedback items]. Product context: [what your product is and the user segment this feedback comes from]. Feedback: [paste the raw feedback — verbatim quotes, ticket descriptions, or summarized observations]. Produce: (1) Top 5 themes — the most frequently occurring patterns, each with a label, a clear description, the number of feedback items supporting it, and 2-3 representative direct quotes, (2) Severity assessment — for each theme, assess whether it's a friction point (annoying but not blocking), a blocker (preventing users from achieving their goal), or a missing capability (something users need that doesn't exist), (3) Quick wins — themes that could be addressed with low engineering effort, (4) Strategic implications — themes that suggest a larger product direction or repositioning, (5) What to watch — themes that are low volume now but worth monitoring. Why it works: Unstructured feedback review produces findings anchored to the most recent or most emotionally salient items. A systematic theme analysis with frequency counts and severity assessment produces a more accurate picture of what actually matters to users.

**Prompt 15: Jobs-to-Be-Done Statement** Use this when: you need to articulate the underlying job a user is trying to get done — separate from the feature or solution — to sharpen the product direction and align the team on what problem they're actually solving. Write a Jobs-to-Be-Done (JTBD) statement for the following user and context. User: [describe the user — role, industry, experience level, relevant context]. Situation: [describe the specific context in which this user faces the problem — when does this come up, what are they trying to accomplish, what's at stake]. What they're currently doing: [how they currently handle this situation — the workarounds, tools, or processes they use today]. Pain with the current approach: [what's frustrating or limiting about the current solution]. Desired outcome: [what 'done well' looks like — not a feature, but the outcome the user is trying to achieve]. Write: (1) A primary JTBD statement in the format: 'When [situation], I want to [motivation], so I can [expected outcome],' (2) The functional dimension — the practical task being completed, (3) The emotional dimension — how the user wants to feel while doing this task, (4) The social dimension — how the user wants to be perceived by others in connection with this task, (5) The competing solutions — what alternatives the user has, including the option of doing nothing. Explain how each dimension should influence product decisions. Why it works: Features built around assumed user needs often solve the wrong problem. JTBD statements that separate the job from the solution force the team to validate whether what they're building actually addresses the underlying motivation — not just the stated request.

**Prompt 16: RICE Scoring Framework** Use this when: you have a backlog of features or initiatives to prioritize and want a structured scoring framework that makes the comparison between items more objective and the rationale transparent. Build a RICE scoring framework for the following backlog items. RICE stands for Reach, Impact, Confidence, and Effort. Backlog items: [list the features or initiatives you're prioritizing — at least 3]. Product context: [what your product is, the user base size or monthly active users, and the business goals for this quarter]. For each backlog item, produce: (1) Reach estimate — how many users or accounts this will affect in the relevant time period (e.g., per quarter), with your rationale for the estimate, (2) Impact score — on a scale where 0.25 = minimal, 0.5 = low, 1 = medium, 2 = high, 3 = massive — the improvement per user who is affected, (3) Confidence level — as a percentage (100% = certain, 80% = high confidence, 50% = medium, 20% = low) reflecting confidence in the reach and impact estimates, (4) Effort estimate — in person-weeks or story points for the full team, (5) RICE score = (Reach × Impact × Confidence) / Effort, (6) A one-sentence rationale for each estimate that would hold up in a prioritization debate. Present as a scoring table with all items ranked by RICE score. Flag any items where the confidence score is the key differentiator. Why it works: Prioritization debates without a shared scoring framework devolve into the loudest voice or the most senior stakeholder winning. RICE forces every item through the same lens and makes the key assumptions explicit — so disagreements become debates about the right score, not about gut feel.

**Prompt 17: Roadmap Prioritization Rationale** Use this when: you've made a prioritization decision and need to write the rationale — for documentation, for stakeholder alignment, or for leadership review — in a way that's clear, defensible, and honest about tradeoffs. Write a roadmap prioritization rationale for the following decisions. Prioritization context: [describe the prioritization cycle — Q3 planning / a specific roadmap decision / a trade-off you're making between two competing priorities]. Items selected for the roadmap: [list what you're building and a brief description of each]. Items not selected (and why): [list what you're not building and the reason]. Decision criteria used: [describe how you prioritized — user impact, revenue potential, strategic fit, technical debt, etc.]. The rationale should include: (1) The strategic context — what the team is optimizing for in this period and why, (2) For each item on the roadmap — why it made the cut (1-2 sentences per item linking it to the criteria), (3) For the top 2-3 items not selected — a clear, honest explanation of why they didn't make the cut, (4) Key trade-offs — what you're explicitly choosing not to do and the accepted cost of that choice, (5) Assumptions — what would have to be true for this to be the right set of priorities. Format as a document that stands on its own without a live explanation. Why it works: Roadmap decisions without written rationale get relitigated every sprint. A documented rationale that explicitly addresses what was cut and why reduces the volume of roadmap challenges and builds trust with stakeholders who didn't get what they wanted.

**Prompt 18: Competitive Analysis** Use this when: you need to write up a competitive analysis — for a strategy doc, a board briefing, an exec review, or to inform a product decision — that goes beyond feature comparisons to strategic positioning. Write a competitive analysis for [your product] in the context of [specific product decision or strategic question — e.g., 'whether to build native reporting or integrate with BI tools' / 'how to position against Competitor X in the mid-market' / 'whether to expand into the [X] use case']. Competitors to analyze: [list 2-4 competitors]. For each competitor: (1) Brief profile — product focus, target customer, pricing model, and company stage, (2) Their approach to [the specific capability or market area in focus], (3) Where they're stronger than us — be honest and specific, (4) Where we're stronger — with evidence, not wishful thinking, (5) Their likely move in the next 12 months based on what you know. Synthesis section: (1) The competitive white space — what none of them are doing well that customers need, (2) The risk — where competitive pressure is most likely to affect our position, (3) The strategic implication — what this analysis suggests we should do differently or prioritize. Format as an analytical document, not a feature comparison table. Why it works: Feature comparison tables show where you're behind but don't tell you what to do about it. A positioning-focused competitive analysis surfaces the strategic choices implied by the competitive landscape — which is the insight leadership actually needs.

**Prompt 19: OKR Drafting** Use this when: you're writing OKRs for your product area — for a quarter, a half, or a year — and want a structured set of objectives and key results that are ambitious, measurable, and genuinely connected to product strategy. Draft OKRs for the following product area. Product area: [the part of the product you own — e.g., 'the onboarding experience' / 'the core analytics product' / 'the enterprise collaboration features']. Strategic context: [what the company or team is trying to achieve this period — the one or two priorities above your OKRs]. Current state: [where you are now — relevant metrics, user behavior, known problems]. What success looks like in [the OKR period — Q / H / year]: [describe the outcome you're shooting for in plain terms — not the metric yet]. For each objective: (1) Write an objective that is inspiring, action-oriented, and qualitative — not a metric, (2) Write 3-4 key results per objective that are: specific, measurable (with a target number and current baseline), owned (clear which team or metric this belongs to), and ambitious but achievable (70% success rate is healthy), (3) Flag any key results that require alignment with another team to achieve. Include a brief 'why this quarter' rationale for each objective — why now, not next quarter. Avoid vanity metrics. Why it works: OKRs written as metric lists ('increase DAU by 15%') without an inspiring objective produce compliance, not commitment. OKRs with a clear connection between the strategic context, the objective, and the measurable key results produce teams that understand what they're optimizing for and why.

**Prompt 20: Opportunity Sizing** Use this when: you need to estimate the size of a market opportunity, a user segment, or a potential product investment — to inform a prioritization decision, a business case, or a resource request. Help me size the following opportunity. Opportunity: [describe what you're sizing — a new user segment, a new use case, a potential expansion into a new market, a feature investment]. What we know: [share any data you have — user counts, survey results, support volume, market research, comparable company data]. What we're trying to determine: [the specific question — e.g., 'How many customers could this feature affect?' / 'What's the revenue potential if we address this use case?' / 'How large is the market for this problem?']. Build a bottom-up sizing model that includes: (1) The addressable population — how many total users, companies, or people face this problem, (2) The serviceable portion — of those, how many are reachable by our product and team, (3) The realistic capture — of the serviceable portion, what percentage we could reasonably win and in what timeframe, (4) The value per unit — revenue, engagement, or retention value per converted user or account, (5) The total opportunity — the ceiling and the realistic near-term number. Make assumptions explicit and show your math. Identify the 1-2 assumptions that most affect the outcome and describe how sensitive the estimate is to changes in each. Why it works: Opportunity sizing done without an explicit model produces either over-optimism (the market is huge!) or paralysis (we can't know for certain). A transparent bottom-up model with explicit assumptions produces an estimate that can be debated and refined — which is what actually moves decisions.

**Prompt 21: PM Interview Prep** Use this when: you have a product management interview coming up and want to prepare structured answers to the most common PM interview question types — product design, metrics, estimation, and strategy. Help me prepare for a product management interview at [company name / company description — e.g., 'a Series B fintech startup' / 'a large platform company' / 'a B2B SaaS company']. Role level: [APM / PM / Senior PM / Group PM / Director]. My background: [brief description of your current role and experience]. For each of the following question types, provide: (1) The question, (2) A structured framework for answering it, (3) An example of how I would apply the framework using a product from my experience. Question types: (a) 'Design a product for [user]' — include: clarify goals → define user → identify pain points → prioritize use cases → design core feature set → define success metrics, (b) 'How would you improve [product]?' — include: understand current state → identify user pain → generate solutions → prioritize → measure, (c) 'What metrics would you use to measure [feature]?' — include: goal of the feature → input metrics → output metrics → guardrail metrics, (d) 'Estimate [quantity]' — include: clarify the question → decompose into estimable components → calculate → sense-check, (e) A behavioral question: 'Tell me about a time you had to make a difficult prioritization decision.' Format each as a prep card with the framework, a worked example, and 2-3 things to avoid. Why it works: PM interviews are structured around well-known question types with expected frameworks. Systematic preparation across each type — not just the ones you feel confident about — is the primary driver of PM interview performance.

**Prompt 22: PM Resume Rewrite** Use this when: you're updating your resume for a PM role and want to translate your product experience into impact-forward bullets that demonstrate scope, judgment, and outcomes — not just tasks. Rewrite the following PM resume bullets for impact. Target role: [describe the role — level, company type, product focus]. My current bullets (rough): [paste your existing resume bullets]. For each bullet: (1) Lead with the outcome — what changed as a result of your work, with a metric where possible (e.g., 'Increased checkout completion rate by 18%' not 'Worked on checkout redesign'), (2) Show scope — the team size, revenue affected, user base, or scale of the decision, (3) Demonstrate PM-specific skills — where possible, surface the product judgment, cross-functional leadership, or discovery work behind the outcome, (4) Cut credential language — 'partnered with,' 'facilitated,' 'supported' are weak; replace with 'defined,' 'led,' 'owned,' 'reduced,' 'launched.', (5) For bullets without metrics: ask me the specific questions that would allow you to add them — what was the before/after, the timeline, the team size, the affected user segment. After each rewrite, explain the change and why it makes the bullet more compelling to a PM hiring manager. Why it works: PM resumes are evaluated by hiring managers who look for evidence of ownership, impact, and scale. Bullets written in task language ('helped design the onboarding flow') signal a supporting role; bullets written in outcome language ('redesigned onboarding, reducing time-to-first-value from 14 days to 3') signal ownership.

**Prompt 23: PM Offer Negotiation** Use this when: you have a PM job offer and want to negotiate — base, equity, signing bonus, or total comp — with a script that's grounded in your specific leverage and delivered in a way that protects the relationship. Write a PM offer negotiation script for the following situation. Offer received: [describe the offer — base, bonus, equity, level, company]. My current / competing compensation: [what you're making now or what a competing offer looks like]. My target: [what you're trying to achieve — specific numbers or ranges]. My strongest leverage: [what makes your ask reasonable — competing offer, specific experience, market data, scarcity of your skill set]. The script should cover: (1) How to respond to the offer without accepting or declining on the spot — and what to say in the moment, (2) The counter email — how to frame the ask using your specific leverage, with a clear number, without ultimatums, (3) How to handle 'That's the top of our band' — two responses depending on whether you want the job enough to accept at band top, (4) How to negotiate non-salary components if base is truly immovable — signing bonus, equity refresh, title, start date, remote work, (5) The close — how to accept once you're satisfied, in a way that sets up the relationship positively. Write in natural spoken and written language, not negotiation textbook language. Why it works: Most PMs are strong communicators in product work and weak negotiators for themselves. A prepared script that uses specific leverage — not generic 'I deserve more' framing — produces materially better outcomes without damaging the relationship.

**Prompt 24: Product Sense Portfolio** Use this when: you're building a portfolio of product thinking work — case studies, teardowns, product critiques, or concept designs — to demonstrate product sense to hiring managers or for a PM portfolio site. Help me build a product sense portfolio piece for [product or company — e.g., 'Airbnb's host experience' / 'Notion's onboarding flow' / 'Duolingo's streak mechanic']. Portfolio format: [teardown / redesign concept / improvement proposal / new feature design]. My target audience: [who will read this — PM hiring managers / a specific company / a product portfolio site]. The portfolio piece should include: (1) Context — brief product overview, the user segment in focus, and the scope of the analysis, (2) Problem identification — specific UX, behavioral, or business problems observed, with evidence (screenshots, data where available, or reasoned hypotheses), (3) Root cause analysis — why these problems exist (not just what they are), (4) Proposed solution — a specific, prioritized set of changes or a new feature concept, with rationale grounded in user needs and business goals, (5) Success metrics — how you would measure whether the proposed change worked, (6) Trade-offs and risks — what you're giving up or what could go wrong with this approach. Format as a structured case study that demonstrates product thinking, not just product opinions. Why it works: PM portfolios that are just opinions ('I would make the button bigger') don't demonstrate product thinking. Structured case studies that move from problem identification through root cause to prioritized solution with defined metrics show the systematic thinking that PM hiring managers are actually evaluating.

**Prompt 25: Career Transition into Product** Use this when: you're transitioning into product management from another role — engineering, design, marketing, consulting, operations — and want to build a compelling narrative and targeted action plan for breaking in. Help me build a career transition plan into product management. My background: [describe your current role, industry, and years of experience]. Transferable skills I want to highlight: [list the skills from your current role that are most relevant to product — e.g., technical depth from engineering / user empathy from customer success / analytical skills from data / commercial instincts from sales]. Target PM roles: [describe the type of PM roles you're targeting — company stage, product type, industry]. What I've done so far toward the transition: [any PM-adjacent work, side projects, courses, or relationships you've built]. The plan should include: (1) Narrative reframe — how to tell your story as a PM candidate, not as a career-changer; the specific 'why PM' framing that uses your background as an asset, (2) Gap analysis — what PM skills or experiences you're missing and the most efficient way to build them, (3) Portfolio strategy — what to build in the next 60-90 days to demonstrate product thinking (case studies, side projects, APM program applications), (4) Networking strategy — how to build PM connections in your target space, specifically leveraging your existing professional context, (5) Application strategy — which roles to target first (where your background is highest-leverage), how to position your resume, and which APM or rotational programs to consider, (6) 30/60/90 day action plan — specific actions with time estimates. Format as a working document I can return to and update. Why it works: Most career transition attempts into PM fail not because of missing skills but because of a missing narrative. Hiring managers see 'career changer' as a risk; a well-constructed story that positions your background as differentiated product experience changes the frame from liability to asset.