The person
Anxious, informed, out of patience
Adults who suspect ADHD or autism, and parents seeking an answer for a child. Often years into a wait, often after a difficult GP conversation. High motivation, low tolerance for another dead end.
Case study ProblemShared · Direct-to-consumer
A self-pay route into ADHD and autism assessment. People were asked for sensitive details and payment before anyone had told them we could help. I reordered the journey around that one problem.
How the journey was ordered
Before
01 Context
ProblemShared is an NHS-partnered, CQC-registered provider of neurodevelopmental assessment. Most people reaching the self-pay route had already waited a long time for an NHS answer. They weren't browsing — they were trying to stop waiting.
The person
Adults who suspect ADHD or autism, and parents seeking an answer for a child. Often years into a wait, often after a difficult GP conversation. High motivation, low tolerance for another dead end.
The purchase
A clinical assessment is a significant, non-refundable-feeling commitment. Anything ambiguous about price, eligibility or what happens next reads as risk.
The constraint
Not everyone is suitable for a remote assessment. Clinicians need specific information; regulation dictates what must be captured and recorded. The flow could be reordered, not shortened.
02 Research
Four sources, chosen because they were fast and already in the building. The most useful evidence wasn't in a research repository — it was in refund requests.
Every refund reason and support conversation from the self-pay route, coded by cause. The single richest source: people telling us, in their own words, what they had misunderstood and when.
Step-by-step drop-off across sign-up, service selection, intake forms and checkout — then watching sessions at the steps that leaked hardest.
Adults and parents who had started and stalled, plus people who had completed. What they were afraid of, and what they were checking for before they trusted us with money.
With assessors and operations: which data is genuinely needed to run a safe assessment, which is needed for compliance, and — critically — when each is actually needed.
Suitability was checked late, and in some paths after payment. Refunds clustered around one sentence: I didn't know you might not be able to see me.
Every pound taken before a yes was a refund waiting to happen — and a trust cost we couldn't buy back.
Sex at birth, GP contact details and an emergency contact were requested early, with no explanation of why or who would see them. Several people stopped at exactly that field.
The questions weren't the problem. Asking them before we'd earned them was.
Completed steps jumped position, so the list read 1, 3, 2, 4. Returning users lost their place and re-read the whole thing to work out what was left.
A progress indicator that moves isn't progress. Order had to be fixed; only state could change.
03 The change
Nothing was removed — regulation and clinical safety wouldn't allow it. What changed was the sequence, and what we explained at each point.
Move 01
A two-minute check moved to the front of the journey, before any payment or clinical intake. A clear yes, a clear not-for-us with an onward route, or a "let's talk first".
Nobody pays for an assessment we can't deliver
Move 02
GP details, emergency contact and background moved behind eligibility and payment — where they're framed as preparing your clinician, not as a barrier to entry.
Sensitive data asked once, in context, with a reason
Move 03
Steps keep a fixed order and only change state: done, in progress, or locked with the reason it's locked. Progress became readable at a glance from any device.
Returning users resume instead of re-reading
Product Getting started
The first screen after sign-up answers three questions immediately: how far along am I, what's next, and what happens after I pay.
Hi Naomi — here's where you are
Four steps. You'll know if we can help before you pay anything.
So you know what you're buying.
Hi Naomi
Steps never move. Only their state changes, so the list is the same shape every time you come back.
A locked step says what unlocks it. A greyed button with no reason reads as a bug, not a rule.
Assessment, report and timings are shown before payment, because that's what people were asking support about.
Product Choosing & disclosing
Two patterns did most of the work: making the commercial offer legible, and explaining every sensitive question at the point it's asked.
Choose your assessment
You've been assessed as suitable. Prices include your report.
Not sure yet
£95 30 min
Most chosen
£1,195 total
Waitlist
£1,795 total
Not what you expected?
Your suitability check is still valid for 30 days — you can come back to this.Your assessor sees this before your appointment. It won't change your price or your booking.
The total, what's in it, and a lower-commitment route for people who aren't ready. Placeholder pricing was the biggest source of support contact.
Sensitive fields carry a one-tap explanation of the clinical reason and who sees the answer. Written by me with the clinical team.
Not suitable, not sure, not now — each has a route onward rather than a stop. The suitability result stays valid for 30 days.
Process AI in the loop
Reordering a regulated clinical journey isn't a Figma decision — it only counts if clinical and engineering agree it's compliant and buildable. I used Claude to prototype the new sequence fast, then spent my time on the conversations that actually de-risked it.
01 · Prototype
I rebuilt the four-step journey as a working prototype with Claude — suitability first, payment, then intake — so the team could click through the new order instead of imagining it. The locked-step pattern and "why we ask" disclosure were far easier to argue for once people could feel them.
My judgementAI built the flow. Deciding what came first, and why, was the design.
02 · Pressure-test
I had Claude walk the journey as an anxious first-time user and as someone found not suitable — the path we understood least. That's where the "nothing is a dead end" rule came from: every negative outcome needed somewhere to go, and the prototype made those gaps obvious.
My judgementI decided which edge cases mattered clinically. AI made them cheap to explore.
03 · Validate
The prototype went into working sessions with clinicians and engineers. Because it was runnable, we could check specifics: is it compliant to take payment before full intake? Can suitability write to the record this way? Answers came in one session, not a fortnight of tickets.
My judgementThe prototype turned "what if" into "here it is — does this hold up?"
Prototype the journey with a free suitability check first, before payment or any clinical intake. If someone's found not suitable, they must land somewhere useful, never a dead end.
Built. Suitable → assessment selection. Not suitable → a page explaining why, with NHS and alternative routes. "Not sure" → a paid consultation, fee credited if they continue. I kept later steps locked until suitability passes. Should the result expire?
Yes — valid 30 days so no one has to redo it. Now show the intake form with a "why we ask" on sex at birth and GP details.
The wording on sex at birth needs to be ours, not generic — it's clinically load-bearing. Send me the copy and I'll adjust it.
Taking payment pre-intake is fine; suitability just needs to write a flag to the record before checkout. Small change. Buildable this sprint.
Reconstructed from the working sessions. Prototyping in hours meant clinical and engineering reviewed something real — so the risky questions got answered before a line of production code was written.
04 Trade-offs
A free suitability check placed first will turn some paying customers away before checkout.
Take the smaller, cleaner funnel. A refunded customer costs twice and tells people about it.
Adding "why we ask" makes forms longer, and conventional wisdom says shorter forms convert.
Explain sensitive fields, collapse the rest. Length wasn't the barrier — unexplained intrusion was.
Intake sat in a stacked modal with a seven-dot progress bar and no sense of scale.
Keep the stepped form, but show the number of steps and let people save and leave without losing their place.
05 Outcome
Fewer people reaching payment before an eligibility answer, and fewer refund requests citing suitability
Fewer abandonments at sensitive fields once each one carried a reason
From "am I eligible?" and "what does this cost?" to clinical and scheduling questions
What I'd do next