Protocol
Capture the context, then account for what went missing
A diary moves the report closer to the event, which can preserve context that a later interview turns into a vague average. But it creates a different measurement problem: people can forget, skip, simplify, or change what they do because logging interrupts the task. Treat the diary as sampled self-report, not hidden telemetry.
Before you use it
- Use when
- A problem happens occasionally and interviews produce vague averages.
Keep this limit in mind
- Recording can change behavior. Missing entries are not proof that the event never happened; protect personal details and allow withdrawal.
Current editorial reading
Closer to the event changes the evidence you can collect
Diary methods are useful when the episode is intermittent and the surrounding situation matters. Bolger, Davis and Rafaeli describe diaries as frequent reports of events and experiences in daily life, allowing researchers to capture particulars that traditional retrospective designs often miss. A later review of ecological momentary assessment makes the same advantage more explicit: reporting near the moment can reduce some retrospective bias and preserve variation across contexts and time. This supports the card's core move — record the situation, attempted action and result while they are still recoverable — but not the stronger claim that a near-event report is a complete or objective record.
Silence in the diary is ambiguous
No entry can mean that the event did not happen. It can also mean the participant forgot, the prompt arrived at a bad time, the task was too demanding, or the participant gradually stopped engaging. Arndt and Rose show this clearly in an event-contingent diary study: daily reminders increased participation, yet 27% of learners still submitted no diary entries, and participation differed across learner groups. That makes missingness part of the method, not empty space to ignore. Record opportunities, delays and missed entries where practical, then avoid turning 'not logged' into 'did not occur'.
The act of recording can disturb the episode
Carter and Mankoff describe a basic trade-off in HCI diary studies. Asking participants to answer questions as events happen can preserve context, but the questions can distract from the main task; without an objective observer, the researcher also cannot fully verify how the log matches the event. Their work on media capture suggests one practical option: make the immediate capture lightweight, then use the captured cue in a later discussion. That reduces interruption but increases the distance from the event. There is no free format: choose how much to capture now according to what would be lost if you wait.
Keep the entry small, then do the interpretation later
For ordinary product discovery, a compact event record is usually more useful than a daily essay. Define the event in concrete terms, ask for the immediate context, the attempted action and the result, and keep a timestamp or delay marker when the tool allows it. If a screenshot, short note or other cue can be collected without creating privacy or workload problems, it can support the follow-up. After the diary period, compare contrasting episodes and ask about gaps instead of averaging everything into 'usually'. When system logs or other non-sensitive traces exist, use them to check timing or opportunity; do not treat either source as automatically superior.
Questions worth asking before you trust the pattern
Does no entry mean no event? No — first check whether the person had a realistic chance and reason to log it. Should every entry be immediate? Not necessarily; immediate capture can interrupt the task, while delayed capture loses detail, so keep the first capture as small as the research question allows. Can analytics replace the diary? Usually not when the missing information is intention, context or an off-system workaround; analytics can show recorded behaviour, while a diary can add the participant's account of why and what happened around it. Can reminders solve missingness? They may improve participation, but they do not remove self-selection or guarantee that every relevant episode was captured.
Take it with you
Use a diary when rare or distributed episodes matter more than a retrospective average. Capture only the context needed to reconstruct the episode, track delay and missingness where possible, and use follow-up or other traces to test the story. A diary is valuable precisely because it is close to real life; it is not a complete log of real life.
Sources and evidence (4)
What we checked
Frequent diary reports can capture particulars of daily events and experiences that are difficult to recover with more traditional retrospective designs.
This supports collecting repeated event-close reports. It does not make those reports complete, unbiased or objectively verified.
Diary Methods: Capturing Life as It Is Lived · Abstract
Momentary self-report is used partly to reduce retrospective bias, but technology and protocol design create competing concerns around engagement, reporting burden, data validity and honest disclosure.
This supports the core trade-off in the editorial analysis: moving measurement closer to the event can improve context while creating participation and measurement costs.
The Design of Ecological Momentary Assessment Technologies · Abstract; Research Highlights; section 1.1
Participant-captured diary data can interrupt the activity being studied, and researchers may be unable to verify how closely a participant log matches the underlying event without another observation source.
This challenges any interpretation of a diary as passive telemetry and supports keeping immediate capture lightweight.
When Participants Do the Capturing: The Role of Media in Diary Studies · Introduction and diary-method discussion
In an event-contingent educational diary, reminders improved participation but substantial non-participation remained, and engagement differed across participant groups, creating a risk of self-selection bias.
This limits conclusions from missing entries and from patterns based only on the participants who kept logging.
Capturing life as it is truly lived? Improving diary data in educational research · Abstract; exemplar study two; reflections on participation
Event-contingent reports completed soon after an event can preserve contextual details that are harder to obtain from later retrospective questionnaires.
This supports asking for a short context-rich entry near the event while preserving the paper's cautions about burden and selective participation.
Capturing life as it is truly lived? Improving diary data in educational research · Exemplar study two; discussion of event-contingent diaries
Editorial sources (4)
- Diary Methods: Capturing Life as It Is Lived — Niall Bolger, Angelina Davis, Eshkol Rafaeli
- When Participants Do the Capturing: The Role of Media in Diary Studies — Scott Carter, Jennifer Mankoff
- The Design of Ecological Momentary Assessment Technologies — Kevin Doherty, Andreas Balaskas, Gavin Doherty
- Capturing life as it is truly lived? Improving diary data in educational research — Henriette L. Arndt, Heath Rose
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingCapture the context, then account for what went missing
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaDeliver the small service before automating its machinery
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
Diary studies collect participant accounts of activities and experiences over a period of time.
Accounts can be selective, delayed or missing; the proposed small diary is not a validated universal format.
Diary Studies: Understanding Long-Term User Behavior and Experiences · Definition, logging instructions and follow-up.
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details