Sprint Omni-Channel Unification
Designing a Scalable, Cross-Channel Service System on the Brink of Merger
Role:
Product Design Lead
Team:
8 UX
1 PM
4 FE
3 BE
Timeline:
1 year
Impact:
12 tools → 1 • 45% drop in handle time • Merger-ready design system
Context
In 2019, Sprint was preparing for its historic merger with T-Mobile, in a move poised to reshape the U.S. telecom industry. But internally, Sprint’s operations were tangled in legacy systems, siloed tools, and disconnected customer experiences.
Every channel—retail, call center, web, telesales—operated in its own vacuum. Customers who jumped between them left trails of fragmented data, and no single agent had a complete view of their journey.
As the project design lead, I worked at the crossroads of a massive operational and customer experience transformation.
The goal:
Create a seamless, cross-channel “concierge” system that unified Sprint’s service tools to meet the demands of a post-merger future.
Team Impact
Served as the key contact point across backend architects (Amdocs), stakeholders(Sprint), and internal design teams.
Translated fragmented business processes into a shared product strategy.
Led contextual research, journey mapping, and visioning workshops across four major service channels.
Designed for a future we couldn’t fully predict—planning for adaptability, theming, and system portability post-merger.
The Problem Landscape
Discovery consisted of workshops, contextual inquiries, interviews and audits of training material over a few months. The following was discovered as major themes to address:
Siloed Systems, Siloed Service
→ 12+ tools across telesales alone. Each team had a different lens on the same customer, resulting in poor handoffs and duplicated effort.
Zero Shared Context
→ Agents lacked visibility into prior interactions. Store visits, support chats, and upgrade calls lived in separate systems.
Training Overhead
→ Agents already needed to learn multiple tools, and devices, as well as understand scripts to help navigate customer interactions, before helping a single customer.
Merger Paralysis
→ Fear of irrelevance slowed momentum. If changes made things "too easy" for certain teams, the uncertainty and doubt about job security would make them less likely to cooperate with design efforts.
ecosystem map was used to visualize the interconnected landscape of users, tools, touchpoints, and systems that required to influence or would be influenced by this effort.
A Turning Point
By shadowing frontline reps in retail, telesales, and web support, a pattern emerged:
Everyone was doing the same three jobs—convert, upgrade, retain—but were going about it in completely different ways.
“The channel doesn’t matter. The context does.”
Strategic Design Interventions
Journey-Aware UI Components
→ Designed modular components that surfaced recent activity, personalized offers, and predictive “next best actions” based on user behavior. We were able to automate parts of this experience by training a model from an expansive sales script already in play.
Channel and Platform-Agnostic Design System
→ Built a flexible design system that could be skinned for Sprint or T-Mobile, ensuring future portability.
Tool Consolidation Strategy
→ Merged 12 disparate telesales tools into a single intelligent interface—reducing training time and improving task efficiency.
Vision Workshops
→ Ran alignment sessions with product, ops, and engineering to translate customer experience goals into scalable system architecture.
Celebrated Wins Along the Way
Customer + Agent Wins
Cut average handle time and in-store dwell time by 45%
Created shared service context across support, sales, and retail
Dramatically simplified onboarding for new agents
System + Strategic Wins
Consolidated 12 legacy tools into 1
Designed a themable, merger-ready design system
Unified previously siloed business units around a common vision
Design and Validation
Cultural Contribution
Cross-Org Alignment:
Created common ground for product, architecture, and CX teams—bridging operational silos.
Design Foresight:
Future-proofed the work by designing systems that could integrate into differing infrastructure.
Change Management:
Helped teams see transformation as a pathway to relevance, not a risk to avoid.