Design Dialects: Embracing Flexibility Over Rigid Consistency

Design systems are often treated like manuals—rigid rulebooks that must be followed to the letter. But this approach can stifle creativity and fail to address real user needs across diverse contexts. Just as languages evolve with accents and dialects that preserve core meaning while adapting to local environments, design systems can benefit from a similar flexibility. In this Q&A, we explore the concept of design dialects, how they differ from one-off customizations, and why they are essential for solving real-world problems. Drawing on experiences from Booking.com and Shopify's Polaris system, we examine the pitfalls of excessive consistency and offer insights for building systems that bend without breaking.

What is a design dialect and how does it differ from a custom theme?

A design dialect is a systematic adaptation of a design system that maintains its core principles—the grammar—while developing new patterns for specific contexts. Unlike custom themes, which might change colors or fonts but still follow the same structure, a dialect can alter components, layouts, and interaction patterns to suit a particular user group, environment, or constraint. For example, a dialect for warehouse pickers might enlarge touch targets and simplify language, even if those choices differ from the main system. The key is that the system’s essential logic remains intact; only the vocabulary expands. Dialects are not one-off workarounds but intentional, reusable variations that preserve the system’s identity while serving unique needs.

Design Dialects: Embracing Flexibility Over Rigid Consistency

Why should design systems be considered living languages?

Thinking of design systems as living languages helps us embrace adaptation. Just as English in Scotland has a distinct accent and vocabulary from English in Sydney, design systems can vary across contexts without losing their core meaning. Design tokens act like phonemes, components are words, patterns are phrases, and layouts are sentences. The more fluently a language is spoken, the more accents it can support—because meaning is preserved through context and behavior. A living design system evolves with its environment, incorporating feedback and new use cases. This view shifts the focus from enforcing visual sameness to enabling effective communication. It recognizes that users in different scenarios need different experiences, yet still belong to the same brand ecosystem.

How can rigid consistency become a problem in design systems?

Initially, design systems promised that consistent components would accelerate development and unify experiences. But as products grow complex, unwavering consistency becomes a prison. Teams file hundreds of exception requests, products launch with workarounds, and designers spend more time defending rules than solving problems. When every interface must look identical, context gets ignored. For instance, a desktop-focused button design might fail badly on a dim warehouse scanner with gloved users. The insistence that components never vary leads to poor task completion and frustrated teams. Consistency for its own sake doesn't equal ROI—solving user problems does. Rigid systems break under contextual pressure; flexible systems bend and adapt.

What lesson did the author learn about consistency from Booking.com?

At Booking.com, the author experienced a culture of ceaseless A/B testing—colors, copy, button shapes, even logo colors. Coming from a graphic design background, this seemed chaotic and visually inconsistent. Yet Booking grew into a massive company without ever prioritizing visual consistency. The profound insight was that consistency isn't ROI; solved problems are. By constantly experimenting, Booking prioritized user outcomes over visual uniformity. This taught the author that a design system's true value lies in its ability to drive results, not in appearance alone. The lesson: don't let the pursuit of a pristine system blind you to what actually works for users.

What happened when Shopify's Polaris system was used for warehouse pickers?

Shopify's Polaris was a mature design language optimized for merchants on laptops. When the author's fulfillment team needed to build an app for warehouse pickers—using shared Android scanners in dim aisles, wearing thick gloves, scanning items rapidly, and often with limited English—they were expected to adopt Polaris as-is. The result? Task completion with standard Polaris was 0%. The interface, designed for a different context, was completely unusable. This “Oh, Ship!” moment forced the team to create a design dialect: enlarging touch areas, simplifying language, and rethinking navigation. It showed that adhering blindly to a system can fail users dramatically, and that adaptation is not a compromise—it's a necessity.

How can design systems maintain core principles while adapting to context?

To maintain core principles while adapting, start by defining what is truly non-negotiable: brand values, accessibility standards, and key interaction patterns. These become the “grammar” of the system. Then, allow optional dialects that override less critical aspects—like component size, color usage, or layout density—based on context. Document these dialects as official variations, not exceptions. Use a token-based architecture where contextual values can be swapped without breaking the system. Regularly test dialects with real users to ensure they solve the intended problems. Finally, foster a culture where designers are encouraged to innovate within the system's guardrails, not just follow rules. This approach turns the design system into a tool for empowerment, not constraint.

What is the role of context and behavior in design languages?

As Kenneth L. Pike noted, language is a coherent system bound to context and behavior. The same applies to design. Context dictates what the user is doing, their environment, device, and state of mind. Behavior refers to how they interact—quickly, one-handed, with distractions. A design language that ignores these factors becomes hollow. For example, a checkout flow for a hurried mobile user should differ from a leisurely desktop shopper. Effective design systems define not just components, but also contexts where certain dialects apply. By embedding context and behavior into the system's logic, we create experiences that feel natural and purposeful. This approach acknowledges that no single interface works for every scenario, and that true consistency is about achieving goals, not visual sameness.