Netflix · Case study

Netflix · Case study

Title Groups

Title Groups

Title Groups

An information architecture and playbook defining how related titles, supplemental content and lifecycle phases connect.

TIMELINE

2018–2019

ROLE

Lead Designer

DELIVERABLE

IA framework

TEAM

Design & Workflow Design Operations Product Creative, Title Artwork Platform Engineering Product Management

Information architecture

Content modeling

Systems thinking

Stakeholder alignment

Documentation

01

/

10

Title Groups · 2018–2019

Two photos side by side: red Netflix DVD envelopes from 1997, and a Netflix home screen full of title art from 2019.
19972019

02

/

10

Problem

A clip, a trailer, an episode and a series are very different things.

The multi-title data structures could not support the flexibility and scale that groups with many titles needed.

03

/

10

Research

Viewers already had rules for what belongs together.

Netflix’s research team ran viewer workshops with adults, tweens and kids in Phoenix and Mumbai. I turned their findings and the technical requirements into a 70+ page synthesis that the model was built on.

01 · Continuity

Characters, worlds and chronology have rules. Break them only with a reason.

02 · Cohesion

Some of the original’s magic has to carry from one title to the next.

03 · Credibility

Another story to tell is welcome. A cash-in is not.

Cohesion = DNA × structure

The looser it gets, the more a group becomes a collection.

04

/

10

Goal and role

Define how related titles connect.

Define the types of relationships between families of content, set the principles and structures each type needs, and document them so teams with very different expertise could use them.

Title GroupPeople & Characters · Continuations · Retellings · Branches · Universes

  • StandaloneMovie/Films · Doc · Stand Up · Interactive · Aftershow · Supporting Content · Others…

  • Standalone (Movie, Series)

    • 1st in Series

    • Sequel

  • Show

    • Seasons

      • Episodes

05

/

10

The model

One base structure, several kinds of relationship.

A group holds standalone titles and series. Supplemental content, like trailers, recaps and behind-the-scenes, attaches to either.

Model · relationships + attachment rules

Base structure requirements

Title Group

  • Standalone

    • Supplemental

  • Series

    • Seasons

      • Episodes

Group → Title or series → Supplemental content

Group → Title or series → Supplemental content

Title Group

  • People & Characters
  • Continuations
  • Retelling
  • Branches
  • Universes
  • Franchises

Standalone

  • Movies/Films
  • Documentaries
  • Stand-Up Comedy
  • Interactive Programming
  • After Shows
  • Supporting Content

Series

  • Episodic
  • Limited
  • Parts
  • Volumes
  • Collections

Supplemental

  • Trailer
  • Recap
  • Behind the Scenes

The model, built up

The Title Group model drawn level by level, from the group to standalones and shows, then seasons, episodes and supporting content.

06

/

10

Worked example

One franchise, mapped end to end.

A group runs from a franchise down through series and limited series to episodes, with trailers, teasers and announcements attached.

My work · IA model + documentation

Chronicles of Narnia Title Group

  • Lion Witch & Wardrobe

  • Prince Caspian

    • Limited series

      • Episodes

  • Voyage of the Dawn Treader

    • Season 1

      • Episodes

    • Season 2

      • Episodes

    • Season 3

      • Episodes

  • The Silver Chair

    • Limited series

      • Episodes

  • The Horse & His Boy

    • Limited series

      • Episodes

  • The Magician’s Nephew

    • Limited series

      • Episodes

  • The Last Battle

    • Part 1

    • Part 2

Base structure + supplemental at any level

Base structure + supplemental at any level

07

/

10

Notation

A kit to map any group.

Every node type, standalone, series and supplemental, was built as a component with its own states: bright for titles on service, faded for titles still to come, and a highlight for the moment in focus. Any franchise could be mapped from the same parts.

A sheet of diagram components in three bands: white, faded grey and purple versions of the same movie, series and supplemental nodes.

Standalone · Series · Supplemental × Bright · Faded · Highlight

08

/

10

Lifecycle · Phase 1

A group has a lifecycle.

It is identified at acquisition, and searchable and linkable first.

System & UI triggers

Phase 1

IP identified and defined as a Title Group as part of acquisition.

Title Group entity: search and link only.

  1. AnnouncementChronicles of Narnia
  2. AnnouncementLion Witch Wardrobe
  3. TeaserLion Witch Wardrobe
  4. TrailerLion Witch Wardrobe
  5. StandaloneThe Lion, the Witch & the Wardrobe
  6. AnnouncementCaspian

09

/

10

Lifecycle · Phases 2 and 3

Promotable after the second title. Complete once editorially ordered.

Each phase says what the system and the interface can do, so engineering and editorial could agree on what was a must-have.

System & UI triggers

Phase 3

Complete Title Group entity.

Editorially ordered.

  1. StandaloneThe Silver Chair
  2. Pre-promoteDawn Treader S3
  3. Series · Season 3Voyage of the Dawn Treader S3
  4. Pre-promoteHorse & Boy
  5. TeaserHorse & Boy
  6. TrailerHorse & Boy
  7. Limited series · 6 episodesThe Horse & His Boy
  8. Pre-promoteMagician’s Nephew
  9. TeaserMagician’s Nephew
  10. TrailerMagician’s Nephew
  11. Limited series · 6 episodesThe Magician’s Nephew
  12. Pre-promoteThe Last Battle P1
  13. StandaloneThe Last Battle P1
  14. Pre-promoteThe Last Battle P2
  15. Standalone · SequelThe Last Battle P2

Acquisition → Searchable + linkable → Promotable → Editorially ordered

Acquisition → Searchable + linkable → Promotable → Editorially ordered

10

/

10

Outcome

A shared model for editorial and engineering.

I ran a working group across three teams, with weekly reviews alongside executives from each and follow-ups with individual groups. The playbook was delivered as a proposal manual: terminology, promotional tactics, triggers and edge cases, content types, and engineering and UI requirements. Once teams signed off, each org took its part back to build, using the playbook as the reference.

A wall of pages from the proposal manual: section dividers, diagrams and tables.

© 2026 Ian Khoogar-Kirk

© 2026 Ian Khoogar-Kirk

© 2026 Ian Khoogar-Kirk