Week 8 Guide: Analysing Feedback
The Real Problem This Solves
After testing you have a lot of raw notes. If you react to every comment you will chase noise and lose direction. This week you find the signal: the patterns that matter, ranked so you know what to fix first. Analysis is what separates a designer from someone who just collects opinions.
Key Ideas You Need First
1. Group before you judge (affinity mapping)
Write each piece of feedback on its own note, then cluster similar notes. Clusters reveal themes. A theme that appears across several testers is a real signal; a one-off comment is usually noise.
2. Separate what people said from what they did
Observed behaviour (a tool slid out) is stronger evidence than a stated preference (I would like it in blue). Weight behaviour higher.
3. Prioritise by impact and effort
You cannot fix everything. Rank problems by how much they hurt the user (impact) against how hard they are to fix (effort). High impact and low effort comes first.
Tools And Materials Needed
- Your Week 7 observation notes and feedback forms.
- The Affinity Map Template.
- The Priority Matrix Worksheet.
- Sticky notes or small paper slips.
Step-By-Step Walkthrough
- Break feedback into single points. One observation or comment per note. Include behaviour, not just words.
- Cluster into themes. Group similar notes on the affinity map. Name each cluster in a few words.
- Count the signal. Mark how many testers each theme came from. Themes seen by two or more are strong.
- Turn themes into problems. Write each strong theme as a clear problem statement, for example "tools slide out of the end pockets".
- Place each problem on the priority matrix. Score impact and effort, then plot it.
- Choose your top three fixes. Take the high impact, lower effort problems first. Write them as an action list for next week.
Demonstrated Example
Raw feedback from two mat tests grouped into themes:
| Theme | Testers | Type |
|---|---|---|
| Tools slide from end pockets | 2 of 2 | Behaviour |
| Ribbon tie is slow and fiddly | 2 of 2 | Behaviour and words |
| Likes the deep pockets | 2 of 2 | Positive, keep it |
| Would prefer a brighter colour | 1 of 2 | Preference, low priority |
Priority decision: the sliding tools is high impact and low effort (a stiffer edge), so it is fix one. The fiddly tie is high impact and low effort (swap to an elastic loop), fix two. Colour is low impact and can wait.
Top three fixes: stiffen the edges, replace the tie with an elastic loop, keep the deep pockets exactly as they are.
Why this is strong: it weights repeated behaviour over one-off preference, and it ranks by impact and effort rather than by whichever comment was loudest.
Your Task This Week
- Break your Week 7 feedback into single notes.
- Cluster them into named themes on the affinity map.
- Turn strong themes into problem statements and plot them on the priority matrix.
- Write your top three fixes as an action list.
Submission Checklist
| Upload item | Pass standard |
|---|---|
| Affinity map | Feedback grouped into named themes, with tester counts. |
| Priority matrix | Problems plotted by impact and effort. |
| Top three fixes | Clear, ranked, and drawn from strong themes. |
Assessment And Pass Criteria
- Feedback is grouped into themes, not left as a flat list.
- Repeated behaviour is weighted above one-off preferences.
- Problems are ranked by impact and effort, not by loudness.
- The top three fixes follow logically from the analysis.
Common Mistakes
- Reacting to every comment. Chase patterns, not one-off remarks.
- Fixing the easy thing first regardless of impact. Impact leads, effort breaks ties.
- Ignoring what hurts. Do not quietly drop the problem you do not want to fix.
- Treating preferences as facts. "I would like blue" is not a usability problem.
Extension Challenge
For your top problem, write two possible fixes and note the risk of each. Having options ready makes next week's iteration faster.