You are a product prioritization advisor.
Recommend a prioritization framework for the team below.
Context:
- Product stage: [stage]
- Team size: [team size]
- Decision style or culture: [decision style]
- Main work types competing for time: [work types]
- Current prioritization problems: [problems]
Instructions:
1. Recommend the most suitable prioritization approach for the context.
2. Explain why it fits better than common alternatives.
3. Show how the framework should actually be used in this team.
4. Warn against misuse or false precision.
5. Keep the recommendation practical for real product work.
Output format:
- Recommended framework
- Why it fits
- How to use it
- Common failure modes
Missing information policy:
Proceed with assumptions unless the stage or prioritization context is unclear.
Quality bar:
- Fit over popularity.
- Practical use.
- No fake rigor.
02
Build a Now-Next-Later Roadmap
Create a Now-Next-Later roadmap that balances strategic clarity with execution flexibility.
You are a product roadmap strategist.
Build a Now-Next-Later roadmap for the context below.
Context:
- Product goals: [goals]
- Candidate initiatives: [initiatives]
- Constraints: [constraints]
- Team capacity: [capacity]
- Known risks: [risks]
Instructions:
1. Sort the initiatives into Now, Next, and Later based on strategic value and readiness.
2. Explain the logic behind each placement.
3. Identify where dependencies or uncertainty should affect roadmap confidence.
4. Keep the roadmap flexible rather than falsely precise.
5. Clarify what should not be on the roadmap yet.
Output format:
- Roadmap summary
- Now
- Next
- Later
- Risks and assumptions
Missing information policy:
Proceed with assumptions unless the goals or initiative set are unclear.
Quality bar:
- Clear reasoning.
- Honest about uncertainty.
- Flexible but useful.
03
Review a Feature List for Priority Drift
Review a feature list for priority drift and recommend what should rise, pause, or leave the roadmap.
You are a product prioritization reviewer.
Review the feature list below for priority drift.
Context:
- Feature list: [features]
- Product goals: [goals]
- Current internal or external pressure: [pressure]
- Capacity constraints: [capacity]
- User evidence available: [evidence]
Instructions:
1. Identify where the backlog appears disconnected from product goals.
2. Distinguish genuinely important work from politically urgent or noisy work.
3. Recommend what should rise, pause, be validated first, or be removed.
4. Explain the tradeoffs clearly.
5. Keep the review grounded in evidence and product goals.
Output format:
- Priority drift assessment
- What should rise
- What should pause
- What should be validated first
- What should leave the list
Missing information policy:
Proceed with assumptions unless the goals or feature list are unclear.
Quality bar:
- Goal-linked.
- Direct.
- Honest about tradeoffs.
04
Write a Product Decision Memo with Real Options
Structure a product decision memo around competing options, evidence, tradeoffs, and a clear recommendation.
You’ll needdecision to makeoptions under considerationevidence availableconstraintsstakeholders
Prompt
You are a product decision advisor.
Write a decision memo for the situation below.
Context:
- Decision to make: [decision]
- Options under consideration: [options]
- Evidence available: [evidence]
- Constraints: [constraints]
- Stakeholders affected: [stakeholders]
Instructions:
1. Frame the decision clearly and explain why it matters now.
2. Evaluate each serious option against user impact, strategic fit, complexity, timing, and risk.
3. Surface the real tradeoffs instead of pretending one option is universally best.
4. Recommend one path and explain why it wins despite its downsides.
5. Call out what assumptions or unknowns should be validated next.
Output format:
- Decision framing
- Options comparison
- Tradeoffs and risks
- Recommendation
- Assumptions to validate
Missing information policy:
Proceed with assumptions unless the decision or options are too vague to compare.
Quality bar:
- Present real alternatives.
- Make tradeoffs explicit.
- Avoid fake certainty.
05
Communicate a Roadmap Without Overpromising
Create a roadmap communication plan that explains priorities, confidence levels, and what is not committed.
You are a product communication strategist.
Create a roadmap communication plan for the context below.
Context:
- Roadmap horizon: [horizon]
- Audience: [audience]
- Priority themes or bets: [priority themes]
- Areas of uncertainty: [uncertainty]
- Political or stakeholder sensitivities: [sensitivities]
Instructions:
1. Recommend how to communicate direction, confidence, and sequencing without presenting the roadmap as a promise sheet.
2. Distinguish committed work, likely work, and exploratory work.
3. Suggest language that sets expectations without sounding evasive.
4. Include guidance for handling stakeholder pushback on omitted work.
5. Keep the plan useful for both live presentations and written updates.
Output format:
- Communication approach
- Roadmap framing by confidence level
- Suggested language patterns
- Pushback handling guidance
- Common mistakes to avoid
Missing information policy:
Proceed with assumptions unless the audience or roadmap horizon is unclear.
Quality bar:
- Be transparent about uncertainty.
- Preserve trust.
- Avoid roadmap theater.
06
Prioritize Workflow Pain Points Worth Turning into Product Bets
Prioritize workflow pain points by severity, repetition, business leverage, and product-worthiness.
You are prioritizing workflow pain points for product investment.
Use the context below.
Context:
- Workflow pain points under consideration: [pain points]
- Affected users or teams: [users]
- Business impact: [impact]
- Frequency or recurrence: [frequency]
- Strategic context: [strategy]
- Resource constraints: [constraints]
Instructions:
1. Evaluate which pain points are true product opportunities versus local annoyances.
2. Compare them by severity, recurrence, leverage, and fit with strategic priorities.
3. Distinguish problems worth building for from problems better solved with process cleanup.
4. Recommend a prioritization order with rationale.
5. Keep the output selective instead of inflating every pain point into a big bet.
Output format:
- Prioritization criteria
- Ranked pain points
- Strongest product bets
- Better solved with process or tooling tweaks
- Recommended next sequence
Missing information policy:
Proceed with assumptions unless the pain points or business impact are unclear.
Quality bar:
- Product-worthiness focus.
- Selective prioritization.
- Clear rationale.
07
Prioritize an Internal Tool Roadmap for Fastest Workflow Leverage
Prioritize an internal tool roadmap for fastest workflow leverage with effort, impact, and adoption considerations.
You are prioritizing an internal tool roadmap for fastest workflow leverage.
Use the context below.
Context:
- Roadmap ideas or candidate improvements: [ideas]
- Workflow pain points being addressed: [pain points]
- User groups affected: [users]
- Current constraints: [constraints]
- Adoption signals or trust issues: [adoption signals]
- Time horizon: [time horizon]
Instructions:
1. Evaluate which roadmap items create the most workflow leverage soonest.
2. Consider impact, adoption likelihood, implementation effort, and dependency load.
3. Distinguish urgent friction fixes from strategic capability bets.
4. Recommend a practical sequencing plan.
5. Keep the roadmap cut selective rather than politically exhaustive.
Output format:
- Prioritization criteria
- Recommended roadmap cut
- Fastest-leverage items
- Strategic later bets
- Rationale and sequencing notes
Missing information policy:
Proceed with assumptions unless the roadmap ideas or workflow pain points are unclear.
Quality bar:
- Workflow leverage focus.
- Selective prioritization.
- Clear sequencing rationale.