“Language will not be merely a set of unrelated sounds, clauses, guidelines, and meanings; it’s a completely coherent system certain to context and conduct.” — Kenneth L. Pike
Article Continues Beneath
The net has accents. So ought to our design programs.
Design Methods as Dwelling Languages#section2
Design programs aren’t part libraries—they’re dwelling languages. Tokens are phonemes, elements are phrases, patterns are phrases, layouts are sentences. The conversations we construct with customers change into the tales our merchandise inform.
However right here’s what we’ve forgotten: the extra fluently a language is spoken, the extra accents it might assist with out dropping which means. English in Scotland differs from English in Sydney, but each are unmistakably English. The language adapts to context whereas preserving core which means. This couldn’t be extra apparent to me, a Brazilian Portuguese speaker, who realized English with an American accent, and lives in Sydney.
Our design programs should work the identical approach. Inflexible adherence to visible guidelines creates brittle programs that break underneath contextual strain. Fluent programs bend with out breaking.
Consistency turns into a jail
The promise of design programs was easy: constant elements would speed up improvement and unify experiences. However as programs matured and merchandise grew extra complicated, that promise has change into a jail. Groups file “exception” requests by the a whole lot. Merchandise launch with workarounds as a substitute of system elements. Designers spend extra time defending consistency than fixing consumer issues.
Our design programs should be taught to talk dialects.
A design dialect is a scientific adaptation of a design system that maintains core rules whereas creating new patterns for particular contexts. In contrast to one-off customizations or model themes, dialects protect the system’s important grammar whereas increasing its vocabulary to serve totally different customers, environments, or constraints.
When Good Consistency Fails#section3
At Reserving.com, I realized this lesson the laborious approach. We A/B-tested all the pieces—colour, copy, button shapes, even brand colours. As an expert with a graphic design schooling and expertise constructing model type guides, I discovered this stunning. Whereas everybody fell in love with Airbnb’s pristine design system, Reserving grew into an enormous with out ever contemplating visible consistency.
The chaos taught me one thing profound: consistency isn’t ROI; solved issues are.
At Shopify. Polaris (https://polaris-react.shopify.com/) was our crown jewel—a mature design language good for retailers on laptops. As a product staff, we have been anticipated to undertake Polaris as-is. Then my achievement staff hit an “Oh, Ship!” second, as we confronted the problem of constructing an app for warehouse pickers utilizing our interface on shared, battered Android scanners in dim aisles, carrying thick gloves, scanning dozens of things per minute, many with restricted ranges of English understanding.
Job completion with customary Polaris: 0%.
Each part that labored superbly for retailers failed fully for pickers. White backgrounds created glare. 44px faucet targets have been invisible to gloved fingers. Sentence-case labels took too lengthy to parse. Multi-step flows confused non-native audio system.
We confronted a alternative: abandon Polaris totally, or educate it to talk warehouse.
The Beginning of a Dialect#section4
We selected evolution over revolution. Working inside Polaris’s core rules—readability, effectivity, consistency—we developed what we now name a design dialect:
| Constraint | Fluent Transfer | Rationale |
| Glare & low mild | Darkish surfaces + mild textual content | Cut back glare on low-DPI screens |
| Gloves & haste | 90px faucet targets (~2cm) | Accommodate thick gloves |
| Multilingual | Single-task screens, plain language | Cut back cognitive load |
Consequence: Job completion jumped from 0% to 100%. Onboarding time dropped from three weeks to 1 shift.
This wasn’t customization or theming—this was a dialect: a scientific adaptation that maintained Polaris’s core grammar whereas creating new vocabulary for a selected context. Polaris hadn’t failed; it had realized to talk warehouse.
The Flexibility Framework#section5
At Atlassian, engaged on the Jira platform—itself a system throughout the bigger Atlassian system—I pushed for formalizing this perception. With dozens of merchandise sharing a design language throughout totally different codebases, we would have liked systematic flexibility so we constructed immediately into our methods of working. The outdated mannequin—exception requests and particular approvals—was failing at scale.
We developed the Flexibility Framework to assist designers outline how versatile they wished their elements to be:
| Tier | Motion | Possession |
| Constant | Undertake unchanged | Platform locks design + code |
| Opinionated | Adapt inside bounds | Platform gives sensible defaults, merchandise customise |
| Versatile | Prolong freely | Platform defines conduct, merchandise personal presentation |
Throughout a navigation redesign, we tiered each factor. Emblem and international search stayed Constant. Breadcrumbs and contextual actions turned Versatile. Product groups may instantly see the place innovation was welcome and the place consistency mattered.
The Choice Ladder#section6
Flexibility wants boundaries. We created a easy ladder for evaluating when guidelines ought to bend:
Good: Ship with present system elements. Quick, constant, confirmed.
Higher: Stretch a part barely. Doc the change. Contribute enhancements again to the system for all to make use of.
Finest: Prototype the best expertise first. If consumer testing validates the profit, replace the system to assist it.
The important thing query: “Which possibility lets customers succeed quickest?”
Guidelines are instruments, not relics.
Unity Beats Uniformity#section7
Gmail, Drive, and Maps are unmistakably Google—but every speaks with its personal accent. They obtain unity via shared rules, not cloned elements. One further week of debate over button colour prices roughly $30K in engineer time.
Unity is a model consequence; fluency is a consumer consequence. When the 2 conflict, aspect with the consumer.
Governance With out Gates#section8
How do you keep coherence whereas enabling dialects? Deal with your system like a dwelling vocabulary:
Doc each deviation – e.g., dialects/warehouse.md with earlier than/after screenshots and rationale.
Promote shared patterns – when three groups undertake a dialect independently, assessment it for core inclusion.
Deprecate with context – retire outdated idioms through flags and migration notes, by no means a big-bang purge.
A dwelling dictionary scales higher than a frozen rulebook.
Begin Small: Your First Dialect#section9
Able to introduce dialects? Begin with one damaged expertise:
This week: Discover one consumer stream the place good consistency blocks job completion. Could possibly be cell customers battling desktop-sized elements, or accessibility wants your customary patterns don’t deal with.
Doc the context: What makes customary patterns fail right here? Environmental constraints? Consumer capabilities? Job urgency?
Design one systematic change: Give attention to conduct over aesthetics. If gloves are the issue, greater targets aren’t “”breaking the system””—they’re serving the consumer. Earn the variations and make them intentional.
Check and measure: Does the change enhance job completion? Time to productiveness? Consumer satisfaction?
Present the financial savings: If that dialect frees even half a dash, fluency has paid for itself.
Past the Element Library#section10
We’re not managing design programs anymore—we’re cultivating design languages. Languages that develop with their audio system. Languages that develop accents with out dropping which means. Languages that serve human wants over aesthetic beliefs.
The warehouse staff who went from 0% to 100% job completion didn’t care that our buttons broke the type information. They cared that the buttons lastly labored.
Your customers really feel the identical approach. Give your system permission to talk their language.
