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

CustomersStory

Building calmly at a climate nonprofit, part 2

Lessons from a team that ships calmly.

Building calmlyat a climatenonprofit, part2HALFTONE / JOURNAL
Dee Marsh
Published 2 min read

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer. This post covers what we changed, why, and what it means for you.

#Results

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.

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.

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

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's next

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.

#The constraint

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

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

#Trade-offs

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.

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

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

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

“A cache key must include everything that can change the output, and nothing that cannot.”
Ivo Santos
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos