In short
- Written feedback is cheap and quick to read, but people tidy up their memories.
- Think-aloud video catches the moment of confusion, but takes time to watch.
- Use written for opinions and bug reports. Use video for anything with steps.
01What written feedback is good at
Typed answers are fast to collect and fast to read. They work well for bug reports, quick opinions on a design, and things like Google Play closed tests, where you need a steady stream of short notes.
The catch: people write what they remember, and they remember the end, not the struggle. "It was fine once I found it" hides the 40 seconds they spent looking.
02What video catches
In a think-aloud recording, testers say what they expect as they go. You hear the pause, the "wait, where's..." and the wrong tap before the right one. That moment is where your fix is.
Okay, add a client. Is it this plus? No, that made an invoice.A tester, thinking out loud
Nobody would write that sentence afterwards. It's the most useful sentence in the test.
03The cost of video: your time
Ten recordings of ten minutes each is nearly two hours of watching, before you've written anything down. That's why recordings often go unwatched.
The fix is to have someone watch them for you and pull out the moments that matter. That's what our fix list is: a designer watches every recording and gives you the five problems, in order, with the second each one happened.
04When to use which
| You want to know | Use |
|---|---|
| Whether a feature has bugs | Written |
| Which of two designs people prefer | Written |
| Why people drop out of sign-up | Video |
| Whether a new user can do the main thing | Video |
| Engagement over 14 days of closed testing | Written notes |

Video, without the two hours.
Every test includes recordings and a fix list you can read in five minutes.





