Corporate jargon is not unclear by accident. It is unclear by function — vague language cannot be proven wrong. Hellbeing on what the jargon is doing and how to stop using it.
Estimated reading time: 4 minutes
Corporate Jargon Is Not Communication. It Is the Avoidance of It.
“Let’s circle back on that.” Translation: I don’t want to decide this now. “We need to leverage our core competencies.” Translation: Do the things we are already good at. “Let’s align on this before we move forward.” Translation: I want to be in the meeting before you do anything. Every piece of corporate jargon translates directly into a simpler sentence. The existence of the jargon version, rather than the simple version, is information. It tells you something about what the speaker is trying to accomplish beyond conveying information.
What the Jargon Is Doing
It is creating distance. Between the speaker and accountability for what they said. Between the listener and the actual content of the message. Between the decision and the moment of making it. “We should explore synergies between our teams” does not commit to anything. It announces the possibility of future commitment without specifying what that commitment would be, when it would happen, or who is responsible for it. The jargon provides the appearance of progress while producing none of the conditions that would allow progress to be assessed.
It is also a sorting mechanism. People who speak the language fluently are inside the group. People who do not, or who ask what it means, are outside the group. The jargon is not obscure by accident. It is obscure by function. It creates a credential — not of knowledge or competence, but of membership. The thought leadership industry runs on this. The corporate meeting runs on this.
The Specific Words Worth Stopping
“Circle back” — say when. “Leverage” — say use. “Synergy” — say work together, or don’t say it at all because usually the concept is either obvious or empty. “Move the needle” — say what specifically should change and by how much. “Bandwidth” — say time and capacity. “Deliverable” — say what you are producing and when. “Stakeholder” — say who, specifically.
None of these translations require more words than the jargon version. Most require fewer. The difference is that the translation makes the content of the statement specific enough to be evaluated, which is exactly what the jargon version was designed to prevent. Specific statements can be wrong. Vague statements cannot be wrong. They can only be unclear, and unclear is a much safer position to be in when the outcome is uncertain.
The Way Out
Say what you mean in the simplest language that accurately conveys it. If you do not know what you mean yet, say you do not know what you mean yet. This is more uncomfortable in the short term and considerably more effective in the medium term. The corporate puppet speaks jargon because jargon is the dialect of the institution and speaking it signals belonging. But belonging to a dialect is not the same as having something to say. The people worth listening to are the ones who can tell you something clearly. Usually they are also the ones who already know this.
More at Infernal Insights.
How To
How to communicate clearly in a corporate environment
- Translate before you speak
Before using a piece of jargon, translate it into plain language first. If “leverage our core competencies” becomes “do the things we are already good at,” say the second version. If you cannot translate it, you probably do not know what you mean yet, which is also useful information.
- Replace vague nouns with specific ones
“Stakeholders” becomes the specific people who need to agree. “Bandwidth” becomes the specific amount of time and capacity available. “Deliverable” becomes the specific thing being produced and by when. Specificity makes statements actionable. Vagueness makes them safe but useless.
- Say when you do not know
Not knowing what you mean yet is a legitimate position. “I don’t have a clear answer on this yet” is more useful than “let’s table this and circle back with aligned thinking.” One is honest. The other is jargon used to avoid saying the first thing.
Frequently Asked Questions
“Circle back” means revisit this later — usually because the speaker does not want to make a decision now. It is useful when you genuinely need more information before proceeding. It is not useful as a deflection when the real message is “I don’t want to deal with this.” If you are using it to delay a decision you have already made, say the decision instead.
Corporate jargon serves two functions: it signals membership in the group, and it creates distance between a statement and accountability for that statement. Vague language cannot be proven wrong. Specific language can. In environments that reward appearance over substance, jargon is the logical dialect because it sounds like communication while carrying very little of its risk.
Say what you mean in the simplest language that accurately conveys it. When in doubt, translate: instead of “leverage our core competencies,” say “use what we’re already good at.” Instead of “align stakeholders,” say “make sure the relevant people agree before we proceed.” Specificity makes communication actionable. Vagueness makes it safe but useless.