Everyone loves a launch day
Launch day is the most photographed day in the life of a product. There are screenshots, a countdown, someone has made a cake. It is the day the work becomes visible.
It is also, and I say this with love, the least important day.
Because by launch day, every decision that mattered has already been made. The launch is a photograph of your habits. If your team ships in small, honest increments, launch day is calm. If your team hides work for six weeks and hopes, launch day is a hostage situation with better catering.
What we changed
Eighteen months ago we made one rule. Every Friday, something ships. Not something big. Something real. A fix, a copy change, a deleted feature.
The first month was humiliating. We shipped things so small they were almost embarrassing, and you could feel the team thinking: is this what we have been reduced to?
But a rhythm is a strange thing. By month three, the embarrassing small things had quietly removed every excuse for the big things. You cannot say a change is "too risky to ship this week" when you shipped six changes last week.
Three things the habit bought us
First: we stopped being afraid of our own codebase, because we visited it constantly.
Second: our estimates got honest. When you ship weekly, you find out in seven days whether you understood the problem, not in seven months.
Third — and this is the one nobody predicts — arguing got cheaper. When the cost of trying something is one week instead of one quarter, disagreements stop being ideological. You just try it.
The invitation
So here is what I would like you to take from today. Do not copy our product. Copy the Friday.
Pick a day. Pick something small and real. Ship it. Then do it again next week, even when it feels undignified, especially then. The version of your team that exists after a year of Fridays is unrecognisable, in the best way, to the version standing here today.