Sylva

Company
Sylva
Role
Design Lead
Team
2 Developers, 2 QAs, Product Owner
Sylva home screen on a phone

Context

Sylva is a mobile app that helps parents of children with additional needs understand their child and find the right support. It is also a Class 1 medical device.

I lead design end to end, from discovery and user interviews to the shipped product and the design system behind it.

What I Led

  1. 01

    Research

    Introduced, found and ran weekly user interviews with parents, and helped on the Bangor University study.

  2. 02

    Design System

    Built Sylva’s Figma component library and a new way of working between design and code in Figma.

  3. 03

    Weekly Sprints

    Ran discovery and shipped in weekly sprints, releasing at least once a week.

  4. 04

    Full Redesign

    Redesigned onboarding and every app page, with a new paywall built on RevenueCat.

  5. 05

    AI Across The Work

    Built agents that check the component library against the build, write tickets, test the product as user personas, and help organise research and user feedback.

Results

10k+ app downloads
4.8/5 mean rating from independent NHS clinical psychologists on clinical appropriateness, accuracy and safety (peer-reviewed)
7 of 7 parents and carers found Sylva helpful after 4+ weeks of use (Bangor University study)
Top 10% trial-to-subscribe conversion in its category (RevenueCat benchmark)

Onboarding

The Sylva onboarding before the redesign
Before
The redesigned Sylva onboarding
After

By adding more depth and personalisation to onboarding, moving account creation to the middle and putting a paywall at the end, trial-to-subscribe conversion reached the top 10% of its category (RevenueCat benchmark).

Tests

Tests are the foundation of Sylva, because their results shape the rest of the app. But too few people were taking them, because they didn’t know why they mattered. The redesign makes the reason clear first, makes each test easier to understand, and gives people everything they need before they start.

AwaitingassessmentExploring /no labelAlreadydiagnosedYesNot nowYesNo / laterReminder +progress evidenceNew useronboardedReframe: “quickcheck-in”, not“test”Stress check-in(everyonetakes this)How do youdescribe whereyou’re at?Waitlist path: shortscreeners, trackover timePre-label path:guided introscreeningDiagnosed path: trackchild or uploadexisting reportShort introscreener first,quick versionWant to godeeper?Unlock fullerdiagnosticassessmentRedesigned results:clear value, what itmeans, next stepProminent “not adiagnosis” note(above the fold)Score suggestsprofessionalinput?Subtle referral toa clinician (soft,not a hard sell)First coach chat,informed bycheck-in resultsHome screen withpersonalised nextcheck-in nudgeReturnhookNextrecommendedcheck-in

The test journey as a decision flow: a reframed check-in, paths for where each parent is at, and results that make the value and the next step clear, with a prominent note that results are not a diagnosis.

Test User Flow In Figma

The Sylva test flow, from a first-time user to an experienced one

The full test flow, from a first-time user taking their first test to an experienced user returning to it.

The Finished Tests

Sylva Tests list and the Why take tests? sheet
Sylva test flow: details, questions and instructions
Sylva ADHD test result on a phone

The redesigned tests: a “Why take tests?” explainer up front, a simpler flow with clear instructions, and results framed as guidance, not a diagnosis.

Chat

Sylva coaching chat list on a phone
Sylva session summary: Ready for Jack’s SENCO meeting
Sylva chat with a Just checking in crisis sheet
Sylva chat in a hand

The chat page needed to be simple and effective for stressed parents, with safeguarding as the first priority. Each Sylva specialism has its own soft personality and colour.

“I feel heard and I feel seen, and it’s so validating.”

Sylva user, parent of an autistic child · Bangor University study

Across The Product

A sample of the new Sylva product flow

A selection of pages from the wider redesign.

How I Use AI

AI sits inside how the team designs, researches and ships at Sylva, with a strict process before anything goes live.

  1. 01

    Design To Code

    An agent, connected to Figma, constantly checks the component library and the built screens against Tailwind and the design system.

  2. 02

    Tickets

    Claude helps write tickets and bug tickets straight from the designs.

  3. 03

    Compliance

    Our compliance document is linked to Claude, so tickets are tested against the standards before they are built.

  4. 04

    User Personas

    An agent acts as different users, taking the onboarding and tests many times and going through the product, for an ongoing feedback loop.

  5. 05

    Research And Feedback

    Claude helps uncover patterns in user data, runs early checks on how the product comes across, and organises and books user feedback.

  6. 06

    Meetings

    Meeting agents keep decisions and actions on track.

Where AI Got It Wrong

Left alone, AI writes long, waffly tickets that tick every box. Now I write the core first, then AI checks it against compliance and our template.

Time Saved

Using agents and strict ticket templates, I’ve 3x’d my design output, which lets me focus more on our users.

Typing in the Sylva chat

Kind Words

“He’s extremely creative, honest, and brings the best out of people.”

George McCann · Technical Lead, Sylva

Visit Sylva