Why Your Design System Might Be Failing: The Case for 'Design Dialects'
A design system used by one of the world's largest e-commerce platforms failed to complete a single task for warehouse workers using ruggedized Android scanners, exposing a critical flaw in how modern design systems are built. The failure occurred at Shopify, where its Polaris design language—optimized for laptop-based merchants—proved utterly unusable for fulfillment staff working in dim aisles with thick gloves and limited English literacy.
"Consistency isn’t ROI; solved problems are," said a design lead who previously worked at Booking.com, where A/B testing of everything from button shapes to logo colors revealed that rigid visual uniformity often undermines user needs. The lesson: design systems must evolve to speak "dialects"—systematic adaptations that preserve core principles while allowing for context-specific variations.
Background: The Language Analogy
Design systems are frequently compared to languages: tokens are phonemes, components are words, patterns are phrases, and layouts are sentences. But as linguist Kenneth L. Pike noted, language is a "totally coherent system bound to context and behavior." The more fluently a language is spoken, the more accents it can support without losing meaning.
English in Scotland differs from English in Sydney, yet both remain unmistakably English. Similarly, design systems must bend—not break—when faced with different users, environments, or constraints. A Brazilian Portuguese speaker who learned English with an American accent and now lives in Sydney understands this instinctively: adaptation preserves core meaning.
The Promise Broken
Design systems were supposed to accelerate development and unify experiences through consistent components. But as systems matured, that promise became a prison. Teams file hundreds of exception requests, launch workarounds instead of using system components, and spend more time defending consistency than solving user problems.
The solution is not to abandon systems but to teach them to speak dialects. A design dialect is a systematic adaptation that maintains core principles while expanding vocabulary for specific contexts—unlike one-off customizations that undermine coherence.
A Real-World Failure
At Shopify, the fulfillment team faced an "Oh, Ship!" moment: building 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 standard Polaris interface assumed a quiet, desk-bound user with perfect vision and a mouse.
Task completion with standard Polaris: 0%. The team had to break the system—changing button sizes, increasing contrast, using icon-only labels—to achieve any success. This wasn't a one-off exception; it was a dialect needed for an entirely different context.
What This Means
Design teams must shift their mindset from enforcing rigid consistency to enabling fluent adaptation. Consistency is not ROI; solved problems are. When a design system fails to complete even a single task for an entire user group, it's not the users who are wrong—it's the system.
Adopting design dialects means allowing teams to create systematic variations that preserve core grammar while serving specific needs. This requires governance that reviews and approves dialects, not just exceptions. It means treating design systems as living languages, not static libraries.
For leaders, the lesson is urgent: review your design systems for places where consistency has become a prison. Test them against extreme contexts—warehouse floors, mobile-first markets, low-literacy users. If your system can't bend, it will break, and your users will pay the price.
Key actions:
- Audit current design system usage for contexts that force workarounds
- Create governance for dialects, not just components
- Measure success by problem-solving, not consistency scores
- Invest in user research across diverse environments
This article draws on insights from design leaders at Booking.com and Shopify.
Related Articles
- White House AI Policy U-Turn Sinks Crypto Czar David Sacks
- Crypto Retreats as Stock Markets Surge on Geopolitical Optimism: Key Questions Answered
- Unlock Procurement Scalability: How to Deploy Trusted AI Agents for Expert Decision-Making
- 6 Key Developments as Pro-Bitcoin Kevin Warsh Takes the Fed's Helm
- The Evolution of AI Coding Assistants: IBM's 20-Year Quest to Reduce Developer Friction
- Docs.rs Streamlines Default Build Configurations: Fewer Targets, Faster Builds
- How to Understand Bitcoin's Financial Future: Key Insights from Strategy and Blockstream CEOs
- Crypto Markets Rally: Meme Coins Surge, Monero Hits ATH, and Regulatory Developments Unfold