There's a reflex in our industry to treat whitespace as virtue and density as debt. Every redesign announcement celebrates how much "cleaner" things got, which usually means the people who actually use the product all day now scroll three times as much.
Working on a design system for clinical software cured me of that reflex.
Clinicians don't want less information. They want the same information to cost less attention.
The compact mode experiment
When we introduced a compact density mode, tightening spacing and sizing tokens across the system without forking a single component, the most interesting outcome wasn't the obvious one. Yes, more rows fit on screen. The surprise was where people wanted it: not everywhere, but in exactly the workflows where they already knew the interface by heart.
Density is expertise-relative. A layout that overwhelms a first-time user is the same layout that lets a veteran move without friction.
What this means for systems
- Spacing tokens need roles (inline, stack, inset), not just sizes
- Components must reference roles so a mode swap cascades cleanly
- Type scale and hit targets have hard floors because density has limits, and accessibility sets them, not aesthetics
The kindest thing you can do for someone who lives in your product eight hours a day is respect how good they've gotten at it.