Skip to content
NewSee how this site publishes in seconds
Halftone

Customers

Building calmly at a hardware startup, part 2

What changed for the people doing the work every day. Lessons from a team that ships calmly. How one team went from a ticket queue to publishing in minutes.

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

#Trade-offs

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.

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's next

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.

“Good defaults are invisible until they are missing.”
Fen Alvarez

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

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

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

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

“The safe path has to be the easy path.”
Fen Alvarez
What atwo-personagency taught usabout speedHALFTONE / JOURNAL

Customers8 min

What a two-person agency taught us about speed

How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.

Hana Pike
How a publicradio newsroomships every dayHALFTONE / JOURNAL

Customers5 min

How a public radio newsroom ships every day

Lessons from a team that ships calmly. How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.

Dee Marsh
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

Lessons from a team that ships calmly. What changed for the people doing the work every day. How one team went from a ticket queue to publishing in minutes.

Jun Calder / Gus Heller