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

CustomersStory

How a public radio newsroom ships every day, part 2

What changed for the people doing the work every day.

How a publicradio newsroomships every day,part 2HALFTONE / JOURNAL
Eli Tanaka / Dee Marsh
Published 2 min read

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox. This post covers what we changed, why, and what it means for you.

#What changed

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.

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#Results

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

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.

“The safe path has to be the easy path.”
Bo Lindqvist

#What's next

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.

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.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#What we would do differently

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

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.

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

#What we measured

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.

“Measure the time from done to live, and treat every minute of it as a bug.”
Cam Okafor

#Trade-offs

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.

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

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.

  • Keep the previous version one click away
  • Run independent steps in parallel
  • Skip what has not changed
  • Cache what never changes
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos