A design system failure at Shopify resulted in 0% task completion for warehouse pickers using standard components on rugged scanners in dim aisles. This extreme case reveals a growing crisis: design systems that enforce rigid consistency are failing users across diverse contexts, and experts warn the problem is spreading as digital products become more complex.
The solution, according to design leaders, lies in 'design dialects'—systematic adaptations that preserve core principles while developing new patterns for specific situations. 'Our design systems must learn to speak dialects,' said a senior designer involved in the Shopify project. 'Perfect consistency becomes a prison when users face different environments.'
The Failure of Perfect Consistency
At Booking.com, extensive A/B testing revealed that visual consistency did not guarantee success. One designer recalled: 'We tested everything—color, copy, button shapes. While everyone loved Airbnb's pristine system, Booking grew without ever prioritizing visual uniformity. Consistency isn't ROI; solved problems are.'
Yet many organizations still treat design systems as component libraries rather than living languages. This leads to hundreds of exception requests, workarounds, and designers spending more time defending rules than solving user problems.
What Are Design Dialects?
A design dialect is a systematic adaptation of a design system that maintains core grammar while expanding vocabulary for specific contexts. Unlike one-off customizations or brand themes, dialects preserve essential meaning—just as English in Scotland differs from English in Sydney, yet remains unmistakably English. 'Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior,' noted linguist Kenneth Pike in a parallel relevant to design.
The key is flexibility without breaking the system. Tokens act as phonemes, components as words, patterns as phrases, layouts as sentences. Fluent systems bend without breaking under contextual pressure.
Background
The promise of design systems was simple: consistent components accelerate development and unify user experiences. 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.
At Shopify, the Polaris design system—perfect for merchants on laptops—failed entirely for warehouse pickers using shared, battered Android scanners with thick gloves and limited English. 'Task completion with standard Polaris: 0%,' the designer stated. 'We had to create a dialect that preserved core functionality while adapting every interaction for that harsh context.'
What This Means
Design dialects represent a paradigm shift: from rigid consistency to fluent adaptability. Organizations must invest in dialect frameworks that allow teams to create contextual variations without fragmenting the overall system. This requires governance models that distinguish between essential principles and surface-level rules.
Early adopters report faster iteration, lower exception rates, and higher user satisfaction. 'The web has accents. So should our design systems,' concluded the designer. As digital products span more devices, environments, and user needs, the ability to speak dialects may become a competitive necessity.