Case Study

Optimize, allocate, anticipate lab
technician's resources

a

Details

Client

MedSpeed (Chicago)

Year

2024 (ongoing)

Role

Design system, motion design, prototyping, user interviews, product strategy,product design

Brief

Revamp the lab dashboard to empower lab technicians with a comprehensive summary of incoming items, forecast future trends, and visualize key data insights

a

Legacy lab dashboard

How I identified the solution

User interviews were conducted to gain insights into the current use of the lab dashboard. Some clients reported dissatisfaction with the existing dashboard, indicating that it did not meet their needs or provide the necessary information for lab technicians. The feedback collected from these interviews was used to guide further improvements and enhancements to the dashboard

a

Providing upfront insights for resource allocation

Why route information was needed at the top?

Lab technicians can view routes and associated items, allowing them to easily identify the quantity of arrivals per route. This enables efficient resource allocation within the lab for subsequent delivery to hospitals or other designated locations

a

Comprehensive insights for every trip class category

Why detail about individual category was important for users

Real-time item tracking empowers lab technicians with instant visibility into item location and delivery status, streamlining workflow and enhancing efficiency

a

Design meets engineering

Using existing flutter package and some additional design implementations to expedite the design process

Understanding the business timeline, I decided with the engineering team to utilize an existing code based flutter package to deploy the dashboard in a dedicated timeline set by the stakeholders

a

MVP phase

Further enhancements

A Minimum Viable Product (MVP) will assess whether lab technicians are satisfied with the dashboard under conditions of high pressure or limited resources. This MVP phase will help determine its effectiveness and initiate discussions about expanding its availability to other clients who previously discontinued use of the dashboard.

a

Learnings

Fail early

Failing early is important to improve the next iteration. The feedback can be critical, and the designs might not be fulfilling the purpose. Align the designs with business goals and timeline to provide a good functional product.

Onboarding stakeholders

Getting everyone agree on new features is important and those conversation should be done early on in the process. I learned that additional features which were added in the initial stages we should present it with ROI