How a public radio newsroom ships every day
Lessons from a team that ships calmly. How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.
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.
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.
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.
Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.
Run independent steps in parallel
Report problems in plain language
Cache what never changes
Skip what has not changed
Where we started
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.
Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.
Rolling it out
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 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.
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.
What changed
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 team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.
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.
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.