General rules
Use clear, neutral and inclusive language, avoiding stereotypes or terms with social history tied to ethnicity, nationality or cultural identity. See: Voice and tone
Use terms that describe processes, technology or jobs, not people or users. See: User management
Avoid idioms, metaphors or slang that may not translate well across cultures or abilities.
Offensive language list
Below is a list of common UI terms and action labels to avoid and includes recommended alternatives for your product's UI text.
Disclaimer and content warning
The list is incomplete and is revised dynamically and iteratively. Exceptions can be made for varying contexts in product lines, but we list - and recommend - more appropriate alternatives here.
Note: The list contains words that may be considered offensive, sensitive or inappropriate. These terms may be triggering, upsetting or disturbing to some individuals. Viewer discretion is advised.
| Offensive language list | Explanation | Recommended alternative terms |
|---|---|---|
| abort | Evokes sensitive medical associations with pregnancy termination. | • cancel • force quit • stop • end • finalize |
| average user | Implies someone is ordinary or lacks special skills, which can feel dismissive or undervaluing. | • standard user • typical user |
| chain | Associated with a lack of freedom, being limited or restrained. | • sequence (a sequence of operations) |
| dismiss | Implies rejection and suggests something is unimportant, which can feel negative when users are simply finishing a task or acknowledging information. | • close • OK • skip • disregard • ignore • finish (depending on the context) |
| execute | Has violent associations and contributes to an insensitive or unwelcoming UI tone. | • run • start • perform • apply • carry out • conduct • submit |
| grooming | Describes the process of an adult building trust to enable the sexual abuse of children. Is now the dominant associated meaning. | • developing • training • preparing |
| backlog grooming | Associated with manipulative behavior. Scrum associations no longer use the term. | • backlog refinement |
| hang | Evokes imagery of execution by hanging, which can be disturbing for users. Often used in contexts involving system processes or application states. | • freeze • stall • stop responding • become unresponsive |
| kill | Evokes violence and death which can sound aggressive in professional contexts. Used historically for terminating processes and operations. | • stop • close • quit • end |
| master (master / slave) | Reinforces associations with slavery and dominance. May be acceptable when it describes expertise, original versions, or authoritative sources such as "master key" or "master copy". | • source / replica • primary / remote • leader / follower • main branch • host • original • manager |
| mob (programming) | Used for collaborative coding sessions but has negative and aggressive associations outside technical contexts. | • team programming • collaborative coding • ensemble programming |
| penetration testing | Although it has sexual connotations, use in contracts, compliance documents, and technical specifications for legal clarity. | • pen testing • security assessment |
| quantum supremacy | Associated with racial or ideological dominance movements and can be perceived as promoting hierarchical or exclusionary thinking. | • quantum advantage • quantum breakthrough |
| slave | Evokes historical connotations of slavery and oppression. In technical contexts, used to refer to a device or process controlled by another (master) device or process. Industry is shifting away from term. | • primary / replica (databases) • leader / follower (systems) • main / secondary (hierarchy) • controller / peripheral (hardware) • primary / subordinate (processes) |
| terminate | Refers to forcefully ending a process, task, or instance. While standard in technical contexts, "terminate" can carry associations with ending life or destruction. Instead use neutral and clear terms that focus on the purpose of the action. | • end • stop • finish • cancel • shut down • disconnect |
| trigger warning | The term "trigger" can trivialize real trauma responses and is associated with gun and gun violence. See content guidelines below. | • content warning • sensitive content ahead • this section includes descriptions of… |
| turned on / turned off | Outdated, imprecise and often associated with sexual connotations. | • on / off • switch on / switch off |
Official Siemens brand resources regarding this theme are exclusively available for Siemens AG employees and partners and can be accessed here.
How to avoid offensive language
We recommend proactively managing and mitigating the use of offensive language in industrial applications. In avoiding these terms, UX writers can contribute to a professional and respectful software environment.
These guidelines have been designed to support teams and product portfolios in avoiding offensive language.
Cultural sensitivity reviews
Conduct regular reviews of common slang and abbreviations in multiple languages to ensure cultural sensitivity and appropriateness.
Industry and context considerations
Develop an internal list of terms that may be specifically offensive or inappropriate within your industrial context.
Automated filtering
Implement filtering software that utilizes databases of known offensive terms, including variations.
Community guidelines and reporting
Clearly communicate acceptable use policies to users and provide a mechanism for reporting suspicious or offensive usernames.
Regular updates and maintenance
Keep lists and guidelines updated with the latest terms as language evolves, and solicit feedback from users and stakeholders.
Consult expertise
Engage with language experts specializing in content moderation to ensure comprehensive coverage and consult with legal and compliance experts to align with regulations and standards.