What healthcare design teaches you that no other industry does

Every designer should spend two years in healthcare. Not because it's noble — though it is — but because nothing teaches you what design actually is faster than designing for a context where being wrong has a body count.

I'm half-joking about the two years. I'm not joking about the rest. Here's what the work has taught me that I didn't know before.

1. Edge cases are not edge cases

In consumer design we deprioritize edge cases because they're "1% of users." In healthcare, the 1% is the patient in septic shock. The edge case is the entire reason the system exists. Design for the median user and the system fails exactly when it needs to work.

This rewires how I think about defaults. The default should be the safest path, not the most common one. Optimize for the common path through speed and clarity — but make sure the rare path is the one that doesn't kill anyone when it's followed under stress.

2. Cognitive load is a design specification

I now think about cognitive load the way an architect thinks about load-bearing walls. It's not a vibe. It's a measurable property of the interface, and you can engineer for it.

Number of items on screen. Grouping. Visual weight. Whether the most important number is in the top-left where eyes land first, or buried in the third column of a table. These are decisions that cost or save mental capacity, and mental capacity is what the clinician spends. You're either being generous with their attention or you're being expensive.

"In healthcare, the interface is not what the user sees. The interface is what's left in the user's head after they look away."

3. Trust is built in the boring moments

The signature healthcare-software trust moment isn't the hero feature. It's whether the loading state is honest. Whether the error message tells you what went wrong, or just blames you. Whether the system saves what you wrote when your shift ends, or makes you re-enter it tomorrow.

Clinicians have been burned by software before. Most of them have war stories about an EHR that ate three hours of charting. They are not going to give your interface the benefit of the doubt. You earn trust the slow way: by being correct in the moments where being incorrect would be easy to get away with.

4. Beautiful is not the enemy. Decorative is.

There's a strain of healthcare-software design that treats aesthetics as suspicious — "this is a serious tool, it should look like 1998." I think that's a misread. Beautiful interfaces in healthcare are absolutely possible. What's wrong is decorative interfaces — chrome that doesn't earn its space, illustrations that hide information, animations that delay critical reads.

You can be beautiful and correct. The two are not in tension. They are in tension with showing off, and that's a different problem.

5. The user you're designing for has more authority than you

In consumer design, the user is the customer. In healthcare, the user is a credentialed professional with a medical license, sometimes 20 years of experience, and the legal responsibility for outcomes. They don't need your interface to teach them medicine. They need it to get out of their way.

This is humbling in a useful way. It strips out a lot of the designer-ego stuff. You're not the expert in the room. You're the one who builds the room so the expert can work.

What healthcare made permanent

I’ll probably work on consumer products again at some point. Consumer work can be fun, expressive, and genuinely valuable. But healthcare changed the way I understand design.

It made the stakes clearer.

It taught me that design is not just about making something easier to use. It is about reducing risk. Protecting attention. Respecting expertise. Making critical decisions easier to see, harder to miss, and safer to act on.

That changes you as a designer.

Once you have worked in a context where clarity can affect care, it becomes harder to treat design as surface. The details stop feeling small. The hierarchy, the defaults, the empty states, the errors, the confirmations, the timing of information, all of it starts to matter more.

Not because healthcare is the only meaningful place to design.

But because it teaches you, very quickly, what design is when the work cannot hide behind taste.

So no, I don’t think every designer literally needs to spend two years in healthcare.

But I do think every designer should spend time in a context where the consequences are real enough to sharpen their judgment.

Healthcare did that for me. And I’m a better designer because of it.

— Victor