Complete firstConcrete subject
Define research question, duration, and triggering event; plan privacy, support, and a short pilot.
Without a boundary the run becomes generic and untestable.
Method guideUX Research
Diary Study
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time1-4 Wochen
Participants5-20
FormatAsync
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstAccess and participation
Research lead · participants · recorder or analyst · domain decision owner
Missing perspectives or access are made visible before starting.
02
Preparation
What needs to be ready before start
Materials
Consent, research protocol, secure raw-data store, and analysis surface
People / roles
Research lead · participants · recorder or analyst · domain decision owner
Pre-read
Define research question, duration, and triggering event; plan privacy, support, and a short pilot. Prepare real cases, sources, and boundaries.
Time needed
One to four weeks plus exit interviews.
Setup
Create a workspace with Study plan · Sample · Piloted template · Diary entries · Longitudinal patterns; keep example values separate from live data.
03
Core question
The one question this method answers
Which recurring experiences, triggers, and changes appear over time beyond a single session?
04
Flow
Phases with goal, actions, output and pitfall
A diary study captures moments close to participants’ lived experience, preserving context and time. Later analysis reveals patterns across duration, change, and repetition in everyday use.
Diary Study · working structure
Fictional example
Fictional values are assigned to explicit method fields.
| Entry | Time | Trigger | Action | Experience | Evidence |
|---|---|---|---|---|---|
| MondayRecord a timely diary entry with trigger, action, experience, and evidence. | 08:42 | Part unavailable in the job | Searched chat, then called warehouse | Frustrated; customer waiting | Screenshot of empty inventory |
| ThursdayRecord a timely diary entry with trigger, action, experience, and evidence. | 15:10 | Alternative suggested | Checked compatibility through a photo | Uncertain but faster than Monday | Label photo and six-minute timer |
| TuesdayRecord a timely diary entry with trigger, action, experience, and evidence. | 11:25 | Same part recurs | Reused own photo | Confident; no call needed | Photo ID and completion time |
1. Time
- Monday
- 08:42
- Thursday
- 15:10
- Tuesday
- 11:25
2. Trigger
- Monday
- Part unavailable in the job
- Thursday
- Alternative suggested
- Tuesday
- Same part recurs
3. Action
- Monday
- Searched chat, then called warehouse
- Thursday
- Checked compatibility through a photo
- Tuesday
- Reused own photo
4. Experience
- Monday
- Frustrated; customer waiting
- Thursday
- Uncertain but faster than Monday
- Tuesday
- Confident; no call needed
5. Evidence
- Monday
- Screenshot of empty inventory
- Thursday
- Label photo and six-minute timer
- Tuesday
- Photo ID and completion time
All details are fictional.
- 1
Design
Study plan
Goal
Study plan: Define research focus, duration, event- or interval-based logging, and privacy.
Inputs for this step
- Define research question, duration, and triggering event; plan privacy, support, and a short pilot.
- Consent, research protocol, secure raw-data store, and analysis surface
Actions
- Define research focus, duration, event- or interval-based logging, and privacy.
Output
Study plan
Define research focus, duration, event- or interval-based logging, and privacy
Quality check
Are question, duration, event logic, and privacy explicit?
Pitfall
When duration and event logic stay unclear, participants later do not know when an entry is due. Fix the research focus, duration, entry triggers, and privacy rules clearly before the study starts.
Timing: Use the time needed within the overall frame; close the step only after its check passes.
- 2
Template
Sample
Goal
Sample: Pilot a diary format with short prompts, timestamps, and optional media evidence.
Inputs for this step
- Study plan
Actions
- Pilot a diary format with short prompts, timestamps, and optional media evidence.
Output
Piloted template
Pilot a diary format with short prompts, timestamps, and optional media evidence
Quality check
Is the template short, understandable in daily use, and piloted with real entries?
Pitfall
When the template uses long prompts or jargon, participants abandon entries in daily life. Pilot the format with short prompts and timestamps against real test entries and simplify it afterward.
Timing: Use the time needed within the overall frame; close the step only after its check passes.
- 3
Recruit
Piloted template
Goal
Piloted template: Onboard participants, practise one entry, and explain the support path.
Inputs for this step
- Sample
Actions
- Select participants for relevant experience and usage contexts; confirm consent before the first entry.
- Onboard participants, practise one entry, and explain the support path.
Output
Onboarded sample
Onboard participants, practise one entry, and explain the support path
Quality check
Can participants create a complete entry and reach support?
Pitfall
When participants start without practice, it stays unclear whether they can create a complete entry or reach support when needed. Select participants deliberately by experience, practice one example entry together, and show the support channel.
Timing: Use the time needed within the overall frame; close the step only after its check passes.
- 4
Diary
Diary entries
Goal
Diary entries: Collect entries over time, monitor completion, and send neutral reminders.
Inputs for this step
- Piloted template
Actions
- Collect entries over time, monitor completion, and send neutral reminders.
Output
Diary entries
Collect entries over time, monitor completion, and send neutral reminders
Quality check
Do reminders remain neutral, with missing entries visible rather than filled in?
Pitfall
When reminders suggest the expected answer or missing entries get filled in afterward, the longitudinal data is distorted. Keep reminders neutral and leave missing entries visible as gaps instead of filling them in.
Timing: Use the time needed within the overall frame; close the step only after its check passes.
- 5
Analyse
Longitudinal patterns
Goal
Longitudinal patterns: Analyse entries across time, triggers, and cases, then deepen findings in exit interviews.
Inputs for this step
- Diary entries
Actions
- Analyse entries across time, triggers, and cases, then deepen findings in exit interviews.
Output
Longitudinal patterns
Analyse entries across time, triggers, and cases, then deepen findings in exit interviews
Quality check
Are longitudinal patterns supported by entries and checked in exit interviews?
Pitfall
When time patterns are asserted only from a gut feeling, they cannot be defended in the exit interview. Ground every pattern in concrete entries and verify it with participants during the exit interview.
Timing: Use the time needed within the overall frame; close the step only after its check passes.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Longitudinal patterns with evidence, open points, owner, and review.
Versioning / ownership
Record date, owner, source state, and review date; preserve earlier versions.
Tool alternatives
- Shared workspace
- Consent, research protocol, secure raw-data store, and analysis surface
- Versioned result repository
diary-study-working-template.md
Plan subject, participation, complete flow, and review.
Diary Study: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Whole initiative Time: One to four weeks plus exit interviews.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Consent, research protocol, secure raw-data store, and analysis surface
- Roles: Research lead · participants · recorder or analyst · domain decision owner
- Advance information: Define research question, duration, and triggering event; plan privacy, support, and a short pilot. Prepare real cases, sources, and boundaries.
- Overall time needed: One to four weeks plus exit interviews.
- Setup: Create a workspace with Study plan · Sample · Piloted template · Diary entries · Longitudinal patterns; keep example values separate from live data.
Prepare for the work steps
Design: Study plan
- Define research question, duration, and triggering event; plan privacy, support, and a short pilot.
- Consent, research protocol, secure raw-data store, and analysis surface
Template: Sample
- Study plan
Recruit: Piloted template
- Sample
Diary: Diary entries
- Piloted template
Analyse: Longitudinal patterns
- Diary entries
Diary Study · working structure
| Entry | Time | Trigger | Action | Experience | Evidence |
|---|---|---|---|---|---|
| Monday | |||||
| Thursday | |||||
| Tuesday |
- Monday: Record a timely diary entry with trigger, action, experience, and evidence.
- Thursday: Record a timely diary entry with trigger, action, experience, and evidence.
- Tuesday: Record a timely diary entry with trigger, action, experience, and evidence.
The blank worksheet contains prompts only.
Reference source · original teaching example
Design: Study plan
Expected artifact: Study plan
Define research focus, duration, event- or interval-based logging, and privacy
Entry:
...
- Are question, duration, event logic, and privacy explicit?
Template: Sample
Expected artifact: Piloted template
Pilot a diary format with short prompts, timestamps, and optional media evidence
Entry:
...
- Is the template short, understandable in daily use, and piloted with real entries?
Recruit: Piloted template
Expected artifact: Onboarded sample
Onboard participants, practise one entry, and explain the support path
Entry:
...
- Can participants create a complete entry and reach support?
Diary: Diary entries
Expected artifact: Diary entries
Collect entries over time, monitor completion, and send neutral reminders
Entry:
...
- Do reminders remain neutral, with missing entries visible rather than filled in?
Analyse: Longitudinal patterns
Expected artifact: Longitudinal patterns
Analyse entries across time, triggers, and cases, then deepen findings in exit interviews
Entry:
...
- Are longitudinal patterns supported by entries and checked in exit interviews?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/diary-study/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
diary-study-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: Diary Study · working structure
| Entry | Time | Trigger | Action | Experience | Evidence |
|---|---|---|---|---|---|
| Monday | 08:42 | Part unavailable in the job | Searched chat, then called warehouse | Frustrated; customer waiting | Screenshot of empty inventory |
| Thursday | 15:10 | Alternative suggested | Checked compatibility through a photo | Uncertain but faster than Monday | Label photo and six-minute timer |
| Tuesday | 11:25 | Same part recurs | Reused own photo | Confident; no call needed | Photo ID and completion time |
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Study planWhen duration and event logic stay unclear, participants later do not know when an entry is due.View in phase
- SampleWhen the template uses long prompts or jargon, participants abandon entries in daily life.View in phase
- Piloted templateWhen participants start without practice, it stays unclear whether they can create a complete entry or reach support when needed.View in phase
- Diary entriesWhen reminders suggest the expected answer or missing entries get filled in afterward, the longitudinal data is distorted.View in phase
- Longitudinal patternsWhen time patterns are asserted only from a gut feeling, they cannot be defended in the exit interview.View in phase
Trap
Study plan
Symptom
When duration and event logic stay unclear, participants later do not know when an entry is due.
What to do
Fix the research focus, duration, entry triggers, and privacy rules clearly before the study starts.
Trap
Sample
Symptom
When the template uses long prompts or jargon, participants abandon entries in daily life.
What to do
Pilot the format with short prompts and timestamps against real test entries and simplify it afterward.
Trap
Piloted template
Symptom
When participants start without practice, it stays unclear whether they can create a complete entry or reach support when needed.
What to do
Select participants deliberately by experience, practice one example entry together, and show the support channel.
Trap
Diary entries
Symptom
When reminders suggest the expected answer or missing entries get filled in afterward, the longitudinal data is distorted.
What to do
Keep reminders neutral and leave missing entries visible as gaps instead of filling them in.
Trap
Longitudinal patterns
Symptom
When time patterns are asserted only from a gut feeling, they cannot be defended in the exit interview.
What to do
Ground every pattern in concrete entries and verify it with participants during the exit interview.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Do not close “Study plan” while this check remains open: Are question, duration, event logic, and privacy explicit?
Do not close “Sample” while this check remains open: Is the template short, understandable in daily use, and piloted with real entries?
Do not close “Piloted template” while this check remains open: Can participants create a complete entry and reach support?
Do not close “Diary entries” while this check remains open: Do reminders remain neutral, with missing entries visible rather than filled in?
Do not close “Longitudinal patterns” while this check remains open: Are longitudinal patterns supported by entries and checked in exit interviews?
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.