Plain language
If a child can understand a task, most people will.
Our instinct says: Does it sound too easy? Too dumb to be posted?
No, it is not! And I will share with you some thoughts I am having during my studying process about plain language.
Plain language is not that easy, it is actually challenging and difficult. It needs simple wording, accessibility studies and usability processes, in all its spectrum. Well, spectrum and usability, are not simple words, let me rephrase this sentence: It needs simple wording in all its range and processes thought for the reader.
When UX writing, we have a task: to always be looking for easier ways for a text to be written and read.
It allows people to understand pages that are not in their primary language (my case).
Allows users that are not domain experts to understand it more easily.
And it is inclusive, when it doesn't leave any person or group feeling out.
Do they understand what am I writing?
We work for it, and we follow some steps to help in the process.
- list and prioritize tasks
- choose words that are easy to understand
- write in present and short words
- remove branded and technical language
- organize the content so that flows logically
- avoid jargon
- use short sentences, bullets and headers
- use a conversational tone
- use design
- check if is the final product is useful and usable
It is not only rewriting, but we also need to make it simple, and clear, think about the reader (have empathy) and make all of it work in a small space and with counted letters. — Talking about a design perspective, when we need to create microcopy, but this is a topic for another text.
The copy works when target users can find what they need, understand what they find, and act on it confidently.
A reminder, also to myself.
"Websites that are easier to be interpreted, are better understood."
And, finally, repeat with me like a mantra: Keep it simple.
