Sorting a Pile of Feedback Into Themes
After a month of widget notes, support tickets and test sessions, you have hundreds of fragments. Grouping them by theme turns noise into a short list of decisions.
Gather everything in one place
Feedback arrives through many doors: the widget, the support inbox, app store reviews, sales calls, test notes. Copy each item into one list, one observation per line, with its source and date. Do not summarise yet; the wording people use is evidence.
Split long notes into single observations
A message like "Search is slow and I couldn't find the returns policy, also love the new colours" holds three separate points. Split it so each can be grouped on its own.
Group bottom-up
An affinity diagram is a tool for organising ideas and data into groups based on their natural relationships. In practice, you place notes that seem related next to each other, and only after the groups form do you give each one a name. Starting with categories you already believe in tends to force notes into boxes they do not fit.
- Work quickly; first instincts are usually fine.
- If a note fits two groups, duplicate it.
- Leave a "not sure" pile and revisit it at the end.
- Do it with at least one other person, ideally someone from support who hears customers daily.
Keep the raw material
Once the groups exist, it is tempting to throw away the individual notes and keep only the headings. Keep them. When someone later asks why a theme matters, the original words of real users are far more convincing than a summary, and they let you re-sort the pile when new feedback arrives and the old groups stop fitting.
Name groups as problems, not solutions
"Add a filter" is a solution someone suggested. "People cannot narrow long lists" is the problem behind it. Naming the problem keeps options open; the best fix may not be the one that was requested.
Count, but carefully
The number of notes in a group is a rough signal, not a measurement. Some problems generate lots of noise because they are irritating but harmless; others are reported rarely because the people affected simply leave. Weigh each theme by how badly it blocks the task, not just by volume.
Turn themes into actions
- For each top theme, write the problem in one sentence with two or three verbatim quotes.
- Decide what you will do: fix, investigate further, or deliberately leave.
- Record the decision and the date, so you can check later whether the notes in that group stopped arriving.
The theme list is only useful if it changes the roadmap. Share it with whoever decides what gets built next.
By Iris Calloway · last checked 2026-11-09