Skip to content
NewSee how fast an edit goes live on this site
Halftone

Customers

What a public radio newsroom taught us about speed

What changed for the people doing the work every day.

What a publicradio newsroomtaught us aboutspeedHALFTONE / JOURNAL
Gus Heller
Published 2 min read

They started with a single project and expanded once the first launch went smoothly. Six months later, every team in the organization is on board. This post covers what we changed, why, and what it means for you.

#Results

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.

What surprised them most was the calm. Launch days used to involve a war room; now they schedule posts the week before and go to lunch.

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

#What we measured

Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

Their editor-in-chief describes the old process as "a ticket and a prayer". Now a reporter fixes a typo and sees it live before they have closed the tab.

  • Skip what has not changed
  • Keep the previous version one click away
  • Report problems in plain language
  • Cache what never changes

#What's next

They started with a single project and expanded once the first launch went smoothly. Six months later, every team in the organization is on board.

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#The details

What surprised them most was the calm. Launch days used to involve a war room; now they schedule posts the week before and go to lunch.

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

“A cache key must include everything that can change the output, and nothing that cannot.”
Ivo Santos

#Rolling it out

Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

Their editor-in-chief describes the old process as "a ticket and a prayer". Now a reporter fixes a typo and sees it live before they have closed the tab.

They started with a single project and expanded once the first launch went smoothly. Six months later, every team in the organization is on board.

Diagram of the request path before and after the change
Figure: the request path, before and after.
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos