0:0018:53

Words mean stuff: Develop a framework for removing biased language at your company

Alyssa Yell 18:53 2023

Some biased terms need a find and replace, others need whole teams

Tech documentation and code bases still carry divisive, disparaging and racist terms, and some sit so deep in commands that removing them can take a number of teams. Alyssa Yell, Senior Staff Technical Editor at Splunk who shaped guidance on biased language in its public style guide, has also worked as the only editor making these calls alone. So how do you decide which words show bias, and which to replace first?

Get a question checklist, a three-tier severity ranking and resources for teams of one

Watch on YouTube

In short

Alyssa Yell, Senior Staff Technical Editor at Splunk, presents a framework for spotting and removing biased language in technical writing and software. She offers a checklist of questions to test whether a term shows bias, a three-tier ranking of how urgently harmful terms should be replaced, and style guides, tools and communities for people who make these decisions alone.

“And just because a term isn't offensive to you that doesn't mean that it isn't problematic for someone else.”
“On the following slides, I'll present some questions that you can ask yourself about a term, but above all, let harm reduction guide your decisions.”

What you will learn

  • Apply a checklist of questions to test whether a term diminishes, excludes, degrades or implies elitism or power.
  • Rank biased terms into first, second and third order concerns to decide what to replace first and how much effort it needs.
  • Distinguish surface fixes in documentation and UI text from changes embedded in code bases and commands that need several teams.
  • Use linters and writing assistants such as the Vale linter with Splunk style rules, Witty Works and woke to catch non-inclusive language.
  • Find peer support through the Inclusive Naming Initiative and the Inclusive Language Advocates LinkedIn group when working alone.

Key takeaways from the speaker

  • Ask yourself questions to determine whether a term shows bias
  • Rank-order the need to replace terminology based on severity
  • Locate outside references who can help if you’re a team of one or otherwise feel like you work in a silo

Details

Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
All career stages
Length
18:53
Published
June 2023

Questions this talk answers

How can I tell whether a word or phrase shows bias?

Ask whether it diminishes others' situation, puts a positive or negative connotation on color, race or people, implies otherness, degrades a group or implies elitism, and whether it makes you uncomfortable, works metaphorically or could be more literal. The more questions you answer yes or possibly, the more likely the term needs replacing.

Which biased terms should be replaced first?

First order concerns, which are egregious, overt or politically charged, should be replaced immediately even if it takes several teams. Second order concerns rooted in war, oppression, appropriation or gender should be strongly considered, and third order concerns that are idiomatic or unclear should be replaced where possible.

What can I do if I am the only person making language decisions at work?

Lean on published guides such as Splunk's, Google's, Microsoft's, Intuit's, Atlassian's and the University of Washington's, and join communities like the Inclusive Naming Initiative's Slack channel, Google group and monthly meeting or the Inclusive Language Advocates LinkedIn group.

Are there tools that flag non-inclusive language while writing or coding?

Yell points to the Splunk style guide rules for the Vale linter, the Witty Works writing assistant for Google Docs and Notion, and the woke config builder, a GitLab project for detecting non-inclusive language in source code.

If language keeps changing, is it worth trying to be inclusive?

Yes. Yell says perfection may never be reached, but that is no excuse not to check your bias, question word choices and consider who you might be excluding.

About this talk

With the increased focus on removing language that actively harms and degrades members of our global community, the tech industry has especially needed to make major changes in its written documentation and software. But how does one determine biased language when they work as a team of one or don’t have a sounding board for what is inclusive and exclusive?

By the end of this talk, you’ll develop a framework of asking yourself important questions to determine whether language shows bias, you’ll rank-order the need to replace existing terminology based on the severity of harm, and you’ll learn about outside resources to consult if you need a shoulder to lean on.

Topics

Related talks

Browse the library

Inclusive AND accessible content

AmyJune Hineline Senior Community Manager, Opensource.com at Red Hat

Everyday words like crazy, guys and culture fit quietly exclude your readers

Beginner Product and design 2022