The Dictionary Senior Employees Carry
Corporate language isn't a character defect. It's a sorting mechanism.
Last quarter a product manager I know spent ninety minutes at her desk rereading a three-paragraph memo from her CEO. She wasn’t slow. She was trying to work out which of three things was happening: a reorg, a project cancellation, or a layoff.
The memo used the words “sharpening focus,” “doubling down on our most defensible investments,” and “a disciplined posture for the quarters ahead.” It named no team, no project, no date. It was, by any reading, an announcement of something — but the something sat just out of view.
The reason she couldn’t interpret the memo isn’t that she’s bad at her job. It’s that the memo was built to be legible to some readers and opaque to others, and she was on the wrong side of the line.
We treat corporate language as a character defect. The people who write in coded terms get called dishonest, cowardly, political. The assumption underneath is that if everyone were braver and clearer, the language would dissolve. That assumption is wrong, and it’s a disservice to the people who haven’t learned to read it.
Corporate language is an equilibrium. And like every equilibrium, it persists because the people inside it are rewarded for staying there.
Corporate language maintains an equilibrium
Consider what a memo from a department head has to accomplish. It has to inform without committing to outcomes that can’t be guaranteed. It has to align with next quarter’s narrative without contradicting the last three months. It has to satisfy a half dozen stakeholders who want different things, while preserving the writer’s room to renegotiate in six weeks when the landscape shifts. And it has to survive the worst-faith reader in the room: the executive looking for someone to blame when a number misses, the board member who skims the first paragraph and asks the question that decides headcount.
A clear statement fails most of those tests. Clarity commits. It names an owner, a number, a date. Being wrong in writing is survivable for a junior employee but expensive for a director or VP — whose pattern of being wrong becomes the case against them at the next reorg.
So the language adapts. “We will ship X by date Y” becomes “we’re doubling down on X to drive durable value over the coming quarters.” The substitution is intentional: the first sentence is a commitment, the second is a posture. The corporate system rewards postures because postures can be revised quietly and commitments cannot.
This dictionary gets used across functions, up and down the org. A finance lead writing “we’re taking a prudent approach to discretionary spend” is doing the same work as a marketing head “reallocating toward higher-conviction channels” or a general counsel describing a settlement as “a pragmatic resolution.” Each phrase is a costume worn over a more direct sentence that someone decided was too costly to say plainly.
People don’t write this way because they’re bad at their jobs. They write this way because the systems they work inside grade them on it.
Who pays the cost in translation
The corporate dictionary isn’t evenly distributed. It’s acquired by proximity to decision-makers, which is a function of who hired you, whether your manager invested in you, whether you got pulled into the room or left outside it.
There's no dictionary to pass down, because the knowledge isn't a list of definitions. It's pattern recognition built from time and proximity, and both are rationed by the org chart. For example, the tenured employees in the room know what “exploring opportunities in the adjacent space” means. They know it means there’s no owner, no scope, no timeline, and a few quarters of churn before anyone agrees what the work even is. They know because they’ve lived through six versions of the same memo and watched what followed each one.
This raises an important point: the dictionary works as a sorting mechanism; a signal sent at one frequency to people already tuned to receive it, and at another to everyone else. The memo that reads as a warning to a VP reads as a strategic update to a mid-level PM. That’s not a flaw in the communication; that is the intent of the communication.
Newer employees take the memo at face value: they write plans against it, set goals to it, and get blindsided when the initiative dies two quarters later. The signals were always there, and the people meant to read the signals did so, while everyone else waited.
The result is that we’ve built a private language inside professional work. The price of admission to senior roles is fluency in a dialect taught nowhere, acknowledged by no one, and acquired only by recognizing the same pattern again and again. This isn’t exclusion of the obvious kind — nobody is denied a job over their reading comprehension. The exclusion is quieter: it happens at the level of which projects feel real, which executive sponsorship is durable, which “strategic priority” survives the quarter and which is already a dead man walking.
The cost isn’t paid in salaries or titles. It’s paid in which careers compound and which stall: who develops senior judgment and who spends a decade confused about why their good work kept landing on the wrong initiatives.
Acting on the hidden dictionary
An equilibrium can’t be moralized out of existence. The genre of critics telling leaders to “just say what they mean” has run for fifteen years without moving a single quarterly memo. The system is stable because it’s doing exactly what the incentives ask of it.
The inescapable truth is that the language is load-bearing, and the scarcity of understanding is the point. A system in which everyone could read the memo accurately is a system in which the memo can no longer sort who belongs in the room and who doesn’t. That’s not a problem anyone is trying to solve.
The PM who spent the time on the memo was trying to solve a puzzle that was not designed to be solved from her seat. The senior people in the room had already moved on: they’d gotten the message (sent at the frequency she couldn’t receive) and were already acting on it. That’s not a communication failure — that’s the system working exactly as intended.