Improving operational efficiency of a lab Information Management System

Context

A LIMS is the operational backbone of a diagnostic lab. It manages every step from the moment a patient walks in to the moment a report leaves the system: registration, sample tracking, test assignment, result entry, validation, report generation, and audit trail.

The people inside it are not casual users. They are operators. A single lab technician can run hundreds of samples through multiple tests in a day, which makes any small interaction cost compound into hours of wasted time per week. That same density also makes mistakes expensive: a mislabeled record or wrong field entry can cascade into incorrect reports, compliance issues, and rework.

IQLine serves four distinct roles, all working in the same product on the same shift:

• Front desk / receptionist registering walk-in patients, often under queue pressure.

• Lab technician entering test results, scanning barcodes, and updating sample status, frequently with one hand on a keyboard and one on a sample tray.

• Pathologist / lab manager validating results, reviewing reports, and approving releases.

• Admin monitoring throughput, looking at status across labs, and resolving exceptions.

The product was technically capable. It captured the data, generated the reports, kept the audit trail. But the interface was holding back every one of these roles in a different way.

The Problem

IQLine was carrying years of UX debt. The product had grown organically: features added, screens stacked, forms extended. The result was a system that worked, but punished the people who used it most.

The business impact

• Slower throughput per technician. Each redundant click compounds across thousands of records per month.

• Higher training burden. New hires took longer to reach proficiency because the interface had no learnable structure.

• Data entry errors. Visual density and weak field affordances led to wrong-field entries that propagated into reports.

• Support tickets as UX. A meaningful share of support traffic was navigation questions, not real bugs.

• Sales friction. Demos to new lab buyers were carried by the salesperson explaining what the product could do, not by the interface showing it.

The Process

1. Setting Goals

We set four goals up front, framed against the HEART model so success was measurable and not subjective:

• Task success - Reduce clicks and keystrokes for the four most-frequent actions: patient registration, opening today's reports, entering test results, and dashboard exception triage.

• Adoption - Make the system learnable in a single shift for a new front desk hire, instead of requiring a multi-day shadow period.

Happiness - Modernize the visual language so the interface signals the same level of seriousness as the lab itself.

2. Context Mapping

We mapped the four highest-frequency flows step by step:

• Register a new walk-in patient

• Open today's report list, filter to a single lab and date range, export

• Enter results for a sample and validate

• Triage the admin dashboard (find the exceptions, act on them)

Each flow was annotated with the keystroke or click count, the number of mode switches between keyboard and mouse, and the number of decision points where the user had to recall rather than recognize.

3. Ux Audit

We ran a heuristic evaluation against Nielsen's ten heuristics, layered with two additional lenses specific to operational software: cognitive load and keyboard accessibility. The audit was structured per-screen with each issue tagged by severity (cosmetic, minor, major, blocker) and by user impact (every session, frequent, occasional).

Sample Report

4. User Research (Insights and Opportunities)

We separated what we learned (insights) from what we should do about it (opportunities). This matters because insights without opportunities is a report; opportunities without insights is a guess.

The Redesign

1. Patient Registration

2. Admin Dashboard

3. Test Registration

The Outcomes

We frame outcomes honestly. Where we have specific behavioral changes, we describe them. Where we have qualitative shifts, we describe those too.

• Reduction in interaction cost on the highest-frequency flow - The new patient registration flow can be completed entirely from the keyboard, with no mouse pickups, for a returning user. Compared to the legacy flow that required an average of multiple mouse handoffs per registration, this is a meaningful saving on a per-record basis that compounds across a shift.

• Faster time-to-first-data on the reports screen - Users see real data on first paint, not an empty form. The most common reports load with one keystroke (the saved view shortcut) instead of four to six configuration steps.

• Triage-oriented admin dashboard - Admins land on what needs attention, not on totals. The dashboard is now the starting point of an admin shift, not a status check.

• Reduced learnability burden - Task-named navigation, grouped form sections, and consistent keyboard behavior mean new staff can learn the product from the navigation labels and visual structure, not from a printed shortcut sheet.

• Modern visual signal - The interface now reads as a current-generation product. This matters in two places: in sales demos with prospective lab clients, and in retention conversations with existing labs whose own teams compare IQLine to consumer software they use outside work.