Corporate jargon is not a sign of expertise. It is often a sign that the writer has not yet figured out what they want to say.

Plain language is not dumbing things down. It is the discipline of saying exactly what you mean, in the fewest words that do the job, in language the reader already understands.

Why jargon spreads

Jargon spreads because it sounds authoritative. "Leverage our core competencies" sounds more strategic than "use what we are good at." "Operationalize the initiative" sounds more serious than "start the project."

It also spreads because it is easier. Jargon is a shortcut. It lets you write something that sounds complete without having to think through what you actually mean.

The problem is that the reader has to do the thinking instead. And often, they cannot.

Common substitutions

  • Leverage → use
  • Synergy → working together
  • Bandwidth → time, capacity
  • Circle back → follow up, talk later
  • Alignment → agreement
  • Operationalize → start, implement
  • Socialize → share, tell people
  • Learnings → lessons
  • Ideation → brainstorming
  • Thought leader → expert

The plain-language test

Read your writing and ask: would a reasonably intelligent person who is not familiar with this organization understand what I am saying? If not, rewrite it.

This is not about writing for the least informed reader. It is about writing clearly enough that the most informed reader does not have to slow down to decode your meaning.

The substitution test: For every piece of jargon, ask: what is the plain-language version? If you cannot answer, you may not know what you mean yet. Figure that out first.

When jargon is appropriate

Technical terms are not jargon. "API," "sprint," and "P&L" are precise terms that mean specific things to people who work with them. Using them with the right audience is efficient, not lazy.

The problem is using technical terms with audiences who do not share the context, or using vague corporate language that sounds technical but means nothing specific.

Starting the habit

The easiest way to reduce jargon is to read your writing out loud before sending it. If you would not say it in a conversation, consider whether it belongs in writing. Most jargon does not survive this test.