When designing a product, terminology can be as important as a product feature or content. Using unrecognizable terms for navigation can make features and content impossible to find. After all, if you can’t find it, it doesn’t exist. To that end, it is generally good UX practice to avoid jargon. But what happens when your users are steeped in jargon?. What should UX practitioners do?
Let’s start with a definition. Merriam-Webster defines jargon as…
- The technical terminology or characteristic idiom of a special activity or group
- Obscure and often pretentious language marked by circumlocutions and long words
- Confused, unintelligible language
Considering the first part of the definition, jargon might be understood by a specialized group of users and therefore, not something you need to avoid. However, for general audiences, jargon can be particularly bad if not harmful to the user experience.
Here are some helpful guidelines to avoid the pitfall of jargon in product design.
- Make sure you have clearly identified the target user of your product
- Understand the nomenclature (the words used in particular discipline 😉
- Use taxonomy validation techniques like “affinity diagraming” or “name that thing”
- Avoid acronyms (TSOHF)
- Use layman’s terms or natural language whenever possible.
- Ask yourself; would my mother, grandmother or uncle understand it?
- Provide simple definitions or examples for questionable terms
- Be sure to remove unnecessary words – keep these short
- Read aloud to a colleague – you may hear something you don’t see
- Write at a sixth-grade reading level