Breaking News – Design systems that enforce strict visual consistency are failing in critical real-world contexts, leading to zero task completion rates in some cases, according to a leading UX strategist. The solution, experts say, is to treat design systems as living languages that can develop 'dialects' – systematic adaptations that preserve core principles while bending to specific user needs.
The Failure of Perfect Consistency
At Shopify, the company's Polaris design system – a mature, polished library built for laptop merchants – proved completely unusable for warehouse pickers using shared Android scanners in dim aisles, wearing thick gloves and scanning dozens of items per minute. Task completion rate under standard Polaris: 0%.
"Every element broke under the constraints," said the strategist, who led the fulfillment team. "We had to rewrite the system from the ground up, not just tweak components."
The Dialect Solution
A design dialect is a systematic adaptation of a design system that maintains core grammar while expanding vocabulary for specific contexts. Unlike brand themes or one-off customizations, dialects preserve essential meaning – much like how English spoken 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," said Kenneth L. Pike, a linguist whose work has influenced design thinking. The same principle applies to design systems, argued the strategist, who is a Brazilian Portuguese speaker learning English with an American accent while living in Sydney.
Background: From Promises to Prisons
Early design system promises were clear: consistent components would speed development and unify user experiences. But as systems matured, consistency became a prison. Teams file hundreds of exception requests; products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems.
At Booking.com, the strategist witnessed the opposite. The company A/B-tested everything – color, copy, button shapes, even logo colors – and grew into a giant without ever prioritizing visual consistency. "Consistency isn't ROI; solved problems are," said the strategist, a graphic designer who had previously built brand style guides.
What This Means
For product teams, the implication is stark: rigid design systems break under contextual pressure. Fluent systems bend without breaking. Teams must empower designers and developers to create dialects that adapt tone, spacing, interaction patterns, and component behavior to match specific environments – whether that's a warehouse scanner, an elderly user's tablet, or an in-car interface.
"The more fluently a language is spoken, the more accents it can support without losing meaning," the strategist said. Design systems must learn to speak dialects. Otherwise, they risk being abandoned – or worse, becoming the very barrier they were meant to eliminate.