Halo
- User research
- UX/UI design
- Responsive web design
- Remote engagement
- 16 weeks
Halo connects clinicians and patients around a shared care plan. Both sides had an app, the two apps described the same appointment differently, and every mismatch became a phone call.
We ran the research with both audiences in parallel and refused to design either view until we had one vocabulary that worked for both. Halo’s clinical advisors vetoed two drafts, which was the point of having them.
One record both sides can read
A booking flow clinicians trust
Accessibility cleared at AA
One vocabulary
A visit, a plan and a result mean the same thing on both sides now, down to the wording of the labels. Where clinicians need a term patients would not use, the patient view carries a plain-language equivalent rather than a different concept.
The clinician view
Dense, keyboard-first, and built for someone who has six minutes. Nothing animates, nothing collapses on its own, and the information a clinician needs to open a consultation is on one screen without scrolling.
The patient view
The same data, paced differently: one question at a time, every clinical term explained on first use, and a plan that reads as a sequence of days rather than a table.
Sample content
Two audiences, one vocabulary. They refused to start designing until both sides agreed what a visit was, and that decision saved us a year of reconciling two products.
Marc Delacroix
