There is a particular way a good idea gets killed in a senior room, and it is not by a better idea. It is by language. The person with the recommendation reaches, under pressure, for the vocabulary they are most fluent in — their specialist language, the framework, the technical scaffolding — and the room, which does not share that vocabulary, hears nothing it can act on. The idea was sound. It died of translation.
Jargon feels like rigour. It is usually the opposite. The leader who cannot explain a complex thing in plain terms has, more often than not, not finished understanding it — they are hiding the unfinished part inside a word that sounds precise and means little to anyone outside the discipline. We need to re-platform to a microservices-aligned target state to unlock strategic optionality is a sentence that asks a board to approve something it cannot see. It is framework-first language, and framework-first language is where decisions go to be deferred, because no one in the room can own a recommendation they cannot restate in their own words.
Executive fluency is the discipline of refusing that hiding place. It is the act of carrying a complex idea across the line into terms the person opposite is accountable for, without diminishing the idea and without burying it. Three of our core systems are nearing end of life. If one fails, we are exposed for weeks. Replacing them now costs this much and buys us this much speed. Here is what I recommend, and here is who would own it. Same decision. No jargon. And now the room can hold it, challenge it, own it — which is the only way a decision ever actually gets made.
There is a test for whether you have done this, and it is unforgiving. Can the person opposite restate your recommendation, in their own words, to someone who was not in the room — and get it right? If they can, you have spoken plainly enough to be owned. If they cannot, you have not made a recommendation; you have made a noise that sounded like one. The jargon that felt like precision was the thing that stopped your idea from being carried out of the room by anyone but you, which means it dies the moment you leave.
Watch the moment it works. A board has spent twenty minutes lost in a technical proposal, nodding politely, deciding nothing. The presenter pauses and says, in effect, let me say what this means for the business. The temperature changes. The chair leans in, not because the idea got better but because it finally arrived in a language they could be accountable for. The questions that follow are real questions — about cost, about timing, about ownership — and a decision becomes possible for the first time in the meeting. Nothing was dumbed down. Something was translated, and translation is what made the decision reachable.
This is a leadership act, not a presentation skill. To strip the jargon is to give up the protection it offers — the protection of sounding expert, of staying inside the discipline where you are safe, of never quite committing to a claim a non-specialist could test. The leader who speaks plainly is choosing to be understood, which means choosing to be challenged, which means choosing to be accountable. That is the foundation everything else in the instrument stands on. You cannot rotate a decision through eight lenses if you can only say it in one language. Plain speech is not the absence of expertise. It is expertise that has finished its work and is willing to be owned.