Skip to Content

Iain Broome

Sheffield, UK

Freelance content designer and founder of Clear Language Club.

49 posts

Posts by Iain Broome

13. Trust your users Newsletter

Trauma-informed principles and content design, style guide features, accessible communications and just avoid metaphors.

Hello there

Welcome to a most belated edition of Plain English not-so-Weekly, the newsletter for clear language enthusiasts everywhere.

In short: asked for freelance work, got lots of freelance work, had to prioritise all the freelance work. Sorry! Forgive me. We're back now. And I won't hold you up.

Enjoy the list of juicy links below.

Iain


Applying trauma informed principles to content design

This talk by Rachel Edwards is an important watch if you work with content for people who may have gone through trauma. It's an area I have a fair bit of experience in too and there is so much to consider.

As with most content, I think working collaboratively with users is always the way to go if you can. As Rachel covers in her talk, I too have come up with what I thought were good ideas only to find they were completely wrong when put in front of people with real lived experience.

Basically: speak to and then trust your users.


5 Features of the Best Content Style Guides

Some solid tips here in this post by Erica Mei-mei Feldfeber. I'm always going to encourage you to include practical advice on how to write clear, inclusive and accessible content in your style guide.

Sometimes, it's tempting to just say, 'Hey, you should write clearly!' But style guides are rarely just for writers and plain English types to use. So feel free to give your team the how as well as the what, so to speak.


Accessible communications: A starting point for fostering more inclusive comms

This is a huge and marvellous guide to accessible communications by Christine Fleming, head of digital content at CharityComms. I've added it to my bookmarks and I'm still reading through it, but I really like the practical tips and lovely lists.


The Good, The Bad, And The Jargon

Nice anti-jargon piece with a focus on NGOs and international development by Sarika Bansal. When you ask people what we mean by plain English, a typical answer is: 'getting rid of jargon'. But it's important to really think about what that means, who the jargon affects and what the alternatives might be.

Wherever you work, I can recommend collecting a list of jargon you come across regularly and including better ways of saying stuff in your style guide.


How metaphors can make or break your design

This blog post by John Saito is from 2017. I share it with you because I largely disagree with the bits that refer to using metaphors in writing.

Sure, visual metaphors are often necessary for all sorts of reasons. But there are few reasons to use a metaphor in your writing, unless it's for a specific audience that you are absolutely sure will get it. Or some branding shenanigans.

And if you are writing guidance content or, you know, really important information that helps people live their lives, just avoid metaphors altogether and forever. In fact, may I suggest simply writing in... plain English.


"Language matters. The words we use shape the stories we construct of people and places, and ultimately, the policies and decisions we make. Words can perpetuate dangerous stereotypes of the world’s poorest places. Words can uphold myths of what it takes to “develop” a place."
Sarika Bansal

New reader?

Join a growing community of 550+ plain language champs and start getting advice and resources that help you write clearer, more accessible content.

12. Sensible headings Newsletter

Heading structures, designing accessible and inclusive content, content patterns, and the cost of not using clear language.

Hello there

Welcome to a slightly late, but very much fashionably here now edition of Plain English Weekly, the newsletter for fans of clear language.

I've shared a one-question survey with you for the last two weeks. You can take a look at the results so far to get an idea of what you might collectively like this newsletter to grow into. I'll leave the survey open one more week.

Things in the immediate pipeline:

  • Directory of bookmarks
  • List of complex words and everyday alternatives
  • Training package for teams

This is all going to grow over the next few months, so your support and sharing is very welcome. Many invisible biscuits available as a reward.

Enjoy the links below...

Iain

🎓
Plain English training
Need someone to introduce the principles of plain English to your team? I run practical workshops where we get hands on with your own actual content – imagine! Email iain@verymeta.com to chat.

Why you should use the correct heading structure in your content

Heading structure really is important for lots of reasons. And I have to tell you, I'm a bit of a stickler for it in Word or Google Docs documents too. If I see headings that are just body text made bold, you betcha I'm applying sensible headings to them instead.

Anyway, I found this slightly stilted but informative video while trawling the headings sections of the writing for GOV.UK manual, like one does.


Example of using everyday instead of complex words

Here is a short example of everyday words in action via the Australian government's style guide. Hang around and you'll find lots of other good information and spiffily presented examples too.


How to design accessible and inclusive content (and why it matters)

A mostly practical post here from the UK Design Institute. It includes a couple of examples, some links out to other useful material and this paragraph:

Writing in plain language makes content easier to read and understand for a wider range of users, including people with cognitive or learning disabilities, non-native speakers, and those with limited literacy skills. This means avoiding complex vocabulary, jargon, and acronyms that may be difficult to understand. You should also stick to short sentences that are easy to read, and use active voice instead of passive voice wherever possible. 

Content design patterns

I've spent some time this week thinking about content design patterns in the context of the UK planning system. I know how to live! If you don't know what the heck that means, this post from 2016 by Natalie Shaw remains a fantastic explainer. In fact, here is the gist:

The idea’s this: when someone struggles for a few seconds over a phrase (or anything), it’s only natural to assume that someone else has been in this predicament before. That’s where the repository comes in – it throws up a solution (designed by consensus), and people never have to suffer alone again.

There is a more recent follow-up post too.


The real cost of not using clear language

A few years ago I was asked by GatherContent to run a webinar on plain English, which I have just discovered is still online. However, the one I'm linking you to in the title here is by Christine Cawthorne, who is ace and runs an online community for content folk. Both are part of a large library of webinars that you can go and get stuck into at your leisure (if you give them your email address)


"Headings help users and search engines to read and understand text. For example, they act as signposts for the readers, making it easier for them to figure out what a post or page is about. Headings also define which parts of your content are essential and show how they’re interconnected."
Yoast

New reader?

Join a growing community of 550+ clear language champs and start getting advice and resources that help you write clearer, more accessible content.

11. All of the pages Newsletter

Two tip-top style guides, loads of accessibility resources, thoughts on dumbing down and hey – I'm soon available for freelance work!

Welcome to issue 11 of Plain English Weekly, sent to you by freelance content designer, Iain Broome. That's me. Hello. Again.

Three things!

  1. Thank you to everyone who answered last week's survey that contains just one question. It's still live. I would love your thoughts.
  2. I'm available for freelance work from December! My current project work is unexpectedly going on pause, so if you have a content design, copywriting or clear language challenge, email iain@verymeta.com and give me a toot.
  3. The survey results so far tell me many of you are interested in plain English training. Look out for an online course on the website in the new year. In the meantime, I run practical workshops with teams. Again, toot away.

Okay, that's it. Enjoy your regular programming below.

Iain


Octopus: a visual sitemap tool and website planner

Let's start by recommending this excellent tool for putting together a lovely sitemap. It has a few features that I like, especially the ability to show what they call 'content bricks' on pages within the sitemap.

I've been using Octopus this past fortnight to prototype some information architecture for user research sessions. It allowed me show and test the overall site structure, but then zoom in to cover more detailed blocks of content on key pages. It's great! Go try it!

Oh – in this blog post, the Octopus team explain the content brick method.


Lisa Riemers' incredible collection of accessibility resources

This is a wonderful collection of links from independent content specialist, Lisa Riemers. I'm pretty sure that you'll find lots of useful stuff, but do check out the section on justifying the use of plain English in particular.


Plain language style guidance from Office for National Statistics (ONS)

As you perhaps know by now, I love finding concise and practical style guidelines and here's another one for the list. This is the plain language section of the ONS style guide and it contains some sound advice and good links out to further reading.


Guide to writing in plain language from The Royal Children's Hospital Melbourne

Here's another style guide I quite like, though I can only find it as a PDF. Sorry! Notice the brevity, again. But also the use of examples to show how the guidance can be practically applied. Lovely stuff.

Basically, I think something like this should be the bare minimum for any organisation. You can use the guides I share in this newsletter for inspiration – explore the archive – just make sure your guidance and examples are relevant to you and what you do.


Thoughts on the 'dumbing down' content argument

I've spent most of the last year working on content and doing user research in the world of planning. By crikey, that's a world packed full of jargon and complex language!

You won't be surprised to hear I've found myself on the receiving end of some occasional pushback when explaining the need for clearer language. It's been suggested that complexity is necessary to avoid 'legal challenge' and that planning content is effectively too complicated to change.

You and I both know that's nonsense, of course. But these discussions can be a challenge. That's why I recommend this piece from Sarah Winters and the Content Design London crew to help you explain why plain English is far from dumbing down and all about making content accessible.


How should we draft our privacy information?

Finally this week, we're off to the Information Commissioner's Office (ICO) and there aren't many newsletters that can say that.

First, a massive high-five to the ICO for wanting to write clear privacy information in the first place. Second, let's all make that a high-ten for this detailed and thoughtful guidance. It contains all sorts of sensible suggestions, including user testing your content!

By the way – what's your organisation's privacy policy like? Not so hot as your homepage, right? Remember, we need to wear our clear language hats when working on all of the pages, all of the time.


New reader?

Join a growing community of nearly 550 clear language champs and start getting advice and resources that help you write clearer, more accessible content.

10. What comes next? Newsletter

Building a plain English culture, the case for letter case, another text analysis tool and a tiny survey to find out what you want next.

I'm Iain Broome and this is another edition of Plain English Weekly. Together, we've managed to hit 500 subscribers in just a couple of months. That's way ahead of my expectations, so thank you again for sharing. Please don't stop!

What would you like to see next? I'd love to know.

When you get a spare 30 seconds, I've created a one-question survey to try and find out what plain English information, training or tools you'd find most useful. Just select the magic button and share your thoughts.

And now enjoy this week's links below...

Iain

PS It looks there may be a (potentially large) pause on the project work that's kept me busy for most of this year. If you need an experienced freelance copywriter, content designer or heck, all-round plain English specialist, do get in touch.


Start building a plain language culture today

We start with a nice piece by James Hanington that covers the importance of creating a culture of plain language in an organisation. I've had a go at this a few times and while it's a challenge, it's also perfectly possible. A style guide helps, of course. As does training. But both are pretty useless if there aren't clear standards to aim for and regular support.


Quick guide to plain language (on just nine slides)

Love these short slides by June C, a content design consultant at SPARCK. While I love a comprehensive online course, you can't beat a few good ideas on a handful of screens to get a message across.


Why we use plain English

This absolutely ancient (from 2015) blog post by Ben Clancy, then at the Department for Environment, Food & Rural Affairs (Defra), stands up rather nicely. Sometimes, it really is important to remind people why you use plain English. It can be helpful for your audience, sure. But also colleagues and teams that you work with from day to day.


Making a case for letter case

I mean, I'm team title case all the way and that's certainly the way most style guides I work with do it. That said, this is a good overview of why some people choose title case over sentence case, even if it doesn't make much sense to me. I'm looking at you, Apple. 👀

Oh – I found this via Adam Silver's excellent newsletter for UX and content folk.


TextBuddy: a plain English text analyzer tool

TextBuddy is another online tool that lets you chuck a in load of text so it can tidy things up and spit out a theoretically clearer version. It highlights any complex words, passive verbs and long sentences that the robots think may need an extra full stop or two.


Over time, as each writer within an organization writes and as the organization itself communicates with customers and the public, this co-accountability leads to a culture that prizes writing that is brief, clear, precise, logical—and therefore persuasive.
James Hanington

New reader?

Join a growing community of 500+ plain language champs and start getting advice and resources that help you write clearer, more accessible content.

9. Explain yourself! Newsletter

Clear microcopy, gender-inclusive writing guidelines, how jargon can empower communities, and a fantastic content-related podcast.

Welcome to another issue of Plain English Weekly. 💌

There are almost 500 of you subscribed now and I am slightly blown away by how quickly that has happened!

I think this probably means I have successfully tested whether there is an appetite for plain English-related advice and information? Next step is to ask you about and make a plan for how this humble, infant newsletter can grow into something more helpful and substantial.

All suggestions and feedback welcome, of course. You can reply to this email or contact me in various ways.

Enjoy this week's links...

Iain

PS If you subscribed recently, do explore previous issues where I am sure you will find even more handy clear language content.

🎓
Plain English training!
I run exciting plain English workshops with teams from all sorts of organisations. Email iain@verymeta.com if you'd like to know more about how they work.

UK Home Office design system's readability guidelines

Some super clear language guidelines but also some examples of users who may have access needs and what they may find helpful. They include people who are blind or partially sighted, dyslexic and non-native English speakers.


UX writing: making our microcopy clear, concise and useful

Miles Taylor, now at Torchbox, wrote this while at University of Bristol. It comes from having pulled a load of information together to try and explain the benefits of UX writing and clear content to internal project teams. This is a job that often seems to fall to us content folk. Plain language? Explain yourself!


The international guide to gender-inclusive writing

I only just found this huge guide put together by the Gender-inclusive Language Project and published by UX Content Collective.

...refer to this guide for suggested best practices around using gender-inclusive language to ensure that all people feel welcome and acknowledged in your experiences.

There is so much useful information in here. I've added it to my bookmarks.


The case for jargon

I like this piece by content designer, Amy Hupe, because it acknowledges the nuances of language and even plain English. Yes, in most cases, jargon should be avoided. But jargon can empower people and communities too.

This is a fantastic paragraph:

Jargon always gives power to those who understand it, and takes power from those who don’t. It’s really important that we recognise this and think about who we’re empowering and disempowering when we use jargon.

The Content Strategy Podcast

There are a few great content-focused podcasts and none more so than the Content Strategy Podcast. It's hosted by Kristina Halvorson, who wrote the book on content strategy, and features excellent interviews with content folk from around the world. Go explore the archives and get started.


"Quality, relevant content can't be spotted by an algorithm. You can't subscribe to it. You need people - actual human beings - to create or curate it."
Kristina Halvorson

New reader?

Join a growing community of 475+ plain language champs and start getting advice and resources that help you write clearer, more accessible content.

8. Is it really clear? Newsletter

Examples of plain English, explaining the active voice, how to write hyperlink text and one of the books that started it all.

Welcome to another edition of Plain English Weekly and a lovely big wave (👋) to you. Quick reminder: I'm Iain Broome, a freelance content designer.

Sorry about skipping last week. I did that thing where you say you are going to take some annual leave and then also say, "Hey, don't worry I will somehow find time to not be on annual leave at all!"

We're back now though. Enjoy the links.

Iain

🎓
I run exciting plain English workshops with teams from all sorts of organisations. Email iain@verymeta.com if you'd like to know more about how they work.

How to Write in Plain English (With Examples)

Another concise guide to writing in plain English, this time from Proofed. This one includes examples, which always helps when trying to understand some of the core principles of writing clearly.


Why plain language and Plain English are different

So, this is a good piece. First, it includes some backstory on the Plain English Campaign and an exciting founder rift I didn't know about. But more importantly, it highlights the problem with claiming to write in clear language if you don't test your content with real users. Is it really clear? How do you know?

This is why whenever I run workshops (did I mention I run workshops?), I always introduce plain English alongside the principles of content design. That includes creating content based on user research and evidence. To write clearly, you need to understand who you are writing for and what they want to achieve.


Quick and useful explanation of the active voice

Here is a smashing and very short post on LinkedIn by Hannah Collins, content design lead at Today. Some people find it tricky to spot the difference between the active and passive voice, so I am very much into this kind of concise overview.


How to write hyperlink text for better web accessibility

As you might have noticed if you've been subscribed to Plain English Weekly from the start, the team at Scope share lots of brilliant resources. This piece on link text is excellent and if you or anyone on your team is susceptible to writing links that say 'click here' or something similar, please pass it on!

A long time ago, I also write a blog post about writing good hyperlinks. True story.


Book: Complete Plain Words by Ernest Gowers

Plain Words is one of the earliest and most influential books on the subject of clear language. First published in 1948, some of it is now dated and – as you might guess – there's no mention of the good ol' internet. But it's still a great read and worthy of a place on your bookshelves.


New reader?

Join a growing community of 425+ plain language champs and start getting advice and resources that help you write clearer, more accessible content.