"Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior." — Kenneth L. Pike
The web has accents. So should our design systems.
Design Systems as Living Languages
Design systems are more than component libraries—they function as living languages. Tokens act as phonemes, components serve as words, patterns form phrases, and layouts create sentences. The conversations we build with users become the stories our products tell. But what we've often overlooked is this: the more fluently a language is spoken, the more accents it can support without losing meaning. English spoken in Scotland differs from English spoken in Sydney, yet both are unmistakably English. The language adapts to context while preserving core meaning. As a Brazilian Portuguese speaker who learned English with an American accent and now lives in Sydney, I've experienced this firsthand. Our design systems must work the same way. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking.
The Pitfalls of Rigid Consistency
The promise of design systems was simple: consistent components would accelerate development and unify experiences. But as systems matured and products grew complex, that promise became a prison. Teams file "exception" requests by the hundreds. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems. Our design systems must learn to speak dialects.
Defining Design Dialects
A design dialect is a systematic adaptation of a design system 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 while expanding its vocabulary to serve different users, environments, or constraints.
Case Study: Booking.com – When Consistency Takes a Backseat
At Booking.com, I learned this lesson the hard way. We A/B-tested everything—color, copy, button shapes, even logo colors. As a professional with a graphic design education and experience building brand style guides, I found this shocking. While everyone fell in love with Airbnb's pristine design system, Booking grew into a giant without ever considering visual consistency. The chaos taught me something profound: consistency isn't ROI; solved problems are.
Case Study: Shopify Polaris – The Warehouse Picker Challenge
At Shopify, Polaris was our crown jewel—a mature design language perfect for merchants on laptops. As a product team, we were expected to adopt Polaris as-is. Then my fulfillment team hit an "Oh, Ship!" moment, facing the challenge of building an app for warehouse pickers using our interface on shared, battered Android scanners in dim aisles, wearing thick gloves, scanning dozens of items per minute, many with limited English understanding. Task completion with standard Polaris: 0%.
Breaking the Rules, Not the System
To implement design dialects effectively, start by identifying core system principles that cannot change—these are the language's grammar. Then, for each new context, allow variations in vocabulary (component variations), syntax (layout adjustments), and even some phonological shifts (token substitutions). The key is systematic adaptation: document the dialect, share it back to the core system, and evolve both. This approach solves the warehouse picker problem without destroying Polaris. The picker app got its own dialect: high-contrast colors, oversized touch targets, voice-enabled interactions, and simplified language. Task completion soared.
Conclusion: Solved Problems Over Perfect Consistency
Design systems are not style guides to be enforced; they are languages to be spoken. And every language develops regional dialects. Embrace them. Allow your system to breathe and adapt. The goal is not pixel-perfect consistency—it's solving real user problems with coherence and flexibility. Break the rules, but not the system.