Diagnostic Dashboard Redesign.
Transforming data into insight: from chaotic feature creep to refined clinical intelligence
C360 was a diagnostic dashboard suffering from "Swiss Army Knife syndrome" (trying to serve every need for every user). How might we cut through the noise to surface what clinicians actually needed in critical moments?
Role: Lead UX/UI Designer
Company: Danaher (Cepheid))
Product Phase: New Software Release
Responsibilities: Led end-to-end UX/UI design from research through high-fidelity prototypes and developer implementation.
Challenge
Product overloaded with features and fragmented data.
Insight
Data visualization isn't about showing everything. It's about lifting what matters most to the surface at the right moment.
Outcome
A redesigned dashboard that rose to meet clinical needs, prioritizing critical information and adapting to workflows to improve patient care.
A classic "Swiss army knife" challenge
C360 was a tool that fell fate to the common Swiss army knife pitfall: feature overload. What started as a simple epidemiology tool then became a hub for disease reporting, patient health management, device health, and customer support.
Each feature made sense in isolation. But together? Chaos. Trying to serve all these needs equally was taking a toll: users failed to grasp what the product was about and product adoption was critically low.
Context is everything
We set out to uncover what value we could surface for our users, working to advance on the product roadmap while paving the way to increased utility and adoption.
This helped us to focus efforts on features with the highest utility or competitive edge, and to de-prioritize work on legacy features.
Leveraging a network of subject matter experts, we identified a unique value proposition in focusing on the unique relationship between patient test results and device maintenance, impacting data reliability.
We then worked with end users to identify specific metrics that could support actionable insights.
The turning point: strategic, workflow-first architecture
As we spoke with clinicians, they didn't ask for "better dashboards." They asked: "Can you help me find what I need faster?" The answer wasn't more features. It was smarter architecture.
We mapped actual clinical workflows, not feature lists. This revealed the hidden key: the integrity of all test results came down to device health, so this was critical to surface front-and-center.
We framed up a range of scenarios and worked with stakeholders across executive, development, customer success, and clinical teams to define our best approach.
Before: home dashboard
Overwhelming displays of mixed data and unconventional interaction and UI patterns subjected users to undue cognitive burden (intentionally obscured to protect data).
After: test results view
We didn't just redesign screens. We redesigned the hierarchy of urgency. Users now have high-level overview where the most actionable and insightful data points are prioritized.
After: device view
Site data tables and filtering tools were cleaned up, standardized, and templatized for the development team. Certain views, like Instruments, leveraged in-table icons to layer additional information into a snapshot view.
Bonus: development expediency
Throughout the design process, I kept in close communication with our developer stakeholders and their needs, as well. With limited resources for this launch, we worked together in sprints to deliver each key workflow. In addition, we created a set of page templates to go with out updated design system so that they could get started on streamlined architecture while we finalized design details.
A total transformation
Through strategic architecture and workflow-first thinking, we transformed a cluttered "Swiss Army knife" into a precision instrument that adapts to clinical needs rather than demanding clinicians adapt to it.