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.

Role
Senior UX Designer
Client
Apex Diagnostics (anonymized)
Scope
Enterprise diagnostics portal
Type
Product / UX case study

Duration ~12 to 18 months, iterative · Users: lab managers, technicians, field service, distributors · White-labeled customer portal

The result

Lab teams can now find any instrument, order, or status in a couple of clicks, so uncertainty stops turning into support calls.

My roleI owned UX for the instrument-focused experiences, from research and information architecture through the shipped interface.

01 · Executive summary

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.

02 · The problem

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.

Questions users had to answer
  • 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?
Instead, information was
  • Fragmented across tools and teams
  • Buried in technical logs and service reports
  • Reactive rather than preventative
  • Hard to interpret for non-expert users
Which resulted in
  • 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
The challenge was to surface meaningful insight without overwhelming or misrepresenting system state.
03 · My role

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.

04 · Research and insights

What lab teams actually needed.

Research methods
  • Interviews with lab technicians and managers
  • Shadowing service workflows
  • Review of diagnostic logs and service reports
  • Usability testing on instrument-health concepts
The core tension

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

01

Users don't want raw diagnostics. They want meaning.

02

Healthy vs. at risk matters more than exact metrics.

03

Inventory anxiety is driven by uncertainty, not absolute quantity.

04

Preventative cues beat reactive alerts.

05

Instrument context is the natural organizing model.

05 · From user signals to design direction

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.

Severity unclear
I see this error code but I don't know if the instrument is down or just warning me.
When I look at the dashboard I can't tell what needs my attention right now.
I don't know if this diagnostic message is urgent or informational.
I need to know: can this instrument run samples right now or not?
Context missing
I check each instrument individually because I can't get a clear status overview.
I need context about what this alert means for my specific instrument.
The logs are full of jargon I don't understand without calling service.
I'm managing six instruments and I can't track all the details.
Alert clarity
The system tells me quantities but not whether that is enough for my workload.
There's too much technical information and I don't know what's critical.
I spend time investigating things that turn out to be non-issues.
Inventory anxiety
By the time I notice we're low on reagents, it's usually urgent.
I wish I knew how many days of supply I actually have left.
I don't want to over-order, but I'm terrified of running out mid-batch.
Reactive workflow
I'm never sure if I should call support or handle it myself.
Inventory tracking feels reactive instead of predictive.
I want to catch problems before they cause downtime.
We've had surprise shutdowns because we missed early warning signs.
I see this error code but I don't know if it means the instrument is down or just a warning.
When I look at the dashboard I can't tell what needs my attention right now.
I'm never sure if I should call support or if I can handle it myself.
By the time I notice we're low on reagents, it's usually urgent.
I check each instrument individually because I can't get a clear status overview.
I need context about what this alert means for my specific instrument.
I wish I knew how many days of supply I actually have left.
The system tells me quantities but not if that's enough for my workload.
I don't want to over-order but I'm terrified of running out mid-batch.
There's too much technical information and I don't know what's critical.
I don't know if this diagnostic message is urgent or informational.
Inventory tracking feels reactive instead of predictive.
I need to know: can this instrument run samples right now or not?
I spend time investigating things that turn out to be non-issues.
I want to catch problems before they cause downtime.
The logs are full of jargon I don't understand without calling service.
We've had surprise shutdowns because we missed early warning signs.
I'm managing 6 instruments and I can't track all the details.

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.

06 · Decision framework

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 signalBehavioral riskDesign response
1I 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.
2Inventory 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.
3I 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.
4I'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").
5The 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.
6I 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.
7By 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.
8I 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.
9I 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.

07 · Design strategy
Rather than exposing diagnostics as data, I designed them as signals.

Principles

01
Organize around the instrument

Everything a user needs is framed by the specific instrument in front of them, not a system-wide list.

02
Translate states into status

Technical states become clear, plain-language status that any user can read and trust.

03
Prioritize risk and urgency

Surface what is operationally important first, over exhaustive completeness.

04
Progressive disclosure

Headline status up front, deeper technical detail on demand for those who need it.

05
One connected system

Diagnostics, inventory, and service live in a single context instead of separate tools.

08 · Key solutions

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.

01

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.

portal.apexdiagnostics.com / overview
Account Selector
South Caroline Medical Center
Home/Overview

Universal Molecular Testing System

Serial Number
A12-94751
Location
Central Diagnostic Laboratory
1040 Research Parkway, Suite 200
Arden Hills, MN 55112, USA
System details
16-module configuration with automated sample-to-result workflow supporting a broad menu of molecular assays.
Overview
Cases (2)
Maintenance History
Diagnostics
Inventory
Software version
System OS 6.5
Current version: 6.5.0
Open support cases
0
No action needed
Service agreement
Active
Valid through 06-Jun-2028
Service History
3
View reports
Module 05 temperature drift
Opened 12-Nov, awaiting field service review
MonitorView
Module 06 fault detected
Opened 12-Nov, blocking runs on affected module
Action RequiredView
Preventative maintenance
06-Jun-2025, all modules passed
CompleteReport
Software update to OS 6.5
18-Mar-2025
CompleteReport
Optics calibration
02-Jan-2025
CompleteReport
ModuleStatusActivityRuns Left
M01ReadyIdle22
M05Temp WarningIdle8
M06Fault DetectedError0
Apex Multiplex Test 24-Pack
Good256 runsReorder
Respiratory Viral Panel 24-Pack
Low48 runsReorder
Quality Control Kit
Critical40 runsReplace
Quick Access...
All open support cases
Browse a complete catalog of available assays and related products.
Access product support and documentation
Find instructions, safety data, and reference materials for assays and consumables.
Technical Support
Troubleshooting instruments, software, and test performance issues. Speak with a diagnostics specialist.
02

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.

portal.apexdiagnostics.com / overview / universal-molecular-testing-system
Account Selector
South Caroline Medical Center
Home/Overview/Universal Molecular Testing System

Universal Molecular Testing System

Serial Number
A12-94751
Location
Central Diagnostic Laboratory
1040 Research Parkway, Suite 200
Arden Hills, MN 55112, USA
System details
16-module configuration with automated sample-to-result workflow supporting a broad menu of molecular assays.
Overview
Cases (2)
Maintenance History
Diagnostics
Inventory
Software version
System OS 6.5
Current version: 6.5.0
Open support cases
0
No action needed
Service agreement
Active
Valid through 06-Jun-2028
Service History
3
View reports
03

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.

portal.apexdiagnostics.com / instrument / A12-94751 / diagnostics
Account Selector
South Caroline Medical Center
Overview
Cases (2)
Maintenance History
Diagnostics
Inventory
Software version
System OS 6.5
Current version: 6.5.0
Open support cases
0
No action needed
Service agreement
Active
Valid through 06-Jun-2028
Service History
3
View reports
Module 05 temperature drift
Opened 12-Nov, awaiting field service review
MonitorView
Module 06 fault detected
Opened 12-Nov, blocking runs on affected module
Action RequiredView
Preventative maintenance
06-Jun-2025, all modules passed
CompleteReport
Software update to OS 6.5
18-Mar-2025
CompleteReport
Optics calibration
02-Jan-2025
CompleteReport
DiagnosticsExpand all details Download full diagnosticsFilters
ModuleStatusActivityRuns LeftTemp
M01ReadyIdle22 Stable+
M02RunningRunning Test12 Stable+
M03ReadyIdle25 Stable+
M04Low SuppliesCompleted3 Stable+
M05Temp WarningIdle8 Slight+
M06Fault DetectedError0 (Blocked) High+
M07CleaningCleaning Cycle10 Stable+
M08ReadyIdle19 Stable+
1-8 of 16
Apex Multiplex Test 24-Pack
Good256 runsReorder
Respiratory Viral Panel 24-Pack
Low48 runsReorder
Quality Control Kit
Critical40 runsReplace
Quick Access...
All open support cases
Browse a complete catalog of available assays and related products.
Access product support and documentation
Find instructions, safety data, and reference materials for assays and consumables.
Technical Support
Troubleshooting instruments, software, and test performance issues. Speak with a diagnostics specialist.
04

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.

portal.apexdiagnostics.com / instrument / A12-94751 / inventory
Account Selector
South Caroline Medical Center
Overview
Cases (2)
Maintenance History
Diagnostics
Inventory
ModuleStatusActivityRuns Left
M01ReadyIdle22
M05Temp WarningIdle8
M06Fault DetectedError0
InventoryExpand all details Filters
Inventory status for this instrument only. See global inventory
Apex Multiplex Test 24-Pack
Good256 runs, reorders Jan 4Reorder
Respiratory Viral Panel 24-Pack
Low48 runs, depletes Dec 14
Lot #:RVP-2051-88-04Storage:2-8°CCurrent Locations:Modules 03, 04, 07Daily Usage:about 4 runs/day (last 2 weeks)Projected depletion:Dec 14, 2025Distributor:Cardinal / In-network
0%Supply Remaining
Respiratory Viral Panel 24-Pack
RVP-24 In Stock
Unit Price$622.00
Total (USD)$2,488.00
Recommended Reorder:12 unitsBased on usage trends
12
Quality Control Kit
Critical40 runsReplace
Extraction Reagents
Good120 runs, reorders Mar 2026Auto Pay
PCR Master Mix 50 mL
Low150 reactionsReplace
Quick Access...
All open support cases
Browse a complete catalog of available assays and related products.
Access product support and documentation
Find instructions, safety data, and reference materials for assays and consumables.
Technical Support
Troubleshooting instruments, software, and test performance issues. Speak with a diagnostics specialist.
09 · Outcomes

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.

10 · Why this mattered

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.

Complex technical data, translated into trustworthy, actionable signals that let people act with confidence in critical environments.
11 · What I would do next
  • 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 →
← Back to selected work