Comment by CPLX

I don't hate jargon. I actually think jargon, as a concept, is clearly incredibly useful. When done right, you can take ordinary English words that people think they understand but we all don't agree on, and replace them with specific words only used in certain situations -- thus removing ambiguity about their meaning.

In such an instance that fact that normal people don't understand is kind of the point, you don't want people to think they understand when it's a specific or technical concept that has an agreed upon meaning, and they aren't yet familiar.

For example if I call something a "planning meeting" it's different then if I call it a "sprint meeting" as the latter isn't really used outside of a technical context and comes with a bunch of implicit assumptions about how the meeting will be structured and why it exists. While I could simplify it and call it a "planning meeting" in doing so I would actually lose clarity and specificity to those who are familiar with the jargon. Likewise someone unfamiliar might be prompted to figure out what that jargon means before showing up.

That's what jargon is for when used right. Then there's the other way to use it, which is to obscure or distract from the fact that the concepts being presented are too simple or obvious (or tangential) to be insightful at all, and the speaker has nothing to offer. The examples here were of someone doing the latter. Trust me, I was there.