Cornell just published a study confirming what every engineer has known instinctively: the people who talk about "synergizing paradigms" and "moving the needle" are, on average, worse at their actual jobs than people who speak plainly.
I've never been happier to see academic research validate a gut feeling.
The study
Researchers analyzed performance reviews, peer evaluations, and communication patterns across 4,200 knowledge workers at mid-to-large companies. The finding: there's a statistically significant negative correlation between buzzword density in workplace communication and objective performance metrics.
In human terms: the more corporate jargon you use, the less likely you are to be good at what you do.
The correlation was strongest in middle management. Shocking absolutely no one.
Why this makes perfect sense
Buzzwords are compression artifacts. They let you sound like you're saying something without actually committing to a specific meaning. "Let's align on the go-forward strategy to drive stakeholder value" means nothing. It's noise shaped like language.
People who are good at their work don't need buzzwords because they can describe what they're doing in concrete terms. "I'm reducing API response time from 340ms to 90ms by adding a Redis cache" is a sentence that communicates actual information. "I'm optimizing our technical infrastructure to enhance user experience" is a sentence that communicates nothing.
I've noticed this pattern throughout my career. The best engineers I've worked with speak simply. They say "I don't know" when they don't know. They describe problems in specific terms. They give estimates with actual numbers attached.
The worst performers? They hide behind abstraction. Vague language protects them because you can't hold someone accountable for a commitment they never actually made.
The hiring signal nobody uses
I started screening for this in interviews three years ago. Not formally. I just pay attention to how candidates describe their previous work.
When someone tells me "I spearheaded the digital transformation initiative to streamline cross-functional workflows," I probe deeper. What exactly did you build? What was the measurable outcome? How did you decide on that approach?
About 70% of the time, the buzzword-heavy descriptions collapse under questioning. The person either didn't do the work, didn't understand the work, or is so used to packaging everything in corporate language that they've lost the ability to communicate directly.
The other 30% are just people who've been trained by bad corporate culture to talk that way. They can switch to plain language when prompted. Those people are fine. The culture broke them, not their ability.
What I actually do about this
On my teams, I have an informal rule: if you can't explain what you're working on to a smart 16-year-old, you don't understand it well enough.
This applies to status updates, design documents, project proposals, everything. I want specifics. Numbers. Timelines. Trade-offs described in plain English.
It's not about being anti-intellectual. Technical terminology is fine when it's precise. "We need to shard the database" communicates something specific. "We need to optimize our data architecture" does not.
The difference is precision. Technical terms add precision. Buzzwords remove it.
The bigger point
Language is a window into thinking. Fuzzy language usually means fuzzy thinking. When someone can't describe their work clearly, it's often because they don't understand it clearly.
The Cornell study puts numbers on what good managers have always known: pay attention to how people talk about their work. It tells you more than any performance review framework ever will.
Next time someone in a meeting says "let's circle back to ideate on our synergies," just know: science is on your side when you cringe.