A diary study asks real users to record what they do, think, and struggle with over several days. For product and UX teams, it shows how an app or service fits into daily life, which a one-hour interview cannot do. Diaries are powerful, but they depend on participants actually completing them.
UX diaries fail when the tool feels like homework software. A phone-first board keeps tasks short, media easy, and support inside the study.
When a diary is the right method
Use a diary when the thing you need to understand happens over time, in the moment, or in places you cannot observe. Examples are habits (when do people check this?), triggers (what made them open it?), and workarounds (what do they do when it breaks?). If your question is about one screen or one flow, a usability test is faster and cheaper.
Swipe to see all columns
| Question | Better method |
|---|---|
| Can people complete checkout? | Moderated or unmoderated usability test |
| What happens around the product during a normal week? | Diary study |
| Why did people leave after signup? | Interviews, possibly followed by a diary |
| How often and where is it used? | Analytics for how often; a diary for why and where |
Why diary studies drop off
- Participants are asked to install an app and forget about it
- Tasks are long and arrive at awkward times
- Uploading a screenshot takes too many steps
- Nobody answers when something breaks
Each of these is a design problem, not a participant problem. A board that opens in the phone’s browser, asks for one clear thing at a time, and offers help in the same place removes most of them.
A simple multi-day structure
- 1Day 1: context and baseline habits
- 2Middle days: in-situ screenshots/photos + friction notes
- 3Final day: tradeoffs, wishlist, and ‘show us the workaround’
‘In situ’ means in the moment and in the real setting, such as capturing a confusing screen while it is happening instead of describing it from memory later. ‘Friction’ is anything that slows people down or annoys them. The final day asks what they would change and what they do to get around problems, which is often where the best product ideas live.
Writing good diary tasks
- Ask for one thing per task. ‘Share a screenshot and one line on what you were trying to do’ works; five sub-questions do not.
- Anchor to moments, not days: ‘the next time you open the app’ beats ‘tell us about your usage today.’
- Use ratings sparingly for quick mood or effort checks, then ask a single open follow-up.
- Make the participant’s effort obvious: say how long it should take.
- End with something that respects their time, such as a thank-you and a preview of tomorrow.
Choosing the right kind of media
Sometimes you want a screenshot someone already has. Sometimes you want a photo taken live, so you know it shows the actual moment. Decide which you need for each task. If authenticity matters, ask for a fresh photo. If you only need to see a screen state, allowing an upload is fine. Short video works well when tone or physical context matters, such as showing where the phone sits during use.
Synthesizing without drowning
Diary data is large: many people, many days, many images. Synthesis means turning it into a small number of findings you can defend. Start with themes (recurring ideas), then check whether each theme holds across participants and across days. Keep one or two vivid quotes or screenshots per theme as evidence. Review themes while the study is running, so a gap on Day 2 can become a sharper task on Day 3.
A scenario
A fintech team wants to understand how people check their balance during a normal week. On Day 1, participants describe their routine. On Days 2 and 3, they capture screenshots at the moment they open the app and write one line about what they were trying to do. On Day 4, they describe a workaround they use. The team finds that people check balances while standing in line at a store, which changes what the home screen should show.
FAQ