Craft
Designing for teams that ship on Fridays
When release cadence is weekly, design debt compounds weekly too. What we changed to keep up without slowing anyone down.
By Ilias Bat
6 min read
Written by
Ilias Bat
Weekly releases changed how design has to work. Not the craft — the cadence. A team shipping every Friday cannot wait three weeks for a design review, and a design system that requires a review to change will simply be routed around.
Design debt compounds at release speed
When you ship weekly, an unresolved pattern gets copied fifty times before anyone notices. The cost of a shortcut is no longer one screen; it is however many screens shipped before someone catches it.
What we changed
First: patterns get documented the day they are invented, even badly. A rough note in the system beats a perfect note written a month later, because the copies happen in between.
Second: we hold a thirty-minute pattern review every week, not every sprint. Anything unresolved goes on a public list with a name against it. Nothing waits for a quarterly audit.
Design is not the bottleneck it thinks it is
The honest observation from three years of this: design is rarely what holds a weekly release. What holds it is the review that nobody scheduled and the decision nobody was empowered to make. Fixing the calendar fixed more than fixing the workflow did.
The Friday rule
Nothing structural ships on a Friday. Copy, colour, spacing, content — fine. New flows, new components, new navigation — Monday. This costs almost nothing and has saved several weekends.