Short version

I am Head of Design at Nourish Care, where I direct product design across a multi-product platform for digital care records used by residential, nursing, supported living and community services. I work day to day with engineering, clinical and regulatory colleagues, and I am still hands-on in the design itself.

Fifteen years in, most of that in regulated or high-consequence software: care records at Nourish, social care at Florence, pharmaceutical data at Evaluate. The through-line is software used by busy people who did not choose it and cannot opt out of it.

My job is to make good design decisions cheap and bad ones expensive. In practice that means a design system people want to use, clinical safety thinking embedded in the components rather than bolted on at review, prototypes that de-risk a decision before anyone builds it, and enough air cover that designers can do the difficult version of the work rather than the fast one.

What I care about

• Error prevention over error messages. In care software, a wrong entry is not a UX inconvenience. It is a record someone will rely on.
• Cognitive load is a safety property. A care worker on hour nine of a shift is the design constraint, not the edge case.
• Evidence beats taste. Taste decides between two good options. It should not be deciding whether the option is good.
• Design leadership is mostly clarity. Most stuck teams do not need more ideas. They need someone to name the decision.

Outside the work

TODO — two or three lines. Keep it human but brief; this is the part people quote back to you.