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

Customers

What a hardware startup taught us about speed, part 2

Lessons from a team that ships calmly.

What a hardwarestartup taughtus about speed,part 2HALFTONE / JOURNAL
Eli Tanaka
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.

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

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.

#Rolling it out

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.

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.

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

#What changed

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.

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

#Where we started

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.

“Good defaults are invisible until they are missing.”
Hana Pike

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

“Good defaults are invisible until they are missing.”
Gus Heller

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

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

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.”
Cam Okafor
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos