More good stuff on plain language basics in the Australian government's style guide:
There are 4 basic elements of plain writing. If you consider these elements, you’ll be well on the way to writing in plain language. They are: structure, word choice, active voice, short sentences.
I really like the last section that explains why plain language benefits everyone. Always worth reminding yourself. And anyone who'll listen.
Time to head into the BBC Bitesize archive for you to meet Frieda Fishmonster. I'm not saying you have to complete these activities as a way of testing your clear language skills, but would it hurt? I won't tell anyone.
This is a great post about designing for people with anxiety by Demelza Feltham on the Tetra Logical blog.
A lot of the ideas (or considerations) here are rooted in principles of good design and writing in clear language. But it's really useful to see how they translate to anxiety specifically.
These considerations focus on reducing cognitive load, lowering stress, and creating experiences that feel calmer and clearer for everyone. It’s not a complete list, but it highlights the areas that make the biggest difference to a calmer, more supportive user experience.
As someone who mostly works on government services these days, the section on transparency hit home:
It’s important to explain why certain information is being requested. If someone in real life asked for your date of birth or your pronouns without context, both personal details that aren’t automatically assumed, you might feel cautious or hesitant. Forms work the same way. Offering a brief explanation reduces worry, builds trust, and reassures people that their information is being requested for a clear, legitimate purpose.
This is in the context of creating a form, but I think it applies to any content where you are asking the user for something.
It's about being honest and clear, but you are also building trust. If a user thinks your website, service or organisation is being straight with them, that reduces the potential for anxiety.
There is another word I'd throw into the mix: acknowledgment. By explaining why you need a piece of information, you are showing empathy and understanding. You acknowledge that your request might cause anxiety, but providing reassurance that there is a reason for the ask.
You can follow a selection of links to other resources at the end of Feltham's blog post, including these designing for anxiety posters from the UK Home Office.
I wrote a lot of letters on the previous project I worked on. You won't be surprised to hear that the UK government's service manual has some guidance on how to write good letters. I will also point you to this shorter piece about designing letters as part of the whole user journey.
I like this piece on jargon by content designer, Amy Hupe, because it acknowledges the nuances of language and even clear language.
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.
Yes, in most cases, jargon should be avoided. But jargon can empower people and communities too. I think this is why it's important that we don't get all... preachy about clear language. There is never one way of approaching a piece of writing. And it's absolutely vital to understand who it's for.
A blog and newsletter for people who write clear, accessible content. Join 1000+ subscribers.