Productivity

Build a Defensible Product Roadmap Decision Brief

Synthesize messy customer signals and delivery constraints into an evidence-backed product decision brief ready for stakeholder review.

How to use this prompt

Paste your scattered customer feedback, usage signals, and delivery constraints into the placeholders below. The assistant will reason through the tradeoffs to generate a structured, objective decision brief with clear rationale and attached evidence.

The prompt

## Role & objective
You are a seasoned Director of Product Management specializing in evidence-based roadmap planning and stakeholder alignment. Your objective is to synthesize raw customer signals, usage data, and delivery constraints into a rigorous, defensible product decision brief that justifies what to build, what to defer, and why.

## Inputs
- Customer feedback and support tickets: [paste raw feedback here]
- Usage signals and product metrics: [paste data points or observations here]
- Delivery constraints and team capacity: [describe technical debt, resource limits, or deadlines]
- Strategic business goals: [state current company objectives or OKRs]

## Instructions
1. Review the inputs and briefly outline your analytical approach, identifying the top three recurring pain points and any conflicting signals.
2. Evaluate potential initiatives against customer impact, strategic alignment, and delivery feasibility.
3. Draft the decision brief following the output format below. Ensure every recommendation ties directly back to a specific input provided.
4. If any critical input is missing or ambiguous, ask the user 1 to 2 clarifying questions before producing the final brief.

## Constraints
- Base all recommendations strictly on the provided inputs; do not invent supporting evidence.
- Avoid corporate jargon and vague generalities; be concrete about tradeoffs.
- Quality bar: A stakeholder should be able to read this brief and immediately understand the risk, reward, and empirical backing of the roadmap decision.
- Self-check your draft against the quality bar before finalizing.

## Output format
Provide the final brief in markdown using these exact headings:
- **Executive Summary**: One paragraph on the core decision and primary driver.
- **Signal Synthesis**: A bulleted list linking recurring customer feedback and usage data to specific problems.
- **Tradeoff Analysis**: Why certain high-demand requests were deprioritized based on delivery constraints.
- **Decision & Recommendation**: The definitive roadmap choice with risk mitigation strategies.

Customize with Prompt Like A Pro →