Global Admin: Editorial Control for Videos

I designed an editorial management system to replace manual JSON updates for Global’s Video Hub which set us up to build Global Admin, a scalable, and fast CMS for Global Player.

The outcome

Product freed up dozens of hours a month previously spent managing update requests with zero reliance on engineering and eliminated errors.

The system now grown and used across all Global brands enabling better editorialisation of all areas of Global Player and an improved news offering from LBC and The News Agents.

Context and Goals

Content management was controlled by a fragile manual process through a storage.json file, and engineers had to clear cache manually.
All content changes needed to go through Product which meant the editorial team did not have direct control over pages in the Video Hub.
The upcoming expansion to branded video pages made scalability critical.

Increase engagement

Allow the editorial team to respond to content trends without handoff and waiting.

Reduce operational risk

Remove manual edits of storage.json and lower the chance of publishing errors.

Improve efficiency

Decouple editorial workflows from product and engineering teams so content updates could scale.

My role

As a product designer in a cross-functional product squad I led design, created interactive prototypes, and user-tested workflows and shipped the product with the product squad and tech leads. This empowered editors to manage content independently.

Steps in managing video content on Global Player in Global Admin — Workflow steps for managing video content on Global Player in Global Admin.

UI kit documentation for Global Admin — UI kit and design specification

My contribution

Collaborated with senior stakeholders, product, and engineering to define a long-term admin strategy.
Worked with tech leads to define and illustrate a domain model to create a shared understanding of the relationship between Features, Blocks, Collections, Sources, and Content to ensure we are building towards the same conceptual vision and everyone uses the same terms for the same concepts.

Domain model used to align the squad on shared terminology and ownership — Domain model of Global used to align the squad on shared terminology and ownership.

Mapped out editorial jobs-to-be-dones and user flows
Built an interactive prototype used to test editorial workflows: block edits, creating and reordering collections, version conflict handling, and saving blocks.
Conducted usability testing with editors from Capital, Heart, and LBC, gathered qualitative feedback and used it to refine designs

Jobs-to-be-done mapping, user flows, and usability-test findings — Jobs-to-be-done, flows, and usability-test findings.

Worked in a cross functional product squad to deliver and go live with the product and hand over content management to editors.

User stories for delivering the product with the cross-functional squad — Delivery planning and support for the cross-functional squad.