NielsenRealWorldMatch [principle] v1.0.0

Nielsen Heuristic 2: the system should speak the users' language, using words, phrases, and concepts familiar to the user rather than system-oriented terms.

The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.

Attributed To

Jakob Nielsen, 1994

Applies To

• error messages: translating system errors into plain-language user guidance
• UI copy: labels, CTAs, and tooltips that map to users' mental models
• icon semantics: using real-world object metaphors users already recognise
• data display: presenting dates, currencies, and quantities in locale-appropriate formats
• onboarding flows: using the user's domain vocabulary, not product/engineering terms

Counter Examples

• Error dialogs showing raw HTTP status codes ('Error 422 Unprocessable Entity') with no explanation of what the user should do.
• A B2B SaaS dashboard labeling a field 'SFDC_OppID' when users call it 'Opportunity Name'.
• A banking app displaying 'Credit memo applied to your ledger' instead of 'We added a refund of $12.00 to your account'.

NielsenRealWorldMatch [principle] v1.0.0

Nielsen Heuristic 2: the system should speak the users' language, using words, phrases, and concepts familiar to the user rather than system-oriented terms.

The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.

Attributed To

Jakob Nielsen, 1994

Applies To

• error messages: translating system errors into plain-language user guidance
• UI copy: labels, CTAs, and tooltips that map to users' mental models
• icon semantics: using real-world object metaphors users already recognise
• data display: presenting dates, currencies, and quantities in locale-appropriate formats
• onboarding flows: using the user's domain vocabulary, not product/engineering terms

Counter Examples

• Error dialogs showing raw HTTP status codes ('Error 422 Unprocessable Entity') with no explanation of what the user should do.
• A B2B SaaS dashboard labeling a field 'SFDC_OppID' when users call it 'Opportunity Name'.
• A banking app displaying 'Credit memo applied to your ledger' instead of 'We added a refund of $12.00 to your account'.

Sources

Examples

• macOS Trash and Windows Recycle Bin use the real-world metaphor of a physical rubbish bin — users immediately understand 'files go here before permanent deletion'.
• Shopify's checkout uses 'Order Summary' and 'Place Order' — plain terms matching how buyers think about purchasing, not 'Confirm Transaction'.
• Apple's iOS uses 'Tap to Pay' and 'Face ID' — consumer-familiar language rather than 'NFC contactless' or 'biometric authentication'.

Source

• Jakob Nielsen, 'Heuristic Evaluation', in Nielsen & Mack (eds.), Usability Inspection Methods (1994)
• https://www.nngroup.com/articles/ten-usability-heuristics/