Design a diary study
Designs a diary study with research questions, daily and event prompts, recruitment, incentives, tactics to keep people logging, and an analysis plan. Use to study behaviour over weeks.
Diary studies capture behaviour in context and over time, which interviews and usability tests cannot. They fail when the prompts are long and identical every day, so entries shrink to "same as yesterday" by day four; when the study logs on a schedule but the behaviour happens on events (or the reverse); when a third of participants drop out because nobody checked in; and when the team collects hundreds of entries with no plan for analysing them.
Design a -day diary study.
If the research questions or the participants are too vague to write prompts (no behaviour, no participant group), ask up to three questions and stop.
- Fit check. Confirm a diary study suits the questions: behaviour that unfolds over time, happens in context, or is rare or hard to recall. If a question is better answered by another method (a survey for prevalence, analytics for frequency, a usability test for task performance), say so and route it. If days cannot capture the behaviour (a monthly bill, a weekly shop observed only once), recommend a better length.
- Research questions. Rewrite them into 3 to 6 answerable questions about behaviour, context, triggers, workarounds and feelings over time.
- Logging approach. Choose event-contingent (log when the behaviour happens), interval-contingent (log at fixed times) or a mix, and say why. Define what counts as an event in plain words participants will understand.
- Prompts schedule. A day-by-day plan: an onboarding entry on day 1 (context, current setup, a photo of where the activity happens if relevant), the core entry prompt, rotating deeper prompts on some days so entries do not become repetitive, and a reflection entry on the last day. Each entry must take under 5 minutes; mix short closed questions (rating, multiple choice) with one or two open prompts and optional photo, screenshot or voice notes. Write every prompt in full, in neutral, past-tense, behaviour-focused language ("What happened just before you...").
- Participants and recruitment. Behaviour-based criteria, segments, a short screener, the target number (usually 10 to 20 completers per segment) and over-recruitment of 20 to 30 per cent for drop-outs. Include the device and tool requirements.
- Incentives and compliance. Incentive structure staged across the study (part paid for onboarding, the rest on completion, with a bonus for full compliance) at a level fair for the total time asked; a kickoff call or video; reminder timing matched to the logging approach; a researcher check-in on days 2 and halfway with follow-up questions on entries; a rule for when a participant is replaced; and what counts as a complete entry.
- Ethics and data. Consent covering photos and what may appear in them (other people, screens with personal data), how to avoid capturing third parties, storage and deletion, and when participants may skip a prompt.
- Analysis plan. Read entries daily during the study for follow-ups, then code entries against the research questions, build a per-participant timeline, compare across segments, and look for triggers, patterns over time and breakdowns. Add optional exit interviews with 4 to 6 participants to explore the richest diaries.
- Do not invent findings, benchmarks or compliance rates. Recommendations about sample size and drop-out are typical ranges; say so.
- Keep the total participant effort realistic and state it in minutes per day and in total.
- Never ask participants to capture other people, sensitive documents or anything illegal; design prompts so they do not need to.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Study overview
Goal, method, length, logging approach and total effort per participant in under 8 lines, then any questions from the fit check that should go to another method, and why.
Research questions
Prompts schedule
| Day | Trigger or time | Prompt (as participants will read it) | Response type | Research question |
Participants and recruitment
Incentives and compliance
Ethics and data
Analysis plan
Pilot and risks
A 2- to 3-day pilot with 2 to 3 people, and the main risks with mitigations.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Design
- category
- UX research
- level
- Intermediate
- made for
- UX researcher, Product / UX / UI designer, Product manager, Researcher / scientist
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install design-diary-study --target claude-codenpx skills add hermes-hq/hodios-dist --skill design-diary-study -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-design@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of UX researchBuild evidence-based user personas
Builds UX personas from research notes, grouping participants by behaviour, with goals, pain points and scenarios traced to evidence and assumptions marked. Use after interviews or field research.
build-user-personasBuild a user journey map from research
Builds an evidence-based journey map with stages, actions, thoughts, emotions, pain points and opportunities, marking every assumption. Use after interviews or studies about one segment.
build-user-journey-mapSynthesize usability test findings
Turns raw usability session notes into evidence-backed issues rated by severity and frequency, with task results and recommendations. Use after a round of usability sessions.
synthesize-usability-findingsUX researcher
UX researcher who matches the method to the question, separates what people did from what it means, and protects participants. Use as a partner for planning, running and synthesising research.
ux-researcherAnalyse session recordings and heatmaps
Synthesises notes from session recordings and heatmaps into usability issues with frequency, severity and evidence, keeping observation apart from interpretation, and plans follow-ups.
analyze-session-recordingsMeasure UX with SUS and task metrics
Plans a UX benchmark with SUS and task metrics, or scores supplied responses, compares them with norms and reports confidence intervals. Use to track UX across releases.
measure-ux-with-sus