
Case Study · Telecom Retail · 2024
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.
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%.
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.
Too many screens and clicks slowing down the process
Complicated activation flow causing user frustration
Inefficient carrier-based payment processing
Understanding the landscape through stakeholder interviews to identify key pain points in the mobile activation workflow.
I conducted 16 stakeholder interviews across store operations, customer support, sales, and IT teams to understand internal perspectives on activation workflow challenges.
"Staff spend too much time on each activation, causing long customer wait times"
"Most calls are about activation failures and payment processing errors"
"Complex workflow leads to abandoned activations and lost sales"
"System timeouts and carrier API failures cause 30% of support tickets"
Too many screens and steps to complete activation
Carrier-based payment collection causing errors
Frequent timeouts and API failures
New staff struggle with complex interface
Deep dive into user needs through interviews, surveys, and contextual inquiry to understand behaviors, motivations, and pain points of store staff.
Conducted 24 one-on-one interviews with store staff across different experience levels, store sizes, and geographic locations.
Distributed a comprehensive survey to validate interview findings and gather statistically significant data on workflow preferences.
Observed store staff using the activation system in real store environments to understand actual usage patterns and environmental factors.
cite too many clicks as their biggest frustration
average screens to complete one activation
spend most time on plan selection
longer activation time vs. industry benchmark
Transforming raw research data into actionable insights through persona development and pattern analysis.
32 • Experienced Sales Rep
"I know the system inside out, but it still takes too long. My customers shouldn't have to wait."
24 • New Store Associate
"I'm always worried I'll mess something up. The training didn't prepare me for all the edge cases."
45 • Store Manager
"I spend more time fixing activation issues than actually managing my store."
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.
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.
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.
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.
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.
These 4 requirements became the non-negotiable constraints for every screen in the prototype. See how each one was implemented →
The Transformation
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.
One field per screen, no grouping
What staff experienced
Related fields consolidated, inline validation
Device Information
IMEI, SIM, device type, carrier — all on one screen
Customer Details
Name, email, phone, address grouped together
Plan Selection
Visual plan cards with side-by-side comparison
Review & Activate
Full summary with one-tap confirmation
What changed for staff
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.
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.
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.
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.
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.
Three rounds of prototyping, each tested with real store staff. Each round addressed the specific failures of the round before it.

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.
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.
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.
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.
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.
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.
The screen staff see first — and the one that set the tone for every interaction that followed. Toggle between the original and redesigned version.
Experience the streamlined 4-step activation process. Navigate through each step to see how we simplified the user journey.
Cricket Wireless • Real Time Technologies
Activate a new line for your customer
Enter device details
Enter device details
Contact information
Choose a plan
Confirm and activate
Enter the device details to begin activation
Dial *#06# on the device to find IMEI
Order Summary
The redesigned activation platform delivered measurable improvements across all key performance indicators.
Average Activation Time
61% fasterActivation Error Rate
-67% errorsSupport Escalations
-58% escalationsStaff Satisfaction Score
+1.6 ptsEarly and continuous user involvement was crucial for identifying real pain points and validating solutions.
Working closely with developers from day one ensured designs were technically feasible and implementation was smooth.
Multiple rounds of testing and iteration led to a 40% improvement in usability scores from initial designs.