Case study
Neo Report
Diagnostic reports
people actually read
- Role
- Design lead · acting PM
- Team
- Head of Product · Engineering · QA · Lab team · Doctors
- Scope
- 0→1, problem framing to release
01
The problem
Every result came as a print-formatted PDF: clinically complete, but written for pathologists, not for the person whose blood it describes. On a phone it meant pinching, zooming and hunting through dozens of pages.
02
The insight
People don't read lab reports, they scan them. The first question is never about a specific enzyme. It's simply “is anything wrong?”, and the PDF made that one question the hardest to answer.
03
The answer
Neo Report answers it first: what needs attention, surfaced immediately, with depth: ranges, trends, explanations, one tap below. It took two versions to learn what that meant. V1's survey scores were glowing, but the recordings disagreed: people skipped the summary page, ignored the trend graphs, and happily scrolled the full report instead. So V2 became one scrollable screen: filters to narrow, a drawer for depth.
search and the range filters narrow it; every parameter carries its last value, its normal band and a trend.
depth on tap. every band explained, and the one you fall in marked relevant for you.
04
The rules
- P.01Trust before delight: a medical document should reduce anxiety, not perform.
- P.02TL;DR first, depth on demand: nobody reads 40 pages to learn that everything is fine.
- P.03No compromise on accuracy: simplify the presentation, never the medicine.
05
The outcome
“I don't have to google my out-of-range parameters anymore.”
user, in-app feedback
Users started leaving the PDF behind, and Neo Report became the foundation for trends, explanations and long-term health context.