We like to believe that better decisions come from having more data.

In healthcare, that belief breaks.

Doctors don’t struggle because data is missing.
They struggle because data is unusable when it matters most.

During a consultation, a physician has minutes to:

• understand the patient’s situation
• identify what changed
• make a decision

But instead, they often:

• reconstruct patient history
• rely on fragmented information
• fill gaps with assumptions

This is not a data problem.

It’s a system design problem.

The illusion of “more data”

Most systems are built to collect.

More forms.
More fields.
More inputs.

But collection without structure creates noise.

Patients:

• forget
• simplify
• misinterpret

Doctors:

• search
• interpret
• guess

And the system does nothing to bridge that gap.

The real problem

Healthcare systems assume that:

• patients provide structured information
• data is complete
• context is obvious

None of that is true.

So decisions are made in uncertainty — not because doctors lack skill, but because the system fails to support them.

What needed to change

Instead of designing better interfaces, I focused on something else:

how information flows through the system

From:

• raw patient input

To:

• structured, evolving context

To:

• decision-ready data at the moment of care

A different approach

The key shift was simple:

Patients provide input.
The system creates structure.
Doctors make decisions.

This required:

• guiding patients instead of questioning them
• detecting missing data instead of ignoring it
• maintaining continuity instead of resetting context every visit

Why this matters

Because in high-stakes environments:

decisions are only as good as the context behind them

And context is not something users should assemble manually.

Final thought

We often design for usability.

But in systems like healthcare, that’s not enough.

We need to design for:

• clarity
• decision-making
• reduced risk

Full case study: [LINK]