See how this site publishes in seconds

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.

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.

Where we started

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

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 details

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.

This change is rolling out gradually and will reach every workspace by the end of the month.

What we measured

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

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

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.

Run independent steps in parallel

Skip what has not changed

Keep the previous version one click away

Cache what never changes

What's next

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.

Keep the previous version one click away

Cache what never changes

Report problems in plain language

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.

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

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