Forgive the MS paint.
But as someone who often straddles two different domains of research and knowledge, how does one translate the jargon that is commonly found in one field and effectively communicate it to someone in another without coming off as a jerk?
Note: the intent was to use generally understood words within the field to communicate, not to come off as a jerk.
The example where my attempts to communicate between members of two different worlds and I received an earful was when I was tasked to develop a website with an existing member of a team who had extensive experience with the dept. but not with the technical details of developing a website.
Words like scrum, development cycles, production and development, were foreign to the individual. When I utilized them, I was called well... less than polite words.
After conferring with trusted confidants, I regrouped and re-approached the topic and design specifications while giving plenty of time to explain concepts that I perceived (through verbal, facial and vocal cues) that the individual did not understand. This resulted in a far better working relationship and the project was completed on time.
Now that I reexamine the subject, I can foresee that as a graduate student, inter-disciplinary collaboration with people from widely different academic backgrounds would be necessary, with differing depths of knowledge of necessary skills to complete a given research objective.
It is one thing to take the time to explain, which I don't mind if the person is willing to listen and learn. But at what point do I decide that the cost/benefit of additional units of effort expended results in diminishing returns? To put it more bluntly "you should know this already, I don't have the time to explain it to you".