Clinicians don’t have time for your product. That is the whole problem, and most teams design as if it weren’t true.
NHS resident doctors now spend four hours on admin for every hour of direct patient contact; non-patient work fills 73% of their day. Whatever you ask a clinician to do lands on that pile. A tool that hands ninety seconds back gets used. A tool that takes ninety seconds, however sharp its output, gets dropped the week you stop watching.
Usability is a safety problem, not a styling one
The time tax gets worse when the software fights them. In the US, physicians score their electronic health record 45.9 out of 100 on a standard usability scale: a grade of F. The same study tied each one-point gain in usability to 3% lower odds of burnout. Usability here is not the coat of paint. It decides whether the people using your product cope or come apart.
Design for the busiest sceptic in the building
The clinician you need to win is tired, rushed and has been sold software before. Build for that person.
- Watch a real shift before you draw a screen. One hour on the ward beats a month of stakeholder calls.
- Count your clicks against the workaround they already use. If your way takes more taps than paper, paper wins.
- Follow the clinician’s mental model, not your database. They think in patients and tasks, not tables and fields.
- Earn one clear win on day one. Save them something early and you buy patience for the rest.
What this looks like in practice
On one clinical product, the users weren’t at desks. They moved between hospital engagements with a phone in one hand and a door in the other. The old interface assumed a mouse and a quiet room. We rebuilt the navigation for a thumb and a thirty-second gap: swipe-only, one-handed, the critical information first. Clinician uptake rose by 30%, and three more clinics asked to join.
That came from designing for the real conditions of the people meant to use it, not from a new feature. Give clinicians time back instead of taking it, treat usability as the safety issue it is, and adoption stops being a fight.
If clinicians are sidestepping a product you built for them, that is the work I do as an embedded product designer. See more of the case studies.
This article was originally posted on olibatstone.com on 09 June 2026.
Oli Batstone is an independent senior product designer specialising in digital health. Over ten years he’s shipped MHRA-approved medical devices, clinician dashboards and patient experiences for teams like Genomics. More about Oli.
