Skip to main content
Healthcare product thinkingPerspective

Healthcare software should reduce cognitive load, not add to it

Designing for people who are interrupted, time-pressured, and accountable for the outcome.

Published
Reading time
7 minutes
Author
Inorbit Solutions — author to be assigned
Review status
Pending subject-matter review

Most healthcare software is used by someone who is partway through something else. A clinician between patients. A coordinator holding a phone line. An administrator reconciling a schedule while someone waits at a desk.

That single fact should shape more design decisions than it usually does. Software designed for undivided attention behaves badly under interruption, and interruption is the normal operating condition.

Design for resumption

The question is not only "can someone complete this task?" but "can they come back to it after four minutes away and know exactly where they were?" That implies saving state aggressively, showing progress explicitly, keeping context visible rather than in the user’s head, and never silently discarding partial work.

Reduce decisions, not just clicks

Click counting is a poor proxy for effort. Three obvious clicks are easier than one that requires choosing between eleven similar options. The expensive part of a workflow is usually deciding, not acting — so the useful reductions are in ambiguity, not in steps.

  • Default to the most common safe option, and make it visible that a default was applied
  • Order lists by likelihood in context rather than alphabetically
  • Hide what is genuinely irrelevant to this role, in this moment
  • Keep the information needed for a decision on the same screen as the decision

Make the safe action the easy action

When the careful path is slower than the shortcut, people take the shortcut — not through negligence, but because the workload is real. If a correct action requires navigating away to check something, that check will sometimes be skipped. Bringing the necessary context to the point of decision does more for safety than a warning dialog.

Warnings that fire too often stop being read. Alert fatigue is a well-documented failure mode, and every low-value alert reduces the effectiveness of the important ones.

Respect what the user already knows

Clinical and administrative staff are experts in their domain. Software that explains their job to them, or forces them through a wizard for something they do fifty times a day, is experienced as friction. Provide a fast path for expert users and a guided path for occasional ones, and let people move between them.

Error states are part of care delivery

An error message that says an action failed, without saying what to do instead, moves the problem to whoever is standing in front of the user. State what happened, whether anything was saved, what to try next, and how to reach help. When a dependency is unavailable, say which capability is affected and what the alternative is.

Density is not the enemy

Consumer design instincts often push toward generous whitespace and progressive disclosure. In clinical and operational tools that can be actively harmful, because hiding information behind interactions increases the work of building a mental picture. The goal is organised density: a lot of information, structured so the eye can find what matters without hunting.

Have a version of this problem?

Tell us what you are building or trying to change. We will help you find the clearest next step — starting with a conversation, not a proposal.