As product leaders, we have the ability to set the tone in product teams and working groups. For the culture of the ream, it is therefore necessary that the language we use be inclusive and accurate. Using appropriate terminology is a vital part of being an effective communicator. Using inclusive language is a way of showing consideration for everyone we work with, and goes far beyond asking someone their pronouns (though that is important too!)
Once you begin to really listen, using inclusive vocabulary simply makes more sense. It is often times more illustrative and interpretable, in addition to being more welcoming. The most important thing is to avoid hurtful, stereotypical language that makes groups or individuals feel excluded, misunderstood, and/or disrespected. One way to do that is by focusing on plain language, which is words or phrases your audience can understand the first time they read or hear it, no cultural context needed.
The Information Technology team at University of Washington put together a site that explains why language is important in IT as well as problematic vocabulary and substitutes. This is the best resource I’ve seen regarding specific language used in technology teams. And it is not just academic institutions evaluating and changing their language. Github renamed their branches in 2020 to move away from previous language that had racist origins. Buffer has an informative article that is a bit of a primer about thinking through the greater principles of inclusive language in technology.
STAND-UP EXERCISE
Have your teams look through the list put together by UW-IT. What language have they found themselves or their teams using that is on this list? What has made them uncomfortable in the past? What alternatives might be acceptable?