Molecular You QA Dashboard

Molecular You QA Dashboard - Health-tech QA dashboard for clinical data review

Role UX Designer
Timeline Jan – Apr 2022
UX DesignHealth-TechDashboard

Molecular You is a health-tech company that provides personalized health insights through biomarker testing. I redesigned their internal QA dashboard used by clinical teams to review and validate test results. The project focused on improving data-dense interfaces, streamlining review workflows, and reducing error rates in the quality assurance process.

Impact

·Jan – Apr 2022

50% reduction in QA turnaround time

validated through usability testing with clinical reviewers

Goal

Reduce turnaround time for customer health reports by redesigning the quality assurance reviewer's decision-making tool.

Deliverables

  • Service blueprint
  • User flow documentation
  • High-fidelity prototype
  • Component library
  • Developer handoff instructions

Team

  • Product Manager
  • Director of Clinical Informatics
  • UX Designer (me)
  • Bioinformatician (QA)
  • 3 Developers

Project Details

Company
Molecular You
Duration
4 months (part-time)
Methods
Staff interviews, co-design workshops, usability testing, technical audits

Research & Scoping

The primary challenge was reducing the turnaround time for generating individual health reports. Multiple factors influenced delays - both internal and external. Our cross-functional team of scientists, product, and design professionals needed to comprehensively identify these factors, then determine which areas would yield the greatest improvement.

Over the first two weeks, I interviewed eight staff members across three teams spanning the full operational pipeline - from blood sample collection to health report delivery. Through screen-sharing sessions and detailed workflow walkthroughs, I mapped each team's daily tasks, touchpoints, and blockers.

Service blueprint mapping the full QA pipeline
Service blueprint documenting the end-to-end pipeline with delay causes and security concerns at each step

Understanding the Existing Workflow

QA reviewers checked algorithmically generated health reports before pushing them to production. They processed every report individually to flag potential mistakes, then published verified reports sequentially. The existing tool had several usability issues: manual error identification, unnecessary information adding cognitive load, excessive tab-switching for comparison, and extra steps to approve each report.

The original QA dashboard design before redesign
The existing QA tool - functional but slow and cognitively demanding

Co-Design & Ideation

Rather than jumping to wireframes, I facilitated co-design sessions with QA reviewers. Participants discussed their preferred tools for reviewing and processing tasks, then sketched their ideal QA tool. This surfaced crucial insights that verbal interviews alone couldn't achieve - subtle preferences around information hierarchy and comparison patterns that directly shaped the final design.

Design Goals

  • QA reviewers should only review flagged or suspicious reports
  • Health data comparison should be efficient and side-by-side
  • Approved reports should be easily accessible as reference
  • All report records should be accessible to QA and other teams
  • Reusable component library for future internal tools

Iterating Toward the Solution

The prototype went through three major iterations, each informed by usability testing with QA reviewers. The first version validated core concepts like task-oriented tabs and table views. The second introduced columnized comparison views and internal communication features. The third refined the decision-making pattern and maximized usable screen space.

Animated walkthrough of the first dashboard prototype
V1 prototype - testing task-oriented tabs, expandable table rows, and QA status tags
Final dashboard design with columnized comparison view
V3 - the approved design with button-based decisions, a finalization flow, and maximized review space

Developer Handoff

After stakeholder approval and a company-wide presentation, I prepared a comprehensive handoff package including a component library, interaction specifications, and user flow documentation for the development team.

Component library and developer handoff documentation
Component library with reusable UI elements for the development team

Focusing on what's important and distinguishing between what's possible versus what's preferred helped maintain clarity when numerous complex problems arose.

- Key takeaway