JL
← All work

Lab Management System · Glidewell Dental · 2024

Related Cases: Return Entry Redesign

Inherited a shelved solution, a hard deadline, and a team expecting the impossible. Here’s what shipped.

Product DesignUX ResearchEnterprise
Role
Product Designer
Company
Glidewell Dental
Year
2024
Platform
Web

TL;DR

Problem

Return entry for a new lab system. The earlier solution was shelved and the deadline was close.

Role

Newest designer on the team. I observed data-entry users and rescoped to a shippable MVP.

Result

Launched at the sister lab as part of the LMS MVP, keeping the legacy case-linking pattern users already knew.

01 / Context & my role

I inherited a complex problem in motion.

The Lab Management System is an internal application built to replace two outdated legacy systems used to manage and track dental restoration cases across the lab. I was brought in to take over one of Glidewell’s largest ongoing initiatives.

The problem

The earlier return entry solution relied on customers initiating returns themselves, but with limited time and shifting priorities, that approach was no longer feasible.

Before my arrival, the UX team had explored improving the return entry workflow, specifically shifting return initiation from internal data-entry users to the customers themselves (dentists). They conducted research and built a robust solution. But with other priorities taking over, the feature was put on hold indefinitely.

When I joined, the deadline was approaching fast. The original scope was no longer feasible. My job was to revisit the shelved work, understand what was still valid, and redesign a scoped version that could actually ship.

02 / Goal

Scope it down. Ship it right.

Redesign the return process to support data-entry users in manually entering returns at case entry, maintaining a familiar workflow from the legacy system while adapting it for the new LMS platform.

03 / Research

I had the least context on the team. So I went and got it.

As the newest member, I had the least familiarity with both the business and the design work that came before me. Rather than guess, I took the initiative to fill that gap directly.

I reached out to stakeholders across departments and arranged a full lab walkthrough, observing how teams actually used the legacy systems, how they handled returns, and where the friction points were.

  • Walkthrough of the legacy system and current return handling process
  • Ethnographic study, observing data-entry users in their actual workflow
  • Review of the previous team’s research and shelved design solution

After gathering my notes, I analyzed the current process and pain points side by side with the previous team’s work, understanding what had already been solved well, what needed to be reconsidered, and what constraints I was actually designing within.

Legacy system walkthrough
One of the legacy systems: the starting point for understanding the existing workflow

04 / Key insight

The familiar path was the right path.

Linking cases wasn’t just a technical requirement, it was a familiar anchor. Replicating the legacy system’s case-linking pattern would help data-entry users transition to the new platform without losing the muscle memory they’d built over years.

A key component of creating returns is the ability to link related cases, a capability that had to be supported at case entry, just as it was in the legacy system. What started as a functional requirement became a hidden win: preserving a familiar interaction pattern gave users something recognizable in an otherwise new environment.

05 / Explorations

Three structures. One familiar answer.

I explored three approaches for surfacing related cases within the case entry flow, each balancing visibility, familiarity, and the complexity of the information being presented.

Exploration 01

Banner notification

A color-coded banner alerts users when related cases are found, with a modal to view details. Familiar and space-efficient, but easy to miss, and the extra click to surface details adds friction.

Exploration 02

Side panel selection

All related cases displayed persistently in a side panel, with no extra click required. More visible, but potentially overwhelming with a high volume of related cases and limited by side panel functionality.

Exploration 03 Chosen

Side panel + modal hybrid

Related cases shown in the side panel for easy scanning, with a modal for focused detail review when needed. Most similar to the legacy system workflow: familiar and scalable.

Exploration 3 won because it matched how users already worked. In a new system full of unfamiliar patterns, giving users one familiar anchor reduced cognitive load and eased the transition.

06 / Final design

What shipped, and why each decision mattered.

Related cases side panel

01

Related cases side panel

Related cases surface automatically based on account number and provider number, with filtering by product. Users can scan the full list without leaving the case entry flow, with no additional clicks required to see what’s there.

Detail modal for verification

02

Detail modal for verification

Selecting a case opens a focused modal for reviewing the specific information needed to confirm the correct case. Users can select one or more products as needed, built to scale with planned enhancements without requiring a structural overhaul.

Pre-populated case details

03

Pre-populated case details

Once a case is linked, relevant information from the original case carries over automatically, reducing manual input and the risk of data-entry errors. A RMA prefix is applied to the case number to track return cases and maintain a clear link to the original.

04

Color-coded return type banners

Different return types are distinguished by clearly color-coded banners, making it easy for data-entry users to identify and switch between return types without confusion. Each type is visually distinct and immediately recognizable.

07 / Outcome & reflection

A scoped solution that held its ground.

The redesigned return entry workflow launched at the sister lab as part of the LMS MVP and stayed in use through the end of my time on the team, giving data-entry users a familiar, functional process in a new system. The case-linking pattern from the legacy system carried over intact, the side panel reduced friction for high-volume users, and the RMA prefix laid the groundwork for future customer-initiated returns.

The design didn’t solve everything the original concept set out to. But it solved what it needed to, for the users who needed it most, within the constraints that existed.

What I’d do differently: I’d advocate earlier for even lightweight usability testing with actual data-entry users before finalizing the side panel layout. We relied heavily on legacy system comparisons and internal review. Real user observation would have surfaced edge cases faster.

08 / Challenges

Challenges I faced.

01

Taking on a complex problem with little business knowledge

As the newest member of the team, I had limited understanding of the business and almost no familiarity with the design work done before my arrival. Getting up to speed quickly wasn’t optional, because the deadline was already close.

What I did: I connected with stakeholders directly to gain business context, and collaborated with fellow designers to review previous documentation and design decisions. The time investment gave me the foundation I needed to make informed decisions rather than assumptions.

02

Designing for MVP with significant constraints

Replacing a robust legacy system with an MVP is never straightforward, especially when the business workflow is complex and edge cases are everywhere. The scope had already been cut once, and I was designing within what remained.

What I did: I kept the first release in perspective: it’s a starting point, not a final answer. I communicated regularly with engineers to align on what was technically feasible, making deliberate compromises that didn’t close the door on future improvements.

Next case studyMultiple Queues: One Dashboard, Every Lead

No direct user access. No clear requirements. Just a hard deadline and a client who needed something that didn’t exist yet.

Read the case study →