Why Jargon Is a Wall

Jargon isn't neutral vocabulary that happens to be unfamiliar. It's a gate. The person in the room who doesn't know what "novation" or "star schema" means isn't just missing a word — they're excluded from evaluating the decision the word is embedded in, whether or not anyone intended that. A business analyst's actual job, underneath the title, is standing at that gate and deciding who gets to understand what's being discussed.

Two walls, not one

A capital markets BA doesn't just cross one language barrier — they cross two, in the same afternoon. The trading desk says the settlement failed because of a novation issue and a DvP break. The data team says the fix needs a change to the star schema and a full regression suite before it ships. Neither side is being deliberately obscure; each is using the fastest, most precise vocabulary available within their group. The BA is the only person required to be fluent on both sides of both walls — the industry's and the delivery team's — because nobody else in the room has to stand in the middle.

The translation isn't the term, it's the sentence

The useful form of a decoded term is never a dictionary entry. It's one plain sentence anyone can act on, plus one more sentence of depth for whoever wants it: "Novation means the clearinghouse steps in as the new counterparty to both sides of the trade — your risk is now to them, not to whoever you originally traded with." That's precise, not dumbed down. A definition that takes three paragraphs to read hasn't been translated — it's been transcribed into different words at the same difficulty.

"Why it matters" is the part usually skipped

A plain-language definition without a "why it matters" is only half the translation. Knowing that a star schema is "one big fact table surrounded by lookup tables" doesn't tell a BA anything actionable. Knowing it matters because it's optimized for fast reporting queries, not for the kind of frequent edits an operational system needs, is what turns a definition into judgment — the difference between decoding a word and understanding what it's about to cost you if you get the design wrong.

The one-question check

Before using a term in a room with mixed technical fluency, ask: could I say this in one plain sentence, and do I know why it matters to the decision on the table right now? If either answer is no, the jargon in that sentence isn't precision — it's a wall you haven't found the door for yet.

Capital Markets Jargon Decoder → · Technical Jargon Decoder →