Building experiences people tune into.

CityNews and 680News shared most of their content but ran on separate, aging technology. Publishing took too long, the mobile experience lagged behind where roughly 80% of traffic actually came from, and every market update meant touching two disconnected systems instead of one.

1. 01

   Mobile-first, not mobile-adapted

   With the majority of users already on mobile, the core experience was designed there first and scaled up to desktop, not the reverse.

2. 02

   Atomic, modular design system

   The page was broken into reusable cards and modules instead of fixed templates, so editors could rearrange content without a dev ticket.

3. 03

   Keep functionality, simplify structure

   Research into App Store reviews showed 61% of negative sentiment was about performance (crashes, freezes) and only 3% about missing features, so the strategy was to stabilize and simplify, not add.

Aligning two brand teams — TV and radio — around one shared information architecture required getting editorial, marketing, and engineering stakeholders from both sides to agree on a single navigation model and visual language, without either brand feeling like it had been absorbed by the other.

Add a specific story here: a moment you resolved disagreement between the two brand teams, or how you structured the working group.

Ran unmoderated usability testing with 15 participants against the System Usability Scale (SUS) on the core journeys — homepage, article, video — before committing to full production.

App store reviews were as low as they'd ever been. Users loved the shows but weren't engaging with the app itself — no AirPlay support, heavy ad load during playback, and reliability issues (crashes, freezing) were driving people away from a product built on genuinely strong content.

1. 01

   Personalize the home screen

   Instead of a static default carousel, the home screen surfaced shows based on individual watch behavior.

2. 02

   Design for “catching up,” not just watching

   A “Continue Playing” rail and a “My List” feature were built around the core user journey of returning to finish something.

3. 03

   One experience across every screen

   An omnichannel approach let a viewer pause on their phone and resume on Apple TV.

The redesign started with research and discovery — market research, analytics review, app store sentiment, user surveys, and guerrilla testing — before a single wireframe was drawn.

Add a specific story: how you got engineering and brand stakeholders behind cutting scope to focus on stability first, or how you ran the guerrilla testing sessions and turned findings into a defensible roadmap.

Every platform — web, mobile app, TV app — was independent: any update meant separate code and a separate release. Content was static, with no way to merchandise based on user preferences or time of day.

1. 01

   Design a system, not screens

   Started with site architecture and a shared design system so future features would launch consistently everywhere by default.

2. 02

   Digital-first, not linear-mirrored

   Designed around live sporting events digitally instead of continuing to mirror linear TV.

3. 03

   Prototype and test the highest-risk feature early

   Interactive timeline markers (letting fans jump to key moments in a live game) were concept-tested with users before being built, surfacing a discoverability issue while still cheap to fix.

Getting three previously independent platform teams (web, mobile, TV/connected devices) to adopt one shared design system required aligning engineering leads across teams that had never had to coordinate releases before.

Add a specific story: how you sequenced buy-in across the three platform teams, or a moment you had to make a tradeoff call between platform parity and platform-specific constraints.