Shad Abbaslou / Contexts
● Open to UK roles
~/artifacts/safe-space
DECK 003
Deck 003 · Safe Space · a CAMHS trust · discovery to beta · names and details anonymised

Three corners, and no shared interest

A teenager, a parent and a clinician are not three users of one product. They are three parties whose needs genuinely conflict, and almost every feature that serves one of them can betray another. This is the deck, with the research that proved it left in.

Weeks logged, weeks shared  the gap between them is the product. Scrub it.

Role
User Researcher · UI Designer
Client
An NHS CAMHS trust · adolescent service
Standard
UK GDS Service Standard, discovery to beta
What this is
The deck, with the research left in
The problemAn hour a fortnight, then silenceClinicians reconstruct the other weeks from memory and second-hand reports; 65% of serious incidents had warning signs nobody had a way to see.
The moveA private space, and a deliberate doorLog in private by default. Share nothing unless you choose to, per item, with a named person.
The proofThree months, 70 responses, one clinicDiscovery to alpha in three months to the GDS standard, then a live beta in a real service.
01Context

A CAMHS service, and a name chosen by rule

The client was a Child and Adolescent Mental Health Services trust working with teenagers living with anxiety and depression. The programme ran to the GDS Service Standard, which decided more than the process: it decided the name.

Deck slide: project context. The service worked on is a Child and Adolescent Mental Health Services trust serving teenagers with conditions such as anxiety or depression. Clinicians often have limited insight into a patient's wellbeing between appointments, leading to missed patterns and less effective therapy sessions. The project followed GDS guidelines on naming and design, and the product name Clinician Data Dashboard was chosen as a consistently referred-to term, with a descriptive tagline. The trust's branding is shown anonymised.
The context slide, with the trust's identity anonymised.SLIDE 01

The name is a small thing that tells you what kind of programme this was. "Clinician Data Dashboard" is not a product name anybody enjoys writing. GDS guidance says a service should say what it does, so the thing that shows clinicians data is called the thing that shows clinicians data, and nobody had to learn a metaphor to find it.

02The triangle

Three points, one fragile network

The Triangle of Care is an existing model in adolescent mental health: patient, parent or carer, clinician. Reading it as a design brief, every edge is a communication channel that can build trust or quietly destroy it, and no edge carries the same traffic in both directions.

THE TEENAGER wants to be understood, not watched THE PARENT wants reassurance, and asking ends it THE CLINICIAN one hour a fortnight, then nothing 64% would let a clinician read the mood tracker 34% would let a parent see the same thing 80% OF PARENTS WANT TO which is the whole problem: the edge with the least consent is the one under the most pressure
The edge with the least consent carries the most pressure.THE WHOLE CASE, IN ONE DRAWING
Read this plate as text

The Triangle of Care with its edges weighted by what the survey found. Between the teenager and the clinician, a solid edge: sixty-four per cent of young people are comfortable with a clinician reading their mood tracker. Between the teenager and the parent, a broken edge: thirty-four per cent. And eighty per cent of parents want that second edge open. The edge with the least consent is the one under the most pressure, which is the problem the product exists to hold.

The teenagerwants to be understood without being watched, and controls nothing about who sees what
The parent or carerwants reassurance, and asking for detail is the thing most likely to end the conversation
The cliniciansees the patient for an hour a fortnight and has to reconstruct the other three hundred and thirty-five
03The plan

Three months, four research methods, written down before any of it started

Discovery was planned as a programme and shown to stakeholders as one, with overlapping phases and a date where alpha begins whether or not the research feels finished. That plan is the reason the work was taken seriously by people who had seen design engagements arrive without one.

MONTH 1 MONTH 2 MONTH 3 ALPHA Stakeholder alignment and assumption mapping Personas and mapping Qualitative research, 19 sessions with 12 people Quantitative research, 70 survey responses Stakeholder and co-creation workshops Prototyping and testing Usability testing Iteration and beta preparation
Eight workstreams, three months, and a date alpha starts regardless.SHOWN BEFORE IT RAN
Read this plate as text

The discovery and alpha programme as it was presented to stakeholders before any of it was run. Eight overlapping workstreams across three months: stakeholder alignment and assumption mapping, personas and mapping, nineteen qualitative sessions with twelve people, seventy survey responses, stakeholder and co-creation workshops, prototyping and testing, usability testing, and iteration into beta preparation. The third month is shaded because that is where alpha begins whether or not the research feels finished, which is the commitment that made the plan worth showing.

04Interviews

Twelve people, three different scripts

Semi-structured interviews, forty-five minutes to an hour, with teenagers, their parents or carers, and clinicians. Three separate question sets, because the three corners do not share a problem and asking them the same questions would have produced a false consensus.

Deck slide: conducting interviews with twelve users. Interview objectives were to gain deep insights into personal experiences and perspectives, identify pain points in communication, trust and managing mental health, and explore what each participant hopes to achieve from a digital solution. The interview process was semi-structured, lasting forty-five minutes to an hour, with confidentiality assurance that responses would be used solely for the project. Three question sets are listed: for the teenagers, covering how they express thoughts and feelings, the biggest challenges in communicating with parents and clinicians, how important privacy is, and what an ideal support system looks like; for parents, covering how they perceive their child's mental health challenges, the difficulties they face in communicating, how they balance respecting privacy with wanting to support, and what tools would help; and for clinicians, covering the main obstacles in building trust with patients, how they handle confidentiality while keeping parents informed, and what features in a digital tool would aid patient care.
Twelve people, nineteen sessions, three scripts.SLIDE 04
Deck slide: patient interviews, co-facilitated by a youth mental-health nurse. Many young patients struggle with in-person communication; one seventeen-year-old said it is sometimes easier to write down what they are feeling than to say it out loud. Patients liked the idea of a mobile diary app but privacy was the top concern: most were open to sharing with their clinician since it could improve therapy, but wary about parents, with one sixteen-year-old saying they would not mind their therapist seeing their mood tracker but would panic if their mother read their actual journal entries. All patients stressed the app must not feel like homework or another clinical questionnaire. Two insight cards record that privacy is everything to young people, which drove granular sharing controls and separate parent summary modes, and that teens prefer calm, non-clinical design and said they would stop using the app if it felt cold or like a form.
Patient interviews. The quotes are the design brief.SLIDE 05
Deck slide: clinician interviews. Clinicians were asked how they prepare for sessions, what information they have or lack, and their reactions to a data dashboard. Many described difficulty getting a full picture of a teenager's week-to-week mood; one admitted finding it hard to keep track of a patient's progress between appointments. Their only sources were sporadic patient self-reports or occasional teacher and parent updates. The conversations revealed specific needs: trending mood or anxiety levels, alerts for critical changes, and a quick summary of any self-harm thoughts or significant events logged by the patient. Clinicians also emphasised time constraints and data overload concerns. Two insight cards record that clinicians lack visibility between appointments, validating the need for a dashboard of real-time mood logs, and that time constraints are real, with clinicians reporting five to ten minutes to prepare for a session, which ruled out dashboards packed with detail.
Clinician interviews, and the five-minute constraint that shaped the dashboard.SLIDE 06
Deck slide: parent interviews. Parents and carers wanted to be supportive without violating their teenager’s trust, and described the difficulty of getting any picture of how their child is doing between appointments. The insight cards record that parents want to help without intruding, that most would accept a summary rather than the entries themselves, and that pushing for detail is the thing most likely to end the conversation.
Parent interviews. The third corner, asked separately.SLIDE 07
"I don't mind my therapist seeing my mood tracker, but I'd panic if my mum read my actual journal entries" INTERVIEW · A SIXTEEN-YEAR-OLD

That sentence is the product. Not the diary, not the dashboard: the fact that one person can be safe to tell and another cannot, that the difference has nothing to do with how much either of them loves the teenager, and that no existing tool in the service let anybody express it.

05The numbers

64% would let a clinician look. 34% would let a parent.

Two surveys were run after the interviews rather than before, so the questions came from things people had already said. Thirty clinicians in the trust, and forty adolescents and parents combined, collected anonymously with parental consent. The gap they found is the one number this entire programme turns on.

CLINICIANS IN THE TRUST · N = 30 I would use a digital dashboard if it saved me time 100% Real-time patient-reported data would improve my care 90% I struggle to track patient progress between sessions 82% I currently rely on patient or parent recall 73% I am concerned about information overload 45% ADOLESCENTS AND PARENTS · N = 40 I worry about who can see what I write 88% I would use an app if my clinician suggested it 76% Having a way to express myself between sessions helps 70% I am okay with my clinician seeing my entries 64% I am okay with a parent seeing my app activity 34%
The same scale for both sides, so the gap is visible rather than described.THE CONSTRAINT AND THE REFUSAL
Read this plate as text

Both surveys drawn against the same scale so the two sides can be read against each other. Among thirty clinicians: every one of them would use a dashboard that saved time, ninety per cent say real-time patient data would improve their care, eighty-two per cent struggle to track progress between sessions, seventy-three per cent rely on recall, and forty-five per cent are afraid of information overload. Among forty adolescents and parents: eighty-eight per cent worry about who reads what they write, seventy-six per cent would use an app a clinician suggested, seventy per cent want a way to express themselves between sessions, sixty-four per cent accept a clinician reading their entries, and thirty-four per cent accept a parent seeing their activity. The two marked rows are the constraint and the refusal the product was built around.

88%of teenagers worry who reads their entriesYOUTH & PARENT SURVEY · N=40
34%would let a parent see their activityAGAINST 80% OF PARENTS WHO WANT TO
100%of clinicians would use a dashboard that saved timeCLINICIAN SURVEY · N=30
45%of clinicians feared information overloadTHE CONSTRAINT INSIDE THE MANDATE

Read those four together and the brief writes itself. The clinicians unanimously want the tool, and nearly half of them are afraid of what it will do to their inbox, so it has to distil rather than dump. The teenagers will use it if a clinician suggests it, and almost nine in ten are frightened of being read, so privacy cannot be a setting buried in a menu. And the parents want twice the visibility their children are willing to give, which means somebody has to be told no, in an interface, gently, forever.

65% of serious incidents or relapses in the past year had warning signs that could have been captured if a tracking tool was in place HISTORICAL CLINIC DATA · THE LINE THAT FUNDED THE PROGRAMME
06Define

Four questions, and one of them has no clean answer

Discovery closed with four research questions rather than a solution. Writing them down this way is a GDS habit and a good one: it forces the team to agree on what is still unknown before anybody starts drawing, and it makes the later refusals defensible.

DISCOVERY CLOSED ON FOUR QUESTIONS, NOT ON A SOLUTION 01 A tool that respects a teenager’s privacy and still gets help to the people who need it PRIVATE BY DEFAULT nothing leaves the diary on its own 02 Features that let a teenager manage their own care between appointments, not only inside them THE JOURNAL AND THE MOOD TRACK built with no streaks and no notification theatre 03 Better communication across the Triangle of Care without compromising anybody’s trust NO CLEAN ANSWER 46 points between what a teenager will permit and what a parent wants 04 An app that adapts to individual preference and need rather than one setting for everybody SHARING SET PER ENTRY not per account, so consent is a decision each time
Three questions were answered. The third was decided instead.ONE OF THEM HAS NO CLEAN ANSWER
Read this plate as text

The four research questions discovery closed on, each joined to the thing that answered it. A tool that respects a teenager’s privacy and still gets help to the people who need it was answered by making the diary private by default, so nothing leaves it on its own. Features that let a teenager manage their own care between appointments were answered by the journal and the mood track, built deliberately with no streaks and no notification theatre. An app that adapts to individual preference was answered by setting sharing per entry rather than per account, so consent is a decision taken each time rather than once. The third question, better communication across the Triangle of Care without compromising anybody’s trust, has its connector drawn and then cut, because it has no clean answer: there are forty-six points between what a teenager will permit and what a parent wants, and no feature closes that. The product chose a side and said so.

The third one is the hard one, and it is phrased honestly: improve communication without compromising trust. Most products in this space quietly resolve that tension by deciding the parent is the customer. We decided the teenager was, and then had to design the parent an experience that was genuinely useful anyway, which is harder and is most of the work in section eight.

07Workshops

Three rooms, and the third one had the governance lead in it

Co-design ran as three separate sessions rather than one mixed workshop, for the same reason the interviews used three scripts. Then a feasibility session with the people who could stop it: the service manager, the trust's clinical safety officer, an NHS digital governance representative and two developer leads.

Deck slide: ideation and co-design workshops. Three focused workshops, one each with clinicians, patients and stakeholders. Workshop one, clinician co-design workshop: twelve clinicians across a mix of roles for a half-day creative session, with an ideation exercise around the question of how to give them the right information at the right time without adding workload. Workshop two, youth co-design session: eight teenagers aged fifteen to eighteen for a two-hour session to co-create aspects of the mobile diary app. Workshop three, stakeholder and feasibility workshop: a mix of stakeholders including a service manager, the trust's clinical safety officer, an NHS digital governance representative and two developer leads from the tech team, converging on feasible solutions and addressing policy, technical and funding constraints.
Who was in each room, and what each room was for.SLIDE 09
Deck slide: workshop three, stakeholder and feasibility workshop, showing a feature prioritisation matrix. Features were plotted against user value and technical complexity and voted on by the group, with stakeholders agreeing to trim non-essential features.
Features plotted against value and complexity, voted in the room.SLIDE 10
Deck slide: workshop three, data and privacy considerations. The digital governance lead guided the team through NHS data compliance needs, with cards covering what data would be stored and where, what consent model applied to a minor's records, how a parent's access is bounded, and what integration with existing clinical systems would require.
NHS data compliance, worked through with the governance lead rather than discovered later.SLIDE 11
08The refusal

Private by default. Shared only by a decision.

The product is three things a teenager can do alone, and one door they control. Logging a mood, setting a goal, writing an entry: none of it leaves the phone. Sharing is a separate, deliberate act, per item, with a named person, and it can be taken back.

Deck slide: tracking moods. Mood logging through simple interfaces for recording daily moods with options to add notes or context. Trend analysis through graphs and charts showing mood patterns over time, helping users identify triggers or improvements. Insights and suggestions, optional tips based on mood trends offering coping strategies or resources. Beside it, the My feelings screen with a mood grid.
Logging, in ten seconds, with nothing asked in return.SLIDE 12
The patient app: the daily prompt, the mood log, the private chart building up day by day, and the goals screen, shown as a row of phone screens.
The app itself: track, plan, reflect, and none of it leaves the phone.PATIENT APP
Deck slide: planning for the future. Goal setting, tools for setting personal goals, both short-term daily tasks and long-term aspirations. Progress tracking, visual representations of progress to motivate and encourage continued use. Reminders and notifications, customisable reminders to help them stay on track without feeling overwhelmed. Beside it, the My goals screen.
Goals, with reminders that were explicitly designed not to nag.SLIDE 13
PRIVATE BY DEFAULT SHARED ONLY BY A DECISION THE MOOD LOG ten seconds, every day, nothing asked in return THE GOALS set and tracked, with reminders that do not nag THE ENTRIES written in full, and never leaving the phone A SUMMARY the week went hard, without the sentences that made it hard A TIMELINE the trend a clinician can read in five minutes AN ALERT FLAG raised on an entry the patient chose to share A REQUEST ANSWERED DECLINABLE PEER MESSAGING an unmoderated channel between vulnerable adolescents STREAKS AND NUDGES the app must not feel like homework ANYTHING SHARED BY DEFAULT consent that is opt-out is not consent AND WHAT WAS REFUSED
One boundary, one gate, three refusals. The request is asked by a named person, is visible to the teenager, and can be declined without a confrontation.TRUST WAS THE FEATURE
Read this plate as text

The sharing model as a boundary. On the private side, everything a teenager can do alone: the mood log, the goals, the written entries, none of which leave the phone. On the shared side, what a parent or clinician can be given: a summary of how the week went without the sentences that made it hard, a trend a clinician can read in five minutes, and an alert flag on an entry the patient chose to share. Between them one gate, a request asked by a named person, visible to the teenager and declinable without a confrontation. Struck through below, the three things the product refused to build: peer messaging, streaks and nudges, and anything shared by default.

A request, not a settinga parent can ask for access, and asking is visible to the teenager, who can decline without a confrontation
Insight without entriesa parent can be told the week was hard without being shown the sentences that made it hard
No peer featuresno messaging between young people, no feed, no comparison: the brief was a safe space, and a social network is not one
Deck slide: the patient journey after the mobile diary app, mapped across the daily routine, engagement with the features, sharing and trust, and how a therapy session integrates what was logged, with the steps at each stage and an emotion curve beneath.
The same week, after: gentle prompts, a private chart, sharing only if chosen.JOURNEY MAP

The decline mechanism is the part I would defend hardest. A teenager saying no to their mother in person is a scene; a teenager leaving a request unanswered in an app is a boundary. Moving that conversation into software was not a convenience, it was the entire therapeutic function of the feature, and it is the reason "share requests" exists at all instead of a simple on and off switch.

09The dashboard

Five minutes to prepare, so five minutes is the design constraint

Clinicians told us they get five to ten minutes before a session. That single number did more to shape the dashboard than any amount of discussion about information architecture: it rules out exploration, it rules out dense tables, and it means the screen has to have already decided what matters.

The Clinician Data Dashboard: today's appointments listed down the left, the selected patient's shared diary entries in the centre with audio notes, and a secure chat panel.
Today's appointments, shared entries, secure chat.CLINICIAN DASHBOARD
Deck slide: the clinician journey as it should run with the dashboard in place, mapped across morning preparation, the session itself with the data to hand, and follow-up afterwards, with the steps at each stage and an emotion curve beneath them.
The clinician journey the dashboard was built to serve.JOURNEY MAP
The patient overview screen in the Clinician Data Dashboard: a mood timeline charted over recent weeks with alert flags marked on concerning entries, and a summary panel beside it.
Mood over time, with flags on the entries that need reading first.PATIENT OVERVIEW
Deck slide: two clinician insight cards. Clinicians lack visibility between appointments: many said they felt in the dark about what happens with their patients between sessions, which validated the need for a dashboard showing real-time mood logs and patient journals so clinicians can spot trends and prepare more effectively. Time constraints are real and data must be quick to read: clinicians said they had just five to ten minutes to prepare for a session, so dashboards packed with detail were avoided in favour of highlighted summaries, mood trends and a clean interface.
The two findings the dashboard was built against.SLIDE 15
10Alpha to beta

Tested mid-build, then run in a real clinic

Usability testing ran against the prototype during alpha, then the system went into a live beta inside one service: three clinicians, ten patients and eight parents at one clinic site, with every approval in place, for about three weeks. Twenty-one people using it as part of care rather than as an exercise.

94%of beta users would keep itCLINICIANS AND PATIENTS, THREE WEEKS IN
4journal entries per patient per weekUNPROMPTED, WITH NO STREAKS IN THE PRODUCT
8 of 8parents opened every weekly summaryTHE SUMMARY THAT CARRIES NO ENTRIES
21people in the beta3 CLINICIANS · 10 PATIENTS · 8 PARENTS
Deck slide: usability testing sessions, with task completion and satisfaction results charted for the clinician dashboard and the patient diary app.
Usability testing against the alpha build.SLIDE 16
Deck slide: low fidelity to mid fidelity design, showing the progression from rough wireframes to resolved screens, with the mood chart and the sharing controls worked out at each level.
Low fidelity to mid fidelity, with the sharing controls resolved last.SLIDE 15
Deck slide: quality assurance for user experience, and managing changes, describing how design review ran alongside development, how changes were logged and agreed rather than absorbed, and what was checked before a build was accepted.
QA for the experience, not only for the build.SLIDE 19
01 CLINICIANS 3 one clinic site, with every approval in place 02 PATIENTS 10 using it as part of care, not as an exercise 03 PARENTS 8 all eight opened every weekly summary 04 WEEKS ~3 a real-world trial, not a controlled usability lab 05 WOULD KEEP IT 94% of beta users said the system should continue to be used
Twenty-one people, three weeks, one real service.THE REPORT BACK
Read this plate as text

The live beta, counted. Three clinicians, ten patients and eight parents at one clinic site with every approval in place, for about three weeks, using the system as part of care rather than as an exercise. All eight parents opened every weekly summary. Ninety-four per cent of the beta users said the system should continue to be used.

Deck slide: live rollout strategy. A phased rollout plan beginning with a small cohort before widening, with onboarding and training for clinicians, a communication plan for patients and parents, a support setup for questions during the transition, and monitoring and metrics defined up front so the rollout could be judged.
The rollout plan, written as part of the design work rather than handed over.SLIDE 18

A rollout strategy in a design deck is unusual and it should not be. A product in a clinical service does not go live because it is finished; it goes live because somebody has planned the training, the comms to families, the support cover for the fortnight everyone is confused, and the measurements that will say whether to continue. Designing the thing and leaving that to somebody else is how good products die in month two.

11The decisions

Four calls, three of them refusals

On most products the decisions worth recording are things you built. On this one they are mostly things we were asked for and did not build, which is why the record matters more than usual.

Month 1 · the position The teenager is the user, and the parent is not the customer

The commissioning assumption was a parent-facing product with a child-facing data source. The survey said thirty-four per cent against eighty per cent, and the position changed to match the evidence.

What it cost Telling the people paying for the work that the product they described would be deleted by the teenagers it was aimed at. The data made that sayable; without it, it is just a designer's opinion about somebody else's family.

Month 2 · the refusal No peer-to-peer features of any kind

Messaging between young people in the service was requested more than once, in good faith, as a way of reducing isolation.

Why An unmoderated channel between vulnerable adolescents is a safeguarding incident waiting for a date. The clinical safety officer agreed in the room, which is the only reason this did not come back every quarter.

Month 2 · the refusal No streaks, no nagging, no notification theatre

Engagement mechanics were on the table. Daily streaks, reminder escalation, the usual apparatus for making a habit stick.

What it cost Measurable engagement, which is the number a product board most likes to see go up. Patients had said plainly that the app must not feel like homework, and a streak is homework with a scoreboard.

Alpha · the correction Rename the chart, lose the better name

"Wellbeing Score over 4 weeks" became "Mood (1 = low, 10 = high)" after two clinicians in the pilot could not tell which direction was good.

Why It is recorded here because it is small and it is the kind of thing that gets quietly fixed and never mentioned. Two people out of five not understanding the central chart is a failure rate of forty per cent on the one thing the dashboard exists to show.

12Outcome

Whose trust the product could not survive losing

12people interviewedTEENAGERS · PARENTS · CLINICIANS
70survey responsesN=30 CLINICIANS · N=40 YOUTH & PARENTS
3co-design workshopsCLINICIANS · TEENS · GOVERNANCE
21people in the live betaONE CLINIC · THREE WEEKS

What I would tell another designer taking this on: in a service with three parties, your job is not to find the feature that makes everybody happy, because there isn't one. It is to work out whose trust the product cannot survive losing, say so out loud, and then design the other two an experience that is honest about its limits rather than quietly generous with somebody else's privacy.

Trust was the feature. Everything else on this page is interface.

The case file carries the argument and the working clinician dashboard. Read case file 003, or use the rebuilt dashboard.