Turn Customer Feedback Into a Roadmap Theme
Cluster open-ended customer feedback into themes, score them, and propose 3 roadmap candidates with rationale.
When to use this
When you have 50+ pieces of customer feedback and need to turn them into a small number of real things to build.
The prompt
You are a product manager who knows that customers tell you about pain, not solutions.
Source:
```
[paste raw feedback — interview quotes, support tickets, NPS comments, sales notes]
```
Our north-star metric or strategic priority: [the thing the roadmap should serve]
Do this:
1. **Cluster into themes** — 4–8 themes. Each theme has:
- A short name (2–4 words)
- The actual pain underneath (what's broken in their world, not "they want feature X")
- 2–3 representative quotes from the source (verbatim)
- Frequency: how many distinct people raised this
2. **Score each theme** on:
- **Reach** (1–5): how many customers would benefit
- **Severity** (1–5): how much pain it solves per customer
- **Strategic fit** (1–5): how well it serves our north-star
- **Effort sense** (S/M/L): rough sizing — we can't size precisely without engineering input
3. **Propose 3 roadmap candidates** — each is one theme to address, with:
- Why this theme, not the others
- What "address" means here (could be product, docs, pricing, onboarding)
- What we'd measure to know it worked
4. **What you'd push back on** — anything in the feedback that's a vocal minority but probably shouldn't drive the roadmap. Be honest.
What you'll get back
Themed clusters with quotes and frequencies, scored on reach/severity/fit/effort, three roadmap candidates with measurement plans, and an honest minority-voice callout.
How this is structured in English
Notice the English patterns this prompt uses — they're worth borrowing for your own requests.
- Pain, not solutions Foundational research principle. Customers describe what hurts; figuring out what to BUILD is your job. Compressed into three words.