Ask target users to keep a one-week pain journal
A pain journal asks a few target users to log each time the problem hits them, for about a week, so you see real frequency and context instead of recalled stories. Across 496 samples, experience-sampling studies lasted 7 days and reached 79% compliance on average, mostly with paid participants. Nielsen Norman Group sizes a small discovery diary study at about 5 to 12 people, plus extras for dropouts.
- Stage
- Stage 1. No proven demandIs the problem real, and does anyone want this solved?
- Category
- Customer research
- Time
- 1 to 2 weeksAwiser's estimate of the active work
- Cash
- No cash
- Live calls
- Live calls optional
- First result
- Within weeks
- Risk
- LowA week of light effort for a few people. The risk is reading a sparse journal as proof that the problem is rare.
- Needs
- Five or more target users who hit the problem several times a week, plus a couple of backupsA simple place to log: a short form or one message thread per personA daily reminder
When does it fit?
- The problem happens several times a week: in a meta-analysis published in Assessment, experience-sampling studies lasted 7 days on average, and rare events call for longer periods.[3]
- You want behavior in context rather than recalled stories: Nielsen Norman Group says contextual and longitudinal insights cannot come from single-session methods such as interviews.[1]
When should you skip it?
- The problem is rare: a one-week journal of a monthly problem records little, and sampling theory suggests longer periods for rare events.[3]
- You can only recruit two or three people: Nielsen Norman Group sizes a small discovery diary study at about 5 to 12 participants and advises over-recruiting for dropouts.[1]
How do you run it?
Recruit five or more, plus backups
People in your target group who hit the problem several times a week. Add a couple of extras: some will drop out.
Make logging take a minute
One short form or message thread per person: what happened, when, what they did, and what it cost.
Log at the moment, not at night
Ask for an entry right when the problem hits, not a recap written from memory at the end of the day.
Remind once a day
A short daily reminder keeps entries coming without nagging.
Set no entry quota
A target number invites padded entries. Ask for every real occurrence, however few.
Walk through the entries
Go through each journal with its author at the end, in a short call or in writing, to fill the gaps.
Thank them
Offer a thank-you if you can: completion is higher when participants are paid.
What usually happens?
- Most entries arrive when people are paid: across 496 samples, experience-sampling studies got 79% compliance on average, and the meta-analysis in Assessment found compliance significantly higher with financial incentives.[3]
- Running it takes attention: a Somia CX team that managed 30 respondents for 5 days says all three researchers were glued to their WhatsApp apps.[4]
- Dropouts are normal: Somia CX plans 10 backup participants for every 20 data points it needs.[4]
What does the evidence say against it?
- Logging changes behavior: Nielsen Norman Group warns that it interrupts people and may prompt them to act as they think the study expects.[2]
- No published data or documented founder case shows a one-week pain journal leading to better product decisions.
How do you read the result?
- What to count
- Participants who logged through the week, and the problem events recorded with time and context
- When to read it
- At the end of the week
- How to decide
- Build for the problem if it shows up often and costs people real time or money. If entries are sparse, the problem may be rarer than interviews suggested, or entries were missed: with event-based logging, compliance can only be measured indirectly, so ask.[3]
What goes wrong?
- Daily recaps from memory: Nielsen Norman Group says people who log later may forget details and make up information.[2]
- Entry quotas: Nielsen Norman Group warns against a response factory where people chase a number of entries.[2]
- No reminders: Nielsen Norman Group recommends them each day or every few days.[1]
- No thank-you at all: Nielsen Norman Group says diary incentives should be higher than for a typical test session.[1]
How was it graded?
- Evidence
- C. Limited evidenceDiary studies are a recognised research method and a large meta-analysis gives completion base rates, but no published data or documented case shows founders learning more from a one-week pain journal.
- Verdict
- SituationalUseful when the problem happens several times a week and you want behavior in context. For rare problems, interviews about the last occurrence teach more.
Sources
- 1Diary Studies: Understanding Long-Term User Behavior and Experiences (opens in a new tab)Nielsen Norman Group, Kim Flaherty. March 29, 2024. Method, from a seller of what it measures.
Contextual and longitudinal insights cannot be collected through single-session moderated user-research methods, like usability testing or user interviews.
Small discovery projects Fairly homogenous user group Problem space is relatively small ~ 5-12
Because a diary study takes place over a longer time than a regular usability-testing study, there is a higher chance that participants will drop out of the study due to unexpected circumstances in their lives. Consider overrecruiting in preparation for potential dropouts so that you have enough data points in the end.
Give periodic reminders each day or every few days.
Diary-study incentives should be higher than those for a typical user-testing session due to the long-term engagement required.
Read on October 20, 2026. - 2Balancing Natural Behavior with Incentives and Accuracy in Diary Studies (opens in a new tab)Nielsen Norman Group, Mayya Azarova. August 20, 2023. Method, from a seller of what it measures.
But the act of logging one's activities as they're doing them is not natural: first, it interrupts the user from whatever they were trying to achieve, and second, it may prompt people to modify their behaviors to match the expectations that they may have about the study goals.
If you allow people to log the activities when it is convenient for them rather than during the activity or immediately after they complete it, they may forget details and may feel forced to make up information to fill out the diary entry fields.
However, you do not want to undermine the study by creating a diary-study response factory where people want to hit that magic number of entries to get paid.
Read on October 20, 2026. - 3Ecological Momentary Assessment: A Meta-Analysis on Designs, Samples, and Compliance Across Research Fields (opens in a new tab)Assessment, Cornelia Wrzus, Andreas B. Neubauer. January 11, 2022. Study.
The results showed that on average EMA studies scheduled six assessments per day, lasted for 7 days, and obtained a compliance of 79%.
Previous theoretical work has suggested sampling less frequent events more often and for longer periods so as not to miss the event
The current meta-analysis included k = 477 articles (496 samples, total N = 677,536).
Compliance was significantly higher in studies providing financial incentives.
Relatedly, in event-contingent EMA studies, which represented about 20% of the reviewed EMA studies, the total number of events and thus of event-based assessments is unknown beforehand, and thus compliance with the study protocol is only indirectly measurable
Read on October 20, 2026. - 4Lessons from Running A Diary Study (opens in a new tab)Somia CX, Chelsea Effendi. March 19, 2025. Method, from a seller of what it measures.
In this study, our team had to manage 30 respondents for a 5-day diary study.
For 5 days, all three of us were glued to our WhatsApp apps to run and monitor the study.
A longer study equals extra backup participants as the dropout rate might be high. That's why, if you need to collect 20 data, you might need to recruit 10 more participants as backups.
Read on October 20, 2026.
Sources last checked on October 20, 2026. First published on October 20, 2026.
Awiser is the builder network where founders show their skills, find collaborators, and grow their projects with an AI copilot.