Week 8 Worked Example: Analysing Feedback
Affinity Map (grouped feedback)
| Theme | Testers | Type |
|---|---|---|
| Tools slide from end pockets | 2 of 2 | Behaviour |
| Ribbon tie slow and fiddly | 2 of 2 | Behaviour and words |
| Deep pockets work well | 2 of 2 | Positive, keep |
| Prefer brighter colour | 1 of 2 | Preference |
Priority Matrix
| Problem | Impact | Effort | Box |
|---|---|---|---|
| Tools slide out | High | Low | Do first |
| Fiddly tie | High | Low | Do first |
| Colour preference | Low | Low | Maybe later |
Top Three Fixes For Next Week
- Stiffen the mat edges so end tools stay put.
- Replace the ribbon tie with a one-hand elastic loop.
- Keep the deep pockets unchanged, they already work.
Why This Passes
- Feedback is grouped into themes with tester counts, not left as a flat list.
- Repeated behaviour is ranked above a one-off colour preference.
- Fixes are chosen by impact and effort, and include keeping what works.
Weak Versus Strong
Weak
"They said make it blue, so I will make it blue." Reacts to a single preference and ignores the two behaviour problems that both testers hit.
Strong
Themes counted, ranked by impact and effort, top three fixes that address the real usability failures and protect what already works.