I love a good style guide. And I applaud anyone encouraging the use of clear English. But the GOV.UK style guide, produced by the United Kingdom’s Government Digital Service (GDS) for the GOV.UK website (the new portal bringing together all, or most, of the UK’s government websites), is really bugging me. More specifically, the part on plain English (mandatory for all GOV.UK websites) is bugging me.
The GOV.UK style guide urges people writing for the site to:
Use plain English. Don’t use formal or long words when easy or short ones will do. Use ‘buy’ instead of ‘purchase’, ‘help’ instead of ‘assist’, ‘about’ instead of ‘approximately’ and ‘like’ instead of ‘such as’.
We also lose trust from our users if we write government ‘buzzwords’ and jargon. Often, these words are too general and vague and can lead to misinterpretation or empty, meaningless text.
But here’s the list of the “buzzwords and jargon” that the guide says we can do without:
- agenda (unless it is for a meeting)
- collaborate (use ‘working with’)
- commit/pledge (we need to be more specific – we’re either doing something or we’re not)
- deliver (pizzas, post and services are delivered – not abstract concepts like ‘improvements’ or ‘priorities’)
- deploy (unless it is military or software)
- dialogue (we speak to people)
- disincentivise (and incentivise)
- facilitate (instead, say something specific about how you are helping)
- foster (unless it is children)
- impact (as a verb)
- key (unless it unlocks something. A subject/thing isn’t ‘key’ – it’s probably ‘important’)
- land (as a verb. Only use if you are talking about aircraft)
- leverage (unless in the financial sense)
- progress (as a verb – what are you actually doing?)
- promote (unless you are talking about an ad campaign or some other marketing promotion)
- slimming down (processes don’t diet – we are probably removing x amount of paperwork, etc)
- strengthening (unless it’s strengthening bridges or other structures)
- tackling (unless it is rugby, football or some other sport)
- transforming (what are you actually doing to change it?)
Some of these choices I have no quarrel with: overarching, empower, progress (as a verb), for example. And I understand that the site and the language it uses need to be accessible to people of all reading levels, and those who aren’t native English-speakers.
But liaise? Commit/pledge? Focusing? Foster? Streamline? Tackling? Transforming? Is the GDS telling us these words are jargon? Buzzwords? They’re kidding, surely. And why, I wonder, is “going forward” not on the list?
They’re not even applying their own rules: the GDS website describes the service as “a new team within Cabinet Office tasked with transforming government digital services”. Their blog tells us that the GDS team has released “a new version of the home page, which is pretty key”, is working on “exemplar delivery”, and will be working “with the departments to deliver [projects]”. Where’s the pizza?
And here’s the head of the UK Civil Service, Sir Bob Kerslake, in a blog post on staff learning and development:
Whilst a lot of the responsibility for personal development lies with individual civil servants, managers have a key responsibility as well. This is why I am asking managers to put a particular focus on key skills and the Capabilities Plan when they do their Mid Year Reviews. [my emphasis]
It’s not just the random (to my eyes) selection of banned words I find so annoying, or the fact that the folk who produced the list themselves use them so liberally. I use a lot of these words myself in my work: tackle, focus, key, foster…
What bugs me is the lack of guidance – which is surely what a style guide is supposed to provide. If the GDS want to ban words like liaise or combating, then they should suggest alternatives. And tell us why the banned words are so wrong. It’s not as if they’re monstrosities newly coined by management gurus intent on murdering the language.
To be continued.
Other posts you might like:
By Marian Dougan