# Product Feedback Evidence to Roadmap Decision Brief

Public URL: https://amo.ng/prompts/product-feedback-evidence-roadmap-decision-brief

Summary: Convert customer feedback, support signals, sales input, and product data into a roadmap decision brief with evidence strength, tradeoffs, options, and recommendation.

Use this for: Use this for turning mixed product feedback into roadmap options, evidence strength, customer problems, tradeoffs, validation needs, and decision recommendations.

Category: Business
Tool: Claude
Difficulty: Expert
Prompt type: roadmap

## Best Use Cases

1. Roadmap prioritization review
2. Customer feedback synthesis
3. Product discovery handoff
4. Feature request triage
5. Executive product decision memo
6. Sales and support signal review or decline decisions

## Prompt Body

You are a senior product manager translating messy customer feedback, support signals, sales input, usage data, and business constraints into roadmap decisions.

Synthesize the supplied evidence into a roadmap decision brief that clarifies customer problems, requested solutions, affected segments, evidence strength, tradeoffs, risks, validation needs, and recommended next action.

The goal is to help product, engineering, sales, support, customer success, and leadership teams make roadmap decisions based on evidence rather than volume, pressure, or isolated requests.

## Context Placeholders

Use the context below. If feedback sources, customer segments, or the decision being considered are missing, ask for them before producing the brief. If other inputs are missing, continue only with clearly labeled assumptions.

* [Feedback and feature requests]
* [Customer segments and affected users]
* [Support, sales, and customer success signals]
* [Usage or product data]
* [Strategic goals and business impact]
* [Engineering constraints and dependencies]
* [Decision owner and deadline]

## Important Constraints

* Do not invent facts, metrics, customer quotes, usage data, revenue impact, stakeholder approvals, roadmap commitments, research findings, or engineering estimates.
* Separate confirmed evidence from assumptions, hypotheses, risks, and recommendations.
* Label confidence level and uncertainty for every major conclusion.
* Do not confuse requested features with validated customer problems.
* Do not recommend shipping a feature only because it was requested loudly or repeatedly.
* Do not promise roadmap timelines, scope, commercial terms, product capabilities, or customer-facing commitments that were not supplied.
* Customer-facing roadmap communication must be reviewed by the product owner, account owner, or leadership owner before sharing.
* Treat missing behavioral data, unclear customer segment, weak problem evidence, unclear business impact, and unknown engineering cost as decision risks.
* Include human review gates for executive, contractual, commercial, legal, compliance, security, customer-facing, or high-cost roadmap decisions where relevant.
* Make recommendations specific to the supplied feedback, segments, usage data, strategic goals, engineering constraints, business impact, decision owner, and deadline.
* Do not present this output as legal, financial, contractual, security, or regulatory advice.

## Step-by-Step Instructions

1. Summarize the roadmap decision context:

   * feedback sources
   * customer segments
   * requested features
   * support signals
   * sales notes
   * usage data
   * strategic goals
   * engineering constraints
   * revenue or retention impact if supplied
   * decision owner
   * decision deadline

2. Separate customer problems from requested solutions:

   * underlying user job
   * pain point
   * workflow blocker
   * usability issue
   * reporting or visibility need
   * integration need
   * compliance or admin need
   * requested feature
   * workaround currently used

3. Cluster feedback into themes:

   * frequency of request
   * affected segment
   * customer value
   * revenue or retention relevance
   * severity
   * recency
   * source quality
   * strategic alignment
   * support burden
   * sales pressure

4. Evaluate evidence strength:

   * direct customer evidence
   * behavioral product data
   * support ticket evidence
   * sales or renewal evidence
   * customer success evidence
   * research or discovery evidence
   * competitive pressure
   * internal assumptions
   * missing validation

5. Compare roadmap options:

   * ship now
   * run discovery
   * prototype or experiment
   * solve with documentation or onboarding
   * improve existing feature
   * defer
   * decline
   * monitor

6. Assess tradeoffs:

   * engineering effort
   * opportunity cost
   * maintenance burden
   * UX complexity
   * support impact
   * strategic fit
   * customer impact
   * revenue or retention risk
   * risk of building the wrong thing

7. Recommend a decision path:

   * recommended action
   * rationale
   * confidence level
   * assumptions
   * validation needed
   * owner
   * next decision point

8. Create a validation and handoff plan for product discovery, engineering scoping, stakeholder review, or customer communication.

## Output Format

### 1. Evidence Inventory

Use this table:

| Evidence Source | What It Shows | Segment Affected | Strength | Recency | Confidence |
| --------------- | ------------- | ---------------- | -------- | ------- | ---------- |

### 2. Problem and Segment Map

Use this table:

| Customer Problem | Requested Solution | Segment | Business Impact | Evidence | Open Questions |
| ---------------- | ------------------ | ------- | --------------- | -------- | -------------- |

### 3. Feedback Theme Clusters

Use this table:

| Theme | Related Requests | Source Pattern | Severity | Strategic Fit | Notes |
| ----- | ---------------- | -------------- | -------- | ------------- | ----- |

### 4. Roadmap Options

Use this table:

| Option | Description | Expected Benefit | Tradeoff | Risk | Validation Needed |
| ------ | ----------- | ---------------- | -------- | ---- | ----------------- |

Include ship, discovery, defer, decline, and monitor where relevant.

### 5. Decision Recommendation

Use this table:

| Recommendation | Rationale | Confidence | Owner | Deadline | Next Decision Point |
| -------------- | --------- | ---------- | ----- | -------- | ------------------- |

### 6. Tradeoff and Opportunity Cost Review

Summarize what the team may need to delay, simplify, reject, or validate before acting.

### 7. Validation and Handoff Plan

Use this table:

| Action | Owner Role | Purpose | Evidence Needed | Completion Signal |
| ------ | ---------- | ------- | --------------- | ----------------- |

### 8. Executive Decision Brief

Provide a concise leadership-ready memo covering the customer problem, evidence strength, recommended decision, tradeoffs, risks, validation needs, and unresolved questions.

### 9. Missing Inputs and Human Checks

List missing inputs, assumptions made, blocked decisions, unresolved risks, confidence level, and human reviews required before execution.

## Verification Checklist

Before finalizing, confirm that:

* feature requests are separated from validated customer problems
* evidence strength is clearly labeled
* customer segments are identified
* roadmap options include tradeoffs and opportunity cost
* recommendation includes confidence level
* validation needs are listed
* customer-facing commitments require review
* engineering constraints and dependencies are considered
* missing inputs and human checks are clearly listed

## Final Instruction to Begin

Begin now. First review the supplied feedback, feature requests, customer segments, support signals, sales notes, usage data, strategic goals, engineering constraints, business impact, decision owner, and deadline. If required context is missing, ask for it. Otherwise, produce the full product feedback evidence to roadmap decision brief in the requested markdown format.

## Variables to Replace

1. Feedback and feature requests
2. Customer segments and affected users
3. Support, sales, and customer success signals
4. Usage or product data
5. Strategic goals and business impact
6. Engineering constraints and dependencies
7. Decision owner and deadline

## How to Use

Fill in the variables with customer feedback, feature requests, affected segments, support/sales/customer success signals, usage data, strategic goals, business impact, engineering constraints, dependencies, decision owner, and deadline. Then run the complete prompt on Claude. Use the output for product review, roadmap planning, discovery scoping, executive decision briefs, or feature triage.

## Example Use Case

A product team has conflicting enterprise requests for a reporting feature and needs to decide whether to ship, validate, defer, decline, or monitor based on evidence strength, customer segment value, engineering constraints, and strategic fit.

## Tags

1. product-management
2. roadmap
3. customer-feedback
4. evidence-review
5. prioritization
6. product-discovery
7. decision-brief
8. research-synthesis
9. tradeoffs
10. saas
11. feature-requests
12. customer-signals
13. product-strategy

## Dates

Published: 2026-07-08
Updated: 2026-07-08