“Language will not be merely a set of unrelated sounds, clauses, guidelines, and meanings; it’s a completely coherent system sure to context and habits.” — Kenneth L. Pike
Article Continues Beneath
The net has accents. So ought to our design techniques.
Design Methods as Residing Languages#section2
Design techniques aren’t element libraries—they’re dwelling languages. Tokens are phonemes, parts are phrases, patterns are phrases, layouts are sentences. The conversations we construct with customers develop 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 may possibly assist with out shedding that means. English in Scotland differs from English in Sydney, but each are unmistakably English. The language adapts to context whereas preserving core that means. This couldn’t be extra apparent to me, a Brazilian Portuguese speaker, who discovered English with an American accent, and lives in Sydney.
Our design techniques should work the identical means. Inflexible adherence to visible guidelines creates brittle techniques that break beneath contextual strain. Fluent techniques bend with out breaking.
Consistency turns into a jail
The promise of design techniques was easy: constant parts would speed up improvement and unify experiences. However as techniques matured and merchandise grew extra advanced, that promise has develop into a jail. Groups file “exception” requests by the tons of. Merchandise launch with workarounds as an alternative of system parts. Designers spend extra time defending consistency than fixing consumer issues.
Our design techniques should be taught to talk dialects.
A design dialect is a scientific adaptation of a design system that maintains core ideas 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 Excellent Consistency Fails#section3
At Reserving.com, I discovered this lesson the exhausting means. We A/B-tested all the pieces—shade, copy, button shapes, even emblem colours. As an expert with a graphic design schooling and expertise constructing model fashion guides, I discovered this surprising. 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 workforce, we have been anticipated to undertake Polaris as-is. Then my success workforce 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.
Process completion with customary Polaris: 0%.
Each element that labored superbly for retailers failed utterly 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 solely, or train it to talk warehouse.
The Start of a Dialect#section4
We selected evolution over revolution. Working inside Polaris’s core ideas—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 |
Outcome: Process 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 creating new vocabulary for a particular context. Polaris hadn’t failed; it had discovered to talk warehouse.
The Flexibility Framework#section5
At Atlassian, engaged on the Jira platform—itself a system inside 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 instantly 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 gives sensible defaults, merchandise customise |
| Versatile | Prolong freely | Platform defines habits, merchandise personal presentation |
Throughout a navigation redesign, we tiered each ingredient. 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 Determination 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 element 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 by way of shared ideas, not cloned parts. One additional week of debate over button shade prices roughly $30K in engineer time.
Unity is a model final result; fluency is a consumer final result. 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 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, evaluate it for core inclusion.
Deprecate with context – retire outdated idioms by way of 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 movement the place good consistency blocks job completion. Could possibly be cellular customers combating desktop-sized parts, or accessibility wants your customary patterns don’t tackle.
Doc the context: What makes customary patterns fail right here? Environmental constraints? Consumer capabilities? Process urgency?
Design one systematic change: Give attention to habits over aesthetics. If gloves are the issue, larger targets aren’t “”breaking the system””—they’re serving the consumer. Earn the variations and make them intentional.
Take a look at 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 Part Library#section10
We’re not managing design techniques anymore—we’re cultivating design languages. Languages that develop with their audio system. Languages that develop accents with out shedding that 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 fashion information. They cared that the buttons lastly labored.
Your customers really feel the identical means. Give your system permission to talk their language.
