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

Customers

How a university lab ships every day

What changed for the people doing the work every day.

How a universitylab ships everydayHALFTONE / JOURNAL
Eli Tanaka / Cam Okafor
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

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

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 would do differently

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

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.

“The safe path has to be the easy path.”
Jun Calder

#Trade-offs

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.

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.

#Results

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

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.

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

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

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

Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos