TLAs: Terrible Language Alternative

 

TLAs (or Three Letter Acronyms) are pervasive in many businesses. For example, I work for a PMO that uses many PMI standards, and many of have our PMP. That may be fairly clear here, this is projectmanagement.com after all, but what would someone else think? Every day I hear all sorts of TLAs to describe tools, processes, departments, and even people. What’s worse is that within an organization, various divisions may have different definitions for the same acronyms.

And it’s not just in business. Consider what happens if you hear someone say ‘osha’ – are they talking about the Occupational Safety and Health Administration? Or a character on Game of Thrones? Maybe they meant OSHAA, Ohio High School Athletic Association. It could be an organization- or department-specific term at a workplace.

It can cause a lot of confusion.

That being said, TLAs have a lot of uses as well. Within a group with a shared understanding, they can be helpful shorthand for speedy communication, particularly in a time where so much happens in fly-by hallway conversations and by text.

The key is clarity. We’re PMs, and the bulk of our work is in communication. Acronyms can be great when talking with your team, but stakeholders may give you blank stares. Or worse, they can nod along in understanding, until you realize you were thinking of two different meanings for XYZ.

Domain-specific language is great – if it stays within the domain.

What has been your experience around acronym confusion? How have you resolved confusion?