Skip to content
NewSee how this site publishes in seconds
Halftone

CustomersStory

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.

Inside a12-person studioHALFTONE / JOURNAL
Jun Calder / Gus Heller
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 would do differently

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.

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.

  • Skip what has not changed
  • Cache what never changes
  • Keep the previous version one click away
  • Report problems in plain language

#What's next

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.

  • Cache what never changes
  • Run independent steps in parallel
  • Report problems in plain language

#The details

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.

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

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

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

  • Report problems in plain language
  • Skip what has not changed
  • Cache what never changes
  • Keep the previous version one click away

#The constraint

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 changed

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.

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

Customers9 min

Inside a two-person agency

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

Bo Lindqvist