As a consequence, we find ourselves translating a lot.
Sometimes it is just different terms:
Marketing: "Permabit Enterprise Archive"
Dev: "clique" or "object store"
Support: "object store"
(Marketing changes names sometimes; dev just goes with what we've generally called it.)
Sometimes it's precision of ideas:
Sales: "When the object store is busy"
Support: "During an some authority transfers resulting from server removal"
Dev: "In phases 4 -7 of an uncontrolled leave"
Sometimes its other things, like avoiding sloppy the use of the word "crash" because that's a scary term to users and to sales.
A good test team will handle this translation seamlessly, using terms and phrasing based on the audience. Much like we are polyglots in the languages we use to code, we need to be polyglots in the language we use to describe features and problems. So look at your "to" list, or at the other attendees in your meeting, and choose your words considerately.