<p>Published on <a href="http://ift.tt/2o6mO6a">| Prototyping: From UX to Front End &mdash; Medium</a> Dominic Warren <img alt="" src="http://ift.tt/2pFmOtH"></p>
<p>Content Designers are enthusiastic about language and constantly talk about user needs and how we read on the web. But, what is content design?</p>
<p>Content Designers are more common than I realised. For the UK government we’re Content Designers, but for other companies we’re Content Writers. Dropbox and Google have UX Writers, and some companies use Content Strategists.</p>
<p>Here, I’ve tried to clearly collect some of the main areas a Content Writer works in. Although not a definitive list, this covers what I’ve found is important.</p>
<h3>Reading on the web and plain English</h3>
<blockquote><p>“Style to be good must be clear. Clearness is secured by using words that are current and ordinary.” — Aristotle</p></blockquote>
<p>Plain English is probably the most important part of writing for the web. Users generally tend to:</p>
<ul>
<li>scan the content, looking for keywords</li>
<li>read in an<a href="http://ift.tt/1OOSAWt"> F shape pattern</a></li>
<li>be put off by jargon and ‘marketese’</li>
</ul>
<p>A study by Nielsen Norman Group showed that<a href="http://ift.tt/1Zf0d01"> 79% of test users scanned a new page, only 16% read it word for word</a>.</p>
<p>This is why considering, and designing, your written content online is so crucial. You could write the world’s greatest prose on how to use your service, but users aren’t guaranteed to read it at all. Writing in a clear, concise language means the user can read the content quickly and get the information they need easily. The following are some good ways to do this.</p>
<h3>Front-loaded headings</h3>
<p>Users generally scan webpages for keywords. Using clear, front-loaded headings breaks up the content into manageable chunks and allows the user to easily navigate it.</p>
<h3>Short sentences</h3>
<p>Sentences should be kept short and clear. The Government Digital Services (GDS) recommend<a href="http://ift.tt/1kywS0C"> sentences should be no more than 25 words</a>. Dropbox commit themselves to<a href="http://ift.tt/2hDD9vr"> only 15 words or less</a>.</p>
<h3>Bullet lists</h3>
<p>Lists within a sentence makes reading more difficult so use bullet lists where you can. Bullet lists can:</p>
<ul>
<li>attract attention, supporting ease of scanning content</li>
<li>clearly separate the content, making it easier to read</li>
<li>emphasise the points you’re trying to make</li>
</ul>
<h3>Structuring content</h3>
<p><img alt="" src="http://ift.tt/2opi8nV"><a href="http://ift.tt/2oXNqpb">The inverted pyramid — Sam Spurlin</a></p>
<p>As<a href="http://ift.tt/1mAmbwo"> users generally only read 20 to 25% of content on web pages</a> it’s best to think of<a href="http://ift.tt/2oXOnOg"> the ‘inverted pyramid’</a> when structuring content.</p>
<p>This is the idea that the most crucial pieces of information are available at the beginning. Then, as you move down the page, these points are explained more. This means that users can get what they need from the content immediately, and read on if they want to understand it further.</p>
<h3>Microcopy</h3>
<p>It’s easy to think of content writing as just guidance and larger pages of information, but every word and sentence should be considered. The user will interact with all aspects of your service or website so making sure everything is consistent is vital. Microcopy is the small, helpful bits of text that instruct the user. One example is when subscribing to an email newsletter and it says “you can always unsubscribe at any time”.</p>
<p>Microcopy is something that often gets missed but can make a huge difference to how users interact with your website or service. The little touches help the user know they’re dealing with humans, even if it’s through a digital service. For the most enjoyable microcopy out there,<a href="https://twitter.com/tinywordsmatter"> @TinyWordsMatter is good to follow</a>.</p>
<p>Microcopy includes elements such as error messages. Although a standard error message might mean something to someone who understands the intricacies of code, it won’t mean anything to a user. If the user is interacting with it, you want to build trust. Having a clear message explaining it’s nothing the user has done and it’s nothing to worry about (if it’s nothing to worry about) reassures them.</p>
<p>If you want your user to return, it’s best not to blame them or make them feel stupid. The Nielsen Norman Group has some clear guidelines that can<a href="http://ift.tt/1VxeLbQ"> help with writing error messages</a>.</p>
<p><a href="http://ift.tt/2mbRRLl">John Saito discusses microcopy, and its benefits, in more detail.</a></p>
<h3>Working in teams</h3>
<p>The easiest way to successfully write content is working alongside others in the team. Agile teams are particular good at getting different roles to work together. For example, working closely with a User Researcher will help support your content decisions, or changes, with evidence. You can test variations of your content and understand how users engage with it. This can then inform how you write, the words you use, and the presentation.</p>
<p>You can also work with a Business Analyst to understand the sort of enquiries your customer support department is receiving. If you group this information into themes you can get an understanding of what users are looking for, but also what they’re unable to find. You can then review your content, or add to it, to support this.</p>
<h3>Building relationships</h3>
<p>Probably the hardest part of being a content writer is making others in your company understand what it is you actually do. As content writing is still new to lots of companies your colleagues, authors, and owners of existing content may struggle to understand what you do. If they’ve never considered the user’s perspective before they might struggle to understand your use of plain English. Lots of people think using<a href="http://ift.tt/MrcQ7p"> plain English is “dumbing down”, but really, it’s “opening up”</a>.</p>
<p>One battle I’ve come across a number of times is the use of internal terminology vs. how users actually refer to things. Government departments famously use a<a href="http://ift.tt/1VS0bgg"> wealth of acronyms and internal terms</a>. If you want users to find your content, however, you have to use the same language as them. A good tool to help prove this to stakeholders is<a href="http://ift.tt/2lHteH3"> Google Trends</a>.</p>
<p><img alt="" src="http://ift.tt/2pForI6">Comparing ‘Content Designer’ with ‘UX Writer’ over the last 12 months in the US on Google Trends</p>
<p>Google Trends lets you enter different terms and compare the use of these in searches. This is a clear way to show your point with hard evidence.</p>
<p>I’ve found the more evidence you can provide a stakeholder showing your way of writing is correct and beneficial, the more trust you can gain. This means, in the future, stakeholders are more likely to follow your suggestions.</p>
<h3>Style guides</h3>
<p>After developing rules and a style of writing you’ll also want everyone else to stick to it, ensuring all content maintains a consistent voice. Style guides are an incredibly useful tool to do this. Style guides are your reference for how to write, how to structure, and what to avoid.</p>
<p>Maintaining the standards of writing is crucial for a consistent voice and tone. At first it can be hard to find and define this. Your voice should stay the same throughout. Your tone is what changes. This is because you want to consider your user’s feelings at every stage and your tone needs to change to support them. For example, if the user has completed a task, you’ll probably want to use more informal language that encourages and congratulates them.</p>
<p>Using active voice is also important. With active voice, the user does the action. You want to avoid passive voice, where the user has the action done to them. Using words like “was” and “by” may be a sign you’re writing in passive voice.</p>
<h3>In summary</h3>
<p>With the explosion in digital services and applications, content design is becoming more and more important. Although one of the main points of content design is the use of plain English, it’s also more than this. It’s having an understanding of how users read and recognise content on the web.</p>
<p>How we write and present content is crucial, but it’s also understanding the language users’ use and the most intuitive way users read. This makes sure the user can understand what they’re expected to do and they can complete the task quickly and easily.</p>
<p>But, ultimately, it’s about building trust. The user needs to trust your service to use it. If you can present your content in a helpful, friendly manner, reminding users they’re dealing with humans rather than computers, then they’ll engage with it.</p>
<p><img src="http://ift.tt/2op7vlg" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="http://ift.tt/2pFbTAx">Writing for the web and content design</a> was originally published in <a href="http://ift.tt/2cAqCpx">Prototyping: From UX to Front End</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Writing for the web and content design

Top Stories