The 10 UX problems we see in almost every health tech product

Why it happens

• Teams confuse what the system needs with what users should provide upfront.
• The result is a registration flow that feels like a medical intake form before the user has seen any value.

What it costs

• Most users abandon forms before completing them, especially when the effort-to-value ratio feels off.
• Every additional field adds friction without adding value.
• Regulatory requirements create real pressure to collect data upfront. Users don't care about compliance constraints — they just abandon the form.

What good looks like

• Lead with a single moment of value.
• Collect information progressively, as it becomes relevant, not all at once.
• The user should experience what your product does before being asked to invest in setup.

Why it happens

• Health platforms often serve both patients and providers.
• Building separate experiences feels expensive, so teams compromise with a single interface that tries to serve everyone.

What it costs

• Patients find the interface clinical and intimidating. Providers find it oversimplified.
• When an interface is designed for neither user well, it can directly contribute to clinical errors — an extreme consequence of a common design shortcut.

What good looks like

• Identify where the experiences need to diverge and design them separately.
• Shared infrastructure is fine. Shared interfaces are where things break down.
• Even small differences in tone and density make a significant impact.

Why it happens

• Clinical products surface everything because everything could matter.
• Physicians are flooded with alerts every shift and override the vast majority of them.
• When everything demands attention, nothing gets it.

What it costs

• Critical alerts get buried next to routine information at the same visual weight.
• In clinical settings, this isn't just a usability issue. It's a patient safety issue.
• Missed alerts have real consequences.

What good looks like

• Build clear information hierarchy.
• Lead with what requires action, separate it visually from background data, and let providers drill into detail only when they choose to.
• Less on screen doesn't mean less capability.

Why it happens

• Teams test with sample data and never experience what a brand new user sees: usually nothing.
• Blank screens, empty tables, zero context.

What it costs

• New users don't understand what the product does or where to start.
• This is especially damaging in health tech where users may already feel anxious.
• A blank screen reads as broken.

What good looks like

• Treat empty states as a feature, not an edge case.
• Welcome users, explain what will appear here and why, and offer a clear first action.
• Your empty state is your first real conversation with the user.

Why it happens

• Health literacy is far lower than most health tech teams assume.
• Health products are built by clinicians and engineers who understand medical language fluently, and they routinely underestimate how foreign it is to most users.

What it costs

• Patients feel confused, intimidated, or excluded.
• They make errors on forms they don't understand. Features get avoided.
• This creates real downstream problems in care delivery.

What good looks like

• Write the way a good doctor actually talks to a patient.
• 'What brings you in today?' does the same job as 'Indicate your chief complaint.'
• Plain language isn't about dumbing things down — it's about removing unnecessary barriers.

Why it happens

• Products grow feature by feature, often with different teams or contractors.
• Without a shared design system, every new feature introduces its own patterns, spacing, and interaction logic.

What it costs

• Users don't consciously notice inconsistency, but they feel it.
• In health tech, inconsistent interfaces have been linked to medical device recalls and patient safety incidents.
• Inconsistency isn't just a trust issue — it's a safety issue.

What good looks like

• Invest in a shared component library early. It doesn't need to be elaborate.
• Even a small set of shared patterns for buttons, forms, and navigation creates consistency that compounds over time.

Why it happens

• Error states are the last thing teams design and the first thing cut when timelines get tight.
• Generic messages get shipped because they're easy to implement.

What it costs

• Usability problems are a documented contributing factor in a significant portion of medication errors.
• A vague error message isn't a minor inconvenience. It's a clinical risk.

What good looks like

• Every error in a health product should answer three questions: what happened, what it means for the user, and what they should do next.
• Offer a direct path to resolution whenever possible.

Why it happens

• The majority of patient portal access now happens on mobile, a share that has grown significantly in recent years.
• Most health apps weren't designed for this. They were built desktop-first and adapted down, which isn't the same thing.

What it costs

• Tap targets are too small. Navigation borrows desktop patterns. Swipe gestures are missing.
• The app fights the phone instead of working with it.
• Users notice immediately, even if they can't articulate why.

What good looks like

• Mobile is not a smaller screen. It's a different context.
• Design for thumb zones, platform conventions, and the reality that your user might be standing in a waiting room with one hand free.

Why it happens

• Most patients are concerned about their health data privacy.
• Far fewer actually know who has access to it.
• The gap between user expectation and what's actually happening is enormous, and most products do nothing to close it.

What it costs

• Most users care deeply about their health data, and they lose trust quickly when they can't find or understand privacy controls.
• In health tech, trust isn't optional. It's the entire foundation of retention.

What good looks like

• Make privacy controls visible, understandable, and easy to act on.
• Surface key controls during onboarding.
• If they're hard to find, users assume you're hiding something.