Product

Product Feedback Summary Prompt

Key Findings, Recommendations, Open Risks — collected feedback compressed for the roadmap discussion, with recommendations the source actually supports.

Overview

Feedback summaries drift in a specific direction: the model's own product opinions leak into the recommendations. This setup compresses collected feedback into Findings & Recommendations structure — Key Findings with numbers as written, Recommendations the source makes OR directly supports (nothing freelanced), Open Risks for what the feedback leaves unresolved — under High Fidelity with Important Quotes, so the feedback's strongest statements arrive in customers' own words. Built for the quarterly roadmap discussion, where the summary competes with opinions.

Workflow

Compress the collection, not the items
Run it on the assembled feedback set — per-item processing is classification and extraction territory.
Audit the Recommendations section
"Makes or directly supports" is the leash — any recommendation without a finding behind it is a red flag.
Bring quotes to the meeting
A verbatim customer sentence ends roadmap debates that summaries can't.

Why This Works

Findings/Recommendations separation keeps evidence and advice distinct
The source-support rule stops the model's product opinions from leaking in
Open Risks gives the skeptics a section, which keeps the summary credible

Best for

Product teams running quarterly planning on real input
Feedback collections too large for everyone to read
Discussions where "customers want X" needs receipts

Not for

Categorizing individual feedback messages — that's the Data Classification Prompt
Mining individual reviews into fields — that's the Extraction Prompt Generator

Use cases

Preparing the feedback digest for roadmap planning
Keeping recommendations tied to what customers actually said
Quoting the strongest customer statements verbatim

Customize This Resource

Opens this setup in Structured Summary Prompt. Generate to get the full summary prompt — then adjust the structure, length, and fidelity rules.

Open in Structured Summary Prompt

Prompt Template

TASK
Summarize collected product feedback for the quarterly roadmap discussion.
Summarize the source text in the input. Do not write new content — compress what is there.

SOURCE
The source is unstructured free text.
Reading guidance: Read the whole text before compressing — the key point may come late.
Emphasis: Surface the main points and the notable details.

OUTPUT STRUCTURE
Use exactly these markdown sections, in this order:
## Key Findings
What the source establishes, with numbers as written.
## Recommendations
Recommendations the source makes or directly supports.
## Open Risks
Risks and unknowns the source leaves open.

LENGTH RULES
- Balance coverage and brevity: cover every major point once, no point twice.
- Per section: 2–4 sentences each.
- Never pad a thin section — a short faithful section beats a full invented one.

FIDELITY RULES
- Summarize only what appears in the source — do not add outside knowledge.
- Keep interpretation minimal; when you interpret, make it recognizable as interpretation.
- Preserve numbers, dates, and names exactly as written.

QUOTE RULES
- Include direct quotes for the most important statements — quote exactly, in quotation marks.
- Attribute each quote to its speaker or section when identifiable.

OUTPUT RULES
- Return only the summary in markdown — no preamble ("Here is the summary"), no closing commentary.
- Use the section headings exactly as written above.
- Do not address the reader or the author — summarize the source.

Related Resources

Explore more resources that work well with this one.

Used in Playbooks

Complete workflows that include this resource as a step.

AI Customer Feedback Analysis Workflow Workflow · 3 steps

Tip: Save time by exploring related resources and tools that integrate with this workflow.

Explore all resources