Prompt Guides for Product Managers
232 in-depth guides on using AI prompts across product strategy, discovery, delivery, and storytelling. Each guide explains when to use the prompt, how it works, and what to watch out for.
Career & Interview
23 guidesBuild a PM influence map for stakeholder strategy
You have no direct reports but need eight people across three functions to commit to your roadmap. This builds a stakeholder influence map — who decides, who recommends, who can block, who informs whom — so you spend your limited face-time with the people who actually move the decision.
Build a managing-managers operating rhythm
You were promoted from managing PMs to managing PM managers and everything you used to do — 1:1s with ICs, roadmap reviews, debugging launches — is now two levels deep and you can't do it directly. This builds a weekly, monthly, quarterly operating rhythm specific to the managing-managers job so you lead through them, not around them.
Draft a compensation negotiation script with BATNA
You got an offer and your instinct is to accept quickly. This drafts a negotiation script with your BATNA (best alternative), anchor, and fallback positions so you negotiate from specifics and leave with comp you'd be proud of in 12 months.
Draft a step-down or lateral move conversation
You realized the management track isn't for you and want to move back to IC — or move laterally into a different PM scope. This drafts the conversation with your manager so it lands as thoughtful career clarity, not a retreat.
Build a manager exit interview outline
You're leaving the company and your exit interview with your manager is scheduled for Friday. This builds an outline that shares useful feedback without burning bridges — what worked, what didn't, what you'd want the next PM to know.
Build a PM interview company research brief
You have a PM interview in 5 days and 2 hours to prepare. This builds a research brief — product, strategy, metrics, team, recent news — so you show up knowing more about the company than some internal candidates.
Run a 30-60-90 day plan for a new PM role
You just joined (or are joining) a new PM role and your manager asked for a 30-60-90. This builds one that's specific — listen in 30, validate in 60, lead in 90 — so you show up with a plan that your new team recognizes as thoughtful.
Conduct a personal brand audit for a PM job search
You're about to job search and your online presence is 3 years stale. This audits your personal brand — LinkedIn, portfolio, conference talks, writing — so recruiters and hiring managers find a coherent story when they search your name.
Design a product sense interview practice loop
Your product sense answers keep collapsing under follow-up probing. This designs a practice loop — question bank, timed answers, self-critique rubric, mock partner — so you build the muscle before the interview, not during it.
Build a PM career growth conversation template
Your next 1:1 with your manager is the career conversation you've been avoiding. This builds a structured template — current level, growth areas, evidence, asks — so you lead with data and leave with a written development plan instead of vague encouragement.
Conduct a peer-360 feedback synthesis
You received 5 peer reviews and the signal is conflicting — "too tactical" and "too strategic" in the same 360. This synthesizes the reviews into themes with evidence, identifies the 2 signals to act on, and decides what to respectfully ignore.
Conduct a manager feedback session before your review
Your formal review is in 4 weeks and you want to reduce surprises. This designs a mid-cycle feedback session where you actively collect feedback from your manager so the written review is a confirmation, not a revelation.
Build a PM portfolio with measurable impact bullets
Your resume has "managed the product" bullets that say nothing. This rewrites your bullets as measurable impact statements — action, context, measurable outcome, scope — so recruiters know what you actually did and senior PMs recognize it.
Design a growth plan for an IC-to-lead transition
You were the top IC PM and just got promoted to lead. Your old instincts — ship things, prove yourself, jump in — are now the wrong instincts. This designs a 90-day growth plan with explicit behavior shifts so you make the transition without regressing to IC comfort.
Write a PM resume quantification rewrite
Your PM resume has stories but no numbers. This rewrites each story into a quantified bullet — using metrics you can defend, ranges where exact numbers aren't shareable, and fallback qualitative signals — so the resume matches the bar senior reviewers expect.
PM Salary Negotiation Playbook
Prepare for PM salary negotiations with data-driven talking points, counter-offer scripts, and negotiation strategies tailored to your level and market. Covers base, equity, sign-on, and non-monetary levers.
PM Mock Interview Simulator
A full mock interview experience covering all PM interview rounds: product sense, execution, behavioral, and strategy. Simulates a 45-minute interview with realistic pacing, follow-ups, and a detailed scorecard.
PM Resume & Portfolio Optimizer
Optimize your PM resume for ATS systems and hiring managers. This prompt rewrites bullet points with quantified impact, maps your experience to the PM competency model, and identifies gaps to address.
How to Transition into Product Management
A structured guide for career changers who want to break into product management. Analyzes your current background, identifies transferable skills, and creates a personalized transition roadmap with concrete action items.
PM Interview: Strategy & Case Study
Practice product strategy case studies — the hardest PM interview question type. Covers market entry, competitive response, pricing, and growth strategy cases with frameworks to structure your thinking.
PM Interview: Behavioral STAR Method
Prepare compelling behavioral interview answers using the STAR method (Situation, Task, Action, Result). This prompt helps you structure your PM experiences into memorable stories that demonstrate leadership, cross-functional collaboration, and impact.
PM Interview: Fermi Estimation Practice
Practice estimation and market-sizing questions commonly asked in PM interviews. The prompt generates realistic Fermi estimation problems, then walks through a structured approach to solve them with clear assumptions and math.
PM Interview: Product Sense Practice
Practice product sense interview questions used at top tech companies. This prompt simulates a real interviewer who asks you to design or improve a product, then provides structured feedback on your answer using evaluation criteria from Google, Meta, and Amazon PM loops.
Delivery
52 guidesConduct a PM team meetings audit
Your PM team spends 18 hours a week in meetings and nobody can name what's shipping because of them. This runs an audit — every meeting's purpose, attendance cost, decision output — and produces a kill-or-redesign list so the team gets 6-10 hours back per PM per week.
Design a one-team-one-roadmap consolidation
Sales has a roadmap, CS has a roadmap, marketing has a roadmap, product has a roadmap, and none of them match. This runs a consolidation exercise that merges the five shadow roadmaps into one operating roadmap with shared ownership — so stakeholders stop making promises product can't keep.
Run a Product Hunt launch playbook
You are launching on Product Hunt in 3-4 weeks and your previous attempt got 20 upvotes because you hit publish and hoped. This builds the launch playbook — hunter selection, pre-launch audience warming, launch-day shift schedule, asset checklist — so the launch produces real signal instead of embarrassment.
Run a DRICE prioritization session with diligence scoring
RICE gave you a ranked list — and three of your top bets flopped last quarter because nobody pressure-tested the reach or impact numbers. DRICE adds a Diligence step that forces evidence for every R/I/C input before scoring, so the ideas that rise to the top earn it and your experiment win rate stops swinging on wishful guesses.
Conduct a feature sunset plan
A feature has 0.5% usage and costs 2 engineers/quarter to maintain. Support keeps getting tickets. The team keeps saying "we'll sunset it" and never does. This builds the explicit sunset plan — criteria, migration, notice period, kill date — so the project actually ships.
Design a 90-day launch metric review
Your launch hit its week-1 activation target and everyone moved on. 90 days later nobody can say whether the feature mattered. This designs a 90-day review that measures sustained engagement, business impact, and the cost of keeping the feature alive — so you can decide whether to double down or sunset.
Run a Shape Up style 6-week cycle kickoff
Your 2-week sprints are producing shallow work and endless ceremonies. This runs the Shape Up kickoff — shaped pitch, appetite check, small-team assignment, hill chart baseline — so the team has 6 weeks of undisturbed focus and a clear stop condition.
Design a go/no-go review template
Leadership needs a clear go/no-go decision and your 40-slide status deck buries it. This produces a 2-page template that forces a yes/no recommendation, lists the evidence and the specific risk, and ends every review with a binary decision — not with "let's revisit."
Run a pre-launch readiness review checklist
Launch day is 5 days out and the team is confident — which is when things break. This runs a pre-launch review across product, engineering, support, sales, marketing, and legal so you find the miss before customers do, not after.
Build a sprint planning facilitator agenda
Your sprint planning runs 90 minutes, everyone is checked out by minute 30, and the output is a backlog nobody believes. This runs a 45-minute structured agenda that aligns on goal, decomposes just enough, commits realistic scope, and ends with everyone knowing why each item is in.
Design a feature flag rollout plan with kill-switch
Ship-on-merge sounds brave until the first regression takes down prod. This designs a flag-gated rollout — cohort-by-cohort exposure, metric-based promotion, one-click kill — so you ship faster with less blast radius, and a junior engineer can kill a bad feature without a war room.
Run a rolling roadmap quarterly re-plan
Your annual roadmap is dead by quarter two. This runs a quarterly re-plan that keeps the strategy pillars fixed but re-sequences the next two quarters based on what you actually learned, producing a rolling 6-month view that stays current.
Build a scope creep defense document
You kicked off a 6-week project and 4 weeks in it is now a 10-week project. Every added item had a good reason. This produces a defense document that flags scope creep in real-time, forces a pre-committed scope boundary, and makes every addition trade off against existing items rather than extending the timeline.
Design a shipping velocity diagnosis using cycle time
Leadership says "we're slow" and the team says "we're shipping plenty." This cuts through the debate using cycle time — from first commit to production — segmented by work type, with the specific stage to fix first and a reforecast of what fixing it yields.
Conduct a merge-conflict root cause analysis
Your team is spending hours per week on merge conflicts and everyone blames the other team. This runs a structured analysis of the last 30 days of conflicts, finds the 2-3 code areas and workflow patterns producing them, and ships fixes — usually smaller stories and clearer ownership boundaries.
Design an engineering excellence review for PMs
You're the PM and you can't tell whether your engineering team is healthy or coasting. This designs an engineering excellence review you can run quarterly — cycle time, incident rate, test coverage trend, on-call load — so you have structured conversations with your EM counterpart instead of vague "velocity feels off" hunches.
Build a sprint retrospective with business-impact scoring
Your retros produce the same 3 action items every 2 weeks and nothing compounds. This restructures the retro around business-impact scoring of the last sprint's shipped work so the conversation shifts from team dynamics to what actually moved the needle — and what didn't.
Conduct a release retrospective with metric check-ins
Two weeks after launch and the team has moved on — but the launch metrics are only now maturing. This schedules structured release retros at 2, 6, and 12 weeks post-launch so learnings land when the data is real, not when the memory is fresh.
Build a cross-team kickoff doc for shared infrastructure
You are building shared infrastructure that 4 teams will consume and three of them weren't at kickoff. This produces a kickoff doc that documents the contract, non-goals, SLAs, and consumer onboarding steps so every consuming team gets the same answer and nobody blocks on you later.
Conduct a blameless incident post-mortem
Your last incident post-mortem turned into a name-and-shame and nobody wants to run the next one. This walks through a blameless post-mortem that finds root causes, produces durable action items with owners, and keeps psychological safety intact so the team runs toward signals, not away from them.
Design a bug SLA tiering system
Every bug feels urgent and engineering is reacting to the last Slack message. This designs a bug SLA tiering system — P0/P1/P2/P3 with explicit definitions, response windows, and routing rules — so triage becomes a 5-minute operation and the team stops thrashing.
Build a technical debt triage framework
Your team wants a "tech debt sprint" and leadership says "ship features." Both are wrong. This builds a triage framework that quantifies each piece of debt by interest rate (how much it slows every future ship) and produces a running allocation rule so debt gets paid down continuously without asking for permission.
Run a beta customer recruitment and success plan
You need 10-20 real customers on a beta in 4 weeks and your CS team is fully booked. This builds the recruitment spec, screening criteria, success metrics, and communication cadence so beta customers feel supported and give you the signal you need without consuming all your bandwidth.
Run a dependency mapping exercise across teams
Your roadmap says Q2 but three teams have silent dependencies on each other's work. This runs a dependency mapping exercise that surfaces hidden coupling, prioritizes the riskiest dependency, and produces an explicit handshake agreement between teams.
Product Changelog & Release Notes Writer
Generate polished, user-friendly release notes and changelogs from raw commit logs, ticket lists, or sprint summaries. Produces multiple formats: in-app, blog post, email, and Slack announcement.
Product Analytics Implementation Plan
Create a product analytics tracking plan that defines every event, property, and user attribute to instrument. Ensures your team captures the data needed to make product decisions.
Incident Post-Mortem Template
Write a blameless post-mortem after a product incident. Structured to capture timeline, root cause, impact assessment, and concrete action items that prevent recurrence.
QA Test Plan Generator
Generate a comprehensive QA test plan for a new feature or release. Covers functional testing, edge cases, regression scenarios, cross-browser/device testing, and accessibility checks.
Product Brief Template
Create a concise product brief (1-2 pages) that aligns stakeholders before full PRD development. Faster than a PRD, perfect for getting early buy-in on problem framing and proposed direction.
Feature Specification Document
Write a detailed feature specification that engineering teams can immediately build from. Covers user flows, edge cases, API contracts, error states, and acceptance criteria — the level below a PRD.
Sprint Planning Facilitator
Run an effective sprint planning session with your team. This prompt helps you prepare the sprint goal, select and estimate stories, identify dependencies, and set capacity-aware commitments.
Product Roadmap Generator
Create a strategic product roadmap organized by time horizon (Now / Next / Later) or quarterly themes. Includes prioritization rationale, dependencies, resource requirements, and stakeholder communication plan.
One-Pager Generator
This prompt helps craft a concise, engaging, and impactful one-pager that effectively conveys your key message. Whether for a business proposal, marketing strategy, or project summary, it ensures clarity and structure, guiding you to communicate ideas efficiently. By focusing on brevity and coherence, this tool enables you to distill complex information into a compelling one-page document that captures attention and maximizes impact.
Design a Viral Product Growth Loop
This prompt helps structure viral loops and network effects to drive organic user acquisition and increase retention through referrals and engagement loops.
Develop a Growth Hacking Playbook
This prompt helps define growth hacking strategies using the AARRR framework (Acquisition, Activation, Retention, Revenue, Referral) to ensure sustainable product growth.
v0.dev PRD Generator (Pro Ver.)
This prompt lets product leaders feed v0.dev a fully structured PRD and receive a multi-file, auto-modular Next.js 19 scaffold in return. v0.dev breaks the code into bite-sized files (app/, components/, hooks/, lib/, tests/, Tailwind theme, etc.), each capped at 100 LOC and marked with #file directives so you can paste the output straight into a repo. After generation, v0.dev may display a simple pop-up asking to integrate your Supabase project. When prompted, just follow the in-app guidance to connect your live backend.
Discover the Best PM Tools
This prompt helps identify essential development and product management tools by generating a comprehensive list of software solutions tailored for various PM tasks. It provides insights into key features, benefits, and use cases, allowing product managers to make informed decisions. If the user has specific tools in mind, they can include them to receive detailed comparisons and recommendations. Ideal for product managers seeking the right tools for roadmapping, analytics, user feedback, collaboration, and workflow management.
Technical Concept Breakdown
This prompt helps explain technical concepts at a user’s desired level of understanding, whether they are a beginner, intermediate learner, or expert. It structures explanations using clear headers and nested bullet points, ensuring clarity and accuracy without oversimplification. Using effective teaching methods such as the Feynman technique, it breaks down complex ideas into digestible components. Ideal for learners who need customized, structured, and engaging explanations.
v0.dev PRD Generator (Simple Ver.)
This prompt guides product leaders through a structured, v0.dev-optimized template to create a share-ready Product Requirements Document (PRD). It lays out clear sections for goals, user stories, functional specs, UX, metrics, and integrations while spotlighting code-generation snippets that match v0.dev’s conventions. Using it ensures consistent, high-quality PRDs that accelerate alignment and delivery.
Diagnose why your product's shipping velocity is declining
Your team grew from 5 to 15 engineers but you're shipping fewer features per quarter than before. Standups feel pointless, PRs sit in review for days, and sprint commitments keep slipping. This runs a structured velocity diagnosis to find the real bottlenecks — process, architecture, or people.
Create a product launch checklist with go-to-market sequencing
You're two weeks from a major feature launch and realize there's no coordinated plan across product, marketing, sales, and support. This creates a sequenced launch checklist that ensures nothing falls through the cracks — from beta testing through post-launch monitoring.
Build a technical debt negotiation case for your engineering team
Engineering keeps asking for 'tech debt sprints' but can't explain the business impact, and leadership keeps saying 'not now.' This builds a data-driven case that translates technical debt into business language — shipping velocity, incident risk, and opportunity cost — so both sides can agree on a realistic paydown plan.
Build a retention-focused onboarding optimization plan
Your signup-to-activation rate is low and users drop off before experiencing your product's core value. This dissects your onboarding funnel step by step, identifies the exact drop-off points, and generates a prioritized optimization plan tied to retention outcomes.
Design a rigorous A/B testing program from scratch
Your team runs occasional experiments but has no systematic approach — tests overlap, sample sizes are guessed, and results are cherry-picked. This sets up a structured experimentation program with proper hypothesis templates, statistical rigor, and a decision framework.
SRS(Software Requirements Specification) Generator
This prompt helps product managers write clear, actionable, and strategic Software Requirements Specifications (SRS). It provides a 13-section structure that covers key areas such as problem definition, AI usage, business objectives, functional specifications, and stakeholder alignment. Each section includes detailed examples and formats to support clarity and collaboration across teams. Ideal for complex or AI-powered products, this prompt helps turn high-level ideas into structured, execution-ready plans.
User Story
This prompt guides a Head of Product in crafting user stories that effectively translate user needs and business goals into actionable tasks for cross-functional teams. It emphasizes clarity, value-driven focus, and alignment with strategic objectives, using a structured framework for user stories, objectives, acceptance criteria, and a clear definition of done.
PRD Generator
This prompt helps product managers create a clear and strategic Product Requirements Document (PRD) with guidance from a Head of Product perspective. It provides a structured framework, covering objectives, target customer, strategic fit, key hypotheses, and solution principles, ensuring alignment with company goals. Users can customize the document by adding sections like success metrics or timelines, making it adaptable to their specific needs. This approach transforms ideas into actionable plans, driving product development success.
Write Jira Issues
This prompt helps create a clear and concise Jira ticket for a product feature. Simply describe the feature’s purpose and functionality, and it will format the details into an actionable ticket for your team. Perfect for quickly documenting ideas without worrying about rigid formatting or excessive detail.
Design a fit-for-purpose delivery methodology for your team
Use this prompt when your team needs to move beyond rigid Scrum or Waterfall and design a customized delivery approach that fits your specific project context.
Key Product Metrics
This prompt helps define critical product metrics, aligning them with business objectives. It ensures a data-driven approach to measuring solution impact, user engagement, and growth.
Amazon-style 1-Pager
This prompt guides the creation of a strategic, execution-focused 1-Pager using Amazon’s silent reading format. It structures product proposals around clarity, logic, and truth-seeking, with clear sections covering the customer problem, proposed solution, key metrics, and action items. It helps product teams align priorities and enable fast decision-making.
Run a value-driven sprint retrospective with business impact scoring
Use this prompt to run a retrospective that goes beyond team process and explicitly connects sprint outcomes to business value—helping teams shift from output-focused to outcome-focused delivery.
Storytelling
29 guidesBuild a cross-functional alignment ritual for recurring conflicts
The same fight between engineering and product happens every planning cycle. This designs a standing alignment ritual — surfaced recurring tensions, cross-team principles, explicit escalation paths — so the next debate takes 20 minutes instead of three days.
Conduct a product naming workshop
You are launching something and the team has been arguing over names in a Slack thread for three weeks. This runs a single 90-minute workshop — constraints, generation, stress tests, decision — that produces a final shortlist of 3 names with the rationale to defend whichever one ships.
Build a sales enablement one-pager for a new feature
A feature shipped and sales is asking "how do we sell this?" This builds a one-pager enablement — buyer personas, pain triggers, objection handlers, discovery questions — that sales can carry into any call without re-reading your launch deck.
Write a product deprecation announcement with minimal churn
You're sunsetting a feature 12% of customers rely on and the comms team is asking you for the email draft. This writes a deprecation announcement that leads with migration, not loss — explicit dates, named migration path, support commitment — so churn stays near historical baseline.
Draft a PR/FAQ in the Amazon style
You're starting a new product and want to force clarity before anyone writes code. This drafts a working-backwards PR/FAQ — press release first, FAQ second — so you know what you're really promising customers before engineering starts.
Build a release notes template that drives re-engagement
Your release notes read "Bug fixes and performance improvements." Nobody opens them. This writes a release notes template that drives re-engagement — one marquee item, one customer win, one behind-the-scenes — and actually brings users back to the product.
Draft a why-now section for an investor deck
Your investor deck has a great product and no sense of urgency. "Why now" is the slide that often decides the meeting. This drafts a why-now argument tied to a specific market shift, technology enabler, or behavior change — not a generic "AI is big."
Write a feature rejection response
You're saying no to a feature request from a major customer or a senior stakeholder. The default email sounds dismissive. This writes a rejection that acknowledges the need, explains the decision, offers alternatives, and preserves the relationship.
Craft a board update with the four key slides
Your board deck is 35 slides and the board members ask the same three questions every time. This produces a four-slide deck — metrics, highlights, risks, ask — that answers their real questions and leaves the detail in the appendix.
Write a product vision statement with evidence
Your product vision statement is vague poetry and the team can't ship against it. This writes a 3-year vision statement grounded in evidence — target customer, problem, solution shape, proof points — so engineers can evaluate tradeoffs against it.
Build a stakeholder update cadence with tiered depth
You're writing the same update three times — short for Slack, medium for the weekly, long for the quarterly — and it's eating your Fridays. This builds a tiered cadence with templates at each depth so each write compounds and you stop re-editing.
Write a one-pager product narrative for the exec team
Your quarterly exec update keeps growing into a 15-slide deck that buries the point. This produces a true one-pager — the bet, the evidence, the ask — so the exec team reads it, asks one sharp question, and you walk out with a decision.
Give feedback using the GAIN framework (Goal, Actions, Impacts, Next actions)
Your report just missed a deliverable for the third time, or your cross-functional partner keeps rewriting your PRDs. You are about to have the conversation and know that "here is what you did wrong" will land badly. The GAIN framework — Goal, Actions, Impacts, Next actions — gives you the exact structure and phrasing to flip from pain-framed to gain-framed so the other person hears an invitation instead of an attack.
Write a launch announcement email for customers
Your launch email will be opened by 20% of customers, read by 5%, and acted on by
Write a changelog that converts free users
Your free users never see your paid-tier features and the upgrade path is invisible. This writes a changelog that mentions paid features with tasteful upgrade prompts — not paywall spam — so free users discover value and convert at 2-3x the baseline rate.
Draft a customer success handoff narrative
A customer closed and is being handed to CS, who will inherit 8 threads and no narrative. This writes a handoff narrative that summarizes what they bought, why, what success looks like, and the top 3 risks — so the first CS call isn't "so what does your company do?"
Investor & Board Product Narrative
Craft a compelling product narrative for investor meetings, board presentations, or fundraising decks. Translates product metrics and roadmap into a strategic story that builds confidence.
Cross-Functional Kickoff Brief
Create a project kickoff document that aligns engineering, design, marketing, and business teams on goals, scope, timeline, roles, and communication norms before development begins.
Executive Summary & Board Update
Write executive summaries and board-level product updates that communicate strategic progress, key metrics, and decisions needed — all in the concise format executives prefer.
Feature Request Rejection Template
Say "no" to feature requests professionally while maintaining strong relationships with customers, sales teams, and stakeholders. Includes templates for different rejection scenarios and objection handling.
Product Update Email Writer
Write compelling product update emails for different audiences: customers, internal team, leadership, and investors. Each format is optimized for its audience's needs and attention span.
Announce Like Steve Jobs
This prompt helps you write compelling and emotionally driven product or feature announcements inspired by Steve Jobs. The focus is on simplicity, elegance, and emphasizing how the feature transforms the user experience. The result is a clear, engaging narrative that highlights the why behind the feature, not just the what.
Product Name Suggestions
This prompt is designed to generate product or feature names that seamlessly integrate with an existing brand’s identity, values, and voice. By emphasizing brand personality, emotional resonance, and market positioning, it guides the creation of unique, memorable names that reinforce the brand’s core essence while standing out in a competitive landscape.
Release Notes
This prompt is designed to help product managers, developers, and marketing teams create clear and engaging release notes. By breaking down the structure into essential components, it ensures that key updates, improvements, and bug fixes are communicated effectively to the target audience. With a focus on user benefits and concise language, this prompt enables the creation of release notes that are both professional and compelling, driving user engagement and excitement for new features or improvements.
Blog Post
This prompt helps transform your personal notes into a polished blog post. Simply input your raw ideas, and it will refine your content while preserving your unique voice, making blog writing effortless and authentic.
Write a product narrative memo that replaces your slide deck
Your product review meetings are death-by-PowerPoint — 40 slides where nobody remembers the key insight by slide 15. This writes an Amazon-style narrative memo that forces clear thinking, structured arguments, and makes the reader understand your product direction in 6 pages, not 60 slides.
Write a product positioning statement using the competitive wedge method
You're launching into a crowded market and your messaging sounds like every competitor's. This uses the competitive wedge method to craft a positioning statement that highlights what you do differently — not just better — so prospects immediately understand why you exist.
Craft a stakeholder alignment brief for cross-functional buy-in
You're about to pitch a product initiative but each stakeholder cares about different things — engineering wants feasibility, sales wants revenue impact, design wants user experience. This creates a single brief with tailored sections that speak to each audience's priorities.
Write a compelling product narrative for stakeholder alignment
Use this prompt when you need to craft a strategic product narrative that aligns executives, engineering, and cross-functional teams around a shared vision and urgency for action.
AI & Automation
31 guidesDraft a shared AI glossary for your product team
Your team says "agent" and means three different things; "RAG" comes up in planning and half the room nods without understanding. This produces a 1-page team-specific AI glossary — 20-30 terms with your product's operational meaning, not textbook definitions — so every planning conversation starts from shared vocabulary.
Run an AI feature eval with golden dataset
Your AI feature needs an objective quality measurement — not vibes, not shipping-week demos. This runs an eval with a golden dataset, blind human scoring, and statistical significance checks so you can report "quality" with a number, not an impression.
Design a conversational AI interaction flow
Users open your AI chat and don't know what to ask. This designs the interaction flow — suggested starts, progressive disclosure, recovery paths, graceful refusal — so first-use succeeds more than 50% of the time and users build the habit.
Build an AI-assisted PRD critique workflow
Your PRD reviews are bottlenecked on senior PMs who read every draft. This builds an AI-assisted PRD critique workflow — checklist prompt, specific quality gates, human review for high-stakes items — so drafts improve before a human reads them and seniors focus on the hard problems.
Build a PM workflow that auto-triages customer feedback
You receive 500 pieces of customer feedback per week across Intercom, NPS, Slack, email — and your team reads maybe 30 of them. This builds an AI triage workflow that classifies, clusters, and surfaces signal so the PM only reviews what matters.
Design an AI product disclosure pattern for users
Your AI feature generates output and users aren't sure if it's trustworthy. This designs a disclosure pattern — signal that AI is involved, confidence indicators, source links, override paths — so users calibrate trust appropriately and don't either over- or under-rely.
Conduct an AI feature trust calibration audit
Users either over-trust your AI (act on outputs they shouldn't) or under-trust it (ignore outputs that are correct). This audits trust calibration with user testing, scenario probes, and behavior data so you surface where calibration is off and design interventions to fix it.
Build an automation opportunity scan for PM work
You're a PM and half your week is spent on meetings, followups, summaries, and doc editing. This scans your last 2 weeks for automation candidates — recurring, time-consuming, low-judgment tasks — and picks the first 2-3 to automate so you reclaim hours per week.
Design an AI feature evaluation rubric before shipping
You're about to ship an AI feature and your only eval is "looks good to the team." This designs a proper eval rubric — task set, scoring criteria, golden answers, regression guardrails — so you can ship with confidence and catch drift later.
Build an AI cost-per-action monitoring dashboard
Your AI feature works but costs are growing faster than users. This builds a cost-per-action dashboard — cost per user, cost per successful outcome, cost drift over time — so you catch runaway costs before the finance team does.
Design a human-in-the-loop safety net for an AI feature
Your AI feature is good but not good enough to trust unattended on high-stakes tasks. This designs a human-in-the-loop safety net — review gates, confidence thresholds, escalation triggers — so AI does the bulk work and humans intervene where it matters.
Conduct an AI vs. non-AI ROI comparison
You're about to build an AI-powered version of a feature. Before you spend months on it, run the ROI comparison — AI cost, quality delta vs. non-AI, risk premium — so you know whether AI actually wins or just looks impressive in a demo.
Build an LLM prompt library for PM workflows
Your team uses AI for PRD drafts, competitive analysis, and interview synthesis — each person has their own prompt and results are inconsistent. This builds a shared prompt library with versioned, tested prompts so the whole team benefits from each improvement instead of re-inventing.
Build a 5-step AI adoption playbook for your team
Your exec just declared "AI-first" but the team is stuck on vague mandates, procurement bottlenecks, and no guidance on which workflows to automate first. This five-step playbook — explain the how, track and reward, cut the red tape, turn enthusiasts into teachers, prioritize high-impact tasks — synthesizes the tactics used at Shopify, Ramp, Duolingo, Zapier, Intercom, and Whoop into a sequenced plan you can put in front of leadership this week.
Design a model upgrade migration runbook
A new model version just dropped and your team wants to upgrade tomorrow. This designs a migration runbook — eval comparison, cost diff, cohort rollout, rollback criteria — so you ship the upgrade without breaking production behavior users depend on.
Run a prompt regression testing suite
You tweaked a prompt to fix one bug and three other behaviors quietly regressed. This runs a regression testing suite — gold test set, automated diff, pass/fail thresholds — so every prompt change is tested before it ships.
Run an AI feature hallucination audit
Users are complaining about AI output that sounds plausible but is wrong. This runs a structured hallucination audit — real user logs, categorization, root cause — so you understand where the model makes things up and can apply the right fix (prompt, retrieval, fine-tune, or scope).
AI Product Metrics Dashboard Designer
Design a product metrics dashboard tailored to your product type and stage. Defines the metric hierarchy (North Star → primary → secondary → guardrail), suggests data sources, and creates a monitoring plan.
AI PRD Review & Improvement
Get an AI-powered review of your PRD that checks for completeness, clarity, technical feasibility gaps, and missing edge cases. Returns a scorecard with specific improvement suggestions.
AI Sprint Report Generator
Automatically generate a polished sprint report from raw sprint data (completed stories, velocity, bugs, blockers). Produces both a team-facing detailed report and an exec-friendly summary.
AI Competitive Monitoring Report
Generate a structured competitive intelligence report by analyzing competitor updates, product launches, pricing changes, and market movements. Use with AI research tools like Perplexity or ChatGPT Deep Research.
AI Customer Feedback Classifier
Automatically classify and prioritize customer feedback from multiple channels (support tickets, NPS comments, app reviews, social media) into product-actionable categories with severity scoring.
AI Meeting Notes to Action Items
Convert messy meeting notes or transcripts into structured action items, decisions made, open questions, and stakeholder follow-ups. Perfect for sprint planning, product reviews, and cross-functional syncs.
AI User Research Synthesizer
Transform raw user research data (interviews, surveys, support tickets) into structured insights using AI. Automatically identifies themes, sentiment patterns, and actionable recommendations.
AI-Powered Daily PM Workflow
Set up an AI-powered daily workflow that automates the most time-consuming PM tasks: standup prep, stakeholder updates, metric summaries, and inbox triage. Saves 2-3 hours per day.
Design an autonomous experiment loop for product optimization
You know something in your product could be better — onboarding copy, pricing page layout, notification timing — but running A/B tests manually is slow and you never get through enough variants. Apply Karpathy's autoresearch pattern (https://github.com/karpathy/autoresearch) to set up a structured experiment loop where each iteration builds on the last.
Run an autoresearch loop to optimize any product artifact
You have a product artifact — landing page copy, onboarding script, email sequence, pricing page — that works but isn't great. Instead of guessing what to improve, hand it to this prompt and let the AI run Karpathy's autoresearch loop (https://github.com/karpathy/autoresearch): generate a variant, score it against your metric, keep or discard, repeat until convergence.
Build an AI-powered user research synthesis workflow
Use this prompt when you have multiple user interview transcripts or feedback sources and want AI to identify patterns, themes, and actionable insights automatically.
Set up an AI-orchestrated QA and ship checklist
You're about to ship a feature and need a comprehensive pre-launch checklist that goes beyond manual testing. With AI-assisted QA becoming the norm, define what your review-test-ship pipeline should actually cover — from code review to post-deploy canary monitoring.
Build a personal AI thinking partner for product decisions
You keep going back and forth on a product decision and need a structured way to pressure-test your reasoning. This sets up an AI-powered sparring partner that challenges your assumptions, surfaces blind spots, and helps you arrive at a well-reasoned call — before you bring it to stakeholders.
Set up an AI agent workflow to automate PM operations
Use this prompt when you want to delegate repetitive PM tasks (ticket triage, backlog grooming, status reporting) to an AI agent that runs autonomously.
Discovery
44 guidesDesign a Foundation Sprint for pre-product clarity
You have a promising idea, a small team, and two weeks of runway before you need to commit engineers. A traditional Design Sprint is for testing solutions — but you're not there yet. The Foundation Sprint forces two days of hard choices on who you're for, what you're offering, and what makes you differentiated, so the next sprint isn't debating first principles.
Run a retention analysis and diagnose the leak
Retention graphs are red and nobody knows where to start. This runs a structured retention analysis — cohort segmentation, event funnel, feature usage correlation — so you find the 1-2 leak points that matter most instead of debating 10 interventions at once.
Run a 5-whys root cause analysis on a user complaint
A loud customer complaint just landed in your exec's inbox and the team's first instinct is to patch the symptom. This runs a 5-whys analysis that traces the complaint to its structural cause so you fix the source, not just the escape.
Design a feature adoption funnel audit
You shipped a feature that 40% of users have *seen* and 3% have *used*. This audits the adoption funnel — discover, try, use, retain — so you find whether the leak is awareness, intent, activation, or value.
Conduct a survey design review before you send
You're about to send a 20-question survey to 5,000 customers and the data will tell you nothing useful. This reviews the survey for leading language, bad scales, response fatigue, and analyzability before you send — so the results actually drive decisions.
Build a customer advisory board charter
Your top customers want more influence on the roadmap and your team keeps having 1:1 calls that produce conflicting asks. This builds a customer advisory board charter — membership, cadence, format, inputs, decision boundaries — so top customers have structured input and your roadmap doesn't fragment.
Design a foundational product-market fit survey analysis
You ran the Sean Ellis PMF survey and got 38% "very disappointed" — is that a pass? This analyzes the survey properly with segmentation, open-text patterns, and next-step recommendations so you know whether to iterate, pivot, or scale.
Design a customer interview guide for problem discovery
You have 6 customer interviews this week and the draft script will produce opinions instead of stories. This builds a behavioral interview guide that uncovers how people actually solved the problem last time — not what they think about your proposed feature.
Design an opportunity solution tree for a new market
You are entering a new market or segment and don't want to commit to a solution until you understand the problem space. This builds the opportunity solution tree — outcome at the top, opportunities in the middle, solutions at the bottom — so you generate multiple solutions per opportunity before deciding.
Build an outcome-based user persona
Your personas are demographic sketches that never inform a product decision. This builds outcome-based personas — what they want to achieve, their current solution, their forces for change — so the persona actually matches behavior and influences shipped features.
Build a user research synthesis document
You ran 12 interviews and now have 400 sticky notes in FigJam. This synthesizes them into a research document with themes, supporting quotes, and product implications — the artifact that actually drives decisions instead of a doc nobody reads.
Conduct a churn exit interview program
Churn surveys give you checkbox answers and no insight. This designs an exit interview program — 15-minute call, structured script, synthesis cadence — so you actually learn why customers leave and which reasons you could have fixed.
Conduct a usability testing script for new features
Your designer says the flow is obvious and your PM says it's confusing. Build a 5-user usability test script that resolves the debate with data — tasks, metrics, severity scale — and produces actionable fixes within a week.
Build a continuous discovery interview cadence
You do research in bursts before a launch and then not again for months. This builds a weekly interview cadence that keeps you in constant touch with users — recruiting pipeline, 4 interviews/week, synthesis ritual — so you always have fresh insights without running a special project.
Run a Jobs-to-be-Done switch interview
Your customers switched to your product and you have no idea why. This runs a JTBD switch interview that reconstructs the exact moment of switch — the trigger, the forces, the struggle moment — so you can find more people in the same situation and design for the same decision point.
Run a market sizing sanity check
Your deck says $12B market, board is skeptical, and nobody can reconcile the number. This runs three independent estimation methods — top-down, bottom-up, and analog — and cross-checks them so the number you show has triangulated evidence, not a single source.
Conduct a competitive UX teardown
Your competitor just shipped a new flow and your CEO sent you the screenshot. This runs a structured UX teardown — jobs-to-be-done, information architecture, friction, differentiation — so the response is data-driven and doesn't collapse into copying.
Design a behavioral cohort diagnosis
Retention curves look flat aggregate and your team has no idea why. This runs a cohort analysis across acquisition channel, feature usage, and behavior pattern so you can identify the 2-3 cohorts that actually drive your numbers — and the ones leaking out.
Opportunity Sizing & TAM Calculator
Calculate Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for a product opportunity. Uses both top-down and bottom-up approaches with clear assumptions.
Problem Statement Workshop
Facilitate a problem statement workshop to ensure your team is solving the right problem before jumping to solutions. Uses the "How Might We" framework and 5 Whys technique to sharpen problem framing.
Usability Testing Script
Create a structured usability testing script with warm-up questions, task scenarios, follow-up probes, and a scoring rubric. Ready to use for moderated remote or in-person testing sessions.
User Persona Generator
Create data-informed user personas from research data, analytics, and customer interviews. Goes beyond demographics to capture goals, frustrations, behavioral patterns, and decision-making criteria.
Customer Journey Map Builder
Create a detailed customer journey map from awareness to advocacy. Identifies touchpoints, emotions, pain points, and opportunities at each stage of the user experience.
MoSCoW Prioritization Method
Apply the MoSCoW method (Must have, Should have, Could have, Won't have) to prioritize features for a release or sprint. Includes stakeholder alignment exercises and trade-off documentation.
RICE Scoring Framework
Apply the RICE prioritization framework (Reach, Impact, Confidence, Effort) to score and rank product ideas objectively. Includes calibration guidance to ensure consistent scoring across your team.
Customer Feedback Survey
This prompt helps draft a structured customer feedback survey for product release. It ensures a well-balanced mix of quantitative and qualitative questions to gather insights on usability, satisfaction, and areas for improvement. Ideal for product teams, UX researchers, and marketers seeking actionable feedback to refine future iterations.
Design Thinking
This prompt defines an assistant that employs deep empathy and human-centered design thinking to solve user problems iteratively. It uses dynamic user inputs (problem, goal, feedback, context) and follows core principles of empathy, iterative exploration, collaborative thinking, and actionable insights. Responses are structured to emphasize understanding the user, reframing issues, prototyping solutions, and refining ideas through continuous feedback.
Customer Interview Questions
A structured prompt for product managers to uncover customer needs, pain points, and desires through in-depth interviews. It helps identify opportunities for innovation and improvement, ensuring insights that drive product growth and user satisfaction.
User Interview Guide
This prompt provides a structured guide for designing and conducting user interviews for a product. It covers key aspects such as preparing effective interview questions, selecting participants, and managing the interview process. Ideal for product teams, UX researchers, and designers looking to gather in-depth user insights to improve product experiences.
Run a product team health check and build an improvement plan
Your team ships features but something feels off — retrospectives are stale, morale is dipping, and cross-functional collaboration is getting harder. This runs a structured health check across 8 dimensions of product team effectiveness and generates a targeted improvement plan.
Map an opportunity solution tree for continuous discovery
Your team keeps jumping from customer request to feature without connecting the dots. This builds an opportunity solution tree from a desired outcome down through opportunities, solutions, and experiments — so every feature you ship traces back to a real customer need.
Run a product-market fit survey and diagnose the results
You've shipped your MVP and have some active users, but you're not sure whether you've actually hit product-market fit or just built something 'nice to have.' This runs the classic 'very disappointed' survey, segments the responses, and tells you exactly what to fix.
ICE Prioritization Helper
The ICE Prioritization Helper Prompt is designed to streamline decision-making by calculating ICE (Impact, Confidence, Ease) scores automatically. This prompt provides a structured and evidence-based framework for evaluating ideas, inspired by Itamar Gilad’s methodologies. By inputting key details like impact, ease of implementation, and confidence levels (derived from various evidence types), you receive not only a calculated priority score but also tailored feedback to refine your approach. With actionable suggestions for improvement and strategic next steps, this tool helps teams and individuals identify high-priority opportunities, uncover blind spots, and accelerate innovation. Whether you’re prioritizing features, projects, or strategies, this prompt ensures your efforts are both data-driven and impactful.
Jobs-to-be-Done (JTBD) analysis
Description for the JTBD Prompt This prompt guides a structured Jobs-to-be-Done (JTBD) analysis by breaking down Customer Jobs, Pains, and Gains. It helps identify functional tasks, social and emotional needs, key challenges, and opportunities for improvement. Ideal for product managers and strategists, it provides actionable insights to refine products, prioritize features, and enhance user experience.
Run a YC-style product diagnostic before building
You have a feature idea or product concept that feels promising but you haven't stress-tested it yet. Before writing a single line of code, run it through the same forcing questions YC partners use to separate real demand from wishful thinking.
User Interview (Teresa Torres Approach)
This prompt provides a structured guide for designing and conducting user interviews based on Teresa Torres’ Continuous Discovery Habits approach. It emphasizes opportunity mapping, assumption testing, and continuous learning to extract actionable insights. The guide covers key aspects like preparing effective interview questions, selecting participants, conducting unbiased interviews, and synthesizing insights. Ideal for product teams, UX researchers, and designers looking to make data-informed product decisions.
Persona-Driven Feature Feedback
Create detailed user personas and generate contextual feedback for product features. This prompt provides diverse, realistic insights by simulating how different user segments would respond to new ideas, ensuring feedback is relevant, actionable, and user-centered.
Identifying Hidden Assumptions
This prompt is inspired by Teresa Torres' framework for Continuous Discovery Habits, which emphasizes uncovering hidden assumptions, identifying Leap of Faith Assumptions, and testing them effectively. By following this structured five-step process, you'll learn to evaluate your product ideas critically and systematically, ensuring that you're addressing the riskiest parts of your solution early.
Interview snapshot assistant
This prompt trains a product discovery assistant to generate structured Markdown interview snapshots based on Teresa Torres’ Continuous Discovery Habits. It enforces a strict schema with required metadata, behavioral stories, journey maps, and insights, while handling missing data with placeholders. The result is consistent, actionable research outputs that help teams uncover user behaviors, pain points, and opportunities.
Synthesizing interview snapshots
This prompt provides a structured framework for synthesizing multiple interview snapshots into actionable insights. It guides users through input validation, pattern discovery, user journey integration, and insight generation, ensuring missing or inconsistent data is flagged. The outcome is a standardized, evidence-based synthesis that highlights opportunities, key insights, and next research steps for product strategy.
Pre-Mortem
Pre-Mortem helps product managers uncover potential risks and develop actionable strategies before launching their product. Inspired by Shreyas Doshi's framework, it categorizes risks as Tigers (real threats), Paper Tigers (overestimated concerns), and Elephants (hidden threats). By analyzing assumptions, challenges, and the competitive landscape, it provides practical solutions and clear next steps to maximize the product's success and minimize unexpected failures.
Product Decision Making
This prompt guides structured decision-making by focusing on data, hypotheses, and actionable solutions. It helps analyze complex challenges, align with goals, and gather stakeholder input to produce clear, evidence-based reports. Suitable for anyone involved in strategic problem-solving.
Discovery-Focused Test & Experiment Plan
This prompt helps product managers create a structured and actionable test/experiment plan to reduce product uncertainty. It guides teams to identify the riskiest assumptions (LoFA), validate them through lean behavioral tests, and determine when to move into formal hypothesis experiments. Ideal for discovery-focused teams working on high-stakes product decisions.
Facilitate a cross-functional discovery alignment workshop
Use this prompt to plan and run a structured workshop that brings engineering, design, and business stakeholders into the discovery process together—critical when teams are siloed or misaligned on customer problems.
Product Strategy
53 guidesBuild a switching cost analysis for your product
Churn is above your target and "we need a better product" is not a plan. This maps the switching costs customers pay to leave you, identifies the three load-bearing ones, and produces a quarter-by-quarter plan to deepen them without crossing into lock-in that damages brand.
Run a pre-mortem on your annual product plan
Your 2026 plan looks great and nobody has argued with it — which is exactly the problem. This runs a structured pre-mortem that imagines the plan has failed at year-end, traces the failure back to the decisions you are making today, and converts each failure mode into a guardrail you can act on before you commit.
Build a disruptive innovation radar for your category
Your category is stable, you are winning, and you cannot see the disruptor coming — which is exactly when one arrives. This builds a radar that scans low-end, new-market, and adjacent-tech disruption vectors every quarter so you spot the threat while it is still cheap to respond.
Conduct a product portfolio pruning review
You support 14 SKUs/features/integrations. Three generate 80% of revenue, four are zombies, and seven are "maybe next quarter." This runs a structured portfolio review that produces a sunset plan with migration paths and a revenue-impact forecast before the conversation with customer success.
Design a "what we are NOT doing" document
Every quarter a new idea slips into the roadmap and nobody remembers why it wasn't on it last quarter. This produces a companion document to your roadmap — the explicit list of what you are not doing and why — so the next time it comes up, the conversation ends in 5 minutes instead of a re-debate.
Map your product's competitive positioning on a Kiviat chart
Your competitive analysis is a wall of feature checkmarks that doesn't tell a story. A Kiviat (spider) chart on 6-8 axes makes the shape of your advantage visible in one frame. This prompt picks the axes buyers actually decide on, scores them with evidence, and produces the narrative to go with the chart.
Build a three-horizons product strategy map
Your roadmap is 100% Horizon 1 (core) or 100% Horizon 3 (moonshots) and leadership keeps asking for balance. This forces a disciplined split across now, next, and future bets with explicit resourcing and kill criteria so you can defend your mix in the next operating review.
Run a Strategy Blocks sprint to craft a 2-year product strategy
Teams keep shipping but argue about *why* those projects and not others. Strategy Blocks is a five-step operator framework — preparation, strategy sprint, design sprint, document, rollout — that forces a disciplined choice of 3 strategic pillars, a 2-year winning aspiration, and stakeholder alignment built into the process rather than bolted on at the end.
Write a kill-or-double strategy memo for a stalled initiative
An initiative has consumed 2 quarters of engineering time and the metrics are flat. Leadership wants either a clear reset or a principled wind-down. This produces a kill-or-double memo that lays out what was tested, what the data actually says, and a binary recommendation with pre-committed criteria so the call stops getting re-debated.
Design a product-led growth to sales-assist crossover plan
Your PLG motion is signing up individual users but enterprise deals are stalling because nobody is working the account. This designs the exact crossover — trigger criteria, handoff spec, joint comp plan — so PLG stops leaving six-figure ACVs on the table without collapsing back into sales-led.
Map your product's network effects flywheel
Leadership keeps saying "we have network effects" and nobody can name the flywheel. This walks you through the eight network-effect archetypes, diagnoses which ones your product actually has, and produces a flywheel diagram with the investments that strengthen each loop.
Build a sequenced Jobs-to-be-Done product strategy
You have 40 JTBD interview snippets and no idea which job to build around first. This converts raw switch-interview data into a ranked job map, picks the first job to win on, and plans the adjacent jobs you will add in the following year without diluting the wedge.
Conduct a pricing positioning audit
Your pricing page hasn't changed in 18 months, discount rates are climbing, and win rates against competitors are dropping. This audits your pricing positioning on value perception, packaging clarity, and competitive anchoring — and produces a 90-day pricing refresh plan without blowing up existing deals.
Map the four big product risks before you build
A feature passes specs review, ships, and flops — and the post-mortem is always the same four risks you did not test. This runs each new bet through Marty Cagan's four-risk checklist (value, usability, feasibility, business viability) with specific discovery actions per risk so you catch the miss at week two, not at launch.
Run a white-space opportunity scan
Your category is mature, competitive, and slowing — and leadership wants "the next big thing." This runs a structured white-space scan across underserved segments, emerging behaviors, and unbundling opportunities so the next bet is informed by data, not by whoever had the loudest idea in the offsite.
Design a product cannibalization guardrail
You are launching a cheaper tier that might cannibalize your premium plan — or a new product that might eat your core. This produces a cannibalization model, sets the net-positive threshold, and designs guardrails so you can ship without the revenue team panicking.
Build a customer concentration risk mitigation plan
Three customers make up 45% of your ARR and your board is about to ask what happens if one leaves. This produces a concentration-risk memo with dependency maps, diversification targets, and a 12-month mitigation plan that doesn't collapse into "sell more" without structural changes.
Run a 10x vs 10% scope choice framework
Your team is debating whether to ship an incremental improvement (10% lift, known path) or a rewrite (10x opportunity, uncertain). This runs the decision through a structured scope frame so you make the call based on the metric ceiling, not on who is more persuasive in the room.
Build a platform strategy roadmap
Your product has one app and the next question is "when do we become a platform?" This walks through the 4 platform archetypes (APIs, apps, data, marketplace), the prerequisites you actually need, and a 12-month sequencing plan that stops you from launching a platform with no partners.
Run a product bets prioritization workshop
Your exec team has 14 ideas and one quarter of capacity. The usual RICE spreadsheet turns into a political knife fight. This runs a 90-minute structured workshop that surfaces hidden assumptions, forces a single ranked list, and leaves with a defensible narrative for every cut.
Design a moat analysis for your product's defensibility
You pitched a feature and a board member asked "what stops a competitor from shipping this in three months?" This runs you through seven moat archetypes — scale, network effects, switching costs, brand, regulatory, embedded data, proprietary tech — and produces a one-page defensibility memo you can hand to leadership.
Design a build-buy-partner decision matrix
Leadership is asking whether to build a capability in-house, buy a startup, or partner with an incumbent. The team keeps re-debating the question each time. This produces a reusable matrix with scored criteria and a default decision rule so the next build-buy-partner call takes a day, not a quarter.
Conduct a TAM/SAM/SOM re-calibration
Your 2023 deck said "$50B TAM" based on a number someone quoted in a blog post. Board is asking why growth stalled against such a big number. This re-derives TAM, SAM, and SOM from your actual pricing, ICP, and funnel conversion so the number you show is defensible for the next five meetings.
Stakeholder Mapping & Influence Strategy
Map your stakeholders by influence and interest, then create a tailored engagement strategy for each. Essential for PMs navigating complex organizational dynamics and getting buy-in for initiatives.
Platform vs Feature Decision Framework
Make the build-vs-buy decision and evaluate whether to build a feature in-house, use a third-party tool, or build a platform/API. Structured evaluation with cost modeling and risk analysis.
Product Localization & i18n Strategy
Plan your product's international expansion with a market prioritization matrix, localization requirements, and phased rollout strategy. Covers language, cultural adaptation, compliance, and go-to-market.
Churn Analysis & Prevention Strategy
Analyze user churn patterns and build a data-driven retention strategy. Identifies churn segments, root causes, leading indicators, and intervention playbooks at each lifecycle stage.
Product Lifecycle Stage Analyzer
Diagnose which stage your product is in (Introduction, Growth, Maturity, Decline) and get stage-appropriate strategy recommendations for product, marketing, pricing, and team focus.
Blue Ocean Strategy Canvas
Apply Blue Ocean Strategy to find uncontested market space. Creates a strategy canvas that visually compares your offering against competitors across key value factors, then identifies what to eliminate, reduce, raise, and create.
Value Proposition Canvas
Build a Value Proposition Canvas that maps your product's value creators and pain relievers to specific customer jobs, pains, and gains. Based on Strategyzer's framework.
Lean Canvas Generator
Create a Lean Canvas — the 1-page business model for startups and new product initiatives. Captures problem, solution, unique value proposition, channels, revenue streams, cost structure, key metrics, and unfair advantage.
Market Opportunity Estimator
This prompt assists in assessing the potential market size for a product or service by breaking it down into Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM). It offers a structured framework to evaluate industry demand, competitive factors, and revenue forecasts, making it valuable for entrepreneurs, product leaders, and business analysts seeking data-driven insights.
Inflections Stress Test
Use this prompt to complete the Inflections Stress Test by providing structured responses to each step in one go. Input your insights following the specified format, and the AI will generate a detailed summary table along with reflections to help validate and refine your idea.
Competitor Analysis
Use the Deep Research mode in services like ChatGPT, Gemini, or Perplexity to explore the competitive landscape around your product idea. This prompt helps you take on the role of a product marketer to identify and analyze key competitors with similar features or targeting similar user needs.
Market Analysis
This executive-level market analysis prompt demands a thorough competitive assessment, identification of market trends and opportunities, and actionable recommendations with an implementation plan. Data sources include industry reports, financial disclosures, and social listening. The deliverable is a concise, data-driven strategic blueprint for growth.
Build a growth model to forecast and diagnose product growth
Your growth feels like a black box — new users come in, some churn, revenue goes up or down, but nobody can explain why or predict what happens next. This builds a bottom-up growth model that decomposes your growth into its component levers so you can forecast, diagnose, and intervene.
Assess your marketplace cold start problem and design a launch strategy
You're building a marketplace or platform and stuck in the chicken-and-egg trap — no supply without demand, no demand without supply. This structures the cold start analysis and designs a sequenced launch strategy to bootstrap both sides.
Design a subscription value loop for your product
Your subscription product is growing through paid acquisition but retention is flat and CAC keeps rising. This designs a value loop where your product's core experience naturally drives conversion, retention, and organic referral — reducing your dependence on paid marketing.
Define and validate your product's North Star metric
Your team tracks a dozen metrics but can't agree on which one matters most. Roadmap debates devolve into 'my metric vs. your metric' arguments. This walks you through selecting, validating, and operationalizing a single North Star metric that aligns product, growth, and business goals.
Apply the DHM framework to sharpen your product strategy
Your team can't articulate why your product wins beyond 'better features.' This prompt uses the Delight-Hard to Copy-Margin enhancing framework to stress-test whether your strategy creates durable competitive advantage or just temporary differentiation.
Run a pricing and packaging audit for your product
Your pricing hasn't been revisited in over a year, or you're launching a major feature and wondering whether to gate it behind a higher tier. This walks you through a structured audit of your current pricing model, identifies packaging gaps, and generates specific recommendations.
Defining a Strong Product Vision
This prompt helps craft a clear and inspiring product vision that aligns with market needs and business objectives. It ensures a strategic approach by defining customer problems, unique differentiators, and success criteria. Ideal for PMs looking to set a strong foundation for product development.
Run a PM Wheel self-assessment and build a growth plan
Use this prompt to assess your product management competencies across Petra Wille's 8-activity PM Wheel framework and generate a personalized development plan with concrete actions for your weakest areas.
Build an orthogonal context brief for AI-powered product analysis
Use this prompt when you need AI to analyze your product metrics, market position, or strategic options but keep getting generic, surface-level responses. It structures your input across independent dimensions so the AI can narrow down to one defensible interpretation instead of defaulting to the most common pattern.
Go-To-Market (GTM) Strategy
Create a winning Go-To-Market (GTM) strategy with this structured prompt. Identify your target audience, define unique positioning, select optimal acquisition channels, and establish measurable success metrics. Perfect for product managers, marketers, and startup founders looking to refine their launch strategy and maximize market impact.
OKR Sparring Partner
This prompt helps users critically evaluate draft OKRs. It uses a structured multi-angle framework assessing clarity, measurability, strategic alignment, assumptions, and phrasing. Users receive detailed critiques, actionable improvement suggestions, and improved OKR examples to drive strategic clarity and executional excellence.
Pricing Strategy
This prompt helps generate three alternative pricing strategies for a new product. It encourages structured thinking around different pricing models, ensuring diverse approaches tailored to market positioning, value perception, and competitive landscape. The response may include cost-based, value-based, freemium, penetration, or premium pricing models, along with reasoning for each approach. Ideal for product managers and business strategists looking to optimize pricing decisions.
Build a Data-Driven User Retention Strategy
This prompt helps you create a data-driven user retention strategy by identifying churn risks, optimizing engagement tactics, and reinforcing habit formation. Use behavioral analytics, segmentation, AI-driven personalization, and experimentation to enhance user loyalty. Designed for product managers and growth teams looking to improve customer retention and reduce churn effectively.
Design a multi-lens product plan review pipeline
You've drafted a product plan or PRD but it only reflects your own perspective. Before committing resources, run it through three independent lenses — CEO (ambition & vision), Engineering (feasibility & architecture), and Design (user experience & polish) — to catch blind spots.
Design a hybrid PLG and sales-assist go-to-market motion
Use this prompt when transitioning from pure self-serve to a hybrid product-led sales model, where the product qualifies leads and sales intervenes strategically for high-value accounts.
Build an AI-assisted competitive intelligence dashboard
Use this prompt when you need to set up a systematic, AI-powered process for tracking competitors in real time—ideal for PMs who spend too much time manually gathering market signals.
Build a 'Boil the Lake' completeness audit for your roadmap
AI has collapsed the cost of doing things thoroughly. You're reviewing your product roadmap and suspect you've been cutting corners out of habit — shipping MVPs when the complete version costs only marginally more. Audit your roadmap for shortcuts that no longer make sense.
Create a profit-driven product prioritization framework
Use this prompt when shifting from growth-first to profitability-first prioritization, helping you evaluate features by their revenue impact and cost efficiency.