The only research method that captures what actually happens between the moments you're watching
A longitudinal research method where participants self-report their experiences, behaviours, and thoughts over days or weeks in their natural context.
What Is a Diary Study?
A diary study is a longitudinal qualitative research method where participants document their own experiences over a set period — anywhere from a few days to several weeks. They log what they're doing, thinking, or feeling in the moment it happens, rather than recalling it later in an interview.
Entries can be structured (prompted at specific times or triggered by a behaviour) or open-ended and participant-driven. The medium varies too — text entries, photos, short video clips, or purpose-built research apps.
The defining characteristic is that data collection happens in the field, in real time. That's what separates diary studies from almost every other method in the Usability Testing family.
What It Captures That Other Methods Miss
Lab sessions and interviews share the same weakness: they're artificial. A user in a test behaves differently than a user at 11pm trying to complete an expense report before a deadline. Interviews rely on recall, and recall is unreliable — people flatten messy experiences into clean narratives, forget pain points that have become normalised, and emphasise the recent over the typical.
Diary studies sidestep this. When a user logs a frustration five minutes after it happened, you're getting unfiltered signal. You learn about the context around the product — the interruptions, the workarounds, the edge cases that never surface in a facilitated session.
"Diary studies reveal the texture of everyday experience in a way that no lab session ever could." — Erin Bradner, UX Research Lead
This makes them particularly valuable when you suspect users' real workflows differ significantly from the happy path your team designed for.
When to Run One (and When Not To)
Diary studies are worth the effort when:
- You're trying to understand a behaviour that unfolds over time — onboarding, recurring tasks, long purchase cycles
- You suspect your product is used in contexts you don't fully understand
- You need data on frequency: how often do users actually do X?
- You're exploring a problem space before designing a solution
They're probably the wrong choice when:
- You need quick answers to a specific usability question (a Usability Testing session is faster)
- Your timeline is under two weeks — setup and synthesis take time
- Your users won't commit to regular logging, or the target behaviour is rare
For teams already doing Contextual Inquiry, diary studies are a natural complement — field observation tells you what happens in one sitting; diary studies tell you what happens across a week.
Running One Without Losing Your Mind
A few things make or break a diary study in practice:
Keep entry friction low. The more work each log entry takes, the fewer you'll get. A photo plus one sentence beats a five-field form every time.
Use triggered prompts sparingly. A few well-timed nudges help maintain participation. Too many feel intrusive and cause drop-off.
Recruit 10–15 participants for most studies. Diary studies don't need large samples. Depth matters more than breadth.
Plan your synthesis time. Raw diary data is messy. Budget at least as much time to analyse as you did to collect. Feed themes into an Affinity Mapping session to organise before drawing product conclusions.