social.design.systems is one of the many independent Mastodon servers you can use to participate in the fediverse.
Social for the design systems community

Administered by:

Server stats:

10
active users

Some concepts are hard for people of various backgrounds to grasp. The usual template I use is: "The <plain language>, you know, <technical term>, ..." I describe something in common terms or example I think the listeners understand, and then I stamp that with technical term. In future conversations I reverse the order: "So that <technical term>, you know the <plain language>, ..." This helps people memorize the meaning.

Why go to this trouble? Why not say "oh yeah the <technical term>, yeah go read so-so's blog|article|book"? Well, I know these busy people aren't going to read it. Also they would have to read the beginning of the book to come up to speed on the technical term.

In communication, it is super important to bring your audience to the same level. I find that if you don't, each person has a different picture of the <technical term> in their head. So when it comes time to coordinate who does what, each person might have different expectations. You need to align everyone in the project for max efficiency.

Amy Lee

It's important not to insult your audience. Assume they know their craft well but you have something to offer. You need to show them how your world intersects with theirs in a way they understand. It needs to be emotional and relevant to them, otherwise they won't care. And once you have the connection and they understand you, then you can use the shortcut technical term. Everytime you say it the audience should recall the structure and nature of the thing.

As you build up this linguistic pyramid, you move into higher concepts. A kind of Bloom's Taxonomy. Since you have guaranteed that everyone has quality knowledge and know what you mean, you can then explain the benefits of your solution at these higher levels. These things take a lot of repetition. But this is how bridges between people are made. It's how one team notices: "hey wait, Team B has been warning us all the time of until now we didn't understand their impact."