From Consistency to Fluency: Why Design Systems Need Dialects
Design Systems as Living Languages
When we think about design systems, we often picture component libraries and style guides. But the truth is more organic: design systems are living languages. Tokens act as phonemes, components as words, patterns as phrases, layouts as sentences. The conversations we craft with users become the stories our products tell.
Yet the key insight we’ve overlooked is that the more fluently a language is spoken, the more accents it can support without sacrificing meaning. English spoken in Scotland sounds very different from English in Sydney, but both are unmistakably English. The language adapts to context while preserving its core. As a Brazilian Portuguese speaker who learned American English and now lives in Sydney, this truth is personal: accents don’t break the language—they enrich it.
Our design systems must work the same way. Rigid visual rules create brittle systems that crack under contextual pressure. Fluent systems bend without breaking, accommodating different environments while retaining identity.
Consistency Becomes a Prison
The original promise of design systems was clear: consistent components would speed development and unify experiences. But as systems matured and products grew more complex, that promise turned into a prison. Teams submit hundreds of “exception” requests. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving real user problems.
What we need instead is for design systems to learn to speak dialects.
What Is a Design Dialect?
A design dialect is a systematic adaptation of a design system that maintains core principles while evolving 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.
When Perfect Consistency Fails: Lessons from Booking.com
At Booking.com, I discovered this lesson through experience. We A/B-tested everything—color, copy, button shapes, even logo colors. Coming from a graphic design background and having built brand style guides, this approach seemed chaotic. While everyone admired Airbnb’s flawless design system, Booking.com grew into a giant without ever prioritizing visual consistency.
The chaos taught me something profound: consistency is not ROI; solved problems are. Perfection in visual uniformity means nothing if the design doesn’t help users achieve their goals.
The Polaris Breaking Point: Shop Floor vs. Laptop Screen
At Shopify, Polaris was our crown jewel—a mature design language optimized for merchants working on laptops. As product teams, we were expected to adopt Polaris as-is. Then my fulfillment team encountered an “Oh, Ship!” moment: building an app for warehouse pickers who use shared, battered Android scanners in dimly lit aisles, wearing thick gloves, scanning dozens of items per minute, many with limited English.
Task completion with standard Polaris: 0%. Every second counted, and the interface simply didn’t work in that context. The system needed a dialect—not a new system, but an adaptation that kept Polaris’s core grammar while altering the vocabulary for extreme conditions.
Embracing Dialects for Real-World Impact
The path forward is not to abandon design systems but to make them fluent. By designating dialects for specific contexts—whether for low-bandwidth connections, accessibility needs, or specialized workflows—you retain the efficiency of a shared language while solving real problems. Key steps include:
- Define core principles that must never change (the system’s “grammar”).
- Identify contextual constraints that demand adaptation (e.g., screen size, input method, user literacy).
- Document dialect patterns as first-class citizens in your system, not exceptions.
- Measure success by task outcomes, not pixel consistency.
Consistency is a means, not an end. When we allow design systems to develop accents, we don’t break the system—we make it more human, more resilient, and ultimately more valuable.