So you print it and post it, or hit ‘send’ – and get an angry reply, or no reply at all. Your cherished customer took offence at something in the document. Not only was all your effort wasted, but you now have to undo the damage to a good relationship.
Most people think that having to be ‘politically correct’ is just a frustrating joke. The press frequently makes fun of po-faced pronouncements about avoiding expressions like ‘the man in the street’ or having to call your cat your ‘companion animal’ instead of your pet.
A quick internet search finds lots of anti-PC websites claiming that it's almost the end of the world as we know it.
This isn't the place for such a debate. Businesses just need to avoid offending customers and staff so let's look at ways to do that while also writing readable documents.
‘He/she’ or, even worse, ‘s/he’ is distracting to a lot of readers, as is alternating ‘his’ and ‘her’ throughout a document. Rewording clunky sentences can sidestep the whole issue. Here are some examples:
|The help desk will be manned between the hours of 09.00 and 17.00 daily.|
|Each staff member should complete his/her expenses by the end of the month.|
You can't avoid male bias by just substituting ‘person’ for ‘man’ wherever you hear it. The story that feminists lobbied to have a large British city renamed ‘Personchester’ is entirely apocryphal.
Sensible alternatives depend on the context. Here are some possibilities:
|Grandfather clause||Exclusion clause|
|And that classic, manhole||Access hole|
Referring to peoples' names can be daunting. Most of you would know to avoid ‘Christian name’ and ‘surname’ but what do you use instead? ‘First name’ and ‘last name’ worked for a while but there are some cultures that put these in a different order.
Safest is to use ‘family name’ and ‘given name’. On a similar note, it's best to avoid BC (Before Christ) and AD (Anno Domini) in dates. Instead, use BCE (Before Common Era) and CE (Common Era).
The accepted usage for people with disabilities is to emphasise that they are people first, thus ‘people with disabilities’ rather than ‘disabled people’.
Basically, the rule is that the condition should not define the person, so someone ‘has diabetes’ rather than ‘is a diabetic’
You need to help your staff avoid writing things that are offensive, while still getting things done in a reasonable time. One way to enable this is to think carefully about the things you have to put into writing often and create a short list of suggested wordings for staff to refer to.
Such a list shouldn't be more than a page or it will be impractical. Staff should know that you expect them to use it.
Ask people to contribute, including the sorts of things they would find offensive. They will see the point, and have some ownership of the whole idea rather than thinking it is just another way of management making their jobs harder.
The important thing to ask them is to consider their reader. This is vital in business writing, but it can get lost in the rush to send something out to a deadline.
You're lucky if writing just gets spell-checked. But anyone who stops to think about their reader would have avoided a mistake we recently heard about. A document describing something as a ‘legal minefield’ was sent to a client in a war zone…