Case · Scale · Product

The tools the streaming industry decides with.

TL;DR

Role
Design Director, Enterprise Products, Whip Media
Scope
Content analytics, licensing automation, and cross-platform UX for Fortune 500 media accounts
Timeframe
2022
Shippeda content-discovery platform, predicted performance by territory
First everthe company's first design system
Fortune 500the media accounts the tools were built for

The situation

Whip Media builds software for global media companies: content analytics, licensing automation, and the tools a programming team uses to decide what a streaming service acquires, where it airs, and what it is predicted to earn. The customers are Fortune 500 media accounts. I ran design for the enterprise products in that stack; this case is about those.

The constraint was domain, not craft. Licensing and territory-level performance are dense, high-stakes, and unforgiving of a pretty interface that gets the model wrong. A programming executive doesn't need a friendlier chart. They need to trust the number under the decision, because the decision commits real money across real markets.

The reframe

A media-analytics tool looks like a reporting product: rows, filters, a cleaner export. I treated it as a decision surface. The screen isn't where someone reviews what already happened. It's where someone commits a catalog to a territory before the outcome exists. Designing it well means designing the moment of judgment, not the display of data.

The work

I built a content-discovery platform that let streaming companies match programming with predicted performance across territories. The design problem was making a prediction legible enough to act on. A number that decides an acquisition has to show its own confidence, or the executive either over-trusts it or ignores it. Both are failures. So the interface had to carry the forecast and the certainty of the forecast at the same time, in a form a non-analyst could commit to.

I led design for the content analytics and licensing tools these media accounts ran on. Licensing automation is where the domain punishes vagueness hardest. Rights, windows, and territories interact in ways that are easy to render and hard to render correctly. The work was getting the model of that complexity right in the interface, so the automation was trustable rather than merely fast.

Underneath all of it, I shipped Whip Media's first design system. Multiple enterprise products, one catalog, one set of primitives. Decide it once as a system, rather than re-deciding it screen by screen forever.

Scroll sideways to view the full diagram.

ONE LANGUAGE, MANY PRODUCTSA green design-system block holds grey primitive chips (tokens, components, patterns, voice) and feeds three grey products below: content analytics, licensing, and content discovery. Green marks the system; grey marks the products.SPECIFICATION · SYSTEMSCALE · PRODUCTTHE SYSTEMTHE PRODUCTSTHE DESIGN SYSTEMdecided once, for the whole suiteTOKENSCOMPONENTSPATTERNSVOICECONTENT ANALYTICSone shared languageLICENSINGone shared languageCONTENT DISCOVERYone shared languageONE LANGUAGE, MANY PRODUCTSshared primitives across an enterprise suiteSHEET 10 / 13N.T.S. · GOLDFOOT.COM
Decision: to give a multi-product platform one shared language, so the tools read as one company to the accounts that depend on them.

The outcome

The content-discovery platform gave streaming companies a way to match programming to predicted performance by territory. The analytics and licensing tools served the media accounts they were built for. The design system became the foundation the enterprise products were built on.

What I'd tell another design exec

Consumer scale isn't only the app in the viewer's hand. It's also the system the industry runs on to decide what that app shows, and that system has to be trusted before it's used.

← All work