Design Systems Must Learn to Speak in Dialects, Experts Warn

Breaking News — Design systems, long hailed as the holy grail of consistent user interfaces, are failing in complex real-world contexts, pushing industry leaders to advocate for a radical shift: allowing systems to develop regional “accents” without breaking core principles.

“The more fluently a language is spoken, the more accents it can support without losing meaning,” says a senior design strategist who worked on systems at Booking.com and Shopify. “English in Scotland differs from English in Sydney, yet both are unmistakably English. Our design systems must work the same way.”

The Problem with Perfect Consistency

Design systems were promised to accelerate development and unify experiences through consistent components. But as products grow more complex, rigid adherence to visual rules creates brittle systems that break under contextual pressure.

Teams file hundreds of “exception” requests. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems. The promise has become a prison.

Consistency isn’t ROI; solved problems are, according to insiders who have seen the damage firsthand.

Case Study: Booking.com — Controlled Chaos

At Booking.com, A/B testing was applied to everything—color, copy, button shapes, even logo colors. While industry peers admired Airbnb’s pristine design system, Booking grew into a giant without ever prioritizing visual consistency.

“The chaos taught me something profound,” recalls the strategist. “Consistency isn’t ROI; solved problems are.”

Case Study: Shopify Polaris – The 0% Task Completion Moment

Shopify’s Polaris design system was considered a crown jewel—perfect for merchants on laptops. But when a fulfillment team faced building an interface for warehouse pickers using shared, battered Android scanners in dim aisles, thick gloves, and limited English, task completion with standard Polaris dropped to 0%.

“Every pixel-perfect guideline collapsed under real-world constraints,” the strategist explains. “We realized we needed a dialect—a systematic adaptation that preserved core grammar but spoke the user’s actual language.”

Background: Design Systems as Living Languages

Design systems aren’t component libraries—they are living languages, explains Kenneth L. Pike, the linguist whose work inspired this approach. “Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior.”

In a design system, tokens are phonemes, components are words, patterns are phrases, layouts are sentences. The conversations built with users become the stories products tell. But without dialects, the language becomes dead.

What This Means: Embrace Dialects, Not Workarounds

Industry experts now call for design systems to learn to speak dialects—systematic adaptations that maintain core principles while developing new patterns for specific contexts, users, or environments.

Unlike one-off customizations or brand themes, dialects preserve the system’s essential grammar while expanding its vocabulary. This approach allows teams to bend without breaking, solving real problems without abandoning the system.

The web has accents. So should our design systems. The shift from rigid consistency to fluent adaptation could define the next generation of digital product design.