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

Customers

Building calmly at a university lab

What changed for the people doing the work every day.

Eli Tanaka / Bo Lindqvist
Published 2 min read

Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug. This post covers what we changed, why, and what it means for you.

#Where we started

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#Rolling it out

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.

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.

#Trade-offs

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

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.

“A cache key must include everything that can change the output, and nothing that cannot.”
Bo Lindqvist

#Results

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 changed

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 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.”
Lu Brandt

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

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.

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