The failure mode that bites design systems teams hardest is not technical. It is mismanagement, and it shows up as too many people in the room with too many opinions.

Button color is the canonical example. Everyone benefits from a consistent palette, since users need to know what to click and designers shouldn't pick from a smorgasbord of options. The hard question at the outset isn't which colors to choose, though — it's how many people are in that room. Three people discussing buttons is fine. Twenty is a serious problem, because it means energy is being spent on the wrong things. Setups like this suggest design systems aren't really about design or even about systems, but about managing people's time, attention and focus.

Why a bigger meeting produces worse decisions

The counterintuitive part of a first large design systems project is that effectiveness falls as headcount rises. The hardest problem turned out to be the too-many-people-in-a-meeting one, not TypeScript, component accessibility or audits.

The dynamic follows the familiar observation from Jason Fried and DHH that asking one more person for their take only makes you less sure:

If you want to be even less sure about something, all you have to do is ask one more person what their take is.

The result is a sense that change is impossible, that no decision can be made without massaging every ego present. Paul Ford's description of the web's fundamental question — "Why wasn't I consulted," abbreviated WWIC — captures the underlying drive: humans need to be consulted, engaged, to exercise their knowledge and thus their power. What shocks newcomers to large organizations is how that instinct scales, until everyone must be consulted to make the smallest decision. The more people who must be consulted to get something done, the more bureaucracy the company carries. Design systems cannot be effective in bureaucratic organizations.

CSS-Tricks star logo

Drawing the line

Someone on a large design team eventually has to decide who leaves the room. It sounds mean, but it is the kind thing to do: when everyone has opinions, nothing gets done, and rifts open once some opinions are heeded and others are shunned.

That doesn't mean feedback is unwelcome — feedback should always be welcome. The distinction is between voicing an opinion on every tiny UI detail and having a designated group own the decision. One of the main advantages of a design systems team is precisely that it offsets those decisions onto someone else, and someone has to draw the line on who is allowed to care about what. Doing so makes the system faster to build and less stressful to maintain.