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

CustomersStory

What a climate nonprofit taught us about speed

What changed for the people doing the work every day.

What aclimatenonprofittaught usHALFTONE / JOURNAL
Jun Calder
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.

#The details

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

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

#Where we started

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

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.”
Ada Rivers

#What we measured

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

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.

#What changed

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

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

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

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

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