Validation SOPs › Problem Validation
SOP 18 of 100 · Problem Validation
Pain Point Diary SOP
- Difficulty
- Intermediate
- Time
- 2-3 days of setup, 7-14 days of logging, 2 days of analysis
- Cost
- $50-500 (mostly participant thank-yous)
- Best for
- Problems that happen in small doses across the week, B2C and frontline B2B work
- Tools
- dscout, Indeemo, WhatsApp, Google Forms, Airtable, Notion
- Measure
- Participant completion rate, Entries per person per day, Theme frequency, Average frustration score, Time lost per entry
A pain point diary SOP captures problems at the moment they happen, so you see what people live through instead of what they remember a week later. Ten to fifteen people from your target group spend 7 to 14 days logging every frustrating moment in a two-minute form on their phone. Interviews give you the story people tell. A diary gives you the count. You finish with a list of real problem moments, how frequently each one hits and how many minutes or euros it costs.
What is the pain point diary SOP and when should you use it?
A pain point diary is a short diary study focused on problems. Psychologists Ladd Wheeler and Harry Reis described three ways to trigger diary entries: event-contingent (log when the event happens), interval-contingent (log at fixed times) and signal-contingent (log when pinged). This SOP uses event-contingent entries plus one daily evening prompt as a safety net.
The reason to bother: Daniel Kahneman's research on the peak-end rule showed that people judge past experiences mostly by the worst moment and the last moment. Ask someone in an interview about last week and you hear the peak. Small repeating annoyances, the ones people pay to remove, vanish from memory.
Use this SOP:
- When the problem is frequent and small, such as lost minutes, repeated messages or tiny admin tasks spread across a week.
- When interview answers feel vague ("it's annoying sometimes") and you need frequency and cost.
- When the problem happens in places you can't observe: at home, on the road, at night, inside private apps.
- Before you quantify impact, because diary entries give you real minutes and money per occurrence.
If you can watch the work in person, ethnographic research gives richer context in less time.
What do you need before you start?
- A problem area, defined broadly enough to catch surprises ("school logistics as a working parent"), and narrow enough to keep entries on topic.
- 10 to 15 participants from one customer group, plus 3 spares. Communities are the fastest source; the F/MS audience and community module covers how to find and approach them.
- An entry form that takes under two minutes on a phone (template below).
- A thank-you budget: a gift card or a small payment per completed diary, paid at the end.
- A tracking sheet to see who logged what each day.
How do you run it, step by step?
1. Define the problem area and the entry trigger
Write one sentence that tells participants when to log: "Every time something about [area] wastes your time, annoys you or costs you money, add an entry." Give two concrete examples so people know the size of moment you mean. Avoid naming the problem you suspect, or that is all you will get back.
2. Build a two-minute entry form
Use Google Forms, a WhatsApp chat, or a diary platform such as dscout or Indeemo if you have budget. Ask what happened, what they were trying to do, what they did next, how frustrating it was (1 to 5) and how many minutes or how much money it cost. Allow a photo or screenshot, since pictures show workarounds people forget to describe.
3. Recruit and brief participants
Recruit 10 to 15 people plus spares and run a 15-minute kickoff call with each one. Walk through one practice entry together. Explain the thank-you and that it is paid on completion, which keeps people logging through day 10.
4. Run the diary for 7 to 14 days
Seven days covers one work week and weekend; 14 days catches problems that hit every other week, such as payroll or school events. Send one short evening reminder each day: "Anything from today you didn't log yet?" Check the tracking sheet daily and message anyone who has gone quiet for two days.
5. Hold a short follow-up call
At the end, spend 20 minutes with each participant on their three most frustrating entries. Ask what happened next and what they have tried before. These calls turn short entries into stories with causes.
6. Code entries into themes
Read every entry and tag it with one problem theme. Count entries per theme, people per theme, average frustration score and total minutes or money lost. Keep exact phrases in a quotes column.
7. Rank the themes and write the memo
Rank themes by people affected first, then by frequency per person, then by average frustration. Write a one-page memo with the top three themes, their numbers and the best quotes.
Template you can copy
DIARY ENTRY FORM (under 2 minutes)
1. When did this happen? [date + time]
2. What were you trying to do? [short text]
3. What got in the way? [short text]
4. What did you do next? [short text]
5. How frustrating was it? 1 2 3 4 5
6. What did it cost you? [minutes] [money, if any]
7. Photo or screenshot (optional)
DAILY EVENING REMINDER
"Quick check: anything from today about [area] that annoyed you,
cost you time or money, and isn't in your diary yet?"
ANALYSIS SHEET COLUMNS
Entry ID | Participant | Date | Theme | Frustration 1–5 |
Minutes lost | Money lost | Workaround used | Quote
Worked example: working parents and school logistics
This is an illustrative case. A founder suspects working parents struggle with school paperwork. She recruits 12 parents with children aged 5 to 10, runs a 10-day diary through Google Forms and pays a $30 gift card per completed diary. Ten of 12 finish, a completion rate of 83%, with 214 entries in total.
Paperwork turns out small: 19 entries, average frustration 2.6. The big theme is last-minute requests (costume days, cash for trips, forms due tomorrow) with 81 entries from 9 of 10 parents, average frustration 4.1 and 23 minutes lost per entry. Six parents attach screenshots of the same pattern: a message sent at 9 p.m. for the next morning, inside one of three different school apps.
The follow-up calls show the root cause: parents read school messages only in the evening, and nothing collects the three apps in one place. The founder rewrites her problem statement around late notice across many channels and moves to problem impact quantification with real minutes in hand.
What should you measure, and when do you stop?
| Metric | Pass signal | Warning signal |
|---|---|---|
| Participant completion rate | 70%+ finish the full period | Under 50% finish |
| Entries per person per day | 1 or more on average | Most days blank, entries only after reminders |
| Theme frequency | Top theme appears in 50%+ of diaries, 2+ times a week each | Top theme comes from 1 or 2 people |
| Average frustration score | 3.5 or higher for the top theme | Under 3 for every theme |
| Time lost per entry | 10+ minutes or a named money cost | "A few seconds" across the board |
Stop at the planned end date; extending a diary past 14 days drains participants. If no theme passes, the problem area is wrong or too narrow: widen it and run a fresh seven-day round with new people.
Which mistakes should you avoid?
- Naming your hypothesis in the briefing. People log what you asked for and nothing else.
- Long entry forms. Anything over two minutes gets skipped on busy days, which are the days you need.
- Paying per entry. It rewards quantity and invents problems. Pay per completed diary.
- Skipping the follow-up calls. Entries tell you what and when. Calls tell you why and what people already tried.
- Counting entries instead of people. One person logging 40 times about one issue is a single data point.
How can AI speed this up?
Export entries to a spreadsheet and ask an AI assistant to propose 6 to 10 themes, tag each entry, and total frustration and minutes per theme. Then read 20 random entries yourself and check the tags; AI tagging lumps similar-sounding problems together. AI also writes good reminder messages in the participant's language and tone. The F/MS AI co-founder can walk through the coding and memo step with you.
Where does this SOP fit in your validation plan?
Run it after a first round of customer interviews, when you know the area but not the frequency. Take the top themes into a problem ranking survey to check them at scale, and use the minutes and money from the entries in problem impact quantification. For problems that happen inside software, digital behavior tracking captures the same moments from usage data. All ten SOPs in this stage are on the Problem Validation page.
FAQ
How long should a diary study last?
Seven days for problems that happen daily, 14 days for ones tied to weekly or biweekly cycles. Longer than two weeks, completion drops and entries get thinner.
How many participants do I need for a diary study?
10 to 15 people from one customer group, plus 2 or 3 spares. That gives you 150 to 300 entries, enough to see clear themes.
Should I pay diary study participants?
Yes, and pay per completed diary. For consumers, budget $25 to $50 in gift cards for a 10-day diary; for professionals, offer a summary of the findings as well.
Can I run a diary study on WhatsApp?
Yes. A private chat per participant works well: people send voice notes, photos and short texts as things happen. Copy entries into a spreadsheet every evening so analysis does not pile up.
Go further on our sister sites
- Method: Problem Journal (100 startup methods)