UX design whiteboard with wireframes and sticky notes

Case Study · Telecom Retail · 2024

Mobile ActivationPlatform Redesign

The tool had 12 screens, no progress indicator, and timed out mid-transaction. Staff had memorized workarounds just to survive a live sale. I went to the stores, watched it happen, and fixed it.

UX ResearchUI DesignVuetify.js Design SystemTelecom Retail
12→4.5
Activation Time (min)
-74%
Error Rate
-58%
Support Escalations
4.7/5
Staff Rating
TL;DR

The activation tool had 12 screens, no progress indicator, and timed out mid-transaction — managers had memorized workarounds just to survive a live sale. I mapped the full workflow, ran usability tests across 3 rounds, and redesigned it into a 4-step flow with inline validation and auto-save — cutting activation time from 12 to 4.5 minutes and dropping the error rate by 74%.

Project Overview

The Challenge

RT2 is a payment processing company that facilitates mobile activation and payment collection for store users based on their phone carriers. The existing workflow required users to navigate through multiple complex screens, creating friction in both the activation process and payment collection.

The challenge was to streamline the entire workflow, making it intuitive and simple to expedite the process without requiring numerous screens or clicks.

Complex Workflow

Too many screens and clicks slowing down the process

Mobile Activation Friction

Complicated activation flow causing user frustration

Payment Collection Issues

Inefficient carrier-based payment processing

Project Details

ClientRT2 Payment Processing
Timeline6 Months (Q1-Q2 2024)
My RoleUX Lead
Team2 Designers, 3 Developers
Tools Used
FigmaVisual Studio CodeVuetify.js
Phase 01

Discovery

Understanding the landscape through stakeholder interviews to identify key pain points in the mobile activation workflow.

Stakeholder Insights

I conducted 16 stakeholder interviews across store operations, customer support, sales, and IT teams to understand internal perspectives on activation workflow challenges.

Store Managers

"Staff spend too much time on each activation, causing long customer wait times"

Customer Support

"Most calls are about activation failures and payment processing errors"

Sales Team

"Complex workflow leads to abandoned activations and lost sales"

IT Operations

"System timeouts and carrier API failures cause 30% of support tickets"

Key Themes Identified

1
Workflow Complexity

Too many screens and steps to complete activation

2
Payment Friction

Carrier-based payment collection causing errors

3
System Reliability

Frequent timeouts and API failures

4
Training Gap

New staff struggle with complex interface

Phase 02

User Research

Deep dive into user needs through interviews, surveys, and contextual inquiry to understand behaviors, motivations, and pain points of store staff.

In-Depth Interviews

Conducted 24 one-on-one interviews with store staff across different experience levels, store sizes, and geographic locations.

24Participants
40 minAvg. Duration

Quantitative Survey

Distributed a comprehensive survey to validate interview findings and gather statistically significant data on workflow preferences.

156Responses
91%Completion

Contextual Inquiry

Observed store staff using the activation system in real store environments to understand actual usage patterns and environmental factors.

12Sessions
3 hrsAvg. Duration

Key Research Findings

74%

cite too many clicks as their biggest frustration

8.2

average screens to complete one activation

68%

spend most time on plan selection

3.4x

longer activation time vs. industry benchmark

Phase 03

Synthesis

Transforming raw research data into actionable insights through persona development and pattern analysis.

User Personas

Marcus Thompson

32 • Experienced Sales Rep

Goals
  • Complete activations quickly
  • Minimize customer wait time
  • Hit daily sales targets
Frustrations
  • Too many redundant screens
  • System crashes during peak hours
  • Can't see all carrier options at once

"I know the system inside out, but it still takes too long. My customers shouldn't have to wait."

Sarah Mitchell

24 • New Store Associate

Goals
  • Learn the system quickly
  • Avoid making errors
  • Get help when stuck
Frustrations
  • Confusing navigation
  • No clear guidance on next steps
  • Fear of making costly mistakes

"I'm always worried I'll mess something up. The training didn't prepare me for all the edge cases."

David Chen

45 • Store Manager

Goals
  • Maximize store efficiency
  • Reduce support escalations
  • Train new staff effectively
Frustrations
  • High error rates from new hires
  • Time spent troubleshooting
  • Inconsistent carrier processes

"I spend more time fixing activation issues than actually managing my store."

What the personas demanded

Marcus was mid-activation when the session timed out — customer watching, no way to recover, restart from scratch. Sarah had just called David over for the third time that shift because an error code told her nothing. Three people, three different problems — but they all traced back to the same four design failures.

01

Lock the flow

Marcus persona — free navigation let staff skip steps, causing the majority of errors. He'd memorized a workaround order that new hires didn't know.

Locked linear flow: step 1 → 2 → 3 → 4, no skipping
02

Always show where you are

Sarah persona — no progress indicator meant she had no idea how many steps remained. When errors hit, she'd abandon and restart rather than continue.

Persistent 4-step progress bar, always visible
03

Errors must explain themselves

David persona — new hires called him over for every error code. He kept a handwritten cheat sheet under the counter. That's a training failure caused by the UI.

Plain-language errors with one clear recovery action
04

One flow, not two systems

All three personas — payment and activation in separate systems meant tab-switching and manual copy-paste on every single transaction. Observed in 100% of shadowed sessions.

Payment embedded as step 4, account data carries over

These 4 requirements became the non-negotiable constraints for every screen in the prototype. See how each one was implemented →

The Transformation

Before & After

The original flow had 12 separate screens — one field per page. We consolidated it into 4 grouped steps with inline validation. Here's what changed and why it mattered on the store floor.

Before — 12-Screen Flow

One field per screen, no grouping

1Login Screen
2Select Carrier
3Enter IMEI (manual)
4Verify IMEI
5Enter SIM Card
6Verify SIM Card
7Customer Name
8Customer Email
9Customer Phone
10Customer Address
11Select Plan
12Review & Submit

What staff experienced

  • Constant back-and-forth navigation with a customer watching
  • No validation until final submit — errors sent you back to step 1
  • No sense of progress; staff couldn't tell how far along they were
  • Average completion time: 8–12 minutes per activation
  • ~42% of submissions had at least one error requiring rework
After

After — 4-Step Grouped Flow

Related fields consolidated, inline validation

1

Device Information

IMEI, SIM, device type, carrier — all on one screen

2

Customer Details

Name, email, phone, address grouped together

3

Plan Selection

Visual plan cards with side-by-side comparison

4

Review & Activate

Full summary with one-tap confirmation

What changed for staff

  • Related fields grouped — fewer page loads, less back-and-forth
  • Inline validation catches errors as you type, not at the end
  • Persistent step indicator shows exactly where you are
  • Average completion time dropped to 2–3 minutes
  • Error rate fell to ~8% — an 81% improvement
67%
Fewer Screens
75%
Time Saved
81%
Error Reduction

Why these decisions were made

Information Grouping

Card sorting sessions with branch managers revealed that staff mentally grouped device info and customer info as two separate tasks. The redesign mirrors that mental model.

Progressive Validation

Errors at final submission were the single biggest frustration. Inline validation was added so staff get feedback immediately — before the customer is still standing there waiting.

Visible Progress

Shadowing sessions showed staff losing track of where they were mid-activation. A persistent step indicator was added so the flow always felt predictable and in control.

Smart Defaults

Carrier context was already known at login. Pre-populating carrier-specific fields and filtering plan options reduced manual input and decision fatigue during busy floor hours.

Design Process

From Research to
Design Decisions

Every screen decision traces back to a specific observation from the store floor. Here's how the research translated into the actual interface — from first sketches to the final prototype handed off to engineering.

Wireframe Progression

Three rounds of prototyping, each tested with real store staff. Each round addressed the specific failures of the round before it.

Paper prototype sketches of mobile activation flow
54%
Task Completion
11.4 min
Avg. Activation Time
Key Change This Round

Collapsed 12 original screens into a 4-step linear model. Grouped device info (IMEI + SIM + carrier) onto a single screen instead of 3 separate ones.

Top Finding

Staff immediately understood the grouped layout — but carrier selection at the bottom caused confusion. Everyone expected it at the very top to set context for the whole flow.

Round Comparison
Paper Sketches54%
Lo-Fi Wireframes76%
Hi-Fi Prototype92%

4 Decisions That Defined the Design

Each one traces directly to a specific observation from the store floor — not a best practice, not a heuristic, but something I watched happen in front of a real customer.

Locked Linear Flow
Locked Linear Flow
The Problem

The original system let staff navigate freely between steps — which meant they could (and did) skip steps, causing the majority of activation errors. New hires had no idea what order things needed to happen in.

The Design Decision

A strictly locked linear flow: step 1 → 2 → 3 → 4. You cannot proceed until the current step is valid. The UI enforces correct order structurally — not through training.

Measured Impact

Activation error rate dropped from 34% to under 8% in round 2 testing. The locked model had the lowest error rate across all 4 flow structures tested.

Before & After: Activation Start Screen

The screen staff see first — and the one that set the tone for every interaction that followed. Toggle between the original and redesigned version.

Original activation screen
Original
What was broken
  • Carrier selection buried at step 3 — staff had to guess plan options before knowing the carrier
  • No progress indicator — staff had no idea how many steps remained
  • Session timeout at 5 min with no warning — mid-activation restarts were common
  • Generic error codes (4402, 5011) with no explanation or recovery path
  • Payment in a completely separate system — required tab switching and manual copy-paste
Interactive Demo

Try the Activation Flow

Experience the streamlined 4-step activation process. Navigate through each step to see how we simplified the user journey.

Mobile Activation Portal

Cricket Wireless • Real Time Technologies

New Activation Lines

Activate a new line for your customer

Cricket WirelessActive Session
1
2
3
4
Device Info

Enter device details

Device Information

Enter the device details to begin activation

Dial *#06# on the device to find IMEI

Step 1 of 4
Impact

Results & Outcomes

The redesigned activation platform delivered measurable improvements across all key performance indicators.

Before11 min
After4.3 min

Average Activation Time

61% faster
Before34%
After11%

Activation Error Rate

-67% errors
Before~40%
After~17%

Support Escalations

-58% escalations
Before3.1/5
After4.7/5

Staff Satisfaction Score

+1.6 pts

Key Learnings

User-Centered Approach

Early and continuous user involvement was crucial for identifying real pain points and validating solutions.

Cross-Functional Collaboration

Working closely with developers from day one ensured designs were technically feasible and implementation was smooth.

Iterative Process

Multiple rounds of testing and iteration led to a 40% improvement in usability scores from initial designs.