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

Customers

What a 12-person studio taught us about speed, part 2

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

Dee Marsh / Ivo Santos
Published 1 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.

#Rolling it out

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.

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.”
Dee Marsh

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

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.

#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 advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

#What's next

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.

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 team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos