Loading

Feedback synthesis to prioritized themes

The five themes that matter, quantified and quoted.

10 minProductClaude Cowork
Loading

Set up

Try a plugin

The Product Management plugin ships with /synthesize-research and other discovery skills as a starting point, already structured to cluster raw signal into themes and rank them. If your admin manages plugins and it's not available yet, skip this; nothing below requires it.

Product ManagementWrite feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
Add
/synthesize-researchSynthesize user research from interviews, surveys, and feedback into structured insights.
Run
/roadmap-updateUpdate, create, or reprioritize your product roadmap.
Run

Connect your tools

Claude Cowork is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Navigate to Customize → Connectors in Cowork to set up.

Zendesk
Read support tickets and their tags so product hears what customers are actually saying, verbatim.
Custom connector
Google DriveOptional
Connect
Browse all connectorsOpen in Cowork

Set your working folder

Drag the files you'll use (the NPS verbatim export, the support ticket CSV, the sales call snippets, the six interview transcripts) into one folder on your machine, then point Cowork at it. Cowork reads from it and writes the Voice of Customer brief back to it. If you run this every quarter, create a Cowork project from that folder so your sources, instructions, and memory stay attached.

Product / voc-q2
nps-verbatims-q2.csvApr 22, 2026412 KB
zendesk-export-feedback.csvApr 22, 20261.1 MB
sales-call-snippets.mdApr 20, 202638 KB
interview-01-ops-lead.docxApr 9, 202652 KB
interview-02 through 06.docxOptionalApr 20265 files
In Cowork’s chat bar:Product / voc-q2

The prompt

Copy this into Claude Cowork

Read this folder plus the #product-feedback Slack channel and the open Zendesk tickets tagged feedback. Cluster everything into 5 to 7 themes, count how often each shows up and how severe it is, pull the best verbatim for each, flag which map to a Linear roadmap item versus net-new, and write a one-page Voice of Customer brief for roadmap review.

Product / voc-q2

Why this works

Prompt

Give a number range. "5 to 7 themes" forces real clustering instead of a forty-row tag list, so the brief fits on one page and the roadmap conversation stays on the top signals.

Prompt

Ask for frequency and severity. Naming both gives Claude your ranking criteria, so the themes come back ordered by what matters to planning rather than just by how often they came up.

Prompt

Ask for the single best example. The single best quote does more in roadmap review than a wall of evidence; Cowork picks the strongest line and links the rest underneath.

Source

Compare against your existing plan. "Map to a Linear roadmap item versus net-new" means the brief arrives already split into validate-what-we-planned and here-is-what-we-missed.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Cowork matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Cowork work for you

A plugin skill is a starting point — customize it with your own practices and expertise. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill, or edit the /synthesize-research skill with my feedback.

Product

Make it repeatable

Run it ahead of every roadmap review

Feedback piles up between planning cycles whether or not anyone is reading it. Type /schedule in the prompt, or open Scheduled in the Cowork sidebar, and the customized skill produces a fresh brief the Friday before each roadmap review.

/schedule Every Friday at 4pm, run /synthesize-research against Product/voc-<current-quarter> plus the live Slack and Zendesk sources, and write the brief to that folder as voc-brief-<date>.md.

Product
Scheduled taskActive
Monthly Voice of Customer brief

Runs /synthesize-research against the quarter's VoC folder plus live Slack and Zendesk and writes the one-page brief back to the folder.

Every Friday at 4:00pmOpen in Cowork

Share with your teammates

Your customized /synthesize-research now carries your severity scale, your standing sources, and your brief format. Share it so every PM on the team clusters feedback the same way, and roadmap review reads one consistent VoC page no matter whose area it covers.

Going forward