Two years ago we had a small rule: every project had to ship something on Friday. A page, a prototype, a commit, a written recommendation — something visible, sent to the client, closed.
It was the single biggest change to how the studio works.
Why Fridays
Before the rule, we drifted. Meetings happened, Figma files filled up, Slack messages accumulated. Then Monday arrived and nobody was quite sure what had moved.
Shipping on Fridays forced a question every Wednesday: what's going to leave this building in 48 hours? If nothing, we had a problem. If something, we had a plan.
What counts
- A deployed staging URL.
- A commit on
mainwith a screenshot. - A written recommendation with a clear decision.
- A 90-second Loom walking through progress.
- A single decision that unblocks next week.
What doesn't count: "we're still iterating." We're always iterating. That's not an update.
The side effect
The Friday rule accidentally made everyone a better planner. You can't ship on Friday if you haven't scoped on Monday. You can't scope on Monday if you haven't understood the problem the week before.
The rule doesn't make the work go faster. It makes the work go honestly. And that, in the end, is the only kind of speed clients care about.