“Language isn’t merely a set of unrelated sounds, clauses, guidelines, and meanings; it’s a completely coherent system sure to context and conduct.” — Kenneth L. Pike
Article Continues Under
The online has accents. So ought to our design methods.
Design Methods as Residing Languages#section2
Design methods aren’t part libraries—they’re residing languages. Tokens are phonemes, parts are phrases, patterns are phrases, layouts are sentences. The conversations we construct with customers turn out to be the tales our merchandise inform.
However right here’s what we’ve forgotten: the extra fluently a language is spoken, the extra accents it may help 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 methods should work the identical approach. Inflexible adherence to visible guidelines creates brittle methods that break below contextual strain. Fluent methods bend with out breaking.
Consistency turns into a jail
The promise of design methods was easy: constant parts would speed up improvement and unify experiences. However as methods matured and merchandise grew extra complicated, that promise has turn out to be a jail. Groups file “exception” requests by the a whole lot. Merchandise launch with workarounds as a substitute of system parts. Designers spend extra time defending consistency than fixing consumer issues.
Our design methods should study to talk dialects.
A design dialect is a scientific adaptation of a design system that maintains core rules whereas growing new patterns for particular contexts. Not like 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 Excellent Consistency Fails#section3
At Reserving.com, I realized this lesson the arduous approach. We A/B-tested every thing—shade, copy, button shapes, even brand colours. As knowledgeable with a graphic design training and expertise constructing model fashion 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 excellent 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, sporting thick gloves, scanning dozens of things per minute, many with restricted ranges of English understanding.
Activity 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 selection: abandon Polaris fully, or train it to talk warehouse.
The Start 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 gentle | Darkish surfaces + gentle 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: Activity completion jumped from 0% to 100%. Onboarding time dropped from three weeks to at least one shift.
This wasn’t customization or theming—this was a dialect: a scientific adaptation that maintained Polaris’s core grammar whereas growing new vocabulary for a particular 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 parts to be:
| Tier | Motion | Possession |
| Constant | Undertake unchanged | Platform locks design + code |
| Opinionated | Adapt inside bounds | Platform supplies good defaults, merchandise customise |
| Versatile | Prolong freely | Platform defines conduct, merchandise personal presentation |
Throughout a navigation redesign, we tiered each component. 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 Resolution Ladder#section6
Flexibility wants boundaries. We created a easy ladder for evaluating when guidelines ought to bend:
Good: Ship with current system parts. 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 help it.
The important thing query: “Which choice 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 by shared rules, not cloned parts. One further week of debate over button shade 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 preserve coherence whereas enabling dialects? Deal with your system like a residing 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, evaluation it for core inclusion.
Deprecate with context – retire outdated idioms through flags and migration notes, by no means a big-bang purge.
A residing 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 move the place excellent consistency blocks process completion. Might be cellular customers battling desktop-sized parts, or accessibility wants your customary patterns don’t deal with.
Doc the context: What makes customary patterns fail right here? Environmental constraints? Consumer capabilities? Activity 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 process 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 Part Library#section10
We’re not managing design methods 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% process completion didn’t care that our buttons broke the fashion information. They cared that the buttons lastly labored.
Your customers really feel the identical approach. Give your system permission to talk their language.
