Design Systems at Breaking Point: 'Consistency Has Become a Prison', Expert Warns

In a stark warning to product teams worldwide, a leading design systems expert has revealed that rigid adherence to visual consistency is causing projects to fail—citing a case where task completion dropped to zero percent when a standard design system was forced onto a real-world context.

The expert, a former designer at Shopify and Booking.com, argues that design systems must evolve to support "dialects"—systematic adaptations that preserve core principles while bending to specific user needs.

“The more fluently a language is spoken, the more accents it can support without losing meaning,” said Kenneth L. Pike, a linguist whose work on language structure underpins the new approach. “English in Scotland differs from English in Sydney, yet both are unmistakably English.”

The key insight: Consistency is not ROI. Solved problems are.

Background: The Promise and Pitfall of Design Systems

Design systems were originally conceived as component libraries—shared collections of buttons, forms, and patterns that accelerate development and unify user experiences. Tokens served as phonemes, components as words, patterns as phrases, and layouts as sentences.

But as systems matured and products grew more complex, that promise has become a prison. Teams file “exception” requests by the hundreds. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems.

The Failure of Perfect Consistency

At Booking.com, the expert witnessed the limits of consistency-driven design. “We A/B-tested everything—color, copy, button shapes, even logo colors,” they said. “While everyone fell in love with Airbnb’s pristine design system, Booking grew into a giant without ever considering visual consistency. The chaos taught me something profound: consistency isn’t ROI; solved problems are.”

The reality check came at Shopify, where Polaris—a mature design language perfect for merchants on laptops—was mandated for all internal products.

“My fulfillment team had to build an app for warehouse pickers using shared, battered Android scanners in dim aisles, wearing thick gloves, scanning dozens of items per minute, many with limited English understanding,” the expert recalled. “Task completion with standard Polaris: 0%.”

Every design pattern—from button sizes to contrast ratios—failed under extreme environmental constraints. The team had to discard Polaris components almost entirely, building custom interfaces that worked while preserving only the core design tokens (colors, typography hierarchy).

What This Means: The Case for Design Dialects

“A design dialect is a systematic adaptation of a design system that maintains core principles while developing new patterns for specific contexts,” the expert explained. Unlike one-off customizations or brand themes, dialects preserve the system’s essential grammar while expanding its vocabulary to serve different users, environments, or constraints.

Fluent systems bend without breaking. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. The web has accents—so should our design systems.

For product leaders, the lesson is clear: stop measuring success by visual consistency. Instead, measure by task completion, user satisfaction, and business outcomes. When a system prevents a team from solving real user problems, the system must adapt—not the user.

“Our design systems must learn to speak dialects,” the expert concluded. “The conversations we build with users become the stories our products tell. And every story needs room for local accents.”