UX and research · Beginner · 11 min
Write a problem statement before you design
By Padding · Updated 18 Nov 2026
Any notes app or shared document · November 2026
You will have one problem statement your team agrees on, naming a person, a situation and a consequence, plus a log of rejected drafts with the reason each one failed.
On this page
A problem statement is one sentence that says who is struggling, when it happens and what it costs them. It comes before sketches, wireframes or tickets, because whatever it says decides what the team will treat as a good answer. If the sentence already contains an answer, every design that follows is that answer with different colours.
Most first drafts already contain an answer. "Patients need text reminders" sounds like a problem, but it is a feature request. Once a team agrees on it, nobody asks whether reminders were ever the issue.
This tutorial follows Larkfield Clinic, a fictional community clinic, where too many patients miss their appointments. You will collect what is known, write a rough draft, then rebuild it around three parts: a person, a situation and a consequence. Then you will run a set of checks that catch solutions hidden inside the problem, test the sentence on your team, and keep a log of the drafts you threw away. The figures in the example are made up. Use your own.
Step 1 · Put the evidence in one place
Open a new document and call it something like "Missed appointments: problem statement". Make two headings: What we know and Drafts.
Under What we know, list every fact you have about the problem, one per line, each with its source in brackets. Facts are things someone saw, counted or was told. Leave out guesses about causes for now, or put them under a third heading, Hunches, so they do not mix with the evidence.
For the clinic, the list might start like this:
- About 1 in 7 booked appointments last quarter were missed without notice (booking system export)
- Most missed slots are weekday mornings between 8:00 and 11:00 (same export)
- Three patients in interviews said they knew they could not come but could not get through on the phone to cancel (interview notes, October)
- All four interviewees who had missed an appointment had a weekday morning slot and said work or the school run made their mornings hard to predict (interview notes, October)
- Reception staff say the phone line is busiest from 8:00 to 9:30 (conversation with the reception lead)
- The next free routine slot is often two to three weeks away (booking system)
If a fact has no source, find one or move it to Hunches. A statement built on guesses will pass every check in this tutorial and still be wrong.
Check it worked
Your document has at least five facts under What we know, each with a source in brackets, and nothing under that heading is a guess about why the problem happens.
Step 2 · Write a rough first draft without stopping
Under Drafts, write the problem in one sentence, the way you would say it to a colleague in a corridor. Do not polish it. The aim is to get your assumptions onto the page where you can see them.
Number each draft. For the clinic:
Draft 1: Patients keep missing appointments, so we need SMS reminders.
Now write two more quickly, each from a different angle: one from the clinic's point of view and one from the patient's.
Draft 2: Our no-show rate is too high and it is costing us clinician time. >Draft 3: Patients do not have a way to reschedule online.
These drafts are useful because they are wrong in different ways. You will come back to them in the last step.
Check it worked
Your Drafts section has at least three numbered sentences, and at least one is written from the point of view of the people affected rather than the organisation.
Step 3 · Name a specific person
"Patients" or "users" is everyone, which means the statement describes no one. Go back to What we know and ask which people the evidence is about. Look for a group that shares a circumstance, not a demographic label.
In the Larkfield notes, the interview fact says that everyone who had missed an appointment had a weekday morning slot and had work or the school run to fit around it. That points to a group such as "patients who book weekday morning appointments around work or childcare". It is narrow enough to picture and wide enough to matter.
Write the person on its own line under a new heading, Parts:
- Person: patients who book weekday morning appointments around work or childcare
If the evidence points to two different groups with different reasons, pick the one with more evidence behind it and note the other under Hunches. You can write a second statement later. One sentence that tries to cover both will blur them.
Check it worked
Under Parts, the person line names a group you could recruit five people from for an interview tomorrow. If you could not say who to invite, the group is still too broad.
Step 4 · Describe the situation it happens in
The situation is the moment the problem shows up: when, where and what the person is trying to do. It is the part most drafts leave out, and it is the part designers need most, because it tells them where the design has to work.
Read your facts again and finish this line: "It happens when ..." For the clinic:
- Situation: when they realise on the morning itself that they cannot attend, and the phone line is too busy to cancel before the appointment starts
Notice what the situation does not say. It does not say "because there is no app" or "because they forgot". It describes what happens, in the order it happens, using only things in What we know.
Check it worked
Your situation line contains a time or trigger (a "when") and an action the person is trying to take, and every part of it can be traced to a fact under What we know.
Step 5 · State the consequence for the person and for the organisation
The consequence is why anyone should care. Write it for the person first, then for the organisation. A statement that only gives the organisation's cost (Draft 2) invites solutions that shift the cost onto patients, such as fines for missed appointments.
- Consequence for the person: they are recorded as a no-show and wait two to three weeks for the next routine slot
- Consequence for the clinic: about 1 in 7 booked appointments are missed without notice, so those slots go unused while other patients wait
Use a figure where you have one, with its source. "Wait two to three weeks" is easier to act on than "experience delays".
Now join the three parts into one sentence under Drafts:
Draft 4: Patients who book weekday morning appointments around work or childcare often realise on the day that they cannot attend, but cannot get through on the phone to cancel in time, so they are marked as a no-show and wait two to three weeks for another slot, while the clinic loses about 1 in 7 booked appointments.
It is long. That is fine for now. You will tighten it after the checks.
Check it worked
Draft 4 contains all three parts from your Parts list, and you can underline the person, the situation and the consequence as three separate phrases.
Step 6 · Hunt for the solution hiding in the problem
This is where most problem statements go wrong, often without anyone noticing. Run each of the checks below on your latest draft, and write the result next to it. A draft fails if any check finds something.
1. The feature-noun check. Circle every noun that names a thing you could build or buy: app, portal, reminder, text, chatbot, dashboard, button, form, notification. Each one is a solution. Draft 1 fails on "SMS reminders". Draft 3 fails on "reschedule online".
2. The "lack of" check. Search for "lack", "no way to", "does not have", "need", "needs a" and "unable to use". These phrases turn a missing solution into a problem: "patients lack a way to reschedule online" really means "we want to build online rescheduling". Rewrite the sentence to describe what happens to the person instead.
3. The three-answers check. Write down three different ways a team could answer the statement, using different kinds of solution (a change to the service, a change to staffing or policy, a digital product). If you can only think of one kind, the statement is pointing at it. Draft 4 passes: the clinic could take cancellations by text reply, open a separate cancellation line before 8:00, or hold back a few same-day slots for rebooking.
4. The cause check. Look for "because". A cause in the statement is a hypothesis presented as a fact. Draft 1 assumes patients forget; the interview notes say they remember but cannot get through. If the cause is not in What we know, remove it.
5. The vendor check. Read the statement as if a salesperson were about to quote it back to you. If it would sell their product without a change of wording, it is too close to that product.
Check it worked
Each draft in your document has a note beside it listing which checks it failed, and your latest draft has no circled feature nouns, no "lack of" phrasing, no unsupported "because", and three different kinds of answer written beneath it.
Step 7 · Tighten it to one readable sentence
A statement the team cannot repeat from memory will not be used. Cut Draft 4 down without losing any of the three parts.
Work through it in this order:
- Remove words that repeat what another word already says ("often realise on the day" and "in time" overlap)
- Replace general verbs with the specific one ("cannot get through" rather than "experience difficulty contacting")
- Keep one figure for the person and one for the organisation, and drop the rest
- Read it aloud. If you need a breath in the middle, split the clause or cut it
Draft 5: Patients who book weekday morning appointments around work or childcare find out on the day they cannot attend, but the phone line is too busy to cancel, so they are marked as no-shows and wait two to three weeks to rebook, while 1 in 7 booked appointments go to waste.
Run the checks from the previous step again on the shorter version. Cutting words sometimes brings a solution back in, for example by shortening "the phone line is too busy to cancel" to "they cannot cancel online".
Check it worked
Your latest draft is one sentence of about 50 words or fewer, you can say it aloud without reading it, and it still passes every check from the previous step.
Step 8 · Test it with the team and agree on one version
Share the document with the people who will design, build and run whatever comes next. For the clinic that might be a designer, a developer, the reception lead and a clinician.
Ask each person to do three things, separately and before any discussion:
- Rewrite the statement in their own words in a comment
- Name the one fact under What we know they think is weakest
- Write the first solution that comes to mind
Then compare. If the paraphrases describe different people or different moments, the statement is still ambiguous: fix the part they disagree on. If everyone writes the same first solution, run the three-answers check again, because the wording may be steering them. If someone challenges a fact, check its source before you continue.
When the paraphrases match, move the agreed sentence to the top of the document under a heading Agreed problem statement, with the date and the names of the people who agreed it.
Check it worked
The top of your document shows one sentence under Agreed problem statement, with a date and names, and every reviewer's paraphrase in the comments describes the same person, situation and consequence.
Step 9 · Keep the rejected drafts and why they failed
Under the agreed statement, add a heading Rejected drafts. Copy each earlier draft there with one line saying why it was rejected. Keep it short and specific.
- Draft 1 (Patients keep missing appointments, so we need SMS reminders): contains a solution (SMS reminders) and an unsupported cause (forgetting); "patients" is too broad
- Draft 2 (Our no-show rate is too high and it is costing us clinician time): no person or situation; gives the consequence for the clinic only
- Draft 3 (Patients do not have a way to reschedule online): "do not have a way to" hides online rescheduling as the answer
- Draft 4 (the long version): has all three parts but is too long to repeat, with overlapping clauses
This log does two jobs. When a stakeholder suggests "why don't we just add reminders?" in three weeks, you can show that the idea was considered and why the problem was framed differently. It also shows new team members how the statement was built, so they can change it properly if new evidence arrives.
Check it worked
Every numbered draft except the agreed one appears under Rejected drafts with a reason, and each reason names a specific check or missing part rather than "not good enough".
Next steps
You now have a problem statement that names who is affected, when it happens and what it costs, with no answer built in. The next job is to open it up into questions a team can generate ideas against.
- Turn the statement into prompts for ideas in Turn a problem statement into how-might-we questions
- If the work started as a request for a specific feature, reframe it first with Turn a feature request into a user-centred brief
Revisit the statement whenever new research comes in. If a fact under What we know changes, run the checks again before you keep designing.
Part of these paths
Related tutorials
- Turn a problem statement into how-might-we questionsYou will have a sorted set of how-might-we questions drawn from one problem statement, with three workable questions chosen to explore and a note on why the rest were set aside.
- Turn a feature request into a user-centred design briefYou will turn a one-line request into a one-page brief that names the people affected, what they are trying to get done, what is known and what is guessed, ready to hand to a team.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials