Breaking News: Design Systems Fail When Consistency Becomes a Prison, Experts Warn
SYDNEY, AU — A growing movement of design leaders is sounding the alarm: the very tools built to unify digital experiences are now suffocating innovation. Design systems, once hailed as the silver bullet for product consistency, are collapsing under the weight of their own rules — forcing teams into costly workarounds and reducing user satisfaction.
“Consistency isn’t ROI; solved problems are,” says Marcelo Somers, a Design Lead at Shopify and former Senior Design Manager at Booking.com. “We’ve forgotten that a fluent language can support multiple accents without losing meaning. Our design systems must learn to speak dialects.”
The Hard Lesson from Booking.com and Shopify
At Booking.com, A/B testing of every element — color, copy, button shapes — revealed that visual consistency rarely correlates with business outcomes. “While everyone fell in love with Airbnb’s pristine design system, Booking grew into a giant without ever considering visual consistency,” Somers recalls.
But the real wake-up call came at Shopify. The company’s Polaris design system, built for merchants on laptops, failed entirely when applied to warehouse pickers using shared, battered Android scanners in dim aisles, wearing thick gloves. “Task completion with standard Polaris: 0%,” Somers reports.
What Are Design Dialects?
Design dialects are systematic adaptations of a core design system that maintain its essential grammar while expanding its vocabulary for specific contexts. Unlike one-off customizations or brand themes, dialects preserve the system’s “phonemes” (tokens), “words” (components), and “sentences” (layouts) while creating new patterns for different users, environments, or constraints.
“Think of English in Scotland versus English in Sydney — both are unmistakably English, but each adapts to context while preserving core meaning,” explains Somers, a Brazilian Portuguese speaker who learned English with an American accent and now lives in Sydney. “Our design systems must work the same way. Rigid adherence to visual rules creates brittle systems that break under pressure. Fluent systems bend without breaking.”
Background: The Rise and Fall of Consistency
Design systems emerged as a solution to fragmented product experiences. Companies like Google (Material Design) and Shopify (Polaris) invested heavily in component libraries, tokens, and guidelines — expecting faster development and unified user experiences.
However, as products grew more complex, teams began filing “exception” requests by the hundreds. Products launched with workarounds instead of system components. Designers spent more time defending consistency than solving user problems. The promise became a prison.
What This Means for Product Teams
Organizations must shift from enforcing rigid consistency to enabling adaptive fluency. This means:
- Embracing design dialects as first-class system extensions — not exceptions.
- Prioritizing solved problems over visual uniformity. Consistency is a tool, not a goal.
- Investing in context-aware systems that automatically adjust tokens and components based on device, environment, or user group.
- Training teams to think of design systems as living languages, not static libraries.
“The most successful systems will be those that can speak in multiple accents while maintaining intelligibility,” Somers concludes. “We need to break the rules — not the system.”