Work

The Care Contextual Initiative

A design standard for the conditions care actually happens in - the cognitive and clinical pressure behind every decision - built alongside our accessibility work, with designers from every squad.

Organisation
Nourish Care
Project period
2025 — Present
Disciplines
  • Accessibility
  • Clinical safety
  • Research
  • Design standards
A care screen, with accessibility on one side (readable in dim light, targets for shaky hands, works with no signal) and Care Contextual Patterns on the other (one decision at a time, right info at the right moment, mistakes stopped early)

In brief

The problem
Accessibility was treated as compliance, with WCAG as the ceiling. A screen could pass an audit and still lead to an error for someone working under pressure, tired, neurodivergent or reading in a second language.
My role
I identified and named the gap, set up CCP as its own discipline and own Phase 1, holding the view across squads.
What changed
Accessibility became a care-contextual standard, with WCAG 2.2 AA as the baseline rather than the ceiling. CCP sits in one of the design team's three core goals, alongside quarterly reviews of our public accessibility statement, an accessibility guild open to the whole business, and planned accessibility checks in the QA release pipeline.
Outcome
Phase 1 brings designers from every squad together on a shared pattern library for cognitive load, crisis-mode interfaces, neurodivergence, language diversity, journeys used by the people we support, and Voice of the Child. Patterns will be tested with people who have accessibility needs, and we shared the work with every product lead at design's first quarterly touchpoint.

Context

Care Contextual Patterns (CCP) is a shared library of patterns for designing decisions under pressure. It covers flows, behaviours, visual hierarchy and prominence: reducing cognitive load during a medication round, preventing errors in complex workflows, and putting the right information in front of someone at the moment of care.

It sits alongside our accessibility work, which deals with the physical side - contrast for dimly lit care homes, touch targets for high-stress moments, staying reliable in rooms with no signal. Accessibility makes sure someone can use the screen; CCP makes sure they make the right decision on it, whatever pressure they're under.

You need both. A screen can have big buttons and high contrast and still lead to a clinical error, because the flow didn't account for someone's cognitive load. A well-designed flow still fails if a care worker can't read it in a dim room. Before CCP, the two were routinely treated as one problem.

My role

I identified and named the gap, then set up Care Contextual Patterns as its own discipline, sitting alongside accessibility rather than folded into it. It's very much a team effort; designers across squads contribute to a shared pattern library, whilst I set the standard and hold the cross-squad view of where it applies.

Constraints

It has to work across a multi-product platform, with squads at different levels of maturity, rather than within one team's roadmap. Regulatory milestones on the horizon also gave us a forcing function instead of open-ended runway.

The people it needs to serve aren't only care professionals either. They include the people we support, whose needs don't show up in a typical accessibility audit.

What we did

Discovery

We defined the scope through research and cross-squad discovery, rather than starting from a solution. It covers:

  • Cognitive load and information hierarchy in care settings
  • Interfaces for urgent clinical moments and safeguarding
  • Neurodivergent users, both care professionals and the people we support
  • Language diversity, across first- and non-first-language English speakers
  • Journeys for people with support needs using the platform directly
  • Voice of the Child, for children's services

These patterns build on WCAG rather than replacing it, and pick up the conditions an audit doesn't see.

Principles we were already using

Looking back, the same three principles had been shaping decisions well before Phase 1 had a name: the person decides and the system informs; we don't interrupt care to serve the product; and information shows up at the moment of action, not in a report afterwards.

You can see them in a few places. In AI features, copy guides people towards reviewing the information rather than asserting a clinical conclusion, and anything predicted stays clearly marked. When in-product satisfaction surveys were being planned, I pushed back on over-surveying and proposed conditional prompts instead, so research doesn't get in the way of care. And we're exploring one shared Pulse pattern for capturing reasonable adjustments under both the Reasonable Adjustment Digital Flag and the Accessible Information Standard, so an adjustment is in front of the care worker when they're actually with the person.

Testing

Testing will run with real users who have accessibility needs, not proxies. It's also a partnership with engineering and PMs, who help us shape and prioritise the journeys carrying the most risk in their areas.

Outcome

Phase 1 is under way, with designers from across squads contributing to a shared pattern library.

Reflection

I'd been applying these principles long before I named them, and naming them is what lets the team make these calls without waiting for me.

The biggest leadership lesson here was that Care Contextual Patterns only mean something because our designers vouch for them, from their own product areas and viewpoints. I never wanted to mandate a standard; I wanted to make the case for one clearly and consistently enough to earn buy-in across design and beyond, because that's the version that holds up under real delivery pressure.