People ask what a twenty-four person studio does all week, and the honest answer is that most of it is protected from interruption on purpose. Here is the shape of it.
Monday: one meeting
Everything that needs the whole studio happens on Monday morning and nowhere else. Ninety minutes: what shipped, what is blocked, what changes this week. Every project has a single lead who speaks for it. Nobody presents slides.
The point of the constraint is the other four days. If a decision can wait until Monday, it waits. If it cannot, it belongs to the project lead and not to a meeting.
Tuesday to Thursday: craft time
Three days with no studio-wide calendar. Client reviews are booked inside them, never across them, and always in the afternoon. The morning belongs to the work.
- No internal meetings before 13:00, for anyone, including the founders
- Reviews happen in the browser, on the real build, never on a static board
- A project is walked through by the person who made it, not by an account lead
This is the part most studios say they want and most studios lose first, because a calendar fills from the outside in unless someone defends it. Ours is defended by refusing the meeting, not by scheduling around it.
Craft time is not a perk. It is the only interval long enough for the second idea to arrive.
Friday: shipping and the cut
Friday is for the unglamorous half — production files, handover notes, the components nobody demos. It is also when we cut. Every project ends the week with something removed: a screen that was hedging, a variant nobody chose, a section that existed because the page felt short.
What does not happen
We do not do all-nighters, we do not do weekend pushes, and we have never moved a launch by working longer instead of deciding sooner. Nine years of evidence says the deadline problem is almost always a decision problem two weeks upstream.
None of this is a productivity system. It is a set of refusals, and the refusals are what the clients are actually buying.
.svg)
