Separate product structure from brand expression
Shared navigation, schedules, video, news, account, and event patterns formed a stable product layer. Theme values and content kept each client experience recognisably their own.
POWERED.BY.LIVE was a greenfield streaming platform for planning, scheduling, ingesting, hosting, and distributing live content.
The challenge 01
One shared platform had to support six client deployments without fragmenting the system, the design process, or the viewing experience.
As lead designer, I worked directly with engineering to establish a responsive white-label system that could support multiple client identities—from multi-day events to single-day broadcasts and multi-screen experiences—without turning each launch into a separate product.
A flexible foundation 02
One product structure, adapted deliberately for every client.



Design decisions 03
Shared navigation, schedules, video, news, account, and event patterns formed a stable product layer. Theme values and content kept each client experience recognisably their own.
Three adaptable template models—single-day custom, single-day multi-screen, and multi-day—covered recurring event formats without treating each new launch as a separate product.
The foundation brought event discovery, schedules, speaker and content pages, streamed viewing, and supporting information into one responsive system across desktop and mobile.
A compact token structure with primitives, semantic roles, and light and dark modes gave engineering a practical way to carry the system into new brand deployments.
Designed to adapt 04
The white-label library paired core product patterns with a structured theming layer, so teams could configure a distinct branded experience while keeping the mechanics of a complex live event coherent.
The outcome 05
The system gave a new product a practical basis for supporting distinct client programmes, live formats, and identities while preserving a common responsive product experience.
How to read these figures. The client count reflects deployments known during my time there; more may have followed. Experience models and token counts describe the design files, not a measured change in delivery speed.
Discuss similar work ↗Let’s connect

For a permanent role, contract, or focused systems engagement, I’d be glad to hear what you’re building.
Connect on LinkedIn ↗