01 Overview

Fill the Gaps

People finish what the AI can't tag.

A working prototype for broadcast media teams.

  • AI-Assisted QC
  • Media Operations
  • Scheduling
  • Design Systems
  • Figma
  • Claude
  • Pen and paper
  • My brain

  • 4

    roles in one console

  • 17

    tables that go full screen

  • 65

    documented components

  • 57

    commits so far

The QC console, pre-filled by the AI

02 The problem

Fewer people, better AI, constant deadlines

  1. Fragment

    A slice of the day

    Each channel's broadcast is cut into fragments. A QC works through each one.

  2. Parameters

    What the AI must fill

    Programme, story, category, place and more. AI fills some; people finish.

  3. Confidence

    When to trust it

    Every suggestion has a score. The console shows when to trust it.

Manual QCs

about 10010% of that

for news channels alone, at the start

AI accuracy

70%90%

when the work reached me

Goals the business set, not results. Nothing is measured yet.

Four roles

  • Quality checkers (QCs)

    Fill what the AI couldn't

  • QC leads

    Who works which queue, and when

  • Admins

    Set up queues; watch the AI

  • Platform owner

    Onboards client organisations

I worked from client screenshots and sketches. Neither is shown here.

Before: a lead allocating work

  1. Pick one date
  2. Auto-allocation runs on load
  3. Scan the grid
  4. Reassign one by one
  5. An edit re-runs it
  6. Re-run to start again

After

  1. Open the shared period
  2. Create the next one
  3. Copy from the last five
  4. Select all unassigned
  5. Reassign to a trained QC
  6. Step through the days

Fewer QCs means each does more. They trust the AI where it's earned.

03 Role & scope

Every design call, in a working prototype

  • Senior UX Designer and prototype builder

  • 2 months

    From August 2026

  • Also designed

    Admin set-up and AI quality dashboards

Decided together

  • The senior business head

    Held the goals and scope

  • The AI coding assistant

    Built screens, laid out options; I chose

04 The QC console

Where a QC spends the day

Console · AI suggestions

From a Use button to pre-filled fields

Tried

Suggestion beside a Use button
Accepting suggestions with Use
  • A suggestion row with a Use buttonReview in place, not opt in.
  • An "AI suggests" tag before each suggestionAn AI icon said it smaller.

Shipped

Reviewing pre-filled values

Fields start filled with the AI's suggestion. A colour-coded score sits inside each.

The QC reviews and corrects. Nothing to accept.

Decided with The senior business head

Console · Timeline

From one fragment to the whole day

Tried

Limited to the fragment
  • A stepped timeline of the fragment onlyStaggered clips were hard to read.
  • A playhead stuck inside the fragmentQCs need what came before and after.

Shipped

Scrubbing the whole day

The track shows the whole day. Only my fragment and edges are editable.

Tags often run across fragment edges.

Decided with The senior business head

05 Scheduling & allocation

Allocation as a decision, not a default

Schedule · Allocation

From auto-allocation to schedule periods

Tried

Re-running auto-allocation
Date ranges per QC
  • Auto-allocation that re-ran after most editsLeads allocate by queue and shift. The grid kept changing under them.
  • A date range per QCTwo views had to agree on dates. One shared period was simpler.

Shipped

One shared schedule period

Both views open on a shared period. Each new period starts empty.

Empty on purpose: allocation is a decision.

Decided with The senior business head

Schedule · Copy and select

From copying the last to choosing

Tried

  • A button copying only the last periodLeads needed any of the last five.

Shipped

Create, copy, select all

Copy Allocation picks from five earlier periods. Select all reassigns a queue fast.

The common case is still one click.

Decided with The senior business head

06 Full-screen tables

Maximise means everything still works

Tables · Full screen

From floating headers to full-page tables

Tried

The header over the table (reproduced)
A sliver of a table (reproduced)
  • Headers lifted above the maximised tableI wanted Add buttons reachable. It broke headings; I reversed it.
  • Pinning the table where it satLong pages shrank it to a sliver.

Shipped

The table covers the page

A maximised table covers everything around it. Only collapse and bulk actions float above.

Decided with The senior business head

Tables · Edit in full screen

From stranded pane to full split view

Tried

The pane left behind
  • Maximising only the AI QC tableIts instructions pane got left behind.

Shipped

Editing in full screen

The instructions pane now expands too. Admins can edit instructions full screen.

My rule: full screen loses nothing.

Decided with The senior business head

Two tried states were never committed. I reproduced them on the current build.

07 Rules that travel

The documents are part of the design

The prototype outgrew its documents. I kept them in step.

System · Rules

From components to rules that travel

Tried

  • A catalogue of components and their statesIt listed parts, not the laws.

Shipped

One section of 65

65 components, each with documented states. Then a portable rulebook of laws.

Decided with The senior business head

08 Checking the work

Reviewed in the browser, not code

I reviewed every change in the browser. All 17 tables were audited full screen.

The same table full screen, covering the page, with only the collapse button above it.A full-screen table with the page title and tabs printing over its column headings (reproduced).BeforeAfter
The bad fix, and its fix. Drag to compare.

What it found

  • Full-screen tables

    Failed in three ways

  • A blank playhead icon

    Now a crosshair

  • Three stale sections

    In the design-system document

Next phase

  • Real reference-table headers

    Replacing provisional ones

  • More reviewers

    Who else reviews the console

← Back to work