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

CustomersStory

What a two-person agency taught us about speed, part 2

What changed for the people doing the work every day.

What atwo-personagency taught usabout speed,HALFTONE / JOURNAL
Ada Rivers / Cam Okafor
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

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.

  • Report problems in plain language
  • Skip what has not changed
  • Keep the previous version one click away

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

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.

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

#What changed

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

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

#Results

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

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.”
Ivo Santos

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

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.

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

#The constraint

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

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

  • Report problems in plain language
  • Run independent steps in parallel
  • Skip what has not changed
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos