
Write the launch checklist before the code
Launch day goes wrong in boring, predictable ways. Why we write the checklist in week one, and the items that catch most of the 2 a.m. surprises.
Tag
5 posts filed under process. Short essays from the workshop, newest first.

Launch day goes wrong in boring, predictable ways. Why we write the checklist in week one, and the items that catch most of the 2 a.m. surprises.

Why Shipped releases small changes every week instead of saving them up, and what that habit does for risk, feedback and the people paying for the work.

The first screen a new user sees is usually blank. Why we design that screen before the full one, and what it teaches us about the whole product.

Most teams have backups. Far fewer have ever restored one. Why we run a full restore drill every month, and the boring checklist that makes it painless.

Before we write any code, every project gets a single page that says what we're building, what we're not, and how we'll know it worked. Here's the template.
Say hello
Send a few lines about your idea or your stuck project. We'll reply with honest feedback and a rough plan to get it out the door.
How it starts