1.1. What do we mean by abbreviations?


Abbreviations are an essential part of all languages. Although we tend to avoid using them in interfaces to ensure content is fully understandable in an international context, we sometimes use them due to character limits imposed by certain components. Of course, such usage does not mean leaving our users in confusion. Our core principle is to use abbreviations that are widely known, understood, tested with target users, and that facilitate comprehension during scanning.

1.2. Abbreviations projection in Horizon


We can generally divide them into two:

1.2.1 Abbreviations everyone thinks they know: 

Just writing an abbreviation might cause confusion for users because it’s not always what they think it is. On top of that, abbreviations can make the average user work a little harder to understand what’s being said. Even with all this, if something is super well-known as an abbreviation and you use it all the time in everyday speaking, then that might be okay. But, like any assumption, this one can easily be wrong. 

No matter what the topic is, test out your content. Things might not be as clear as you think. Here’s another thing to remember especially that we mostly use abbreviations to save space. We recommend you avoid using them in a paragraph, especially.

1.2.2 Abbreviations in aviation terminology: 

Obviously, these are more technical and people who already know them will understand them right away. You’ll see these a lot in interfaces designed for businesses talking to other businesses (B2B). Don’t use these kinds of abbreviations in interfaces meant for regular people (B2C).

2. Usage

2.1. Amounts


Use “m” for millions, “bn” for billions, and “k” for thousands in limited spaces. Generally, do not abbreviate amounts in the hundreds to avoid confusion.

Consult with the local UX writer for appropriate abbreviations in other languages.