<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joanne Schofield on Medium]]></title>
        <description><![CDATA[Stories by Joanne Schofield on Medium]]></description>
        <link>https://medium.com/@joanne.schofield?source=rss-3b5e918e9b41------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BxNRmqUZ8rQdh_WPwOstYQ.jpeg</url>
            <title>Stories by Joanne Schofield on Medium</title>
            <link>https://medium.com/@joanne.schofield?source=rss-3b5e918e9b41------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:52:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joanne.schofield/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Editing someone else’s words: how to get context, quickly]]></title>
            <link>https://medium.com/@joanne.schofield/will-you-look-over-this-how-to-get-context-quickly-2a1bf49c7c48?source=rss-3b5e918e9b41------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a1bf49c7c48</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[editing]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[content-strategy]]></category>
            <dc:creator><![CDATA[Joanne Schofield]]></dc:creator>
            <pubDate>Sun, 04 Mar 2018 17:39:34 GMT</pubDate>
            <atom:updated>2018-10-31T13:14:53.612Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve got ‘content’, ‘copy’ or ‘editor’ in your job title, it’s likely that at some point you’ve been asked to look over someone else’s work, with limited context and to a tight deadline. You might be asked to sense-check it, proofread it or make it fit with the brand style.</p><p>But doing a good job with content you know little about can be hard.</p><p>How can you make sure information’s clear if you’re unsure what the most important messages are?<br>How can you check it’s saying what the audience needs to know if you don’t know who the audience is?<br>How do you know if the information’s structured effectively if you don’t understand the wider context?</p><p>Whatever you’re asked to look over — a report, a presentation, a handout, a webpage — here are some questions you can ask that might help give you some context, quickly:</p><p><strong>Who’s the audience?<br></strong><em>What are their needs? Why are they interested in this?</em></p><p><strong>Why are we communicating this? <br></strong><em>What message(s) do we want to get across? Why is it worth communicating?</em></p><p><strong>What do we want the audience to do as a result of reading this information?<br></strong><em>What are they responsible for doing, deciding or approving?</em></p><p><strong>What do they know already?<br></strong><em>How involved have they been in this? What else has been communicated to them, and how?</em></p><p><strong>What’s the easiest way for the audience to get this information?<br></strong><em>Is the suggested format the most effective format?</em></p><p><strong>How are we measuring this?<br></strong><em>How will we know if we’ve done a good job?</em></p><p>Understanding more about the purpose and audience of the piece of content means we can make more effective suggestions, more confidently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a1bf49c7c48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Grating expectations: why we shouldn’t use time to set expectations]]></title>
            <link>https://medium.com/@joanne.schofield/grating-expectations-why-we-shouldnt-use-time-to-set-expectations-a738dbd6d9de?source=rss-3b5e918e9b41------2</link>
            <guid isPermaLink="false">https://medium.com/p/a738dbd6d9de</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[forms-design]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joanne Schofield]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 21:16:03 GMT</pubDate>
            <atom:updated>2017-12-07T12:54:52.912Z</atom:updated>
            <content:encoded><![CDATA[<p>Average or maximum completion times are often cited to introduce forms and surveys (like, ‘this survey should take no more than 10 minutes to fill out’). It might help people decide whether to continue. They don’t need to check ahead to see how long it is. Expectations are set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQGVKQKToQoIhfsSK_-6Aw.png" /><figcaption>Google Garage survey</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*A6YbrsNDTbUdje8IMSHJjQ.png" /><figcaption>LinkedIn survey</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*eJii9nuDsMdDHZ2ToA93IA.png" /><figcaption>British Airways survey</figcaption></figure><p>But telling people how long something ‘should’ or ‘will’ take them can be disrespectful and insensitive.</p><h4>Why using time to set expectations can be insensitive</h4><p>The problem with using time to set expectations is that it’s presumptive — it assumes a certain level of speed and ability of the user.</p><p>People may take longer to complete a form or survey if they:</p><ul><li>have dyslexia — 10% of the UK population are dyslexic (source: <a href="http://www.bdadyslexia.org.uk/about">www.bdadyslexia.org.uk/</a>)</li><li>have low literacy — around 16% of adults can be described as ‘functionally illiterate’ (source: <a href="http://www.literacytrust.org.uk/adult_literacy/illiterate_adults_in_england">www.literacytrust.org.uk</a>)</li><li>are one of the 2 million people in the UK with sight loss (source: <a href="http://www.rnib.org.uk)/">www.rnib.org.uk)</a></li><li>have cognitive conditions or learning difficulties</li><li>have motor control disorders</li><li>have English as a second language</li><li>are stressed or distracted</li></ul><p>As it’s not clear to the user how the time stated is calculated — they cannot see the data that makes it up — they cannot assess if it’s an accurate representation of their personal circumstances.</p><p>And it does not take into account how complex a user may find the questions, how emotive they find the subject matter or which emotional triggers it may prompt.</p><p>By using time to set expectations we’re creating a subjective measure of objective data which the user cannot control. And which may not take into account their individual needs.</p><p>This means that a stated completion time will often be inaccurate. It can also be thoughtless and hurtful. It highlights an oversimplification of user needs.</p><h4>How it affects the user</h4><p>Using time to set expectations can be demoralising and undermine users’ confidence. Users can feel like they’re to blame — that they’re doing something wrong — if they don’t complete the task in the time stated.</p><p>They can also feel misled. This can make them distrustful of the information or service they’re interacting with. And they may stop interacting with it.</p><h4>Research other ways of setting expectations</h4><p>Using objective metrics could give users enough information to set their own expectations. These metrics should be:</p><ul><li>factual</li><li>accurate</li><li>unambiguous</li><li>non-discriminatory</li></ul><p>Instead of time, perhaps we state how many questions a form contains and what format they’re in. This may give the user enough information for them to decide whether to continue in a way that makes sense to them.</p><p>Researching these different approaches with a diverse user group will help us to build products and services that are sensitive to more diverse user needs.</p><p>It will help remove the arrogance of assumption, increase trust and put all users in control of when and how they interact with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a738dbd6d9de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you speak agile?]]></title>
            <link>https://medium.com/@joanne.schofield/do-you-speak-agile-cf6160a1d138?source=rss-3b5e918e9b41------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6160a1d138</guid>
            <category><![CDATA[plain-english]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Joanne Schofield]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 18:37:13 GMT</pubDate>
            <atom:updated>2018-02-28T14:48:00.907Z</atom:updated>
            <content:encoded><![CDATA[<p>Content designers pursue clarity and comprehension relentlessly. We do this so that anyone, no matter what their level of knowledge, experience or education, has the best chance possible of understanding the content we’re working on.</p><p>And, content designers often work in ‘agile’ environments.</p><h3>Where agile and content design fall out</h3><p>Working in an agile way is now <a href="https://techbeacon.com/survey-agile-new-norm">the norm for software development, IT and digital professionals</a> (two thirds of companies describe their way of working as ‘agile’ or ‘leaning towards agile’).</p><p>Agile is a way of building products and services in gradual phases, instead of delivering it all at once, at the end. It means giving value to the people who will use the product as early as possible and letting them influence the direction of the product — it puts the user at the centre of the design and development process.</p><p>It also comes with its own set of unique terminology and jargon.</p><p>Search for ‘agile jargon’ and you’ll be met with a collection of dictionaries, glossaries and jargon-busters to help you understand the specialist vocabulary. ‘Sprint’, ‘kanban’, ‘scrum’, ‘MVP’, ‘retrospective’: there’s hundreds of terms that make up these aids.</p><h3>What is jargon?</h3><p>The Oxford Dictionary defines jargon as:</p><blockquote>“Special words or expressions used by a profession or group that are difficult for others to understand.”</blockquote><p>Sometimes jargon can be used as a shortcut to communicate a complex concept. It can be used to show that a person is a specialist in their field or connected to a certain community.</p><p>But, if we use jargon, we restrict the audience to those who understand the terms — it’s <em>only</em> understandable to those who know.</p><h3>Why jargon’s a problem</h3><p>Many agile teams work with more traditional organisations. Part of this opportunity is showing the value that the agile way of working can add to a project and the rest of the business.</p><p>And agile often works best when it converts people — when it’s demonstrated an effective way of working to people who were initially sceptical. We should make the effort to make this transition as easy as possible for people.</p><p>But, by openly using agile jargon within a wider setting, we risk isolating the very people we want to help work in this way.</p><p>If someone does not understand the vocabulary being used, it can:</p><ul><li>unnerve them</li><li>alienate them</li><li>mean they misinterpret an important part of what’s being said</li></ul><p><a href="http://journals.sagepub.com/doi/abs/10.1177/0146167210386238">Research shows that the less people understand, the less they trust</a> the people telling them the information.</p><p>Using jargon can be inaccessible, ineffective and damaging.</p><h3>What agile teams can do better</h3><p>However we communicate, we should be inherently humble of what we assume. And good communication should not assume any specialist knowledge of the audience.</p><p>When we write for users we learn about the language that they use and make a considered effort to speak to them in a language we know they understand. We should do the same when we’re communicating about our processes.</p><p>That means not using specialist terminology (or, at the very least, adding a plain English definition at the point any specialist terms are used) if we’re communicating:</p><ul><li>publically about our work</li><li>to people outside of our immediate team</li><li>to people who are new to a team or organisation</li></ul><p>By doing this we’re not only removing barriers to comprehension, but showing that we’re transparent, mindful and respectful of our audience’s time.</p><p>We’re making agile user focused.</p><h3>Read more:</h3><p>‘Economic jargon promotes a deficit in understanding’, The Guardian</p><p><a href="https://www.theguardian.com/media/mind-your-language/2015/aug/14/economics-jargon-promotes-a-deficit-in-understanding">https://www.theguardian.com/media/mind-your-language/2015/aug/14/economics-jargon-promotes-a-deficit-in-understanding</a></p><p>‘Why workplace jargon is a big problem’, The Huffington Post</p><p><a href="http://www.huffingtonpost.com/2014/04/25/work-words_n_5159868.html">http://www.huffingtonpost.com/2014/04/25/work-words_n_5159868.html</a></p><p>“Dumbing down’, Sarah Richards</p><p><a href="http://www.sarahjrichards.com/blog/dumbing-down">Dumbing down</a></p><p>I work as a content designer for Co-op. This is taken from a blog post I originally wrote for <a href="https://digitalblog.coop.co.uk/">the Co-op Digital blog</a> in September 2017.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6160a1d138" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using contractions could be making your writing inaccessible]]></title>
            <link>https://medium.com/@joanne.schofield/using-contractions-could-be-making-your-writing-inaccessible-4034bb3cd76a?source=rss-3b5e918e9b41------2</link>
            <guid isPermaLink="false">https://medium.com/p/4034bb3cd76a</guid>
            <category><![CDATA[people-with-disabilities]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[grammar]]></category>
            <dc:creator><![CDATA[Joanne Schofield]]></dc:creator>
            <pubDate>Wed, 21 Jun 2017 18:59:41 GMT</pubDate>
            <atom:updated>2017-06-21T19:37:57.959Z</atom:updated>
            <content:encoded><![CDATA[<p>Content designers decide what, how and where to write things based on evidence and research with users.</p><p>Many modern content style guides promote the use of contractions. A contraction is a shortened form of a group of words, such as ‘there’s’, ‘I’m’, ‘you’ve’. They’re usually encouraged as a way to make the tone more informal and friendly — the way that people naturally speak.</p><p>But, I’ve learnt that using some contractions can lead to:</p><ul><li>decreased understanding</li><li>misinterpretation of meaning</li><li>an increase in the mental effort required to read them</li></ul><h3>Writing for all</h3><p>I’ve previously worked as a content designer in government, mainly on digital services for people with disabilities and health conditions. So, the majority of research we did was with people with disabilities or health conditions, or with people who supported them.</p><p>Making content accessible and easy to understand is essential to what we do as content designers — using plain English and consistent language, keeping sentences short and to-the-point, explaining complex concepts in simple terms and so on. The content I wrote for the digital services followed the government style guide, including using contractions to make the tone more conversational. It seemed like a logical place to start.</p><h3>Sacrificing understanding for style?</h3><p>One of our research sessions was with people with learning disabilities. There are approximately 1.4 million people with a learning disability in the UK (source: <a href="https://www.mencap.org.uk/learning-disability-explained/research-and-statistics">Mencap</a>).</p><p>We found that some of these users did not understand sentences that had negative contractions in them (negative contractions are words like ‘can’t’, ‘won’t’, ‘don’t’). They interpreted the sentence without inferring the ‘not’.</p><p>Further research supported this finding, such as Change People’s ‘<a href="http://www.changepeople.org/free-resources/">How to make information accessible</a>’:</p><blockquote>“Use ‘do not’, ‘can not’, ‘would not’ and so on instead of ‘don’t’, ‘can’t’ and ‘wouldn’t’ because some people rely on reading the ‘not’ to understand what is being said.”</blockquote><p>And the Department of Health’s publication, ‘<a href="https://www.gov.uk/government/publications/making-written-information-easier-to-understand-for-people-with-learning-disabilities-guidance-for-people-who-commission-or-produce-easy-read-information-revised-edition-2010">Making written information easier to understand for people with learning disabilities</a>’:</p><blockquote>“Do not use contractions and avoid apostrophes, except where they indicate possession.”</blockquote><h3>It’s a problem for other users too</h3><p>I shared this insight with other teams in government.</p><p>People working in different digital services had seen similar issues. They’d noticed that people who have English as a second language (approx 4.2million at <a href="https://www.ons.gov.uk/peoplepopulationandcommunity/culturalidentity/language/articles/languageinenglandandwales/2013-03-04)">2011 Census</a>), and people with other reading difficulties, can also be slowed down by contractions.</p><h3>Using negative contractions can decrease understanding</h3><p>Although some people may understand and use contractions in their everyday speech, they can take time to recognise them in writing.</p><p>And recognising and understanding the word ‘not’ is, usually, crucial within an interaction — the difference between right and wrong, between lawful and unlawful, between safe and unsafe.</p><p>By contracting ‘not’ we could be making the meaning of our content not only ambiguous to some people, but potentially dangerous.</p><h3>Design for users</h3><p>Content design is not about satisfying our own personal preferences and habits. It’s not about the brand personality that a company wants to portray. Content design is about focusing on the needs of those who will use the service.</p><p>We should write for our users, not for ourselves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4034bb3cd76a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>