Sling

Sling Experience Overhaul.

Redesigning Sling’s core experience to improve engagement and drive growth.

Cross Platform RedesignPrincipal DesignerCore Product Redesign15+ Devices · 18 MonthsDesign Leadership · 4 TeamsTV · Mobile · Web

Background
Streaming War: As competing streaming services raised the UX bar, users came to expect easier, more intuitive streaming experiences.
TL;DR
Problem
Years of feature layering buried content beneath overlapping menus and labels, while aging UI and interaction patterns slowed the path to content.
Approach
I proposed and led a core experience overhaul, aligning teams around a shared product model, decision framework, and rollout strategy.
Outcome
The redesign first launched on Roku within one year and scaled to all platforms within 18 months, with post-launch readouts showing improved efficiency, engagement, retention, and paid conversion signals.
+9.7%
+182K
6/6
ACSI customer satisfaction
Subscribers initial rollout
Product signals improved

Context / Why Now

Streaming expectations changed. Sling needed to evolve.

TV streaming had become more competitive, giving users more choices and raising expectations for faster, more intuitive experiences. For Sling, the challenge was to make its core value easier to access—helping users get to live and on-demand content with less effort, while preserving its speed to content.


Problem

The core problem was ambiguity across the experience.

As Sling expanded across devices, years of feature layering created overlapping destinations, mixed content states, and inconsistent patterns. Users had to interpret where to go, whether content was live, on-demand, or saved, and where to return later—often falling back on Guide or Search.

Ambiguous home screen
My TV sounded personal, but its role was unclear.
Mixed content states
Live, on-demand, and saved content appeared across different areas.
Unclear saved-content model
No clear destination for saved content.
Overlapping destinations
Top-level navigation mixed user goals, content types, and product areas.

Legacy patterns no longer matched user expectations.

The dated visual and interaction model made content harder to evaluate, while competing services made streaming feel more intuitive, personalized, and seamless.

LEGACY SLING TV

As Sling’s core experience grew more complex, users struggled to navigate and find content. This wasn’t simply a visual or a navigation cleanup. Sling needed a new experience foundation.


The Goals

Make Sling easier to use, so engagement could turn into growth.

The goal was to improve the core experience in ways that could change user behavior and support long-term product health—not just make the product look or feel more consistent.

Better Experience
Higher Engagement
Stronger Retention & Revenue Growth
Better product experience: Create a more intuitive and consistent experience across TV, mobile, and web, so users could find, choose, and continue watching with less effort. Higher engagement: Reduce friction across navigation, discovery, and viewing so users could find what they wanted faster and spend less time browsing and more time watching. Lower churn / revenue growth: Improve engagement signals that could support retention, reduce churn risk, and drive long-term growth.

Research

Multiple signals pointed to the same four friction patterns.

I gathered problem input from four Cross-Journey Teams, conducted user interviews and survey research, reviewed product analytics, and completed competitive reviews to identify where the core experience was breaking down.

Cross-Journey Teams
4
User Interviews
30+
Survey responses
600+
Competitive reviews
15+

The same four friction patterns kept showing up.

Wayfinding — Where do I go? Navigation felt inconsistent across surfaces, so users often fell back on Guide or Search.
Choice overload — What should I watch? Too many rows and menus slowed decisions before users found something worth watching.
Unclear relevance — Why is this for me? Recommendations did not feel personal or explainable, so users returned to manual browsing.
Interrupted viewing — How do I keep watching? Exploration often pulled users out of playback and made re-entry harder.
These four patterns shaped the three product decisions that followed.

Product Decisions

The research shaped three decisions for rebuilding core experience.

Each decision was sequenced deliberately. Foundation came first to make the product easier to navigate. Personalized Discovery came next to reduce decision time once the foundation was stable. Seamless Viewing closed the loop between browsing and watching. Together, the three decisions addressed the core path from finding content to staying engaged.

Foundation
Fix wayfinding first.
Make the core experience easier to navigate. Time to Video ↓
Personalized Discovery
Make discovery relevant
Reduce decision time across discovery surfaces. Browsing Time ↓
Seamless Viewing
Protect viewing momentum
Keep browsing connected to playback. Viewing Time ↑

Decision 1 · Foundation

Build the foundation first.

Before improving discovery or viewing continuity, we needed to make the core experience easier to navigate and more predictable across platforms. ✭Of the three decisions, this had the broadest scope, touching nearly every part of the product.

The foundation created a clearer path for users and a shared model for journey teams—allowing the redesign to scale without reintroducing fragmentation.

1
2
3
4
5
Information Architecture
Main Navigation
UI & Video Foundation
Interaction Rules
Shared Patterns

1. Information Architecture

The existing IA had overlapping destinations and unclear content paths.

Sling offered a broad mix of live and on-demand content, but overlapping destinations made it harder to find and manage. Many users fell back to the familiar Guide instead of navigating the broader experience.

The evidence pointed to three IA breakdowns.

Too much effort to get to content
Guide became the default path
Content was harder to find and manage
Users had to take too many steps before they could start watching.
When the broader experience felt confusing, users returned to the familiar live TV guide.
Users missed On Demand content and struggled to manage DVR or saved content.

The key IA decision was how to organize content around user intent.

Both models had trade-offs. The category-based model offered familiar entry points, but continued to mix live and on-demand content and duplicate paths. The goal-and-state model organized destinations around what users wanted to do and whether content was live, on demand, or saved.

I chose the model that best addressed Sling’s core IA problem: reducing overlap and making each destination more predictable.

Option A · Category-based
▪Movies, Shows, and Sports as primary destinations▪Familiar content categories▪Continued overlap between live and on-demand content
Option B · Goal-and-state-based
▪Guide for live TV▪On Demand for VOD browsing▪Library for saved and recorded content▪Clearer, more distinct destination roles

The key alignment challenge was balancing DVR visibility with IA clarity.

Senior leadership wanted DVR to remain highly visible because DVR upgrades generated revenue. I advocated for grouping recorded and saved content in Library, where users expected to find it.

The trade-off
DVR supported upgrade revenue, but a separate top-level destination risked adding complexity to an already crowded navigation model.
My position
Group DVR, My List, My Channels, and saved content under Library so users had one clear saved-content destination.
How we aligned
Use Library as the primary saved-content destination, preserve DVR exposure through Home modules, and test whether DVR needed a top-level entry after launch.

The new IA organized Sling around clearer user goals.

The new structure reduced overlapping destinations and created clearer paths to start with relevant content, watch live TV, explore on-demand content, return to saved content, or search directly.

The result was a simpler five-destination model. ▪ Home — Personalized, promotional, and curated content across live and on-demand. ▪ Guide — Familiar live TV browsing for cable-oriented users. ▪ On Demand — A dedicated destination for Sling’s on-demand library. ▪ Library — Saved content, favorites, watchlists, and DVR. ▪ Search — Direct access for users who already knew what they wanted.

2. Main Navigation

The navigation model had to balance immersion and wayfinding.

After simplifying the IA, I compared top and left navigation against the needs of a content-heavy TV experience: preserving screen space, supporting frequent destination switching, and remaining predictable with a remote.

I chose left navigation for Sling’s TV experience.

A collapsible left rail better matched Sling’s frequent task switching. It preserved content space when collapsed, made core destinations easier to reach, and created a clearer boundary between navigation and browsing.

Preserved browsing space
A collapsed left rail used less vertical space than top navigation on TV.
Faster destination switching
Users could quickly move between Guide, DVR, Search, On Demand, and Home with a remote.
Clear navigation mode
Expanding the rail made it clear that users were switching destinations, not browsing content.
Market signal
Six of eight paid streaming services reviewed used left navigation, and 56% of participants preferred it.

Trade-off

Top navigation offered greater visual immersion, but made destination switching heavier once users were deep in content. Because Sling’s larger problem was wayfinding, I prioritized faster, more predictable access to destinations over maximum visual immersion.


3. UI & Video Foundation

The redesign needed a base model for browsing and playback.

With the IA and navigation defined, I compared two structural models for how browsing and playback should coexist. The decision had to balance usability, cross-platform feasibility, ad viewability, and future viewing continuity.

Video overlay UI (Lean-forward)
Video behind UI (Lean-back)

I chose the model that balanced usability, feasibility, and ad viewability.

After comparing both models, Video Behind UI offered a more continuous live TV experience, while Video Overlay UI provided clearer separation between browsing and playback, lower delivery risk, and stronger protection for ad viewability.

Trade-off

We traded the more continuous, always-on live TV feel of Video Behind UI, which kept playback visible during browsing, for the clearer separation of Video Overlay UI. The selected model fit Sling’s existing architecture, protected ad viewability, and created a more consistent foundation across platforms while still supporting future continuity patterns such as picture-in-picture and muted preview.


4. Interaction Rules

I turned familiar TV interaction patterns into shared rules.

With the IA, navigation, and video foundation defined, I reviewed platform guidance and common streaming TV conventions, then established consistent behavior for Sling’s remote-based experience.

The rules defined behavior across four interaction areas.


5. Scaling the Model

I defined a shared model so four journey teams could move in parallel.

The foundation was translated into high-level screen models, reusable patterns, and platform guidance. Each team could adapt the model to its journey without reopening core product decisions.

Shared screen models, reusable patterns, and platform guidance.

Decision 2 · Personalized Discovery

Make discovery relevant by default.

With the foundation in place, the next challenge was helping users decide what to watch faster. Discovery was not about showing more content—it was about matching the right surface and content to the user’s intent.

Three surfaces served three different intents.

Home became the primary discovery surface, while On Demand supported deeper exploration and Search supported high-intent tasks.

Home modules and use-case planning.

I made Home a tunable discovery system.

Modules were organized around personalized relevance, real-time availability, and curated breadth, allowing Home to adapt to different user states.

A module framework balanced three content types.

The same system extended beyond Home: On Demand supported deeper exploration, while Search helped high-intent users evaluate and act faster.

Too much personalization could make Home feel repetitive, while too much curation could make it feel less relevant. The system was designed to tune that balance over time. Discovery became a decision-supporting system—not a static collection of rows.
Trade-off: relevance vs. freshness

Decision 3 · Seamless Viewing

Protect viewing momentum across browsing and playback.

After improving navigation and discovery, the next challenge was preserving viewing context. Users needed to browse, evaluate, and switch live content without stopping playback, losing context, or committing too early.

Picture-in-Picture, Muted Previews, and Channel Zapping.

I connected browsing and playback into a more continuous viewing flow.

I defined three complementary patterns around the moments where viewing momentum broke most: browsing while watching, evaluating content, and switching live channels.

Picture-in-Picture
Keep watching while browsing.
Video remained visible while users explored other surfaces, with a clear path back to full playback.
Evaluate before committing.
Users could assess content before opening a detail page or starting playback.
Muted Previews
Switch live channels without losing flow.
Users could move between live options without returning to the Guide.
Channel Zapping
Browsing became part of the viewing flow—not an interruption to it.

Process · Core + Cross-Journey Team Model

I separated foundation decisions from journey-level execution.

The core team aligned leadership, Product, Engineering, Research, and Design on product direction, interaction models, platform constraints, and quality guardrails. Four Cross-Journey Teams then applied that foundation to their own flows, using review checkpoints to resolve trade-offs without reopening core decisions.

CORE TEAM
CROSS JOURNEY TEAM
01
DISCOVERY AND IDEATION
Gather data and ideate
04
GUIDELINE HAND-OFF
Create high-level screens and hand off to CJTs
07
DEV HAND-OFF
Hand off to engineering
05
BUILD DETAILED UX
CJTs develop journey-level UX
06
VALIDATE
Test, validate, and iterate
08
BUILD & TEST
Build, test, and fix bugs
02
IA & HIGH-LEVEL DESIGN
Define IA and concept direction
03
HIGH LEVEL DESIGN TEST
Test, learn, and validate
09
FEEDBACK LOOP
Learn with users and improve UX and features
CORE & CROSS JOURNEY TEAM PROCESS
CJT execution with Core review checkpoints
Core foundation decisions
Core decisions set direction; Cross-Journey Teams adapted, validated, and delivered detailed flows.

Outcome · New Design

A full core experience redesign across TV, mobile, and web.

The redesign applied one shared experience model across Sling’s core ecosystem—not as identical screens, but as a flexible product foundation adapted to each platform.

This section highlights representative screens, not every journey, to show how the redesigned experience came together across TV, mobile, and web. Same system, device-specific experiences.

The redesign applied one shared experience model across Sling’s core ecosystem—not as identical screens, but as a flexible product foundation adapted to each platform.

This section highlights representative screens, not every journey, to show how the redesigned experience came together across TV, mobile, and web. Same system, device-specific experiences.

Before

TV Experience

Mobile Experience

Web Experience


Impact · Post-Launch Signals

Post-launch signals moved in the intended direction.

Success metrics were defined before rollout. Post-launch readouts showed improvement across the core signals. The rollout was followed by higher customer satisfaction, stronger repeat engagement, and deeper viewing. Core behavioral indicators also moved toward faster starts, less browsing, and more time watching.


Closing / Reflection

Shipping the redesign established the foundation—not the finish line.

Leading this system-level redesign reinforced that my role was not only to define the experience, but also to make trade-offs visible, align teams around shared decisions, and create a foundation they could extend after launch.

What this project reinforced

Align the system before the screens
Defining the foundation first gave teams shared rules for making local decisions without fragmenting the experience.
Make trade-offs explicit
Making usability, feasibility, revenue, and platform constraints visible helped teams understand decisions and revisit them as conditions changed.
Design for team execution
Reusable patterns, decision boundaries, and review checkpoints helped four teams adapt the experience without reopening foundational decisions.