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

CustomersStory

Building calmly at a hardware startup

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

Building calmlyat a hardwarestartupHALFTONE / JOURNAL
Jun Calder / 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.

#What's next

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.

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.

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

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

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.”
Jun Calder

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

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.”
Fen Alvarez

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

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

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 we measured

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.

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.

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

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

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.

  • Cache what never changes
  • Skip what has not changed
  • Run independent steps in parallel
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos