Case Study / 01 — Systems & Research

Device Return
Journey

Six return programs, seven backend systems, one agent trying to answer a customer's question. I owned UX for device returns across call-center desktop and in-store tablet, and initiated the research that proved a reframe was the right call.

RoleUX Designer
CompanyTelecommunications
Timeline2024
TeamProduct · Business · Retail · User Research
CASE 01

The Problem

Frontline experts had no single, return-type aware view of a wireless return. The interface that existed answered a different question than the one customers were asking.

6Return programs, each with its own rules
7Backend systems behind one answer
4Places an expert might search for one return
2Platforms: call-center desktop, in-store tablet

Every return type looked identical in the interface, with raw backend values like cash-carry and DF/INBOUND left to interpret mid-call. This case study focuses on Device Protection and Warranty, the highest-friction returns.

The fragmented starting point: no single view was aware of the others, so an expert reconstructed return status by hand, one tab at a time.

The question underneath the problem

Every symptom traced back to one missing answer. I reframed the redesign around three questions, answered in order:

01

Does the customer still owe a device?

02

What evidence explains the current status?

03

What should the expert do next?

My Role & Approach

I owned the return experience for Device Protection and Warranty end to end, with day-to-day autonomy and light design-lead oversight.

An in-store handoff and a mailed exchange look identical to a customer but carry different obligations, so I wasn't willing to guess. I brought in the research team myself and scoped the study with researcher Angie DeFord.

UX — MeOwner; initiated the research
ResearchAngie DeFord
Content DesignLaura Landgren
Product & Business
Retail
Customer Connect Platform
OrderGraph Backend

Research I Initiated

Device Protection & Warranty Order Research — with UX Researcher Angie DeFord

9Frontline experts
4Teams: Mobility Loyalty, Sales & Service, CX Labs, Support Desk
3Scenarios: initial claim, first and second revision
2Proposed tabs tested: Order and Returns

What we heard, and what changed

SignalWhat experts didDesign response
Clear labelsSpotted an open insurance claim quickly once "Insurance" and "Device Protection" were visibleKept program labels up front
RevisionsPast the first revision, could tell something changed but not why; fell back to call notesGrouped related order revisions
DensityCalled the return screen "overwhelming": density without hierarchySectioned by scenario, not data source
Unowned fieldsNobody could explain "Refund Amount"; "Claim ID" was an Asurion-side identifierCut "Refund Amount" entirely
Load-bearing fieldsNamed RMA number one of the most useful fields, especially for lost equipmentRMA shown only on returns that have one

"You have to section this stuff — you can't just have it as a list."

Research Participant, Device Protection Study
The three scenarios tested with frontline experts: an initial insurance claim, a first revision, and a second revision — each pressure-testing the proposed Order and Returns tabs against a real claim history.

The Design Decision That Mattered Most

Organize the interface around customer responsibility, not backend structure.

A store might accept a device and ship it to a warehouse later. The customer's obligation ended at handoff, so tracking detail after that point can't imply otherwise.

The tradeoff I had to resolve

Device Protection and Warranty close the moment a carrier scans pickup, but a generic tracker still implied "Received" was required.

Simplify

Remove the shipment timeline for these journeys; it shows a milestone that isn't required.

Preserve

Keep full shipment history; Drop Off and Returned events are what an expert needs in a dispute.

Resolution

Both. A primary status uses each journey's real completion logic, and shipment evidence stays underneath for disputes.

Where I chose to hold the line

I pushed to pause raw Order Type/Action values like Modify.change… in Order History. I'd rather ship less and have every field mean something than ship more and make experts guess.

The split that resolved the tradeoff: a primary status communicating whether the customer's obligation is complete, with internal logistics events labeled as internal and never implying an active customer obligation.

The Solution

Translate the backend into plain language

With content designer Laura Landgren, I turned raw fulfillment values into two labels experts could act on.

In-Store Return

  • BRE type, receipt & transaction ID
  • Device IMEI, serial, SKU, make/model
  • Store location, return date & reason
  • Refund amount & restocking fee
  • No RMA shown — the handoff is already complete

Mail-In Return

  • RMA number, status, creation date
  • Return-by date & non-return fee
  • CTN and shipment tracking
  • Original order & payment detail
  • Full RMA lifecycle, since the device is still in transit

Fix the navigation, not just the page

Added return/exchange visibility directly to the Equipment tab — the most-cited pain point in the study. Related order revisions were grouped so experts didn't reconstruct them manually.

The shipped Warranty return view: plain-language status stepper in place of raw backend state, and a reprint-label action with a sample preview so an expert can confirm the label before it's regenerated.

The accountability/logistics split generalized without a second version of the model:

Device Protection Warranty Trade In Same Day Delivery

Make validation part of the process, not an afterthought

I proposed frontline validation as a formal checkpoint, so changes are caught while they're still cheap:

Design
→
Frontline Checkpoint
→
Iteration
→
Feasibility Review
→
Development

Grounded in Existing Research, Too

I cross-referenced my study with an existing AT&T persona framework I didn't run, a second, independent signal that consolidation was the right problem.

75+Interviews
60Survey Responses
Dozens of HrsRetail & Call-Center Observation

Consistent pattern: too many disconnected systems — every extra swivel erodes efficiency and confidence on a live call.

My synthesis of the existing AT&T persona framework's scope and headline finding — not a reproduction of the source document.

Collaboration

Return logic touched refunds, non-return fees and RMA deadlines, so I worked closely with business stakeholders to keep the interface honest, not just cleaner-looking.

Design, research, content, and backend engineering working a return-status edge case together.

Impact

Validated — Frontline Review

Before a line of it was built, frontline reviewers evaluated the redesigned Figma directly:

"Will SAVE so much time trying to find returns."

Frontline Expert, Design Review

Modeled — Business Case

A projected 203-second cut per Device Return contact across 3.6M+ annual calls. The full model is below.

  • Experts called the new flow easier to navigate and expected it to meaningfully cut click time, especially for new hires.
  • Several asked to join the eventual pilot — an informal but strong vote of confidence.
  • Conditional field display fixed the confusion research surfaced: no RMA info on returns without one, and the unexplained "Refund Amount" field cut entirely.

Two internal dollar-benefit estimates existed for the broader returns initiative this work supported ($20M and $6M annually, tied to different scoping assumptions); as of my last review, neither had been finance-vetted, so I'm not quoting either as a personal result here.

Projected annual savings · Device Return call type
3,613,799Annual calls
3.38 minHandle time saved per call≈ 203 seconds
$0.3806Cost per minuteFinance-approved rate
$4.65MProjected annual savings

A moderate handle-time reduction applied to the full Device Return call volume. Projected from the business case, not measured after launch.

The finance-partnered model this redesign was tied to: annual calls × minutes saved × cost per minute.

Reflection

Bringing in research wasn't process for its own sake — I didn't trust my own assumptions about what "overwhelming" meant to someone who reads this screen fifty times a day. And separating customer accountability from backend structure wasn't a stylistic choice — it was the one reframe that made every other decision on this project obvious. That's the judgment I want a team to trust me with on a messy, high-stakes system.