Apex Diagnostics · Enterprise Product / UX
Designing navigation for complex systems.
An enterprise portal for a universal molecular testing system, redesigned so lab teams could read system health, diagnostics, and consumable readiness at a glance, and act before problems escalated.
Duration ~12 to 18 months, iterative · Users: lab managers, technicians, field service, distributors · White-labeled customer portal
My roleI owned UX for the instrument-focused experiences, from research and information architecture through the shipped interface.
Turning system state into confidence.
Clinical labs rely on complex diagnostic instruments with strict uptime requirements, yet users lacked clear visibility into system health, diagnostics, and consumable readiness. I led the design of an instrument-centered experience that unified diagnostics, inventory, and service context, enabling labs to anticipate issues, reduce downtime, and act before problems escalated.
Instrument downtime is operational failure.
For clinical labs, an instrument that cannot run samples stops the work entirely. Users needed to answer time-critical questions quickly, but the answers were scattered and hard to interpret.
- Is my instrument healthy right now?
- Are there active issues I need to address?
- Do I have enough consumables to keep testing?
- What is running low or expiring soon?
- When should I reorder or escalate?
- Fragmented across tools and teams
- Buried in technical logs and service reports
- Reactive rather than preventative
- Hard to interpret for non-expert users
- Unplanned downtime
- Last-minute reorders
- Increased service calls
- Stress and uncertainty for lab staff
Constraints
- Highly regulated diagnostics environment
- Limited ability to expose raw diagnostic data
- Hardware-driven system states and dependencies
- Global variability in lab workflows
- Mixed audiences, both technical and non-technical users
- Regulatory requirements around data accuracy and traceability
Owning UX for instrument-focused experiences.
- Instrument overview and navigation
- Diagnostics visibility and status modeling
- Inventory and consumables tracking
- Service agreement and maintenance context
- Cross-functional collaboration with Engineering, Service, and Product
- Iterative validation through usability testing
The through line: turning complex system signals into actionable understanding.
What lab teams actually needed.
- Interviews with lab technicians and managers
- Shadowing service workflows
- Review of diagnostic logs and service reports
- Usability testing on instrument-health concepts
Users were rarely missing data. They were missing clear signals about severity, timing, and context, which made it hard to decide what needed action versus monitoring.
Key insights
Users don't want raw diagnostics. They want meaning.
Healthy vs. at risk matters more than exact metrics.
Inventory anxiety is driven by uncertainty, not absolute quantity.
Preventative cues beat reactive alerts.
Instrument context is the natural organizing model.
Clustering the real signals.
To move beyond surface-level usability issues, I synthesized qualitative interview data and contextual observations into patterns that explained why users hesitated, over-ordered, or escalated prematurely. The goal was not to catalog pain points, but to identify the signals users relied on, or lacked, when making time-sensitive decisions.
Tap a cluster to isolate its signals. Raw statements captured during moderated usability sessions, synthesized into five recurring decision signals.
Raw user statements captured during moderated usability sessions and interviews, clustered across lab managers, technicians, distributors, and global users. Confusion stemmed less from missing data and more from unclear severity, timing, and context.
From user signals to diagnostic design decisions.
To ensure the experience addressed real operational risk, not just system completeness, I mapped recurring user signals to the downstream behaviors they triggered and the design response each demanded. This framework decided which signals required clarity, guidance, or escalation, and which could remain informational.
| User signal | Behavioral risk | Design response | |
|---|---|---|---|
| 1 | I don't know if this alert is urgent or informational. | Delayed or incorrect action; users may ignore critical alerts or overreact to informational ones. | Severity indicators with plain-language labels ("Action Required", "Monitor", "Informational") and prioritization by operational impact. |
| 2 | Inventory feels reactive instead of predictive. | Over-ordering, wasted inventory, or mid-batch shortages from a lack of forward visibility. | Days-of-supply projections and usage-based forecasting instead of raw quantity counts. |
| 3 | I check each instrument individually because I can't get a clear overview. | Missed issues across multiple instruments and inefficient monitoring workflows. | Instrument-level dashboards with aggregated status views and contextual drill-down. |
| 4 | I'm not sure if I should call support or handle this myself. | Increased support load from unnecessary calls, or unresolved issues from user hesitation. | Contextual guidance and recommended next actions embedded in alerts, tailored by severity and role ("Contact Support", "Monitor", "No Action Needed"). |
| 5 | The logs are full of jargon I don't understand without calling service. | Dependency on support for routine diagnostics and delayed troubleshooting. | Human-readable diagnostic summaries, with technical logs available on demand. |
| 6 | I want to catch problems before they cause downtime. | Reactive incident response leading to unexpected shutdowns and operational disruption. | Preventative alerts and early-warning indicators that surface issues before they become critical. |
| 7 | By the time I notice we're low on reagents, it's usually urgent. | Emergency ordering, expedited shipping costs, or workflow interruptions. | Proactive inventory notifications triggered by usage patterns and lead-time thresholds. |
| 8 | I spend time investigating things that turn out to be non-issues. | Wasted time and alert fatigue, desensitizing users to real problems. | Reduced noise through intelligent filtering and a clear split between informational and actionable alerts. |
| 9 | I need to know what matters right now across all my instruments. | Cognitive overload leading to missed critical issues or delayed intervention. | Progressive disclosure and prioritization across dashboards, alerts, and inventory to surface the most operationally impactful signals first. |
Decision framework: common user signals mapped to behavioral risk and design response, to reduce downtime, alert fatigue, and unnecessary support escalation across instrument and inventory workflows.
Principles
Everything a user needs is framed by the specific instrument in front of them, not a system-wide list.
Technical states become clear, plain-language status that any user can read and trust.
Surface what is operationally important first, over exhaustive completeness.
Headline status up front, deeper technical detail on demand for those who need it.
Diagnostics, inventory, and service live in a single context instead of separate tools.
Navigation and clarity for a complex system.
Four interface decisions carried the strategy: land users in context, keep them oriented, make status legible, and turn inventory from a reactive chore into a proactive signal.
Simplified global navigation
The portal opens on an instrument-centered overview, so users land in context rather than on a generic dashboard. A single global bar, an account selector, and a focused left rail replaced a sprawl of disconnected tools, while the overview surfaces System OS version, open cases, service-agreement status, and service history at a glance.
ResultUsers could assess instrument health in seconds.
Universal Molecular Testing System
1040 Research Parkway, Suite 200
Arden Hills, MN 55112, USA
| Module | Status | Activity | Runs Left |
|---|---|---|---|
| M01 | Ready | Idle | 22 |
| M05 | Temp Warning | Idle | 8 |
| M06 | Fault Detected | Error | 0 |
Breadcrumbs and location awareness
Every view anchors the user with a persistent breadcrumb and the instrument's identity: serial number, location, and system configuration. In a portal where a lab may run many instruments across sites, always answering "where am I" and "which instrument is this" removed a constant source of hesitation.
ResultLocation and instrument context stay visible on every screen.
Universal Molecular Testing System
1040 Research Parkway, Suite 200
Arden Hills, MN 55112, USA
Contextual side navigation
A contextual left rail (My Instruments, My Assays, My Support) pairs with in-page tabs for Overview, Cases, Maintenance History, Diagnostics, and Inventory. Diagnostics render as clear module-level status, Ready, Running, Low Supplies, Temp Warning, and Fault Detected, with human-readable labels and expandable detail for deeper investigation.
ResultLabs could act appropriately without misinterpreting severity.
| Module | Status | Activity | Runs Left | Temp | |
|---|---|---|---|---|---|
| M01 | Ready | Idle | 22 | Stable | + |
| M02 | Running | Running Test | 12 | Stable | + |
| M03 | Ready | Idle | 25 | Stable | + |
| M04 | Low Supplies | Completed | 3 | Stable | + |
| M05 | Temp Warning | Idle | 8 | Slight | + |
| M06 | Fault Detected | Error | 0 (Blocked) | High | + |
| M07 | Cleaning | Cleaning Cycle | 10 | Stable | + |
| M08 | Ready | Idle | 19 | Stable | + |
Findability and proactive inventory
Inventory is expressed in runs remaining, not raw units, with good, low, and critical indicators, expiration awareness, and days-of-supply projection. A recommended reorder quantity is derived from usage trends, and reorder and service actions sit inline, one step from the signal that triggered them.
ResultLabs could plan proactively instead of reacting.
| Module | Status | Activity | Runs Left |
|---|---|---|---|
| M01 | Ready | Idle | 22 |
| M05 | Temp Warning | Idle | 8 |
| M06 | Fault Detected | Error | 0 |
Measured in downtime avoided, not speed.
Because this work focused on preventative visibility rather than workflow efficiency, results were measured in reduced downtime and avoided escalations rather than raw speed.
- Unplanned instrument downtime decreased by approximately 12 to 18% through earlier visibility into system health and consumable risk.
- Emergency reorders and rush shipments declined by approximately 14 to 22%, as users could anticipate inventory needs before hitting critical thresholds.
- Successful early identification of potential system issues increased by approximately 25 to 30%, driven by clearer prioritization of diagnostic signals.
- User confidence in understanding instrument health improved by approximately 18 to 22% in usability testing and follow-up surveys.
- Service calls triggered by uncertainty or misinterpretation of diagnostics decreased by approximately 10 to 15% following rollout.
- Proactive alerting and inventory forecasting cut unplanned intervention costs by roughly 12 to 18% as operators spent less time in reactive troubleshooting.
Representative, anonymized outcomes based on usability testing, platform usage trends, and internal service data.
Reliability is non-negotiable.
In clinical diagnostics, an instrument that cannot be trusted stops real testing. By translating complex diagnostic and inventory data into clear, preventative signals, this work helped labs maintain testing continuity, reduce stress, and operate more predictably, without exposing sensitive system internals or compromising regulatory requirements.
- Predictive failure indicators based on diagnostics trends
- Cross-instrument health dashboards
- Automated reorder suggestions tied to test volume
- Deeper integration with service scheduling
- Validating predictive indicators against real usage data to further reduce reactive workloads
Building something operationally complex?
Enterprise product and UX work that turns dense system state into clear, confident decisions.
Start a project →