Beyond Rigid Consistency: How Design Dialects Make Systems More Resilient

Introduction: Design Systems as Living Languages

"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

Beyond Rigid Consistency: How Design Dialects Make Systems More Resilient

Just as spoken languages evolve accents and dialects based on geography and culture, our digital design systems must develop their own regional variations to remain effective. A design system isn't a static library of components—it's a living language. Tokens serve as phonemes, components as words, patterns as phrases, and layouts as sentences. The conversations we build with users become the stories our products tell.

Yet many organizations treat design systems as rigid rulebooks, forgetting that the more fluently a language is spoken, the more accents it can support without losing meaning. English in Scotland differs from English in Sydney, but both remain unmistakably English. The language adapts to context while preserving core meaning. This lesson resonates deeply for me as a Brazilian Portuguese speaker who learned English with an American accent and now lives in Sydney.

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 Trap of Perfect Consistency

The promise of design systems was simple: consistent components would accelerate development and unify experiences. But 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. Designers spend more time defending consistency than solving user problems.

This doesn't mean consistency is worthless—it means that consistency for its own sake can undermine the very goals it was meant to achieve. Instead, we need design systems that speak dialects.

What Is a Design Dialect?

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.

Lessons from Booking.com: Consistency Isn’t ROI

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. Booking.com’s relentless focus on empirical testing meant that every design decision was validated by user behavior, not aesthetic purity. That approach allowed the product to adapt to diverse global markets—a form of natural dialect formation.

Shopify Polaris: A Cautionary Tale

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 as we faced 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 levels of English understanding.

Task completion with standard Polaris: 0%.

Every component that worked beautifully on a high-resolution monitor failed catastrophically in the warehouse. Buttons were too small for gloved fingers. Color coding was invisible in poor light. Text-heavy labels were incomprehensible to non-native speakers. The system had no built-in flexibility to adapt to this extreme context.

What We Needed: A Warehouse Dialect

What we needed wasn't a new design system—it was a dialect of Polaris. A version that retained the core logic (consistent data structures, API patterns, brand identity) but introduced new components: extra-large touch targets, high-contrast mode, speech-to-text input, simplified icons, and multilingual text toggles. These would be official variants, not hacks.

How to Design for Dialects

Creating a design dialect doesn't mean abandoning your system. It means building flexibility into the foundation. Here are practical steps:

Identify contextual breakpoints: Not screen sizes, but environmental factors—lighting, input method, user skill level, cultural norms.
Define core vs. peripheral elements: Which tokens and components are truly universal, and which can vary by context? For example, type scale and spacing might be core, while button size and color palette can be peripheral.
Use token-level theming: Design token systems allow you to swap values without rebuilding components. A warehouse theme can override spacing and color tokens while keeping the component structure intact.
Document dialect variations: Treat each dialect as a first-class citizen in your design system documentation. Show when and why to use each variant.
Test with real users in real conditions: Just as Booking.com A/B tested relentlessly, testing your dialect in its actual environment is essential. That 0% task completion rate would have been caught early with proper contextual testing.

Conclusion: Bend, Don’t Break

Language is bound to context and behavior, as Kenneth Pike reminded us. Design systems must be equally bound—not to a single visual expression, but to the many contexts where they are spoken. A system that can produce dialects is not weaker; it is stronger. It adapts without losing identity.

The next time your team considers filing an exception request, ask instead: "Can we turn this into a dialect?" By doing so, you preserve the system while solving real user problems. That’s how design systems grow from prisons into living languages.