Model features around real-world domain conceptsExpose internal system structures to usersUse entities users already recognizeForce users to adapt to technical abstractionsAlign workflows with real-world processesDesign flows based only on backend logic
Familiar Language
The system uses words, phrases, and concepts that are familiar to users, avoiding technical or internal terminology.
Use everyday language users already know: Payment received
Use technical or developer-centric terms Transaction OK
Match terminology to the user's context Save changes
Assume users understand system jargon Persist data
Keep wording simple and concrete Your order is on the way
Overcomplicate labels with precision Order status: dispatched (ID: 78432)
Human Time and Units
Time, quantities, and measurements are expressed in forms people naturally understand.
Use relative and human-readable time formats About 3 minutes remaining
Expose raw timestamps or system units Progress: 42%
Round numbers to meaningful values 2 items left in stock
Show unnecessary numerical precision Inventory level: 2
Adapt units to user expectations Every Monday
Force users to convert measurements RRULE:FREQ=WEEKLY;BYDAY=MO
Logical Information Order
Information is presented in a sequence that feels natural and expected.
off
on
Joan Baez+1 (555) 123-45671234 Oak Street, Apt 5BSan FranciscoUSA+1 (555) 123-4567USAJoan BaezSan Francisco1234 Oak Street, Apt 5B
Follow real-world or task-based sequencesOrder information by technical priorityGroup related information togetherScatter dependent fields across screensRespect user expectations from similar productsInvent unconventional sequences without reason
Meaningful Feedback
System responses are expressed in terms of real-world outcomes, not abstract system states.
off
on
Send Email
Process Request
Explain what actually happenedShow raw system statuses or codesFocus on user-impacting resultsDescribe internal operationsUse feedback that confirms user intentLeave outcomes ambiguous
Natural Mapping
Controls and outcomes are arranged in a way that mirrors real-world cause-and-effect relationships.
off
on
Bug report
Current behaviorWhen the attribute type is se to number and the controls are shown, the style is not fully consistent with the rest of the design language and design system style.
Component affected mds-input
Align controls with real-world behaviorInvert or obscure cause-effect relationshipsMake outcomes predictable from the actionRequire learning arbitrary interactionsUse spatial consistencyBreak established interaction patterns
Real-World Metaphors
Digital concepts are represented using metaphors users already understand from everyday life.
off
on
Checkout
Wireless Headphones Premium noise-cancelling headphones with 30-hour battery life
Qty: 1$89.99
Smart Watch Fitness tracker with heart rate monitor and GPS
Qty: 2$249.99
Buy items list
Wireless Headphones Premium noise-cancelling headphones with 30-hour battery life
Qty: 1$89.99
Smart Watch Fitness tracker with heart rate monitor and GPS
Qty: 2$249.99
Use widely understood real-world metaphorsInvent obscure or mixed metaphorsKeep metaphors consistent across the systemBreak metaphor rules with unexpected behaviorSupport understanding without explanationRely on metaphors that require learning
Related references and bibliographypotentially outdated
Articles & Posts
Anna Kaley — Match Between the System and the Real World (Usability Heuristic #2)
Systems should speak the users' language with familiar words, phrases, and concepts rather than system-oriented terms. Interfaces that follow real-world conventions and make information appear in a natural and logical order demonstrate empathy and acknowledgement for users. https://www.nngroup.com/articles/match-system-real-world/
Meganne Ohata — Match Between System and Real World
