Designing for patients, not power users
What changes when the person using your product shows up once, stressed, and never reads the manual.
Minhaz Ahmad Didat
Senior Product Designer
Most of my work is for people who use software all day. Operations staff, providers, teams who know the product better than I do. Designing for them is its own craft. You can add density, shortcuts and power, and they will thank you for it.
Then I worked on the patient side, and almost everything I knew got turned around.
A different kind of user
A patient requesting their own medical records is not a power user. They usually arrive once. They are often stressed, sometimes dealing with something serious. They will not learn your interface. They will not read a tooltip. They want to finish one important task and get on with their life.
The old patient flow had borrowed patterns from our internal tools. Dense tables, stat tiles, language that made sense to staff. For a patient it was a wall. I realised we had designed for ourselves, not for them.
Remove, do not add
For power users, good design often means adding capability. For patients it is the opposite. The best thing I did was take things away.
I cut the dashboard. Patients do not want to manage requests, they want to make one. So I led with a single obvious action and got out of the way. One question at a time, plain words, clear progress. The KPIs and tiles that felt so useful internally had no place here.
Tone is part of the interface
Words carry the mood. A status that reads like a database field feels cold when you are anxious about your health information. The same status, written like a human explaining what happens next, feels like someone is looking after you.
I spent real time on the waiting and empty states, because those are the moments a patient is most likely to worry. Telling someone clearly what is happening, and when to expect the next update, does more than any illustration.
The point
Accessibility and empathy are not a checklist you run at the end. When someone is asking for their own health records, they are the whole point. Designing for patients taught me that removing friction is often more valuable, and more difficult, than adding features.