Making Lab-test packages easier to choose
Turning scattered health signals into a story people can understand, act on, and keep improving.
Users aren't struggling to find a lab test. They're struggling to know which package is right for them. I moved package discovery from catalogue-first to need-first: a user starts with a health concern, sees only relevant packages, and compares them on what the extra parameters actually add not on how many tests are in the box
The problem wasn't finding a test. It was knowing what to choose.
Knows the concern, not the parameters
Knows exactly what they need
When users don't know which parameters matter, a long list of packages doesn't help them decide. It makes the decision harder
Multiple packages can appear relevant, but the differences between them aren't immediately obvious.
Users may recognize a health concern but not know which parameters are relevant to it.
Users compare packages to see what’s included, what’s missing, and whether upgrading is worth it.
The interface gave users options, but not enough context to make the choice feel easy.
I started by looking at how people are asked to choose today.
Already offers package categories such as women's health, lifestyle checkups and health concerns, alongside individual tests and full-body packages. It also provides a package comparison view.
Similarly offers a broad range of packages organized around preventive health and specific concerns such as diabetes, thyroid, PCOD, fertility and women's health
Both platforms make a large catalogue discoverable.
The opportunity I saw was to make that catalogue easier to navigate when the user starts with a health concern rather than a test name.
What if users could start with what they know?
I shifted package discovery from catalogue-first to need-first.
Choose a health concern and we’ll show you relevant packages
From “Which one?” to “Here's the difference.”
Once the user selects PCOD, packages aren't just listed. They're shown in a way that supports a decision.
From finding a test to finding what fits.
The redesign changed the role of the landing page.
Users can start with a concern rather than a test name.
Package differences become visible instead of requiring mental comparison.
Users can move from a symptom or concern to relevant testing options
