Shad Abbaslou / Contexts
● Open to global roles
Case file 003 · NHS mental health trust · 2020 · discovery → live beta

Safe Space, NHS mental health care when it moved home

What a private diary for teenagers, a summary for parents, a simple app for older adults, and one clinician tool for callsFor an NHS trust’s young people’s and older adults’ mental health teamsProblem COVID sent clinicians and patients home, and the notes system was built for a room

In 2020 COVID sent an NHS trust’s mental health clinicians home, and the people they cared for were already there. Care that had happened across a desk had to happen through a screen, for the first time, at both ends of the age range. This built the connection in between: a diary private enough for a teenager to use, an app simple enough for someone making their first video call, and one clinician tool made for calls rather than rooms.

24 min read · 16 min skimmed

Three weeks  a mark per entry written, one shared by choice. Scrub it.

Safe Space · The three apps Rebuilt & running · the diary, the parents’ app and the older adults’ app · every person is fictional
The diaryDavid, 15 Private by default. Every share is his, entry by entry: who, and how much, from his mood alone to the whole entry. Full screen ↗
Parents & carersClaire, his mum That he wrote this week and which way it went. Never the words, unless he shares them with her. Full screen ↗
Your care teamMargaret, 78 One button to join a call, a phone call instead, and four questions about her body. Built for a first video call. Full screen ↗

Write an entry on the left and choose who reads it, and how much. In the middle, what his mum sees: that he wrote, which way the week went, never the words. On the right, the other end of the same service: Margaret, 78, reaching her nurse through a screen for the first time.ONE SERVICE, TWO ENDS OF IT

Safe Space · The clinician dashboard Rebuilt & running · one tool, two teams · every patient is fictional
Open ↗
booting the product…

Open a record and it starts on the brief for the call: what matters to them, their body beside their mood, what you agreed last time. Write a session note and leave one thing to remember. Switch the team to see the same tool at the older adults’ end.USE IT, DON’T READ ABOUT IT

Accessibility: The clinician tool, the three phone apps and the notes system before all pass axe-core’s WCAG 2.1 AA rules at desk and phone, in both settings, and in the 16 states this file links into. Not yet tried with a screen reader. The statement

Weight on a first visit: the clinician dashboard, 349 KB of script and 13 KB of style, compressed, against budgets of 365 and 15 KB; the phone apps, 293 KB of script and 16 KB of style, compressed, against budgets of 310 and 18 KB. The build fails if a product passes its budget.

The states around it, each one a link: a caseload search that finds no one. Each says what is true, names the next step and offers one action.

On a phoneThe clinician tool Four tabs at the thumb, Today, Caseload, Messages and Settings. The risk flag and the call stay above the fold, the way a clinician between visits would need them. Full screen ↗
The Safe Space clinician dashboard on a desk: the day’s appointments on the left, a young person’s episode of care, risk flag and health summary in the middle

The clinician tool works on a phone, as it had to once the clinic was a kitchen table: the day’s calls as cards and each record in full. Open it full screen for the whole tool.

Open Safe Space ↗
Role
Product Designer
Client
NHS trust, mental health services (anonymised)
Duration
A year · discovery → beta
Framework
GDS Service Standard
I owned
The discovery research, the privacy model, and the design of the diary, the parents’ summary and the clinician tool, through to the beta; and the older adults’ app, proposed on the same model
With
The CAMHS clinicians, a youth mental-health nurse who co-facilitated the teen interviews, the trust’s clinical safety officer, digital governance, and two developer leads
Theirs
The constraints, set by the trust’s clinical safety officer and digital governance in the feasibility session, and the beta, run by the clinic as part of real care
Constraints
Care that moved home overnight in 2020, a teenager’s privacy under Gillick competence, the GDS Service Standard, the trust’s clinical safety and digital governance, and not one minute of added workload for clinicians
Friction
Parents wanted to see what their teenagers would not show them, by forty-six points; parents get a summary, never the words
The outcome21 people, 3 weeks, 1 real clinic19 interview sessions with 12 people and 70 surveys in; a live beta out, used as part of real care.
The problemCare moved home overnightIn 2020 clinicians and patients were sent home. The notes system assumed a room, and the clinic lost sight of people between calls.
The moveThree apps, one clinician toolA diary private enough for a teenager, an app simple enough for a first video call, and a clinician tool built for calls rather than rooms.
00When care went home

Two ends of one service, sent home at once

I came to the trust’s work through an agency, with access across its projects. The largest was this one. In 2020 COVID moved its mental health care out of clinics and into people’s homes, and the software it ran on was built for a room.

The young people were fluent on their phones, on Instagram and the rest, and guarded about how much of themselves left them. Plenty were not at home on Zoom. They needed somewhere that felt safe enough to write in, like a diary, with full control over how much of it reached a clinician or a parent.

The older adults were the other end of the same spectrum: people who needed to talk to their nurse more often than ever, could not see them, and were asked to use a computer or a phone to do it, often for the first time. They needed the lowest barrier to entry that could be built.

The clinicians were at home too, with four or five people to see an hour. In each call they had to build a connection through a screen, and write down enough of what mattered that the next call, with no waiting room and no corridor to warm it up, could start where this one ended.

And the two were joined. These are services where the body and the mind show up in each other first: a teenager’s sleep before their mood, an older adult’s meals and pain before theirs. Shut in at home, both got worse together, and the old system recorded neither.

Before · The notes system Reconstructed from memory · not a copy · every name invented
Open ↗
booting the old system…

Try to record today’s video call. There is no such contact type, a room is mandatory, a phone call is refused as administrative, and the history is a printout to an office nobody is in. This is the kind of system the clinicians had, rebuilt from memory to show the problem; it is not a copy of it.

A reconstruction of the old notes system: a grey, fixed-width form of mandatory fields, refusing to save a telephone contact against a clinical episode

The old system is a fixed 1024 pixels wide, as it fitted an office monitor. On a phone it is a picture, which is the point.

What the old system assumed, and what the new one does instead. Each line opens the tool at the place it does it.

Before and after: the old notes system against the new clinician tool
The old system assumedThe new tool does
A contact happens in a room, and a room is mandatoryA contact is a call, by video or by phone, and a room is the exception. Book one
One appointment at a time, in a buildingFour or five calls an hour, with the hour on screen: how many, how many done, who is next. See the day
The history is a printoutEach call opens on a brief: what has changed since you last spoke, what you agreed, what matters to them. Open Josh’s
A note is a free-text box for the recordA note keeps one thing to remember for next time, and the next call opens on it. Open Hannah’s
Mood, if anything, typed up afterwardsThe body beside the mood, from the person’s own check-ins: sleep, meals, getting out, pain. Open Margaret’s
One kind of patient, at a desk in an officeOne tool for the young people’s team and the older adults’ team, on a laptop at a kitchen table or on a phone. Switch team
01The blueprint

The system drawn first, then the screens

Before the dashboard: the service as a system, the one gate everything crosses, the four numbers it was built to move, the evidence under each decision, and the spec the rebuilt product is held to on every release.

SERVICE BLUEPRINTThe diary and the clinician dashboard as a service: twelve moments across two people, with the consent gate as the moment the whole service rests on. Pan, zoom, pick a moment, count the clicks to any point, switch the sad paths on.
Wheel to pan, pinch to zoom, click a moment for its detail. ← → walk the moments, f fits the map.Open the blueprint full screen →
THE SERVICE, END TO END: WHERE EACH PIECE OF DATA LIVES AND THE ONE GATE IT CROSSES THE DIARY THE YOUNG PERSON’S PHONE Mood, sleep, entries, voice notes Private by default No streaks, no escalating reminders THE RECORD THE TRUST, DATA CONTROLLER Shared entries only Encrypted in transit and at rest Withdrawn entries leave a note THE DASHBOARD CLINICIAN DATA DASHBOARD Today’s appointments first Episode, risk flag, QoL timeline Notes end in chips and a booking THE CLINIC CAMHS, NORTH LOCALITY Prep before the session Escalation to the safeguarding lead Weekly trend to parents, no entries THE SERVICE TRUST GOVERNANCE Gillick competence Documented parental consent Anonymised outcomes, counts only CONSENT GATE entry by entry, withdrawable RECOMMENDATION CHIPS AND THE NEXT BOOKING GO BACK TO THE APP NOTHING LEAVES THE DIARY WITHOUT THE YOUNG PERSON CHOOSING IT; THE GATE IS THE PRODUCT
Five places the data can be, and one gate between the first two. Everything the dashboard shows has crossed it; everything it writes back goes round the return leg.THE SYSTEM BEFORE THE SCREENS
Read this plate as text

The service drawn as five stations on one line: the diary on the young person’s phone, the record held by the trust as data controller, the clinician dashboard, the clinic and the service’s governance. Between the diary and the record sits the consent gate, crossed entry by entry and withdrawable. A return leg carries recommendation chips and the next booking back to the app.

The dashboard is the fourth thing in that drawing, not the first. The diary is private on the phone, the record holds only what crossed the gate, and the clinic reads the record. Draw it in that order and most of the product decisions make themselves: a clinician cannot see an entry the young person did not share because there is no path on the drawing by which they could.

The return leg is the part the first sketches missed. A session ends in recommendation chips and a booking, and those go back to the app in the same thread as the conversation, which is the only reason the dashboard adds no admin step of its own.

WHAT THE SERVICE WAS MEASURED ON: THE ROLLOUT METRICS, AGREED BEFORE THE BETA RAN USED AS PART OF REAL CARE 21 people, three clinicians, ten patients and eight parents, at one clinic site for about three weeks with every approval in place BETA · 1 CLINIC · 3 WEEKS 94% WOULD KEEP IT of beta users said the service should continue to be used BETA REPORT · BASE NOT GIVEN 4 ENTRIES A WEEK, PER PATIENT unprompted, in a product built with no streaks and no escalating reminders BETA · 10 PATIENTS 8 of 8 PARENTS OPENED EVERY WEEKLY SUMMARY the summary that carries a trend and no entries BETA · 8 PARENTS 5 of 5 CLINICIANS NAVIGATED THE PROTOTYPE naming the timeline graph and the alert flag as the parts they would use CLINICIAN PILOT THE METRICS WERE AGREED BEFORE ROLLOUT, SO THE BETA COULD NOT BE READ KINDLY AFTERWARDS
One root, four branches, every number from the beta report. The tree was agreed before the beta ran, which is the only way a beta metric means anything afterwards.AGREED BEFORE, READ AFTER
Read this plate as text

A tree with one root and four branches. The root is the beta itself: 21 people used the service as part of real care at one clinic for about three weeks. The branches are the four rollout metrics agreed before it ran: 94 per cent would keep it, four entries a week per patient, all eight parents opened every weekly summary, and five of five clinicians navigated the prototype.

WHAT THE DESIGN WAS BUILT FROM: EACH INPUT, THE FINDING IT GAVE, THE DECISION IT FORCED INPUT FINDING DECISION 19 interview sessions with 12 people, across all three corners of the triangle Teenagers will not volunteer how the week really went, and anything that reports on them quietly makes them report less. Private by default, shared entry by entry. The consent gate is the product, not a setting inside it. 70 survey responses: 30 clinicians, 40 young people and parents Any tool that adds administration to a clinic does not get used, however good the data in it is. Admin inside the clinical flow. Notes end in recommendation chips and a follow-up booking. 3 co-design workshops: clinicians, teenagers, governance The teens themselves rejected peer-to-peer messaging, on privacy grounds, in every workshop. Refused. No peer messaging, no notification theatre, nothing shared without a choice. 1 feasibility session with the clinical safety officer and digital governance Consent, data controller and identity settled after the screens exist start costing rewrites. Privacy model first: trust as controller, Gillick competence, documented parental consent. NOTHING WAS DRAWN BEFORE THE FIRST TWO COLUMNS WERE FULL
Each decision on the right has a finding behind it and a count behind the finding. The research section further down carries the programme in full; this is the part of it that became the product.INPUT · FINDING · DECISION
Read this plate as text

Four rows, each running input to finding to decision. Nineteen interview sessions found that teenagers under-report when reported on, so the diary is private by default and shared entry by entry. Seventy survey responses found that added admin kills a clinical tool, so the admin went inside the clinical flow. Three workshops found the teens rejected peer messaging, so it was refused. One feasibility session found that consent settled late costs rewrites, so the privacy model was written first.

The spec below is the part of this that is new. The rebuilt dashboard on this site is held to six statements, each written as an acceptance test before the screen was rebuilt, and each verified by a check that runs before every release of this site. The right-hand column names the check. Spec-driven in the plain sense: the sentence came first, the screen had to satisfy it, and something other than my eye confirms that it still does.

The specAcceptanceVerified by

SS-01No diary entry is visible to a clinician unless the young person shared it.

Given a record, when the conversation opens, then only entries marked as shared appear, each stamped with who shared it, and the settings page says who can see an entry.

The shared-entry card in every thread, and the consent list under Settings.THE PRODUCT, EVERY THREAD

SS-02A risk alert cannot be switched off while a clinician holds a caseload.

Given Settings, when the clinician reaches the risk-flag preference, then it reads Always on and carries no switch.

The check “the risk alert cannot be switched off”.THE INTERACTION SUITE, RUN BEFORE EVERY RELEASE OF THIS SITE

SS-03Escalation is one act, is logged, and notifies the safeguarding lead.

Given a flagged record, when Escalate is pressed, then the flag rises to High, the risk history gains a dated entry and a notification is raised.

The checks “Escalate raises the flag to High” and “the escalation is confirmed in a toast”.THE INTERACTION SUITE, RUN BEFORE EVERY RELEASE OF THIS SITE

SS-04The dashboard opens on the next appointment, not on a menu.

Given the day loads, when nothing has been clicked, then the first appointment’s record is on screen with its episode and its risk flag.

The check “opens on the first appointment’s record”.THE INTERACTION SUITE, RUN BEFORE EVERY RELEASE OF THIS SITE

SS-05A booking reaches the young person’s app.

Given Book, when an appointment is saved, then it appears on the week, in notifications, and the confirmation says it was sent to the app.

The checks “Book opens the appointment dialog” and “booking confirms in a toast”.THE INTERACTION SUITE, RUN BEFORE EVERY RELEASE OF THIS SITE

SS-06The whole dashboard works on a phone.

Given a 390-pixel viewport, when any screen opens, then four tabs are on screen, nothing scrolls sideways, and the record reads in full.

The check “nhs phone: 4 bottom tabs, no sideways scroll, no errors”.THE INTERACTION SUITE, RUN BEFORE EVERY RELEASE OF THIS SITE

02The setup

One hour a fortnight, then the teenager disappears

A FORTNIGHT OF A TEENAGER’S LIFE, AS THE CLINIC COULD SEE IT THE HOUR FIFTY MINUTES NO MOOD · NO SLEEP · NO INCIDENT · NO CONTACT · NOTHING AT ALL 1 hour to see all of it, diagnose against it, and decide what happens next 13 days a fortnight with no signal of any kind, reconstructed at the next appointment from memory THE CLINICAL DECISION WAS MADE ON A FIFTY-MINUTE SNAPSHOT OF A FORTNIGHT
One hour the clinic sees, thirteen days it does not. Everything the service does is an attempt to close that gap without taking the teenager’s privacy to do it.THE GAP THE SERVICE EXISTS TO CLOSE
Read this plate as text

A fortnight drawn as fourteen days. The first is filled, the appointment, and the thirteen after it are empty outlines that run off the edge of the drawing. Between appointments the clinical team had no signal at all, no mood, no sleep, no incident and no contact, unless the young person volunteered it at the next session and remembered it accurately. One hour to see all of it, diagnose against it and decide what happens next, against thirteen days a fortnight reconstructed from memory. The clinical decision was made on a fifty-minute snapshot of a fortnight, and closing that gap without taking the teenager’s privacy to do it is what the whole service is.

The team called it the Triangle of Care, and every corner of it was blind.

WHAT EACH CORNER HELD, AND COULD NOT SEE 01 THE YOUNG PERSON 7 days a week of it, and almost none of it said out loud COULD NOT SEE that the worry downstairs was about them, not at them 02 PARENTS & CARERS 0 reliable signal between appointments. They worry in the dark COULD NOT SEE anything at all, unless it was volunteered, and it rarely was 03 CLINICIANS 50 minutes a fortnight, and a decision made inside them COULD NOT SEE the thirteen days in between, which is where the week happened
Each corner held information the others needed. The service bridges the triangle without breaking the teenager’s privacy.THE TRIANGLE OF CARE
Read this plate as text

The Triangle of Care. The young person lives the week seven days a week and says almost none of it out loud, and cannot see that the worry downstairs is about them rather than at them. Parents and carers have no reliable signal between appointments and worry in the dark, able to see nothing at all unless it is volunteered, which it rarely is. Clinicians get about fifty minutes a fortnight and make a decision inside them, with no sight of the thirteen days in between, which is where the week actually happened. Each corner held something the other two needed.

The answer wasn't one app but two connected ones: a mood diary a teenager would actually trust, and a clinician dashboard that surfaces what matters before the session, named "Clinician Data Dashboard", in the GDS habit of saying what a thing does.

The older adults’ service, sent home in the same weeks, needed the same connection with almost none of the screen: one app, one button to join the call, and a phone call always offered instead.

Four jobs, one per person at the table

Written from the interviews, not quoted from them: what each person was trying to get done when the service went home.

  • The young personWhen I have had a hard day and cannot say it out loud, I want to write it down privately, so I can choose later whether my clinician sees it.
  • The parent or carerWhen I am worried about my child between appointments, I want to know how their week went without reading their diary, so I can help without breaking their trust.
  • The clinicianWhen I have five minutes before the next call, I want to see what has changed since we last spoke, so the call starts where the last one ended.
  • The older adultWhen the nurse is due to ring, I want one button that connects me, or a phone call if it will not, so I can talk to my nurse without learning a computer.
03Research · 19 sessions · 70 surveys · 3 workshops

I asked all three corners before drawing anything

FIG. 006 · NINETY-TWO PEOPLE19 INTERVIEWS + 70 SURVEYS + 3 WORKSHOPS

19 interviews With 12 people: clinicians, young people and parents

3 workshops The smallest block, and the one that moved the design

Two months of discovery, qualitative first, checked against numbers, then three co-design workshops: a half-day with 12 clinicians, two hours with 8 teens, and a feasibility session with the safety officer, digital governance and two developer leads.

REBUILT FROM THE DECKThe discovery programme, three corners of the triangle, then the numbers.
Clinicians8one-to-one interviews, psychologists, psychiatrists, MH nurses
Young people2 × 4interview rounds, ages 16–19, co-facilitated by a youth MH nurse
Parents3parents of current patients
Clinician surveyN = 30anonymous online form
Youth & parent surveyN = 40run with parental consent
Records pass1missed appointments and crisis incidents, for operational grounding: 65% of serious incidents in the past year had warning signs a tracking tool could have caught
01 INTERVIEWS 19 one to one, with 12 people: clinicians, teens, parents 02 SURVEYS 70 responses: N=30 clinicians, N=40 youth and parents 03 WORKSHOPS 2 half a day with 12 clinicians, two hours with 8 teenagers 04 FEASIBILITY 4 in the room: safety officer, governance, two dev leads 05 THE LIVE BETA 21 people, one clinic, three weeks
Qualitative first, then checked against the numbers. The feasibility session is where the constraints were agreed, not discovered late.DISCOVERY · 19 · 70 · 2 · 21
Read this plate as text

The discovery and validation programme, counted. Nineteen one-to-one interview sessions with twelve people across the three corners: clinicians, teenagers and their parents or carers. Seventy survey responses, thirty from clinicians and forty from young people and parents, run after the interviews rather than before so the questions came from what people had already said. Two co-design workshops, half a day with twelve clinicians and two hours with eight teenagers. One feasibility session with the safety officer, digital governance and two development leads, which is where the constraints were agreed rather than discovered late. Then a live beta with twenty-one people in one clinic over three weeks.

The programme above is how the research ran. This is what it found, and it is the reason the product has the shape it has: two of the three relationships in the triangle are uncontested, and one is not.

WHAT EACH SIDE WILL ALLOW · YOUTH AND PARENT SURVEY, N = 40 A CLINICIAN READING THEIR ENTRIES teenagers who say yes 64% A PARENT SEEING THEIR ACTIVITY teenagers who say yes 34% THE SAME THING, ASKED OF PARENTS parents who want it 80% 46 POINTS OF DISAGREEMENT between what a teenager will permit and what a parent wants, inside the same family, about the same screen
Two edges agree. One does not, by forty-six points.WHOSE TRUST THE PRODUCT NEEDED
Read this plate as text

What each side of the Triangle of Care will allow, from the youth and parent survey, forty responses. Sixty-four per cent of teenagers are comfortable with a clinician reading their entries. Thirty-four per cent are comfortable with a parent seeing their activity. Asked the same question, eighty per cent of parents want exactly that. So two of the three relationships are uncontested and one is not, by forty-six points, inside the same family and about the same screen. That gap is not a preference to be averaged out; it is the thing the product had to be built around, because a diary that satisfies the eighty per cent loses the thirty-four and then has nothing in it to read.

Three scripts, not one

The three corners do not share a problem, so they were not asked the same questions: one set would have produced a false consensus. Each interview was semi-structured, forty-five minutes to an hour, and the young people’s were co-facilitated by a youth mental-health nurse.

The young people

  • How they express what they think and feel
  • What is hardest about talking to parents, and to clinicians
  • How much privacy matters
  • What an ideal support system would look like

Parents and carers

  • How they see their child’s mental health
  • What makes it hard to talk about
  • How they balance privacy with wanting to help
  • What tools would help

Clinicians

  • How they prepare for a session, and what they have or lack
  • What gets in the way of a young person’s trust
  • How they keep confidentiality and keep parents informed
  • What a digital tool would need to do

Both surveys, one scale

Run after the interviews, so the questions came from what people had already said. Each bar is the share who agreed. Three rows became the product’s shape, and the findings below open the product where each shows.

Clinicians in the trust N = 30

  1. I would use a digital dashboard if it saved me time100%
  2. Real-time patient-reported data would improve my care90%
  3. I struggle to track patient progress between sessions82%
  4. I currently rely on patient or parent recall73%
  5. I am concerned about information overload so the record opens on highlights45%

Young people and parents N = 40

  1. I worry about who can see what I write so it is private by default88%
  2. I would use an app if my clinician suggested it76%
  3. Having a way to express myself between sessions helps70%
  4. I am okay with my clinician seeing my entries64%
  5. I am okay with a parent seeing my app activity so parents get a summary, never the words34%

Six findings, and where each one lives now

The deck’s insight cards, grouped by who said it. Each carries its evidence and opens the product at the place it changed.

The young people

Parents and carers

Help without intruding

Most would accept a summary rather than the entries, and pushing for detail is what ends the conversation. 34% of young people would let a parent see their activity; 80% of parents want to.

A weekly summary, never the words

Clinicians

04Decisions

The teens rejected the feature adults assumed they'd love

Everything from the workshops went through a value-versus-complexity matrix, with point 2 of the GDS Service Standard, do less, as the tie-breaker. Peer-to-peer messaging died in the bottom-right quadrant: the teens themselves killed it, on privacy grounds.

The settings page of the clinician dashboard: text size, the week, notifications, and no switch for the risk alert
Notifications and data-sharing defaults, with the one that cannot be switched off marked as such.THE PRODUCT, AS IT RUNS
REBUILT FROM THE DECKThe prioritisation matrix, user impact against technical complexity. Point 2 of the GDS Service Standard ("do less") broke the ties.

High impact · low complexity, kept

Journal entry with optional promptHigh emotional value; technically just text input and storage.
Clinician dashboard, patient list with mood statusSaves prep time; straightforward with NHS UI components.

High impact · high complexity, deferred

Real-time clinician notificationsNeeds polling or sockets; flagged for a later release.
Patient-to-clinician messagingClinical boundaries and safeguarding complexities.

Low impact · low complexity, parked

Mood input via emoji stickersThe standard slider already works.
Motivational quotes of the dayLow engagement impact.

Low impact · high complexity, rejected

Peer-to-peer messaging between patientsThe teens themselves rejected it on privacy grounds.
Custom dashboard widgets per clinicianToo much variation; not worth the build.
← user impact · technical complexity →

Privacy wasn't a checklist at the end; it shaped the product:

REBUILT FROM THE DECKThe privacy model, designed with the trust's clinical safety officer and digital governance.
Trust as data controllerdefined before a pixel was drawn
Parental consentfor younger users, documented in session
Gillick competenceteenagers deciding for themselves
Encryptionin transit and at rest
Email + PIN loginaligned with NHS identity standards for the pilot
Adoption by conversationa clinician introduces the app and records agreement
"My Mind Diary, your private space to share, only if you want." THE WAITING-ROOM POSTER LINE, PRIVACY AS THE PITCH, NOT THE FOOTNOTE
ABOVE THE LINE THE YOUNG PERSON 0 entries leave on their own. The diary is private by default THE BOUNDARY · SOLID EXCEPT WHERE THEY OPEN IT SHARE THIS ENTRY? an explicit choice, entry by entry PARENTS & CARERS otherwise worrying in the dark CLINICIANS prepped, not surveilled WHAT NEVER CROSSES no peer messaging no notification theatre nothing shared silently
The product decisions that mattered most were refusals. Trust was the feature.TRIANGLE OF CARE · THE PRIVACY BOUNDARY
Read this plate as text

The privacy boundary drawn through the Triangle of Care. Above the line sits the young person and a diary that is private by default, where nothing leaves on its own. The boundary runs the full width and is solid except for a single gap, which the young person opens entry by entry as an explicit choice. Below the line sit parents and carers, who otherwise worry in the dark, and clinicians, who otherwise decide on a fifty-minute snapshot; both receive only what came through the gap. Three things never cross the line at all: peer messaging, notification theatre, and anything shared silently.

05The design

Private by default, shared only by choice

Try the shipped privacy model below, log a week, then decide, entry by entry, what your clinician sees.

The diary app’s share sheet over an entry: who can read this entry, three possible readers each with a switch, all off, and the choice to keep it private
The young person’s side of the model: one entry, three possible readers, nothing on until he says so.THE DIARY, AS IT RUNS
The parents’ app’s what-you-can-see sheet: four things a parent sees and four they do not, with the reason it works this way
The parent’s side: that he wrote and which way the week went; never the words, his messages or his notes.THE PARENTS’ APP, AS IT RUNS
LIVE REBUILDThe privacy model. Log a week, then choose what your clinician sees.

The young person's diary

What the clinician sees

A rebuild of the shipped model: private by default, shared entry by entry, and only ever by the young person's choice.CLICK A DAY
Four screens of the teen-facing app: home, mood calendar, weekly mood, planner
The shipped design: mood calendar, weekly view, planner. Private by default.PATIENT APP
The mood tracker as it was worked out on the ideation board: a strip of days in spring 2021 with one mood a day, a day's mood as a split bar, and the week as a calendar of dots
Tracking a spring, one day at a time.PATIENT APP

The clinician's side opens on today, not on a database: the day's appointments with change chips ("stronger symptoms", "improved mood", "no episodes"), a patient timeline of quality-of-life indicators, and the entries a patient chose to share, right in the communication thread where the conversation happens. Session notes end with recommendation chips (micro-goals, DBT, thought journal) and a follow-up booking, so the admin happens inside the clinical flow.

Clinician dashboard: today's appointments, patient thread with a shared diary entry and voice note
Today's appointments, a shared entry, a voice note, the hour between sessions, visible.CLINICIAN DASHBOARD
The patient overview in the clinician dashboard: today's appointments on the left, and for the open record a quality-of-life chart over four weeks with symptom severity, episode frequency and self-reported status
Patient timeline: quality-of-life indicators over time.CLINICIAN DASHBOARD
Clinician dashboard session notes view
Session notes with recommendation chips and follow-up booking.CLINICIAN DASHBOARD
Screen recording of the interactive prototype
The interactive prototype in motion.PROTOTYPE · APR 2025

Where AI does not go

A position rather than a finding: nothing a young person writes is read, summarised or scored by a model, and the products say so where the data is set, in the diary and in the clinician’s settings.

  • Why notThe research’s first finding was that privacy is everything to the young people, and 88% of them worried about who could see what they wrote. A model is one more reader, and the one they could not see.
  • What it would takeNICE’s evidence standards ask a digital health tool for evidence in proportion to what it does, and a tool that shapes care asks for the most. The constraints this beta ran under were set by the trust’s clinical safety officer and digital governance; a model reading entries would go back through both before it was built.
  • Where it might belongIf a model ever helped, the place it would have to earn is the clinician’s five minutes before a call, over what the young person has already chosen to share, and it would say it was a model wherever it spoke.
06Testing & beta

Tested mid-build, then run in a real clinic

Scenario-based sessions with 5 clinicians and 5 young patients changed the build where the evidence said: an entry-tagging system was added; a "your clinician read your entry" notification was postponed. QA ran on real iPhones and Androids.

  1. 1 · WireflowsEvery key task in sequenceThe dashboard: log in, the patient list, a patient’s detail with charts. The app: consent, the daily mood, a journal entry, past entries, the sharing settings.
  2. 2 · ReviewToo many chartsReviewed in the team and with a few friendly stakeholders. The dashboard became one main chart and a few key metrics, after a clinician said: “just show me the highlights”.
  3. 3 · Mid-fidelityClickable, with real-looking dataFigma for the app, a web prototype for the dashboard, the trust’s components, and fictional records: Alex’s month of moods, a journal line about a rough day at school.
  4. 4 · UsabilityFive clinicians, five young patientsEntries gained tags and a mood scale that says which way it runs; the read notification was postponed.
  5. 5 · BetaA live clinic, three weeksThree clinicians, ten patients and eight parents, on the build the four passes left.
The usability tasks, word for word, and what they found
TaskWithWhat it found
“Imagine you’re about to see patient Alex. Use the dashboard to get ready and tell us what you gather.”5 clinicians5 of 5 got ready from the dashboard and found the data useful 95% interval 51% to 100%
Reading the mood graph, labelled “Wellbeing Score over 4 weeks”5 clinicians2 of 5 could not tell whether higher was better 95% interval 12% to 77% Relabelled Mood (1 = low, 10 = high), and the rebuild gives every measure on the record’s chart its direction
“You’ve just had a hard day. Can you log that in the app? Now imagine a week passed, can you see how you were feeling over the week?”5 young patientsFed the two changes the sessions made: entries gained tags, and the “your clinician read your entry” notification was postponed
The clinician dashboard's caseload table: young people sorted by risk, last contact and next appointment
The beta's caseload: three clinicians, ten patients, eight parents, three weeks.THE PRODUCT, AS IT RUNS
Twenty-one people, three weeks, one real clinic. Find one.
21 people, in real care The beta put the system into one live clinic for three weeks with 3 clinicians, 10 patients and 8 parents, and the rollout metrics were defined before rollout: clinician usage rate, entries per user per week, qualitative clinical outcomes. THE BETA COHORT · NEXT: THE TRUST'S ADOLESCENT UNIT, THEN NEIGHBOURING TRUSTS
07The flow · end to end

Two apps, one lane each, and a gate between them

The young person's week and the clinician's day run as separate lanes, and nothing crosses from one to the other without an explicit choice.

LANE 1 · THE YOUNG PERSON, PRIVATE BY DEFAULT A GENTLE PROMPT once a day, never a streak MOOD, 1 TO 10 about ten seconds of work THE DIARY text, voice or tags. Private THEIR OWN CHART patterns, for them first THE CONSENT BOUNDARY SHARE THIS ENTRY? one entry at a time, and only ever upward LANE 2 · THE CLINICIAN, NO EXTRA WORKLOAD THE CASELOAD opens on today, not on a search PRE-SESSION only what was shared, plus the trend THE SESSION the hour they always had SAME-DAY FLAG surfaces before the session, not after it
One arrow crosses the boundary, and only because the young person put it there.TWO LANES, ONE GATE
Read this plate as text

Two-lane service flow for Safe Space. In the young person’s lane a gentle daily prompt leads to a mood log of one to ten, about ten seconds of work, then a private diary in text, voice or tags, and a weekly chart that is theirs to read first. Between the lanes runs the consent boundary, solid except for a single gate, operated one entry at a time and only ever from the lane above. In the clinician’s lane the caseload opens on today rather than on a search, the pre-session view shows only what was actually shared plus the trend, the session is the hour it was always going to be, and a same-day flag surfaces before that session rather than after it.

08What was broken · what changed

Where the service broke, and what closed it

Six things the discovery work found, the design decision taken on each, and what happened next.

A young person's record on the risk tab: the risk history with the flag, its source and the escalation
What moved, in the product: the risk history and the one-act escalation.THE PRODUCT, AS IT RUNS
Where the service broke, and what closed it: the six rows of the table below, each crossed off by your scroll. Hold one to find it in the table.
Was brokenWhat I changedWhat it moved

A CAMHS team sees a teenager for one hour, then loses sight of them until the next appointment, so clinical decisions were made on a fifty-minute snapshot of a fortnight.

Two connected apps rather than one: a mood diary with an optional prompt, and a dashboard that opens on today's appointments with change chips, a quality-of-life timeline and the entries a patient chose to share.

21people used it as part of real care: 3 clinicians, 10 patients and 8 parents, with the rollout metrics agreed before rollout.BETA · 1 CLINIC · 3 WEEKS

Teenagers will not volunteer how the week really went, and anything that reports on them quietly makes them report less.

Private by default, shared entry by entry. Nothing syncs on a schedule and nothing leaves the diary without the young person choosing it; the consent gate is the product, not a setting inside it.

Privacy became the pitch rather than the footnote: the waiting-room poster led with “your private space to share, only if you want”.THE POSTER LINE, VERBATIM

The adults in the room assumed teenagers wanted to message each other, and a feature list built on that assumption would have swallowed the budget.

Asked all three corners of the triangle first, then ran every workshop idea through a value-versus-complexity matrix with point 2 of the GDS Service Standard ("do less") as the tie-breaker. The teens killed peer-to-peer messaging themselves, on privacy grounds.

19 / 70interviews and survey responses before anything was drawn, and three features refused rather than built.19 SESSIONS WITH 12 PEOPLE · N=70

The mood graph was labelled “Wellbeing Score over 4 weeks”, and two clinicians could not tell whether a higher number meant a better week or a worse one.

Renamed it in plain language as “Mood (1 = low, 10 = high)”, in the GDS habit of saying what a thing does, which is also why the dashboard is called the Clinician Data Dashboard.

5 of 5clinicians then navigated the prototype successfully, naming the timeline graph and the alert flag as the parts they would use.CLINICIAN PILOT

Any tool that adds administration to a clinic does not get used, however good the data in it is.

Put the admin inside the clinical flow: session notes end in recommendation chips (micro-goals, DBT, thought journal) and a follow-up booking, in the same thread where the conversation happened.

The dashboard asks for no separate write-up step, which is the only reason a clinician with a caseload of twenty opens it before a session.DESIGNED WITH THE CLINICAL TEAM

Consent, data controller and identity are usually settled after the screens exist, which is when they start costing rewrites.

Wrote the privacy model first with the trust's clinical safety officer and digital governance: trust as data controller, Gillick competence, documented parental consent, encryption in transit and at rest, email and PIN aligned to NHS identity standards, and adoption by conversation.

The model was fixed before the first screen, so the beta ran inside a real clinic as part of care rather than as a trial bolted onto it.FEASIBILITY SESSION · SAFETY OFFICER & GOVERNANCE

09Outcome

The decisions that mattered were refusals

Measured against the rollout metrics agreed before the beta ran
It worked ifResultStatus
It is used as part of real care21 people, three clinicians, ten patients and eight parents, at one clinic for about three weeks, with every approval in placeMet
The people using it want to keep it94% of beta users said the service should continue; the beta report gives the share, not the number it is a share ofMet
Teenagers write without being nudged4 entries a week per patient, in a product with no streaks and no escalating remindersMet
Parents read the summary8 of 8 parents opened every weekly summaryMet
Clinicians can find what they need5 of 5 clinicians navigated the prototypeMet
19interview sessionsWITH 12 PEOPLE, ACROSS THE TRIANGLE
70survey responsesN=30 CLINICIANS · N=40 YOUTH & PARENTS
3co-design workshopsCLINICIANS · TEENS · GOVERNANCE
94%of beta users would keep itTHE BETA REPORT’S SHARE · ITS BASE NOT GIVEN

The beta ran with three clinicians, ten patients and eight parents at one clinic site for about three weeks, with every approval in place. The beta report puts those who said the system should continue to be used at ninety-four per cent; it gives the share, not the number it is a share of. Patients wrote an average of four journal entries a week each, unprompted, in a product that was deliberately built with no streaks and no escalating reminders, and all eight parents opened every weekly summary, which is the one that carries a trend and no entries. The deck carries the full beta report.

What I'd tell another designer taking this on: the product decisions that mattered most were refusals, no peer messaging, no notification theatre, nothing shared without an explicit choice. Trust was the feature. Everything else was UI.

The booking dialog over today's appointments: a slot, a clinician, a note, and the young person's app named as where it lands
The outcome, running: a booking that reaches the young person's app.THE PRODUCT, AS IT RUNS
The diary app’s thread with the keyworker: a session card carrying two recommendations and the next appointment, then the conversation and a shared entry
Where the booking lands: the session’s recommendations and the next appointment, in the same thread as the conversation.THE DIARY, AS IT RUNS

What I would do differently

  1. Test the riskiest assumption before it reaches the build. Peer messaging was in the build when the teenagers killed it. A paper version in front of them would have cost an afternoon.
  2. Keep the research records with the work. The breakdown behind the nineteen interview sessions survives only in this portfolio’s own earlier text, which makes it the weakest figure on the site.
LIVE ARTIFACTThe full Safe Space case study: the interactive site, personas and journey included.
Enter the artifact full screen →

Source notes

  • Trust identity, staff and patient details anonymised throughout; personas in the full deck are labelled fictional.
  • Research figures (interview counts, survey Ns, workshop rosters, beta cohort) are from the project's research plan and rollout deck, shown above.
  • Full interactive case study: withcontexts.com/artifacts/safe-space