Skip to content
HalftoneJournal
← All articles

Customers

What a two-person agency taught us about speed

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

Dee Marsh

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.

What we would do differently

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.

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

What's next

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.

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.

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.

Results

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.

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.”
Bo Lindqvist

The constraint

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.

“The safe path has to be the easy path.”
Cam Okafor

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

  • Cache what never changes
  • Run independent steps in parallel
  • Skip what has not changed