Yeah, I think of it kind of like protocol negotiation. If I speak a technical protocol my conversation partner doesn't, my options are either to get them using my protocol, I switch to a common protocol, or we don't speak. Sometimes, if the topic is important enough, the first and third options are preferable. Other times, particularly in casual conversation, I opt for the second one. I still try to be precise, and that can mean an occasional specialty word and accompanying definition, but it's costly to the conversation and if I'm not careful I can get bogged down in explaining minutia instead of getting to my point. Maybe it's more like treating new concepts economically rather than treating jargon as a discrete protocol, though I tend to think of jargons as protocols, you can kind of add them into a common protocol a la carte. They're just computationally expensive for people absorbing them if they're also trying to follow a conversational thread at the same time, and too many can blow the budget and cause people to tap out, so I try to add only the ones I really need.