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

CustomersStory

How a climate nonprofit ships every day

How one team went from a ticket queue to publishing in minutes.

How a climatenonprofit shipsevery dayHALFTONE / JOURNAL
Eli Tanaka
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.

#Results

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.

“Good defaults are invisible until they are missing.”
Eli Tanaka

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

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 advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

#Where we started

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.

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.

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

#What's next

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.

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 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.”
Eli Tanaka
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos