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

Customers

Inside a public radio newsroom, part 2

Lessons from a team that ships calmly.

Inside a publicradio newsroom,part 2HALFTONE / JOURNAL
Jun Calder
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#The constraint

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

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.

#What's next

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.

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

#Results

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.

#Where we started

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.

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

#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.

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.

Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos