noabbreviations
If someone sent you this page, don't take it personally. You probably want to be efficient when communicating, but this can actually be a problem. I want our communication to be clear!
Please stop using made-up abbreviations in chat.
You've probably sent something like this:
That's 5 minutes wasted just deciphering what the abbreviations meant.
The real cost of abbreviating
Think about it: the time you save typing "REQ" instead of "requirement" is much less than the time your colleague loses not understanding what you wrote.
- 1 Stop what they were doing to figure out what the abbreviation means
- 2 If they don't know, ask you directly what it means (interrupting their flow)
- 3 Wait for your reply before they can tackle the original problem
Do this instead:
As you can see, you got your answer much sooner, and you didn't make anyone guess what your abbreviations meant.
Examples of problematic abbreviations:
These are abbreviations that are not universal and may confuse your teammates:
When IS it OK to use abbreviations?
- ✓ When they are industry standards (API, URL, HTTP, SQL)
- ✓ When they are officially documented in your company
- ✓ When you have already explained them earlier in the same conversation
What about standard abbreviations?
Some abbreviations ARE widely known: ASAP (As Soon As Possible), BRB (Be Right Back), AFK (Away From Keyboard), API, URL, etc.
The problem is when you create your own abbreviations or use acronyms that only 2 people on your team know. If your colleague has to ask you what it means, then it wasn't standard.
Share this page with teammates who should learn to communicate more clearly in chat :)