Perplexity Prompts for Product Management

Write a Product Requirements Document for [feature name]. Include: 1. Problem statement (2-3 sentences). 2. Target users and use cases. 3. Success metrics (quantifiable). 4. Functional requirements (numbered list). 5. Non-functional requirements (performance, security, accessibility). 6. Out of scope. 7. Open questions. Format with clear headers. Audience: engineering and design team.

Write [N] user stories for [feature]. Format: 'As a [user type], I want to [action] so that [benefit].' For each story include: acceptance criteria (3-5 Given/When/Then scenarios), priority (P0/P1/P2), estimated complexity (S/M/L), and any dependencies. Focus on [specific user type or workflow].

Apply the [RICE/ICE/MoSCoW] prioritisation framework to these [N] feature requests: [list features]. For each, score: [Reach/Impact/Confidence/Effort or appropriate framework dimensions]. Show your scoring rationale in one sentence per feature. Output as a ranked table. Final recommendation: top 3 to build next quarter.

Write a weekly product update email for [stakeholders: executives/investors/cross-functional team]. Tone: concise and confident. Include: 3 key wins this week (with metrics if possible), 1 challenge and how we're addressing it, key milestones this coming week, and a metric-of-the-week callout. Under 250 words. No jargon.

Compare the [feature area] across these competitors: [list competitors]. For each, document: feature availability (yes/no/partial), key differentiators, pricing tier it's available on, user sentiment (if known), and gaps we can exploit. Output as a comparison table, then a 3-bullet strategic recommendation for our roadmap.

Write a quarterly OKR set for [team name] aligned to the company goal of [company objective]. Include: 1 Objective (aspirational, not a metric), 3-4 Key Results (measurable, time-bound, leading indicators), and 2-3 initiatives per Key Result. Avoid vanity metrics. Each Key Result should clearly indicate how we'll know if the Objective was achieved.

Create a 45-minute user interview script for researching [problem area/feature]. Include: warm-up questions (5 min), problem exploration questions (20 min), current behaviour and workflow questions (10 min), solution reaction questions (10 min if concept to test). Total: 12-15 questions. Avoid leading questions and yes/no formats.

Create a product launch checklist for [feature name] launching to [audience size/segment]. Organise by team: Product (readiness criteria), Engineering (technical checks), Design (UX review), Marketing (announcement plan), Customer Success (support prep), Legal/Compliance (if applicable). Format as a checklist with owner and due date columns.