How a public radio newsroom ships every day
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.
Rolling it out
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.
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.
“A cache key must include everything that can change the output, and nothing that cannot.”
Results
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.
- Run independent steps in parallel
- Keep the previous version one click away
- Cache what never changes
What changed
The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.
Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.
- Run independent steps in parallel
- Skip what has not changed
- Report problems in plain language
What we measured
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.
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.
“Measure the time from done to live, and treat every minute of it as a bug.”