Organize messy user research notes into meaningful clusters so you can identify patterns, prioritize themes, and make confident product decisions.
The template
Raw Notes & Observations
Paste or write every individual observation, quote, or note captured during research — one idea per sticky note or row.
Example: "User said she always forgets where the export button is." / "P3 mentioned onboarding felt overwhelming on day one." / "Two users tried to find billing under Settings first."
Affinity Clusters (Themes)
Group related notes together under a descriptive theme label that captures the shared idea across all notes in that cluster.
Example: Theme: "Navigation Confusion" — includes notes about misplaced export button, unexpected billing location, and difficulty finding account settings across 6 participants.
Frequency & Severity Score
Record how many participants mentioned each theme and rate its impact on a 1–3 scale so you can objectively prioritize what to act on first.
Example: "Navigation Confusion" — mentioned by 7 of 10 participants, severity 3 (blocks task completion); "Slow load times" — mentioned by 3 of 10, severity 2 (causes frustration but workaround exists).
Recommended Actions
Write one concrete next step for each theme — a design change, a follow-up question, or a team to loop in — so insights don't stall in a doc.
Example: For "Navigation Confusion": run a card sort with 5 users to validate a revised information architecture before next sprint; share findings with the design lead by Friday.
How to use it
Dump all your raw notes After your research sessions, paste every observation, quote, and field note into the Raw Notes section — don't filter or interpret yet, just get everything out.
Group notes into clusters Read through all notes and physically or digitally move similar ones together, then write a short theme label that honestly describes what connects them.
Score each theme by frequency and severity Count how many participants contributed notes to each cluster and rate how seriously the theme affects the user experience on a 1–3 scale.
Define one action per theme For every cluster, write a single specific next step — a design change, a stakeholder to brief, or a hypothesis to test — so the map drives real decisions.
What it looks like filled in
Navigation Confusion
"I kept looking for the export option under File — I never thought to check the dashboard header."
→ Redesign the top navigation to surface export and key actions as persistent, labelled icon buttons before the next usability round.
Overwhelming Onboarding
"There were so many steps on day one — I wasn't sure what I actually needed to do versus what was optional."
→ Introduce a progressive onboarding checklist that separates must-complete setup steps from optional feature discovery to reduce cognitive load.
Lack of Confidence in Data Accuracy
"I always double-check the numbers in a spreadsheet because I'm not 100% sure the dashboard is pulling from the right date range."
→ Add a persistent data source and date-range indicator to every chart so users can verify context without leaving the dashboard.
Why teams skip the template
Manually clustering hundreds of notes takes hours Moving sticky notes or rows one by one into theme groups is time-consuming and easy to abandon halfway through when research backlogs pile up.
Theme labels are subjective and inconsistent across teammates Two researchers grouping the same notes will often produce different clusters, making it hard to compare studies or build a reliable pattern library over time.
Insights lose urgency by the time the map is finished By the time you've clustered, scored, and written up actions — often days after fieldwork — stakeholder interest has moved on and the window to act has narrowed.
Analyze your user research notes automatically — no template needed
