The Case for Slower Design
When teams grow quickly, speed can become the enemy of quality. Here is how we learned to build better by building less.
I spent two weeks last January staring at a design file with 847 components in it. Our system had grown from a tidy library of buttons and inputs into a sprawling set of choices nobody fully understood. Engineers were building from outdated specs. Designers were creating one-off variants instead of reusing what existed. We needed a reset.
The Speed Trap
When we scaled from twelve designers to forty in under a year, we made the classic mistake: we optimized for velocity. Ship faster. Prototype quicker. Iterate relentlessly. But speed without structure creates entropy. By October, we had three button styles, four spacing scales, and a navigation pattern that changed by team.
Consistency is not a constraint on creativity. When designers stop reinventing basics, they have more energy for the work that matters.