The Design System Trap: When Consistency Becomes a Cage

Every design system starts as a solution to inconsistency, and every design system, if left unchecked, eventually becomes an argument for sameness. We've watched teams reach for the existing card component when the actual answer was a completely different layout, simply because the component already existed.

The tell is usually a sentence in a design review: 'we already have a pattern for this.' That sentence is true and useful nine times out of ten. The tenth time, it's the system quietly vetoing a better idea because the better idea is more work to build.

On the Bramwell design system project, we built in an explicit escape hatch: any team could propose a one-off pattern, but had to document why the existing system didn't fit. Over eight months, about 12% of proposals became new system components. The rest were legitimately one-off, and that was fine.

A design system's job is to make the common case fast, not to make the uncommon case impossible. If your system has no recorded exceptions after a year of real use, that's not a sign of a good system — it's a sign nobody felt safe deviating from it.