In a stark warning to the tech industry, a former design lead at Booking.com and Shopify has revealed that strict adherence to visual consistency in design systems has led to catastrophic user failures—including a warehouse app that achieved 0% task completion when using standard components. The expert argues that design systems must evolve to speak 'dialects' that bend without breaking core principles.
"Consistency isn't ROI; solved problems are," the source told reporters today, recounting a decade of experience building design systems at two of the world's largest e-commerce platforms. The revelation comes as thousands of companies struggle with bloated exception processes and workarounds that undermine the very purpose of design systems.
Background
Design systems emerged as a solution to fragmented user experiences, promising consistent components to accelerate development and unify products. However, as systems matured, teams began filing 'exception' requests by the hundreds, and launches relied on workarounds instead of system components. "Designers spend more time defending consistency than solving user problems," the source noted.
Drawing from linguistic theory, the expert proposes a new model: design systems as living languages where tokens are phonemes, components are words, patterns are phrases, and layouts are sentences. "The more fluently a language is spoken, the more accents it can support without losing meaning," they explained, comparing how English in Scotland differs from English in Sydney yet remains unmistakably English.
The Breaking Point at Shopify
At Shopify, the Polaris design system was considered a crown jewel—perfect for merchants on laptops. But when the fulfillment team needed to build an app for warehouse pickers using shared, battered Android scanners in dim aisles, wearing thick gloves, and scanning dozens of items per minute—many with limited English—the system collapsed. Task completion with standard Polaris: 0%.
"Every pixel screamed 'designed for a different world,'" the source recalled. The team eventually built a custom adaptation that preserved core grammar but expanded vocabulary for extreme constraints. That adaptation became a prototype for what the expert now calls a design dialect.
What This Means
A design dialect is a systematic adaptation that maintains core principles while developing new patterns for specific contexts. Unlike one-off customizations or brand themes, dialects preserve the system's essential grammar. The expert contrasts this with Booking.com's approach, where A/B testing everything—color, copy, button shapes, even logo colors—led to chaos but ultimately taught that "solved problems are what matter, not visual consistency."
Industry observers predict a shift from rigid consistency to 'fluent systems' that support multiple dialects. The impact could reach far beyond e-commerce: healthcare, banking, and government services all face contextual constraints that break uniform design. "Design systems must learn to speak dialects," the source concluded. "Fluent systems bend without breaking."
- Key Insight: Consistency becomes a prison when applied universally without contextual adaptation.
- Practical Takeaway: Teams should identify high-stress contexts (e.g., warehouse, field operations, emergencies) and develop dialects before systems crack.
- Next Steps: Companies are urged to audit their design systems for 'zero tolerance' points and create adaptation frameworks.
For more on the linguistic analogy, see the original concept in Background above.