CTV News Local Video Discovery overview

Case Study · Bell Media / CTV News

Local Video Discovery

CTV News covers 15+ local stations, and local newscasts are one of the most-watched content types on the platform. The Local tab held it all: stories, newscasts, and featured video. But the tab was split across sections that required users to switch views before finding anything.

Platform iOS & Android App
Role Product Designer
Shipped January 2025
Outcome 60% to 100% task completion
Methods SUS Benchmarking, Competitive Analysis
Team PM, Engineering, Editorial

Content buried, structure broken

I ran usability tests on the old flow with 10 participants, asking each to find CTV News Toronto at Six from the home screen. Most couldn't. The content existed, but the section switch needed to reach it was easy to miss entirely.

Before state: local newscasts hidden behind section switching

Before: local newscasts and featured video were hidden behind section switching in the Local tab

Baseline usability study

  • Time-on-task averaged 57 seconds
  • Task completion rate: 60%
  • SUS score: 59.5
  • The content wasn't broken. The structure around it was.

How competitors surface video

Before wireframing anything, I reviewed how leading news and video apps surfaced video content. A few patterns came up consistently: video was treated as its own content type, not mixed into a general feed. It was usually given a dedicated, labeled module with a distinct card pattern that made it easy to identify on scan. CBC News and CNBC were the clearest examples of this, and both informed how I approached the Local tab structure.

Competitive landscape: CBC News and CNBC video surfacing patterns

CBC News

  • Single scrollable feed mixing articles and video
  • Local content surfaced inline, no tab switching
  • Video and stories share the same vertical path

CNBC

  • Persistent video rail pinned at top of feed
  • Live and recent video always above the fold
  • Horizontal scroll keeps feed flow intact

Exploring a unified feed

I wireframed several structural models before landing on a three-section feed. The goal was simple: replace section-switching with a single scrollable path.

Early wireframes exploring the Local tab structure across tabs

Early wireframes exploring the Local tab structure and scalable content patterns across tabs

1

Top Stories

Leading article cards from the user's local market. Familiar entry point, matching the existing mental model.

2

Top Videos

A horizontal video rail with the most-watched and most-recent clips from that market. Visually distinct from article cards.

3

Local Newscasts

Full newscasts from that city's CTV station: noon, evening, and late news. Always visible, no switching required.

Aligning on scope and designing for what came next

In weekly reviews with editorial, product, and engineering, we aligned on the Local tab's content set: Top Stories, Top Videos, and Local Newscasts. Developing Stories was scoped out to keep the launch tight.

Two constraints shaped the work. The Home tab was already in development, so new patterns had to reuse existing components to stay consistent. The Watch tab was next in the queue, so I designed with scalability in mind rather than solving Local in isolation.

Before and after

The Local tab moved from a section-switched experience to one unified, scannable feed.

Before: local newscasts and featured video hidden behind section switching

Before: local newscasts and featured video required navigating into a hidden sections drawer

After: Local tab organized into one scrollable feed

After: Local tab organized into one scrollable feed. Top Stories, Top Videos, and Local Newscasts always visible.

Results across every metric

After launch I re-ran the same benchmark with 10 participants on the same task. Every metric moved. An error was any tap that did not move the task toward the newscast, such as opening the wrong section or backtracking to try a different path.

Usability benchmark summary before and after the redesign

Usability benchmark summary, before and after the redesign

92.5
↑ from 59.5
SUS Score
18s
↓ from 57s
Avg Task Time
to Find Newscast
0
↓ from 1.8
Avg Errors
Per Task
100%
↑ from 60%
Task Completion
Rate

What this project reinforced

1

Placement beats packaging

CBC News and CNBC solved video discovery in different ways, but neither hid it behind a switch. That was the principle worth borrowing, not either layout on its own, which is why it held up once applied to a different structure.

2

Scoping out is a design decision

Cutting Developing Stories was what kept Top Stories, Top Videos, and Local Newscasts always visible without a hidden switch. A fourth module would have pushed newscasts below the fold and reintroduced the problem the redesign was solving.

3

Designing for the next tab, not just this one

The Watch tab was already next in the queue, so the Top Videos module was built with scalability in mind rather than solving Local in isolation. Designing for what comes next costs little at the time and saves a second round of work later.

Next Project

TSN Connected TV

10-foot UI · On-Demand Discovery · Usability Testing