For instance most people don’t know that even though both CAP and ACID contain consistency, they do not refer to the same idea. In CAP it’s about linearizability, while in ACID it’s about preserving invariants.
But wouldn't people still be unaware of the difference in meaning if the acronyms were spelled out? The word "consistency" appears in both names, with no indication that its meaning is context-dependent. I don't think you can lay the blame for this one at the feet of the acronyms.
You will always have to dumb it down for upper management. As soon as the acronyms come out, they will delay making decisions so that they don't have to take questions or be held accountable. If there is an acronym they use that's spelled the same way but means something totally different, you will have to avoid using yours even when it's the most appropriate term to avoid confusion.
My favorite example is ServiceNow using the term "CI" for "configuration item". You'll have to tell them in a lot more words what the deployment process is. :)