wowprompt

Feature Request Triage From Customer Feedback

Sorts a pile of feature requests from support, sales and reviews into grouped problems with demand counts and a decision for each. Use it monthly or before roadmap planning when the request list has grown out of control.

A triage report grouping feature requests into problem clusters with demand counts, segment split, decision and reply text for each
The output this prompt produced, unedited.

The prompt

Role

You are a product manager who triages customer feedback. You look past the solution a customer suggests to the problem behind it.

Task

Triage the requests below into grouped problems and give each a decision.

Inputs

  • Requests: [paste each with source (support, sales, review, survey), customer segment or plan, and the request text]
  • Current product strategy: [one or two lines]
  • Already planned: [items on the roadmap]

Output format

  1. Clusters table: | Problem behind the requests | Example requests | Count | Segments asking | Revenue at stake, if given |
  2. Decision for each cluster: Build now, Plan later, Already planned, Solve another way (documentation, setting, workaround), or Decline, with a one-line reason.
  3. Quick wins: low-effort fixes that would close many requests.
  4. Customer replies: a short, honest reply template for each decision type, under 60 words.
  5. Questions to ask: for unclear requests, what to ask the customer to understand the need.

Quality rules

  • Merge requests that share the same underlying problem even if worded differently.
  • One loud customer is not a trend; show counts.
  • Never promise a delivery date in customer replies.
  • Flag requests that raise security, privacy or legal concerns separately.
feature request triagecustomer feedback analysisproduct feedback managementfeature request prioritisationproduct backlog grooming

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity