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

CustomersStory

Inside a university lab, part 2

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

Inside auniversity lab,part 2HALFTONE / JOURNAL
Fen Alvarez
Published 2 min read

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox. This post covers what we changed, why, and what it means for you.

#What's next

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.

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

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#The details

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.

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.

#What we measured

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.

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

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 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 safe path has to be the easy path.”
Ivo Santos

#What changed

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

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