Skip to content
NewSee how this site publishes in seconds
Halftone

CustomersStory

Building calmly at a climate nonprofit

What changed for the people doing the work every day. Lessons from a team that ships calmly. How one team went from a ticket queue to publishing in minutes.

Building calmlyat a climatenonprofitHALFTONE / JOURNAL
Cam Okafor
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#What we measured

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.

#Trade-offs

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.

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 safe path has to be the easy path.”
Lu Brandt

#Where we started

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

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.

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.

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.

  • Run independent steps in parallel
  • Keep the previous version one click away
  • Skip what has not changed
What atwo-personagency taught usabout speedHALFTONE / JOURNAL

Customers8 min

What a two-person agency taught us about speed

How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.

Hana Pike
How a publicradio newsroomships every dayHALFTONE / JOURNAL

Customers5 min

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.

Dee Marsh
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

Lessons from a team that ships calmly. What changed for the people doing the work every day. How one team went from a ticket queue to publishing in minutes.

Jun Calder / Gus Heller