Introduction: Beyond a Single Voice
"Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior." This observation by linguist Kenneth L. Pike holds a profound lesson for modern design systems. Just as a living language adapts to its speakers and environments, our design systems must learn to speak in dialects — systematic variations that preserve core meaning while embracing context. The web, after all, has accents. So should our design systems.
Design Systems as Living Languages
A design system is far more than a library of components. It is a living language. Tokens serve as phonemes, components as words, patterns as phrases, and layouts as sentences. The conversations we craft with users become the stories our products tell. Yet many teams have forgotten a key linguistic truth: the more fluently a language is spoken, the more accents it can support without losing meaning. English spoken in Scotland differs from English in Sydney, but both remain unmistakably English. The language bends to context while preserving its core grammar.
As a Brazilian Portuguese speaker who learned English with an American accent and now lives in Sydney, I experience this daily. Our design systems must mirror this flexibility. Rigid adherence to visual rules creates brittle systems that fracture under contextual pressure. Fluent systems bend without breaking.
When Perfect Consistency Becomes a Prison
The original promise of design systems was simple: consistent components accelerate development and unify user experiences. But as systems matured and products grew more complex, that promise has often turned into a prison. Teams file hundreds of "exception" requests. Products launch with workarounds instead of system components. Designers spend more energy defending consistency than solving real user problems.
The solution lies in embracing design dialects — systematic adaptations that maintain core principles while expanding the vocabulary for specific contexts. Unlike one-off customizations or brand themes, dialects preserve the system's essential grammar. They allow teams to speak with different accents without losing mutual intelligibility.
Real-World Lessons in Design Dialects
Learning from Booking.com's Chaos
At Booking.com, I witnessed a stark lesson in the limits of consistency. The company A/B-tested everything — color, copy, button shapes, even logo colors. As a designer with a graphic design background and experience building brand style guides, I found this approach shocking. While the industry admired Airbnb's pristine design system, Booking grew into a giant without ever prioritizing visual consistency. The chaos taught me something profound: consistency isn't ROI; solved problems are.
The Shopify Polaris Wake-Up Call
Later, at Shopify, I experienced a more direct confrontation with rigid design systems. Polaris was our crown jewel — a mature design language perfectly suited for merchants working on laptops. As a product team, we were mandated to adopt Polaris as-is. Then my fulfillment team faced an "Oh, Ship!" moment: we needed to build an app for warehouse pickers using shared, battered Android scanners in dimly lit aisles. Workers wore thick gloves, scanned dozens of items per minute, and many had limited English proficiency.
Task completion with standard Polaris: 0%. Every interaction that worked on a laptop failed in this context.
Humbled, we returned to the drawing board. We stripped away everything that didn't help the picker complete their task faster:
- No brand elements — no colors, icons, or logos
- Content in large chunks using native typefaces for readability on tiny screens
- Large buttons positioned near tactile elements close to the thumb
- Gestures replacing complex controls
- Alert sounds instead of chimes
- Bold contrasts acting as cognitive anchors
- Navigation and layout adapted entirely to the context
The result? Task completion soared to high percentages, with average tasks completed in just two seconds. By speaking a design dialect — stripping the system to its core grammar and adding new vocabulary for the warehouse context — we turned failure into a blueprint for adaptive design.
Conclusion: Embrace the Accents
Design systems must evolve from monoliths to living languages. Consistency is valuable, but it must never become a prison. By embracing design dialects, teams can maintain a coherent brand and system structure while adapting to the unique needs of different users, devices, and environments. The most fluent systems are those that can speak with many accents — because the web is full of contexts, and every context deserves a voice that fits.