<?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 Ema Thornhill on Medium]]></title>
        <description><![CDATA[Stories by Ema Thornhill on Medium]]></description>
        <link>https://medium.com/@ema.thornhill?source=rss-717d71b9269f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Gf--WSvgd5oPcDzb8Everw.jpeg</url>
            <title>Stories by Ema Thornhill on Medium</title>
            <link>https://medium.com/@ema.thornhill?source=rss-717d71b9269f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:05:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ema.thornhill/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[Changing content to improve page performance]]></title>
            <link>https://medium.com/content-at-scope/changing-content-to-improve-page-performance-b15437e07589?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b15437e07589</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[content-maintenance]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[content-strategy]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 10:41:50 GMT</pubDate>
            <atom:updated>2026-02-11T10:41:50.579Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A black labrador dog laid on a checkered bed. The grey wooden frame of the bed has ‘Douglas’ stencilled on it." src="https://cdn-images-1.medium.com/max/1024/1*47b0pLgtVigFWg0FLj3XWA.jpeg" /><figcaption>Douglas the User Research dog wants to know that a change of bed will improve his naps before he is willing to try it.</figcaption></figure><p>We have written before about how important it is for us to <a href="https://medium.com/content-at-scope/how-we-improve-content-b6644f290b8c">maintain and improve content</a>. This is still true. But we face a new problem. The information needs of disabled people are increasing and becoming more complex. And while the need for information is expanding, our team capacity is not. So, we face a challenge. Which is a higher priority: creating new content or improving existing content?</p><p>We tried to work out a quicker way to improve our content. And, shock horror, the answer to “can you do more with less?” is still a hard “no”. So, we looked for a more strategic approach. We analysed the effect of different types of content changes. We compared page performance data from before and after the changes to see what we could learn.</p><h3>Using data to identify improvements</h3><p>We analyse the performance of each page when it is due for an annual review.</p><p>We use data for the last 12 months to account for seasonal variations.</p><p>We look for signs that:</p><ul><li>people do not read the content (custom event in Google Analytics)</li><li>people do not click on internal or external links to additional content (custom events in Google Analytics)</li><li>people do not find the content helpful (pages with a lower percentage of positive ratings)</li><li>people say there is something missing from a page (feedback left in our on-page survey)</li></ul><p>We use the data to decide on possible improvements. We make the changes and check again after 6 months to see if our changes worked.</p><p>I will be honest. Not all the changes we make have an impact. Sometimes page performance does not change. If this happens and the page meets our deletion criteria, then we would remove the content from the website. Sometimes one metric improves and another gets worse. For example, helpful rating may get better but there may be fewer page views. But most changes do have a positive impact on page performance. This is because we make changes based on data and <a href="https://medium.com/content-at-scope/how-we-use-page-feedback-a826a4b92a14">feedback from people who use our content</a>.</p><h3>What we learned</h3><p>We wanted to understand which types of improvements have the biggest impact on the performance metrics. So we compared before and after data for 49 pages from the <a href="https://www.scope.org.uk/advice-and-support/">advice and support section of the Scope website.</a> This is about a fifth of the total advice and support pages.</p><p>We found that some changes had a bigger impact on some metrics than others:</p><h3>Low helpful rating</h3><p>If a page had a low helpful rating, the changes that led to the greatest improvements were:</p><ol><li>Changing the title. Changes were based on <a href="https://medium.com/content-at-scope/how-we-use-keywords-and-search-data-to-improve-our-content-ef7071c6cc9">keyword research</a> and queries that had clicks in Google Search Console.</li><li>Adding more content in response to page feedback.</li><li>Adding jump links to headings on the page if people did not find what they were looking for but the answer was on the page.</li><li>Adding internal links to related pages.</li></ol><h3>People could not find what they were looking for</h3><p>If page feedback said that people could not find what they were looking for, the changes that led to the greatest improvements were:</p><ol><li>Adding more content in response to page feedback.</li><li>Adding jump links to headings on the page if people did not find what they were looking for but the answer was on the page.</li><li>Adding internal links to related pages.</li></ol><h3>Low page views</h3><p>If a page had low page views, the changes that led to the greatest improvements were:</p><ol><li>Merging content with another page on the same topic</li><li>Changing the title. Changes were based on <a href="https://medium.com/content-at-scope/how-we-use-keywords-and-search-data-to-improve-our-content-ef7071c6cc9">keyword research</a> and queries that had clicks in Google Search Console.</li><li>Adding more content in response to page feedback.</li><li>Adding internal links to related pages.</li><li>Changing the order of the content on the page.</li><li>Changing the meta description.</li><li>Adding an example box to explain how a rule or calculation works. For example, how savings affect the amount of means-tested benefits somebody can claim.</li><li>Adding external links.</li><li>Adding a new user story to the page to meet more user needs.</li><li>Changing the headings to target different keywords.</li></ol><h3>Low link clicks to internal or external pages</h3><p>If a page had low link clicks to internal or external pages, the changes that led to the greatest improvements were:</p><ol><li>Adding more headings to the page. Break information into smaller chunks. Make it easier for people to find what they are looking for.</li><li>Adding more content in response to page feedback</li><li>Changing the title. Changes were based on <a href="https://medium.com/content-at-scope/how-we-use-keywords-and-search-data-to-improve-our-content-ef7071c6cc9">keyword research</a> and queries that had clicks in Google Search Console.</li><li>Merging content with another page on the same topic</li><li>Adding internal links to related pages</li><li>Removing links to American websites</li><li>Changing the headings to target different keywords.</li><li>Adding jump links to headings on the page if people did not find what they were looking for but the answer was on the page.</li><li>Adding a new user story to the page to meet more user needs.</li><li>Changing the order of the content on the page.</li><li>Adding an example box to explain how a rule or calculation works. For example, how savings affect the amount of means-tested benefits somebody can claim.</li></ol><h3>Changing how we work</h3><p>Finding out which changes have the greatest impact does not increase our team capacity. We will still have to reduce the number of pages we improve each year. But now we know which changes are more likely to improve specific metrics. This will help us to make effective decisions about the pages we try to improve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b15437e07589" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/changing-content-to-improve-page-performance-b15437e07589">Changing content to improve page performance</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recommendations for user research with disabled people and their families]]></title>
            <link>https://medium.com/content-at-scope/recommendations-for-user-research-with-disabled-people-and-their-families-45834d8ad630?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/45834d8ad630</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[accessible-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 10:48:56 GMT</pubDate>
            <atom:updated>2026-01-06T11:23:50.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A black labrador stood in the woods. There are green leaves on the trees behind him and autumnal coloured leaves on the ground below him." src="https://cdn-images-1.medium.com/max/1024/1*dUxw5dWYSi0fkMuwGi7YxQ.jpeg" /><figcaption>Douglas the User Research dog likes to guide people through the woods. But he knows that the right path for one human or hound might be different for another human or hound.</figcaption></figure><p>As a user researcher at a disability charity, people sometimes ask how we make research sessions accessible for disabled people. Or if there are any best practice guides I would recommend.</p><p>There are quite a few guides out there and some of them offer some good practical advice. But:</p><ol><li>The advice has often been created by researchers without including the experiences of disabled people.</li><li>Some take a medical model approach which says people are disabled by their condition. The medical model looks at what is ‘wrong’ with the person, not what the person needs. At Scope, we take a <a href="https://www.scope.org.uk/social-model-of-disability">social model</a> approach.</li><li>The advice often assumes that the only changes that need to be made to research sessions are to accommodate access needs.</li></ol><p>So, we have created a <a href="https://www.scope.org.uk/user-research-with-disabled-people">guide that contains recommendations for carrying out research with disabled people and their families</a>. This guide:</p><ol><li>draws on lived experience and feedback from disabled people and their families.</li><li>takes a social model approach which focuses on what people need.</li><li>focuses on creating research sessions that are inclusive, accessible and comfortable.</li></ol><h3>Based on lived experience and feedback</h3><p>We regularly review our user research practice. We ask participants for feedback on their experience of taking part in user research sessions with us. We ask participants:</p><ol><li>Before your session, what did we do that made you feel comfortable taking part?</li><li>What could we do to make you feel more comfortable?</li><li>During the session, what did researchers do to help you feel at ease?</li><li>Is there anything they could have done to help you feel more relaxed?</li><li>Is there anything you would like to happen after a session has ended?</li><li>What could we do to follow up with people who have helped with our research?</li></ol><p>We also carried out a survey specifically to help us design a guide we could share with other user researchers. In that survey we asked:</p><ol><li>What do you want to know about a research project before deciding to take part?</li><li>What would make it harder for you to take part in research?</li><li>What adjustments or support would help you to take part in research?</li><li>What would help you to feel listened to and respected in a research session?</li><li>Is there anything you would like researchers to do after a session?</li></ol><p>We used the 108 responses we got from both surveys to create <a href="https://www.scope.org.uk/user-research-with-disabled-people">our guide.</a> We hope people will use the guide with a human-centred approach that focuses on what people need.</p><h3>Focus on what people need</h3><p>Guides often suggest ‘doing things’ rather than asking people what they need. As a practice, user research is about finding out what your users need. This is something we should apply to all parts of our work. For research sessions, our participants are our users. So, we should be finding out what they need to take part in our research. From them.</p><p>At Scope, our user research practice tries to take an equity-focused design approach. Equity-focused research design means to design research that meets the needs of specific individuals in groups who have been excluded in the past. As part of this:</p><ul><li>we do not ask people to tell us about their health or condition. It is not relevant and people can share what they want with us.</li><li>we do not assume we know what people need. Disabled people are experts in their own access needs. Ask them. Just because you have done a research session with somebody who has a specific condition does not mean somebody else with the same condition will have the same access needs.</li><li>we do not give people a list of adjustments to choose from. For 2 main reasons:</li></ul><ol><li>What if the thing the person needs is not on the list? Does that mean they cannot take part? Or do they need to get in touch and ask you? That is just an extra cost for participants.</li><li>We have tried things I would probably never have thought of based on asking people what they need.</li></ol><p>It is also important to remember that it costs people to take part in research. Those costs can be financial, physical, psychological and social. Understanding the costs of taking part to your participants is important to think about in advance. If research sessions are not accessible, those costs increase.</p><p>I wrote about the <a href="https://medium.com/content-at-scope/what-does-it-cost-to-take-part-in-research-de8307f946d0">costs of taking part in research in a previous post</a>. Not everybody can ‘afford’ the costs needed to take part. But if you design your research to be as accessible, inclusive and comfortable as possible, you reduce the costs to your participants. You also open up the opportunity for participation to a wider group of people. And you can do that by focusing on what people need.</p><h3>Inclusive, accessible and comfortable</h3><p>Not all disabled people will need or want changes to a research session to make it accessible for them. But disability does not occur in a vacuum. Disabled people have other parts to their identities. Those other parts have needs too. It is not just about making research accessible. It is about designing research sessions to be accessible, inclusive and comfortable for the people who are taking part.</p><p>Disabled people have told us that environments often force them to choose between different parts of their identity. For example, being a young person or being disabled. Choosing between their sexuality and their disabled identity. We want people to be as comfortable as possible when they are taking part in our research. So we ask “are there any changes we can make to the session so that you are comfortable taking part?” We ask it in this way because we do not mind why people want us to change something. It could be because of their condition, another part of their identity or how they are feeling that day. But the reason is not important, their comfort is. By asking it in this way, we are focusing on what people need.</p><p>It is a kind of extension of the “please let us know if there are any reasonable adjustments we can make”. But hopefully this shows that we are not just thinking about a legal obligation not to discriminate against disabled people under the Equality Act. And also, what is reasonable and who decides? That’s a debate for another day!</p><p>Another thing we have learned is that lots of people do not identify as disabled. And those people do not see terms like ‘reasonable adjustments’ and ‘access needs’ and think that is something for them. Those terms also sound like things people might permanently need. Whereas a change for comfort might only be needed on a specific day based on how somebody is feeling that day.</p><h3>Using the recommendations guide</h3><p>We hope that the <a href="https://www.scope.org.uk/user-research-with-disabled-people">recommendations for carrying out user research with disabled people and their families guide</a> will be useful for other user researchers. We hope that people will use it whilst taking a human-centred approach and focusing on what people need.</p><p>Research is a 2-way exchange between a researcher and a participant. Researchers want to be able to collect data and findings for our research. Participants also want to share their experiences and have a voice. People want the opportunity to make a change or have an impact. People said this when they took part in the surveys. So creating a research session where people are comfortable allows that exchange to take part in a more ‘equal’ way. It lowers, but does not remove, the power differential between researcher and participant.</p><p>My best piece of advice is to be flexible and be prepared to change. We design all of the research that we carry out. But we also plan to be flexible. We always have a back-up plan. And if the back-up plan does not work then we go with the back-up plan for that, which is often “roll with it”. Sometimes the research sessions we do look nothing like the research sessions we planned. But that is OK because it means the participant took part in a way that was accessible, inclusive and comfortable for them. And, for me, giving participants a space to share their experiences in a comfortable setting where they feel heard is the most important responsibility of a researcher.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45834d8ad630" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/recommendations-for-user-research-with-disabled-people-and-their-families-45834d8ad630">Recommendations for user research with disabled people and their families</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Which AI tools are disabled people and their families using?]]></title>
            <link>https://medium.com/content-at-scope/which-ai-tools-are-disabled-people-and-their-families-using-0dd20df66c50?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dd20df66c50</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ai-tools]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 15:11:17 GMT</pubDate>
            <atom:updated>2025-11-03T16:33:53.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An AI-generated image of a woman with wavy blonde hair in a red coat holding a sparkler. She is stood next to a black labrador wearing a red scarf. There are red and orange fireworks in the sky. A bonfire burns in the background behind them." src="https://cdn-images-1.medium.com/max/1024/1*f4qp0mIlU7pPoKMi4Tgekg.png" /><figcaption>An AI-generated image of Ema and Douglas the user research dog celebrating Bonfire Night.</figcaption></figure><p>We are carrying out a research project to find out how disabled people and their families use AI to find information and advice online. You can read more about why we are doing this project in our <a href="https://medium.com/Researching%20how%20disabled%20people%20and%20their%20families%20look%20for%20information%20and%20advice%20using%20AI%20tools">Researching how disabled people and their families look for information and advice using AI tools</a> post.</p><p>We said we would share the findings of our research as we go. And we have just finished analysing the survey data. This post will focus on:</p><ul><li>which AI tools disabled people and their families are using</li><li>what they are using AI tools for</li></ul><p>88 people volunteered to take part in the survey in September and October 2025 through <a href="https://www.scope.org.uk/services">Scope’s Services</a>.</p><h3>AI tools</h3><p>16% of participants said they do not use any AI tools.</p><p>The 84% of participants who use AI said the tools they use are:</p><ul><li>63% ChatGPT</li><li>47% Amazon Alexa</li><li>36% Copilot</li><li>32% Gemini</li><li>30% Google AI mode</li><li>26% Google AI summaries</li><li>25% Siri</li><li>24% Canva</li><li>22% Google Assistant</li><li>22% Grammarly AI</li><li>9% Grok AI</li><li>7% Bixby</li><li>7% CapCut</li><li>7% Claude</li><li>5% Perplexity</li><li>3% Quillbot</li><li>2% Notion AI</li><li>1% Co-counsel</li><li>1% DeepL</li><li>1% Hemingway AI</li><li>1% Lumo</li><li>1% Meta AI on Facebook</li><li>1% Speechify</li></ul><h3>What people are using AI for</h3><p>We asked people ‘what do you use AI tools for?’ The most common thing people said they were using AI for was to search for information online. 51% of participants use AI tools to search for information online and many see it as a better or faster way of finding information than traditional search engines.</p><p>32% of participants said they use AI for writing. This included starting with their own words and using AI to edit, format or spellcheck. Or, starting with an AI written response and then editing it themselves.</p><p>10% of participants said that they use AI to help with their memory. They mentioned things like reminders and timers, tracking events in calendars, and keeping notes of ideas or important information.</p><p>8% of participants used AI as a social companion. Participants spoke of AI being there to talk to emotionally, or for a general chat. Some participants spoke of AI as being a friend or person.</p><p>7% of participants use AI to create or edit images.</p><p>5% of participants used AI for interpersonal help. Participants use AI to give the correct tone in their communication with others, or to help interpret the correct tone from others.</p><p>5% of participants mentioned that they used AI for voice control to operate things like setting alarms, contacting friends and family, and controlling household appliances.</p><p>5% of participants said that they use AI for employment support. For example, searching for jobs and applying to jobs.</p><p>5% of participants use AI for organisational tasks. Such as goal setting, managing projects and to-do lists.</p><p>5% of participants said that they use AI to help with technology. For example, coding and learning how to use devices.</p><p>3% of participants said they use AI to generate ideas and prompts for themselves.</p><p>3% of participants use AI for online shopping.</p><p>3% of participants use AI to help them understand information.</p><p>2% of participants said they use AI to summarise long pieces of text or multiple pieces of information.</p><h3>Using AI to look for information and advice</h3><p>51% of people mentioned using AI to search for information earlier in the survey. But in answer to the direct question: ‘do you use AI tools to look for information and advice online?’ 75% of participants said yes. The percentage of people who said they looked for specific topics using AI were:</p><ul><li>25% medical</li><li>14% hobbies and interests</li><li>11% employment. For example, finding and applying for jobs, references and running a business.</li><li>9% “serious admin”. For example, admin related to systems like benefits, policy and local authorities.</li><li>9% general knowledge. For example, current affairs and the weather.</li><li>8% of participants said they use AI tools to find information or advice about “everything”</li><li>8% rights and legal information</li><li>8% disability-related topics</li><li>7% financial. For example, financial support.</li><li>7% technical knowledge</li><li>7% household. For example, cooking and DIY.</li><li>5% products and services</li><li>5% social and interpersonal. For example, how to interact with different people in different contexts.</li><li>3% travel</li><li>2% accessing support</li></ul><h3>Sharing what we learn</h3><p>In a future post we will share:</p><ul><li>the benefits and concerns around AI tools</li><li>what barriers people experience when using AI tools</li><li>the perceived trust, ease of use and usefulness of AI for finding information and advice online</li><li>how confident people feel using AI tools to find information and advice online</li></ul><p>We are part of a user behaviour and AI learning group. We meet monthly to share and learn about how our audiences use GenAI. Our second meetup is on 10 November at 12pm. You can <a href="https://events.teams.microsoft.com/event/779e8249-421f-41f4-acf2-4c966f459225@9e80049b-f723-4dc7-af0b-f748fc582b96">sign up to attend</a> and help shape the future of the learning group.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dd20df66c50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/which-ai-tools-are-disabled-people-and-their-families-using-0dd20df66c50">Which AI tools are disabled people and their families using?</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Researching how disabled people and their families look for information and advice using AI tools]]></title>
            <link>https://medium.com/content-at-scope/researching-how-disabled-people-and-their-families-look-for-information-and-advice-using-ai-tools-1750d04eb5e9?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1750d04eb5e9</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research-and-testing]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 16:17:51 GMT</pubDate>
            <atom:updated>2025-10-27T16:27:21.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An AI-generated image of a woman with wavy hair in a witch hat. She is hugging a black labrador dog who is wearing a wizard hat and cape. They are sat on a porch surrounded my pumpkins with faces carved in them." src="https://cdn-images-1.medium.com/max/1024/1*tzJguBzWxcxUt91y55VXOQ.png" /><figcaption>An AI-generated image of Ema and Douglas the user research dog dressed up for Halloween.</figcaption></figure><p>The Content Design team at Scope creates and maintains information that aims to support disabled people and their families to solve problems. Like many organisations, <a href="https://medium.com/content-at-scope/the-impact-of-ai-on-online-support-and-advice-aa8452af0aa7">views of our online information and advice from visits to our website have decreased over the last year</a>.</p><p>We want disabled people and their families to find the information they need when they need it. Increasingly this may be through Artificial Intelligence (AI) platforms and tools such as ChatGPT and AI overviews in Google search results.</p><p>Earlier this year we tried to update our content strategy to improve how we design content for disabled people who are using AI tools. We found a lot of information on best practices to be included in AI-generated responses. But we could not find any research on how disabled people are using AI to find information and advice online. Without research, we do not know:</p><ul><li>what attitudes disabled people have towards AI</li><li>if or how disabled people are using AI to find information or advice online</li></ul><p>We design content to be human-centred. But AI has changed the tools people are using to look for information and we do not know if this means that user behaviour has changed too. This means we do not know if we:</p><ul><li>are still meeting our users’ needs</li><li>need to change our content strategy or design process</li></ul><p>So, we are doing a research project to find out.</p><h3>A mixed-methods design</h3><p>There is a lot we do not know about how people are using AI to find information online. So, we are using a mixed methods design to find out:</p><ul><li>what AI tools disabled people are using</li><li>what they use AI tools for</li><li>how they use AI tools</li><li>the benefits and concerns around AI tools</li><li>what barriers they experience when using AI tools</li><li>the perceived trust, ease of use and usefulness of AI for finding information and advice online</li><li>how confident they feel using AI tools to find information and advice online</li><li>what actions people take based on their AI use</li></ul><p>The research includes a survey and usability testing.</p><p>The survey will collect a mixture of quantitative and qualitative data.</p><p>The usability testing will include scenario-based tasks so that we can observe people using AI tools to find information about disability-related topics online. We will look at how people use dedicated AI tools, such as ChatGPT, as well as AI summaries.</p><p>We will carry out the observational usability testing with participants who have:</p><ul><li>a diverse range of personal characteristics</li><li>different access needs</li><li>differing levels of digital literacy and confidence using technology</li><li>varying levels of experience with using AI</li><li>different opinions on the use of AI generally</li></ul><p>This will allow us to understand the impact people’s information-seeking behaviour using AI may have on Scope’s <a href="https://www.scope.org.uk/advice-and-support">online information and advice pages</a>.</p><h3>A flexible approach</h3><p>The AI landscape is changing rapidly. And we do not know if these changes will have an impact on user behaviour. So, we plan to repeat the research at intervals to monitor changes to disabled people’s use of AI to find information and advice over time.</p><p>We will use the same methods and materials each time we do the research to allow for comparisons over time. But we do not know how frequently we will repeat the research yet. To help us decide how frequently we will need to repeat the research we will use:</p><ul><li>the findings from the first data collected</li><li>changes in AI technology and tools</li><li>changes to user behaviour we can measure from Google Analytics and Google Search Console. For example, if active user numbers reduce and impressions in search results increase.</li></ul><h3>Sharing our materials and findings</h3><p>Many organisations are facing the same challenges as us. Many will also have small teams and limited resources. As a team we like to work in the open. So, we will be sharing the findings of our research, through blogs and meetups, as we go.</p><p>We are also happy to share the materials we are using for the survey and usability testing with other organisations. And it would be great if those organisations would share what they learn too.</p><p>We are part of a user behaviour and AI learning group. We meet monthly to share and learn about how our audiences use GenAI. Our second meetup is on 10 November at 12pm. You can <a href="https://events.teams.microsoft.com/event/779e8249-421f-41f4-acf2-4c966f459225@9e80049b-f723-4dc7-af0b-f748fc582b96">sign up to attend</a> and help shape the future of the learning group.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1750d04eb5e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/researching-how-disabled-people-and-their-families-look-for-information-and-advice-using-ai-tools-1750d04eb5e9">Researching how disabled people and their families look for information and advice using AI tools</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Year’s resolution for online information and advice: say no.]]></title>
            <link>https://medium.com/content-at-scope/a-new-years-resolution-for-online-information-and-advice-say-no-fe554c91a346?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe554c91a346</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 12:14:51 GMT</pubDate>
            <atom:updated>2025-01-06T15:28:38.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A black labrador peeking around the side of a sofa. He has his head resting on his legs and is giving puppy dog eyes." src="https://cdn-images-1.medium.com/max/1024/1*kCH9SFZqBPsIlF-7EtR8cw.jpeg" /><figcaption>Douglas the user research dog is not a fan of being told no.</figcaption></figure><p>Telling people ‘no’ is hard. Being told ‘no’ is hard. But to take a truly human-centred approach, you need to meet people’s needs. And sometimes that will mean telling them no.</p><h3>Imagine yourself as a user</h3><p>Imagine the scenario. You have a question. So you go to a search engine to look for the answer. You click on the result that looks the most relevant. You cannot find the answer on that page.</p><p>What do you do next? Assume that the answer to your question is no because the page you looked at did not mention it? Or go back to the search results and try another page?</p><p>Most people go back to the search results and try another page. But what happens when you’ve looked at 5 pages or 10 pages and still do not have a definitive answer? How can you decide what action you need to take next if you do not have all of the information you need? You cannot.</p><p>Aside from causing frustration and not being a good user experience, it can make information-seeking inaccessible to a lot of disabled people. So I am asking that this year’s New Year’s resolution be a simple one: give your users clarity. If the answer to something is no or it does not exist, tell people. Just say ‘no’. That clarity will allow people to take action, it just might not have been the action they were expecting.</p><p>How do I know? Because we tried it in 2024.</p><h3>Cost of living payments</h3><p>In 2023 and early 2024, disabled people who received certain benefits were eligible for cost of living payments. When the cost of living payments were first announced, we created content based on the user needs at the time.</p><p>Heading into autumn and winter 2024, keyword data and trends showed us that search queries for ‘cost of living payment 2024’ were increasing. By 70% between October and November. And we started to receive more feedback on the page asking about the next set of payments that covered 2 main questions:</p><ol><li>Will I get another cost of living payment this year?</li><li>Why does your page only include the amounts for older payments?</li></ol><blockquote>“It only contained payment from 2023 it doesn’t mention if there will be any additional payments for autumn/winter 2024 for people on benefits so I don’t think it’s helpful at all”</blockquote><p>We had updated the page a couple of times as the government announced new dates. But no extra dates had been announced and <a href="https://www.gov.uk/guidance/cost-of-living-payment">GOV.UK’s</a> cost of living page also only had past payments.</p><p>Remember the scenario from earlier? Our page feedback survey asks people what they will do next. In this situation, people answered “find up to date information on extra payment for people on benefit in autumn/winter 2024 not information about last year’s”. They did not assume the answer was no, they planned to keep looking.</p><h3>Changing user needs</h3><p>The user need had changed. And the answer to the new question was no. So we updated the page to tell people that no new payments were planned for 2024. But kept the information about how to claim the payments if you were entitled to them but had not received them.</p><p>This change affected the helpfulness rating of the page, as it has with other pages we have done similar things on. Some people rated the page helpful. For example, somebody said:</p><blockquote>“I’m on PIP &amp; was expecting a cost of living payment this month. Received the April one. Your site assured me I’m not going to get it”</blockquote><p>But some people rated the page as not helpful. The written feedback tends to say that the page answered their question, but the answer was not the one they were looking for. Because they were told no. So, has the user need been met? I guess it depends. We could not tell them when they would get a payment that does not exist, so no. But we did give them a clear answer that they would not get it, so yes.</p><h3>A pattern in other places</h3><p>This situation has popped up in our work a couple of times this year in different situations. For example, before we have a <a href="https://medium.com/content-at-scope/first-rule-of-crit-club-talk-about-the-content-9f14e7dd47d7">crit</a> for a piece of content, a user researcher will check that the acceptance criteria for all of the user stories have been met. There have been a few times when acceptance criteria have not been met because the thing people are looking for does not exist. But just because it does not exist does not mean people are not going to look for it. All of our user stories are based on evidence. So we can see that people are looking for it! In this situation, their need in life cannot be met. But their need in information can be. By telling them that they will not find the thing they are looking for. For example, “there are no new Cost of Living Payments in 2024”.</p><h3>Final thoughts</h3><p>As a user researcher, it is not a great feeling to know that you cannot meet people’s needs. But sometimes knowing that you have given clarity has to be enough. The aim of online information and advice is to help people solve problems and take action. But people cannot solve problems or take action if they do not have all of the information they need. The purpose of our team is to provide information and advice for disabled people and their families. Saying when the answer is no still does that.</p><p>So I will approach 2025 with the same soundbite I ended 2024: if the answer is no, we need to tell people no.</p><p>Will you join me?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe554c91a346" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/a-new-years-resolution-for-online-information-and-advice-say-no-fe554c91a346">A New Year’s resolution for online information and advice: say no.</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does it cost to take part in research?]]></title>
            <link>https://medium.com/content-at-scope/what-does-it-cost-to-take-part-in-research-de8307f946d0?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de8307f946d0</guid>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-research-design]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 29 Apr 2024 08:52:28 GMT</pubDate>
            <atom:updated>2024-04-30T08:29:48.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A black labrador puppy sat on his bum facing the camera. He’s putting his right paw on a human left hand." src="https://cdn-images-1.medium.com/max/1024/1*5UqY1ruCT0_J7GpBRj8PTA.jpeg" /><figcaption>For Douglas the user research dog, the cost of taking part in a ‘paw’ has been the same since he was a puppy. 1 paw = 1 treat. He just wishes the cost of taking part in research was as clear.</figcaption></figure><p>I had to take a point out of the <a href="https://medium.com/content-at-scope/do-you-really-need-more-research-50eca65f46d1">do you really need more research blog</a> because:</p><ol><li>the post was already long</li><li>the point deserved more attention than to be a bullet point in a list</li></ol><p>I’ve spoken to people about the blog post and had chance to reflect on that point. Mainly about how it fits with the original blog, but also how it fits with doing research more generally.</p><p>So what was the point? It costs people to take part in your research. And not everybody can ‘afford’ it. And by ‘afford’, I don’t just mean financially. Although it does cost people financially too.</p><p>So, what does it cost a person to take part in your research? And what if the people who need your information, technology or service are the people who cannot ‘afford’ to take part?</p><h3>Financial costs</h3><p>If your research sessions are in person, what will it cost a participant to get there? There may be travel costs such as bus or train fares. Some organisations reimburse travel expenses for participants. But what if people do not have the spare income for an extra journey? What if they cannot afford to wait to be reimbursed?</p><p>If you pay for the tickets in advance, that would be one less cost for a participant. But what if public transport was not accessible? Could you find and pay for accessible transport?</p><p>And what if the participant needs assistance when they’re out and about? Many disabled people tell us that their social care package does not meet their needs. There is also a <a href="https://www.bbc.co.uk/news/uk-england-wiltshire-65034207">shortage of Personal Assistants</a> (PA). If the participant has to use 3 hours of their PA time to attend your research, that is a cost. The participant now has less PA hours that week, which might mean missing out on daily support. The PA is not taking part in your research, but the disabled person is responsible for their travel expenses. So who will pay that cost?</p><p>Online research sessions are not free either. <a href="https://www.scope.org.uk/campaigns/scope-is-here-to-help/about-cost-of-breathing-scope-itv/">Scope’s cost of breathing campaign</a> highlighted the extra costs disabled people are facing during the cost-of-living crisis. We hear from people who do not have gas and electricity. Talking part in online research will cost people in electricity. They’d also need a digital device and access to the internet. But disabled people are twice as likely not to use the internet because they:</p><ul><li>do not have digital skills</li><li>cannot afford the technology or data to get online</li><li>do not have the assistive technology they need to use the internet</li></ul><p>So, what if people do not have the resources or skills they need to take part online?</p><h3>Time</h3><p>Ok so this is an obvious one, you are asking people for their time. But what is that time costing people and what would they have been doing instead?</p><p>Are you looking for people who can take part in sessions at a specific time? Or asking people when they are available and being flexible?</p><p>If people work, they may have taken time off to participate. This could cost them wages, annual leave or their lunch break.</p><p>You might be asking for time of other people and not know it. For example, if people have children or caring responsibilities. Participants may have had to ask somebody to help whilst they take part. And they may have to pay for that.</p><p>If the sessions are in person, incentives may not include travel time. But it will still cost participants that time. For example, the session is 1 hour and the journey is 1 hour each way. So taking part has cost the person 3 hours, but the incentive was for 1 hour.</p><p>Do participants need to do anything before taking part in the session? Emailing the researcher, filling out consent forms, reading information all cost time.</p><h3>Accessibility and identity</h3><p>People should be able to access your research sessions. The Equality Act (2010) says that disabled people have the right to reasonable adjustments that make jobs, education and services accessible to them. But checking if the research session is accessible for them will probably cost your participant.</p><p>People are individuals and what they need will be individual to them. So do not offer a list of adjustments you are willing to make or assume you know what adjustment a participant will need based on their condition. Because what will it cost them if the thing they need is not on the list and they have to ask for it? Or if the adjustment has made your research less accessible to them?</p><p>As a researcher, asking people if there are any ‘reasonable’ adjustments you can make is a start. But who decides what is reasonable? And are you only willing to make adjustments based on disability? As <a href="https://karinacotran.com/blogs/hearingdifferently/unveiling-the-true-self-disability-as-a-fraction-of-identity">Karina Cotran wrote</a>, ‘disability is a fraction of an identity’. So, what about the other fractions of participants’ identities?</p><p><a href="https://medium.com/the-establishment/disabled-people-of-color-struggle-to-be-heard-b6c7ea5af4b4">Keah Brown said</a> that intersecting identities, such as disability and race, can make people feel even more of an outsider. So the cost of not making adjustments to sessions based on other parts of a participant’s identity is that you could make them feel like an outsider.</p><p>We ask people if there are any changes we can make to a session so that they will be comfortable taking part. We don’t mind if they want that change because of their condition, or because of another part of their identity. We want people to be comfortable when they speak to us.</p><h3>How many spoons does your research session cost?</h3><p>Christine Miserandino wrote the <a href="https://butyoudontlooksick.com/articles/written-by-christine/the-spoon-theory/">Spoon Theory</a> to describe how some disabled people have a set number of spoons to use each day. Each task throughout the day costs spoons. So people need to make choices and think consciously about how they use their spoons.</p><p>The way we design research may affect the number of spoons a person needs to take part. For example, travelling to an in-person event may cost more spoons than an online session.</p><p>For one person, an online focus group with other people may use more spoons than an interview with one researcher. But for somebody else, the online focus group may cost fewer spoons than the interview because the person is not expected to speak for the full session.</p><p>So how many spoons are you asking people to give you? And are you willing to ask for fewer spoons, by changing the way you run your sessions? It might mean that people can take part and have spoons left for their evening meal.</p><p>But even if you ask for fewer spoons, there might be extra costs for participants after the research session. For example, some people:</p><ul><li>will need recovery time after taking part</li><li>may spend too many spoons and have to pay them back. This will leave them with fewer spoons for the next day, week or month.</li></ul><p>And for some people, regardless of how many adjustments you make, taking part in your research will be too many spoons. And those spoons will have to be paid back.</p><h3>Final thoughts</h3><p>As researchers, we’re always grateful that people take part in our research sessions. Without them, we would not exist. When I started writing this blog, I wanted it to be a short follow-up. A short list of questions that could help us when planning research or collecting data. Instead, I’ve asked lots of questions. But they are worth considering because they all add up.</p><p>I always knew there was a personal cost to taking part in research. Sometimes you witness it. But when I started writing, I realised how expensive it could be. And how it can lead to research excluding people who cannot ‘afford’ to take part. This can reduce the diversity of participants and could mean that the people who need your information, technology or service the most are excluded.</p><p>There are other practical costs that I haven’t covered. And there are others that I haven’t even touched on, such as the emotional, psychological and social costs. All costs will vary depending on:</p><ul><li>who you are doing research with</li><li>the topic you are researching</li><li>the type of research session you are asking people to take part in</li></ul><p>So here we are, many more words later than I had planned, with me asking again: <a href="https://medium.com/content-at-scope/do-you-really-need-more-research-50eca65f46d1">do you really need more research</a>?</p><p>If you do, can you offer flexibility in how you do research and collect data to reduce the cost? Because if people cannot ‘afford’ to take part, how can we listen to what they have to say?</p><p>Be user-centred and let people choose how they want to have their voices and stories heard. It will reduce the costs to participants and make research more inclusive.</p><p>But taking part in research will never be free! And as researchers, we set the cost of participation.</p><p>P.S. I acknowledge that there is a cost for researchers too. But this point deserved a post of its own.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de8307f946d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/what-does-it-cost-to-take-part-in-research-de8307f946d0">What does it cost to take part in research?</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Content designers as users of user researcher’s content]]></title>
            <link>https://medium.com/content-at-scope/content-designers-as-users-of-user-researchers-content-87c430a2fff0?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/87c430a2fff0</guid>
            <category><![CDATA[information-and-advice]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-needs]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 25 Mar 2024 09:34:13 GMT</pubDate>
            <atom:updated>2024-03-25T09:41:24.889Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OztVK1RquFHkuBtGJNRkyA.jpeg" /><figcaption>Douglas the user research dog is a big advocate of understanding what his audience needs.</figcaption></figure><p>To all content designers and word people, I apologise for the title of this post!</p><p>Somebody once told me that the internal content you create is just as important as the external content you create. So, when content designers kept asking us the same questions about user stories, we thought we might have a problem.</p><h3>The old way of working</h3><p>A user researcher used to write user stories in a set format. For example:</p><p><strong>When…</strong> my savings are going to increase</p><p><strong>I want to…</strong> know how this could affect my benefits</p><p><strong>So that…</strong> I can prepare for changes to my benefits and manage my finances</p><p><strong>As a…</strong> disabled person</p><p><strong>Acceptance criteria</strong></p><ul><li>I know which benefits are affected by savings</li><li>I can find out how my benefits will be affected when my savings increase</li></ul><p>We added these into our workflow, and they were picked up by a content designer. This was how we shared user needs in the team.</p><p>But content designers would often come back to user researchers with the same types of questions. Or a different user researcher would be designing the testing sessions and would ask questions.</p><p>We needed a shared understanding of user needs within the team.</p><p>The first thing we tried was introducing a refinement session. A user researcher would write user stories. Then the user researchers and content designers would have a meeting.</p><p>In this meeting we would look at:</p><ul><li>how users experience problems</li><li>how users move between problems and tasks</li><li>search data to find out the language people use</li><li>how user stories and related pieces of content fit together</li></ul><p>The aim of the session was for us all to have a shared understanding of the user needs. These were helpful and we still do them now. But content designers were still asking the same types of questions in the meetings.</p><p>So we did what user researchers do best… planned a research project to understand our users’ needs.</p><p>The only difference is that our users were content designers.</p><h3>Understanding our users’ needs</h3><p>The aim of the research project was to improve the research outputs we provide content designers. We had 2 research questions:</p><ol><li>What problems and questions do content designers have when using our research to plan and write content?</li><li>What research outputs (content and format) could we provide to help with these problems and answer those questions?</li></ol><p>We did interviews with the content designers to find out their information needs when planning and writing content. For example, some of the questions we asked were:</p><ol><li>What is the first thing you do when you start a new piece of content</li><li>What do you need to know to decide how to organise content?</li><li>What questions do you have about the audience you are writing for at this stage?</li></ol><p>We analysed the data and created journey maps for the content designers. From this, we were able to identify the gaps in the research outputs we created. The content designers needed:</p><ul><li>More information about the audience. For example, who the people are, the tasks they need to do and what people are struggling with.</li><li>More information on context. For example, other challenges people might be experiencing, differences in language and terminology.</li><li>To be able to identify overlapping or related content.</li><li>To be able to group user stories in a structured way.</li></ul><h3>Developing and testing prototypes</h3><p>Based on the needs we identified, we created 4 prototypes for user stories. Each prototype showed the same need in a different format. We tested these with the content designers and asked questions such as:</p><ul><li>What are your thoughts on this user story?</li><li>Is there anything that you still need to know to write content to meet this need?</li><li>Is there anything that is unhelpful?</li><li>What questions would you have when using this?</li></ul><p>We also asked which prototype was the most useful for writing content. And of course they picked 2 different ones! But they were seen as useful for different reasons.</p><p>So, we iterated. We combined the features that content designers found most useful. And took out the things they said were unhelpful.</p><p>We wrote a new user need using a more detailed format. We still call them user stories but they expand on the traditional format. This was the format after iteration:</p><p><strong>When…</strong> I am going to receive inheritance money or property</p><p><strong>I want to…</strong> check how this could affect my benefits</p><p><strong>So that…</strong> I can make the most of my finances and prepare for any changes to my benefits</p><p><strong>As a…</strong> disabled person</p><p><strong>Acceptance criteria</strong></p><ul><li>I know how inheritance will affect my benefits</li><li>I know what I need to contact</li></ul><p><strong>People</strong></p><ul><li>claiming ESA, looking to buy a property</li><li>claiming income-related ESA in the support group, DLA and housing benefit</li><li>claiming old style ESA and PIP</li><li>claiming lower rate PIP and ESA</li></ul><p><strong>Triggers</strong></p><ul><li>I have inherited money.</li><li>I am soon to inherit money.</li><li>I have inherited a property with another person, but they do not want to sell for at least 12 months.</li><li>The property will be rented out and I will receive half of the rental income.</li></ul><p><strong>Contexts</strong></p><ul><li>recently bereaved</li><li>living in unsuitable housing</li><li>in need of disability equipment</li><li>in debt</li><li>worried about losing their benefits when they receive the inheritance or property</li></ul><p><strong>Tasks</strong></p><ul><li>working out what type of benefits they receive</li><li>working out whether inheritance is classed as savings and needs to be declared</li><li>working out what they can use their inheritance for and the effect it will have on their benefits</li><li>planning for the future</li></ul><p><strong>Questions</strong></p><ul><li>If I buy the property with the inheritance can I still receive my benefits?</li><li>Would I need to declare the money?</li><li>Will I still be eligible for means-tested benefits?</li><li>How do you end a claim with DWP when it involves being over the savings threshold?</li><li>When savings go below the £16,000 threshold do you then make a new claim for UC?</li><li>How will the inheritance affect my ESA and PIP?</li><li>What am I allowed to do with the inheritance?</li></ul><p>The content designers agreed that this was a more helpful format. So we started using it. The benefits of this have been that we’ve been more open to trying different ways of presenting user needs. For example, if people in different situations are experiencing the same problem, we used to write 3 separate user stories. But now we’ll write the same user story and show the different situations people are in through the ‘when’, ‘people’ and ‘context’ sections. We are no longer in the habit of sharing our research outputs in a set format because “we’ve always done it that way”.</p><p>Since we started using the new format, we’ve also added to it. We now have a section for keywords which are specific to that user story. This means content designers can:</p><ul><li>see connections between user stories if they have similar search profiles</li><li>avoid using the same keywords across multiple pages of content which is bad for SEO and could cause confusion for users</li></ul><p>One of the needs we could not fully meet with the new user story format was giving content designers the information they needed to be able to group user stories in a structured way. This is because how they should be grouped sometimes depends on the answer. To help meet this need, we added scoping sessions with a subject expert into our workflow. Chloe talks about <a href="https://medium.com/content-at-scope/rewriting-our-social-care-content-6b3cec464137">how content designers structure user stories in her blog on the social care rewrite.</a></p><h3>Stand the test of time?</h3><p>We did this project in autumn 2021. So why has it taken so long for us to write about? We had to try them in real life.</p><p>We cover content on lots of different topics. Some are more complex than others. Some can overlap with other user needs or topics. We’ve tried the new format for lots of different scenarios. So far we have noticed:</p><ul><li>we have shorter refinement sessions and can cover more user stories in them</li><li>content designers are asking less, if any, questions about the user needs</li><li>it is easier for us to design scenarios and tasks to test if a user need has been met</li><li>we are identifying relationships and dependencies from the start of our workflow</li></ul><p>As Chloe mentioned in her recent blog, the content we’ve been working on recently has been complex and interconnected. This is because the user needs are complex and interconnected. Some of our recent user stories have had 20 acceptance criteria. But the new user stories are still working as a way of:</p><ul><li>describing user needs</li><li>sharing an understanding of user needs between user researchers and content designers</li><li>testing if user needs have been met</li><li>showing the situations people are likely to be experiencing</li><li>identifying relationships and overlap between needs and topics of content</li></ul><p>We have even used the new format of user stories to improve existing content. By revisiting the data we have on a topic and rewriting the user stories in the new format, we have been able to:</p><ul><li>merge 2 or more existing pages</li><li>expand the scope of content</li><li>use internal links to help people solve problems and move through content that is interlinked</li></ul><h3>Final thoughts</h3><p>Internal content is just as important as external content. And taking the time to meet your users’ needs as a user researcher can improve your ways of working and save you time in the long run.</p><p>The format of the new user stories is not set in stone. Because user needs are not set in stone. They are a snapshot of a set of users at a specific moment in time. So, if:</p><ul><li>content designers start asking questions or need more information</li><li>we cannot test if a need has been met</li><li>we cannot show the relationships between needs and topics</li></ul><p>we’ll revisit the format and iterate so we can keep on meeting our users’ needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87c430a2fff0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/content-designers-as-users-of-user-researchers-content-87c430a2fff0">Content designers as users of user researcher’s content</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you really need more research?]]></title>
            <link>https://medium.com/content-at-scope/do-you-really-need-more-research-50eca65f46d1?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/50eca65f46d1</guid>
            <category><![CDATA[cost-of-living]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[trauma-informed]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 09:51:13 GMT</pubDate>
            <atom:updated>2024-02-05T11:44:48.621Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A big black labrador stood on his back legs with his paws on a wooden kitchen counter. His little pink tongue is peeking out as he serves the humans 2 plated of blueberry pancakes with little dishes of maple syrup." src="https://cdn-images-1.medium.com/max/1024/1*9_IXpxECi-jYVL0BBN-7gg.jpeg" /></figure><p>Douglas, the user research dog, says you can never have too much!</p><p>Content warning: this blog talks about the cost-of-living crisis and the financial hardship people are experiencing.</p><p>The title of this blog might sound like I’m trying to talk myself out of a job. I’m not! It might also sound like the title of a blog just for researchers. It’s not.</p><p>This blog is an opportunity for reflection for anybody who does research or uses data and research findings in their work. So yes, it is for researchers. But it’s also for leaders, decision-makers, policymakers, press, academics, government officials and anybody else who uses data in their work.</p><p>It’s a reflection of how 2 things that have taken up a lot of my headspace for the last few months can be connected:</p><ol><li>trauma-informed research practice</li><li>waste</li></ol><p>And about asking ourselves if we really need more primary research using traditional data collection methods like interviews and surveys. Especially for ongoing topics that are causing distress or trauma to the people who are experiencing them.</p><p>I’ve used the cost-of-living crisis as an example, but this can be applied to everything.</p><h3>Before the cost of living became a crisis</h3><p>In early 2022, long before ‘cost-of-living crisis’ became a household term, we were doing a discovery project to identify gaps in the advice and support we offer disabled people. As part of this, we analysed the emails sent to the Scope helpline to identify information needs.</p><p>Analysing the emails offered us insights on:</p><ul><li>the naturally occurring information needs of disabled people</li><li>the language people use to talk about problems they are facing</li><li>what problems people come to Scope for help with</li></ul><p>At this time, the cost of energy was increasing and lots of people were getting in touch with us for advice on paying for gas and electricity. But we noticed another pattern. A lot of people were asking for help to get food at the same time. At the time, the media were talking about a choice between heating or eating. But lots of disabled people were already going without gas, electricity AND food. There was no choice.</p><p>From the data in the emails we analysed, we were able to write a user story and prioritised creating the <a href="https://www.scope.org.uk/advice-and-support/food-no-money-food-banks/">free food and food banks</a> page in our workflow. We aim to provide content that helps people to solve problems. We tested the page with people who had accessed food banks in the past.</p><p>From testing, we learned that sometimes the biggest barrier to solving a problem is experiencing negative attitudes. Participants spoke about the emotional cost of having to retell their story over and over when seeking help. They also told us about the shame and judgement they felt when needing to access a food bank. Shame and judgement can lead to <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7613638/#:~:text=Shame%20anxiety%20is%20commonly%20characterised,part%2C%20is%20not%20necessarily%20experienced.&amp;text=Shame%20anxiety%20appears%20in%20first,labelled%20and%20rejected%20by%20others.">shame anxiety</a> and trauma. Shame anxiety and trauma can make it hard for people to ask for help. And so the cycle continues…</p><h3>Is now the right time to be asking questions?</h3><p>Living in poverty and food insecurity can cause trauma responses and affect the physical and mental health of children and adults (<a href="https://www.therobertsontrust.org.uk/about-us/about-poverty-and-trauma/">The Robertson Trust</a>). This is something we have heard from disabled people and their families. For example, people have told us that:</p><ul><li>symptoms of their condition are getting worse</li><li>they are experiencing anxiety, depression and hopelessness</li><li>they are trying to access mental health services but there are long waiting lists</li><li>they are <a href="https://www.samaritans.org/how-we-can-help/contact-samaritan/">contacting Samaritans</a> more frequently</li></ul><p>Disabled people have told us that their current situation is “filling me with fear”. So should we be doing research with people who are experiencing trauma and fear? In our user research ethics policy, we say that we balance the safeguarding of participants with the need to include their voices. One of the ways we can do this is by being flexible about how we collect data.</p><p>Over the last 18 months we have been asked a few times what evidence and insights we have on the cost-of-living crisis. And if anything has changed in the last few months.</p><p>Some of this data has been collected for a specific purpose, such as to support a campaign. But most of it is data that we collect in our daily working. We aren’t asking people about their experience of the cost-of-living crisis, but people are telling us about it when they contact us for advice and support. We can still identify the problems and needs of disabled people during the cost-of-living crisis, but we aren’t risking causing further distress or harm to people.</p><p>For example, by using a survey to get feedback on <a href="https://www.scope.org.uk/advice-and-support/">Advice and support</a> pages. And asking for consent to use the responses for research, marketing and campaigns.</p><p>What one person experiences as a sensitive or traumatic topic might be fine to talk about with somebody else. But trauma is trauma. Ethically, you would be very cautious when asking somebody living in an abusive home about their experience. You wouldn’t go back to those people on multiple occasions to ask them how much worse their situation is compared to last year. So why would you do it for other topics which can cause trauma responses?</p><p>We’ve tried to avoid going back to disabled people and asking them how much worse the cost-of-living crisis is this winter compared to last winter. We’ve been quite successful in this. But mainly because people are coming to us to tell us how much worse it is. We haven’t asked a question. But we still have the research findings.</p><h3>What a waste!</h3><p>The <a href="https://publications.europa.eu/resource/cellar/d375368c-1a0a-11e9-8d04-01aa75ed71a1.0001.01/DOC_1">European Commission</a> estimates that the cost of not having research data that is Findable, Accessible, Interoperable and Reusable (FAIR) is €10.2 billion. So, instead of doing more research, is there anything you could do to improve your <a href="https://researchops.community/about/">ReOps</a> (the people, mechanisms and strategies that support researchers to deliver research findings)?</p><p>Specifically, could you improve your:</p><ul><li>admin — to ask for consent to use data you are already collecting for research purposes</li><li>tools — to collect and store data in a way that makes it accessible and findable</li><li>data and knowledge management — to make the data you already have accessible to the people who need it and reusable for other projects</li></ul><p>Could you make your research data FAIR? Ask yourself:</p><ul><li>What data do you already have on a topic?</li><li>What do you already understand about a problem your audience are experiencing?</li><li>How easy is it to find it?</li></ul><p>For example, asking people for their consent to use the data they are giving you in a contact form, would let you use that data in your research. That data is the naturally expressed experiences of people, told in their own words. It would also avoid the emotional cost of people having to retell their story over and over.</p><p>Also, where do people naturally come into contact with your organisation? In our team, we talk about meeting people where they are to solve problems. This applies to research too. Where are the people coming into contact with your organisation? Can you meet them there? Are you already collecting data there?</p><p>For example, at Scope, we have:</p><ul><li>colleagues who speak to people every day</li><li>helplines and services</li><li>emails, online forums, social media accounts</li><li>feedback forms</li></ul><p>As well as reducing the costs of doing research and being better for the environment, it could mean that you only need to do more research when you actually need more research. And that means there is less risk of harm to people.</p><h3>Final thoughts</h3><p>So yes, in an ideal world, we would do research and collect data that is:</p><ul><li>representative</li><li>replicable</li><li>generalisable</li><li>rigorous</li></ul><p>But do any of those characteristics outweigh research that is ethical and humane? I don’t think so.</p><p>Does an event or a phenomenon that disproportionately affects a smaller group of people, but has devastating consequences on their lives, make it any less worthy of research? I don’t think so.</p><p>So maybe sometimes it’s ok if data tells a story about the experiences of a smaller group of people. And maybe it’s ok if you’ve analysed data that you’ve collected without asking anybody any questions. The findings are still valid. You should still use them.</p><p>In an earlier blog on <a href="https://medium.com/content-at-scope/participant-wellbeing-c7db5edc6781">participant wellbeing</a>, Grace spoke about “do no harm” and if the avoidance of harm is the best we can aim for as researchers. She spoke about how we can make research flexible and give participants agency. But there is something else we can do. We can ask ourselves “do we really need more research?”</p><p>An important part of being a researcher is being reflective. This includes before doing things, as well as after. So please, when you’re planning your next research or planning to use research findings in your work, ask yourself:</p><ul><li>What data do we already have on this?</li><li>Do we, or can we, collect data about this in our organisation’s existing work?</li><li>Is asking people about this right now likely to cause them distress or harm?</li><li>Does the benefit of having the data outweigh the costs to the participants?</li></ul><p>After answering those questions, you might decide you do need to do more research. That’s ok.</p><p>But if there is an opportunity, be bold. Do research differently using non-traditional methods.</p><p>Or be even bolder, and don’t do research at all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50eca65f46d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/do-you-really-need-more-research-50eca65f46d1">Do you really need more research?</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A happier new year with GA4?]]></title>
            <link>https://medium.com/content-at-scope/a-happier-new-year-with-ga4-1d63c49940ff?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d63c49940ff</guid>
            <category><![CDATA[ga4]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[digital-analytics]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Mon, 08 Jan 2024 10:13:02 GMT</pubDate>
            <atom:updated>2024-01-08T15:22:31.665Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*e7taYnOUnt6uH_3e9OqMuw.jpeg" /><figcaption>A white and red firework exploding in a clear dark sky.</figcaption></figure><p>I had lots of fun work stuff I wanted to do in 2023. But instead, I spent a lot of time learning how to use GA4.</p><p>For anybody who uses Google Analytics, GA4 gave 2023 the parody and meme content we all needed. I was just glad I wasn’t the only person who thought that GA4 was an atomic bomb on my to do list.</p><p>I spent a lot of early 2023:</p><ol><li>opening GA4</li><li>pressing buttons</li><li>getting frustrated that I couldn’t make it do what I wanted it to do</li><li>closing GA4</li></ol><p>But when the warning banners and countdown clock appeared I knew I had to start getting to know it. We had a lot of help with the setup from Graham at <a href="https://www.dotfound.co.uk/">dotfound</a>. I also attended <a href="https://www.measurelab.co.uk/training/google-analytics-4-immersion/">Measurelab’s GA4 immersion course</a>. This course really helped me, and Dan was fab. For anybody who, like me, needs to know the ‘why?’ for everything, this course answered that without making you feel like a nuisance. And no, they haven’t paid me to say this!</p><p>Now it’s the start of 2024 and I’ve had some time to learn to live with it. We’ve had some problems along the way, and I don’t love it for reasons I’ll go into. But it has given us some new data points. And we have new ways of measuring page performance which have helped us make better decisions. So hopefully 2024 will be a happier new year with GA4!</p><h3>Accessibility</h3><p>I’ll get this one out of the way first. Mainly because it’s just plain sad.</p><p>There are some positives. For example, GA4:</p><ul><li>announces when something is a text field, such as a search box</li><li>reads tables from left to right</li></ul><p>But, for all their work on assistive tech and providing support services like the <a href="https://support.google.com/accessibility/answer/7641084?hl=en#:~:text=The%20Google%20Disability%20Support%20team%20is%20available%20to%20support%20users,,%20functionalities,%20and%20assistive%20technology.">Google Disability support team</a>, GA4 is not accessible. I’d had higher hopes because:</p><ul><li>GA4 is brand new and could have been designed to be accessible from the start</li><li>some of the accessibility issues are basic, such as having a structure and labelling buttons</li><li><a href="https://about.google/belonging/disability-inclusion/">Google claim they’re co-creating a world where disabled people can thrive</a>, just not if they need to use GA4 at work</li></ul><h3>Usability</h3><p>As a user researcher, usability is obviously pretty high on my list of priorities. GA4 is a lot faster than Universal Analytics (UA).</p><p>But it’s not intuitive and it’s not user friendly. There are some big things like it is visually overwhelming. But then there are smaller things like only being able to search an entire data table rather than a specific column within the table.</p><p>On the plus side, the interface is customisable which means you can hide the things you don’t need. Being able to show only the data we need in a <a href="https://support.google.com/analytics/answer/10659307?hl=en">collection of reports</a> has improved the usability for our team.</p><p>Learning to use GA4 after using UA is hard. I wonder what it is like for somebody new to digital analytics. The best advice I’ve had, and that I have since passed on, is forget everything you know about analytics.</p><h3>Custom events</h3><p>Now, onto the good stuff. If you work in an organisation where lots of people use analytics, but one person manages Google Tag Manager, GA4 lets you create events without adding to somebody else’s workload!</p><p>You can create new events<a href="https://www.measurelab.co.uk/blog/create-customised-events-ga4/"> using the User Interface</a> (UI). You can give the event a custom name and set the parameters. The event will start collecting data straight away and be visible in your list of events, normally, the next day.</p><p>You create new events based on existing events, which means you can adapt the automatically collected events to meet your needs. For example, we have created 2 new events that only our team use based on the automatically collected Click event:</p><p>1. internal link click: link clicks to other advice and support pages</p><p>2. external link click: link clicks to any external organisations (this excludes clicks which have different domains such as our online community)</p><p>The addition of creating custom events on the UI also means you can add events beyond automatically collected events. So you can collect the data that will best help you to make decisions. My favourite custom events that we have are page_read and view_content.</p><h3>page_read</h3><p>Before GA4, we used to do what we called a red flag audit. It was a complicated spreadsheet that included UA data on scroll depth and link clicks. It included data from other sources such as a helpful rating that is collected in our CMS. We used it to identify the 5 pages we thought were performing least well so that we could look at ways to improve them.</p><p>Our hypothesis was that if people were not scrolling down a page or clicking on any links on the page, then the engagement rating for the page was poor. We had some great improvement successes from doing this, but it was time-consuming for the team.</p><p>With GA4, page_read tracks how many times users scroll to 75% of a page and spend at least 30 seconds on the page. Combined with the internal and external link clicks in 1 report, this gives us a better understanding of how pages are performing without having to export and manipulate the data manually.</p><h3>view_content</h3><p>Before GA4, we relied on scroll depth to try to work out how far down a page people were reading. But we could only guess exactly how far down a page 50% scroll depth was. We had trialled <a href="https://www.measurelab.co.uk/blog/create-customised-events-ga4/">Silktide heatmaps</a> which show you which part of the page people are reading to. This was useful for us, but not in our budget this year.</p><p>How far down a page people read is important for designing advice content. If there is something that is important or could cause harm to people, it needs to be where people will see it. But the order of information on a page must make sense too.</p><p>Sometimes we get feedback to say that something is missing from a page. When we check, the information is often there. But not near the top of the page. We wished we could see which headings people were reading to so that we could decide if we needed to change the order of the page.</p><p>With GA4, we now have the view_content event. This event tracks how many times users view each heading on a page. This event has a partner select_content event that tracks how many times users click on a heading title in a side menu. These 2 events show us how often users go to a specific section of the page. This makes it easier to decide if we should change the order of information.</p><h3>2024 with GA4</h3><p>This year, I feel more comfortable with GA4. We’ve updated our data report templates and built some Looker Studio dashboards for internal reporting. I like the freedom custom events offer and how they let you look at your data in a different way. Hopefully it’s something that we’ll develop and update as our design needs change. I’d be interested in hearing about the custom events other people have set up!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d63c49940ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/a-happier-new-year-with-ga4-1d63c49940ff">A happier new year with GA4?</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing content about death]]></title>
            <link>https://medium.com/content-at-scope/testing-content-about-death-98ecb0f56911?source=rss-717d71b9269f------2</link>
            <guid isPermaLink="false">https://medium.com/p/98ecb0f56911</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[death]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Ema Thornhill]]></dc:creator>
            <pubDate>Tue, 29 Aug 2023 14:01:10 GMT</pubDate>
            <atom:updated>2023-08-29T14:37:05.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An old willowy tree with a hollow trunk. It has a mixture of dead branches and branches covered in deep green leaves." src="https://cdn-images-1.medium.com/max/1024/1*b_dsxAIBKiQ5M3B7oeYIjA.jpeg" /></figure><p>Content warning: this blog post talks about providing information and people’s experiences of planning for their death and bereavement.</p><p>It’s the circle of life.</p><p>Yes, The Lion King is my favourite Disney film. But it’s also something that was said to me in a recent testing session about explaining death.</p><p>Other things that people have said when we’ve been testing content on the topic of death include:</p><ul><li>I am human. I will die.</li><li>Death is inevitable. It will happen to us all.</li><li>Everybody dies. Knowing everybody dies will make it less of a big deal.</li></ul><p>There was an acceptance that death is an event that will happen in all our lives. But research by <a href="https://www.mariecurie.org.uk/globalassets/media/documents/policy/public-attitudes-to-death-and-dying-report-final.pdf">Marie Curie</a> found that 51% of participants thought that, as a society, we do not talk enough about death and dying.</p><p>So, if we don’t talk about it enough, what do we do when we need to plan for our death, or somebody dies? Our analysis of emails to our helpline, posts to our online community and interviews we did with disabled people showed that people come to Scope for advice and support about:</p><ul><li>planning for their own death</li><li>what to do when somebody dies</li></ul><p>Our research found that planning for death and somebody dying can be even more challenging for disabled people.</p><ul><li>Communicating what you want and need when you die is important for disabled people, especially if they have had negative or traumatic experiences with the health and social care systems.</li><li>The cost of planning for death can often be higher for disabled people and their families, both financially and emotionally. For example, the legal costs of setting up a trust and not wanting to affect the lives of other people by asking them to care for their disabled child.</li><li>There is greater pressure on parents of disabled children to get it right. They must balance what they want to happen when they die, with what their child may need for the rest of their life. The decisions they make and the plans they leave will affect:<br>- their child’s quality of life<br>- who will care for their child and keep them safe<br>- where their child will live<br>- their child’s financial security<br>- if somebody has control of, or manages, their child’s finances</li><li>Accessing financial support after somebody has died and paying for a funeral is difficult for disabled households who already need an <a href="https://www.scope.org.uk/campaigns/extra-costs/disability-price-tag-2023/">additional £975 a month to have the same standard of living as non-disabled households.</a></li></ul><p>Keyword research also showed that lots of people look for information about death using search engines.</p><p>The information needs we identified and created content for covered a broad range of topics including:</p><ul><li>making a will</li><li>setting up a trust for inheritance</li><li>what to do when somebody dies</li><li>explaining death and bereavement support</li><li>benefits, financial support and housing when somebody dies</li></ul><h3>Recruiting participants</h3><p>We did not know how easy or hard it would be to recruit participants to give us feedback on content about death. For the content on wills and trusts, we recruited people who used our <a href="https://www.scope.org.uk/giving/free-will-offer/">free wills service</a>.</p><p>For the content on what to do when somebody dies and the support pages after somebody dies, our awesome Panel Executive recruited people from <a href="https://www.scope.org.uk/research-panel/">Scope’s Research Panel</a>.</p><p>Our Panel Executive said that there are far more people interested in talking about death than you think there would be and had the following advice.</p><ul><li>Give extra detail about what the sessions will be like.</li><li>Give extra examples of adjustments we can make and ways that participants can take control. For example, giving people the option to meet the researchers before the session was appreciated.</li><li>Include more death-focused signposting in pre- and post-session emails, alongside the usual! And be extra speedy sending post-research emails.</li><li>Be aware of the balance between “Speaking to you really helps us” so they know we appreciate their time and experiences and “We won’t be worse off if you don’t fancy it” so they don’t feel guilty at the idea of saying “Actually, no thanks”. This is always needed, but especially with these sessions.</li><li>Knowing that I’m sending them to excellent researchers who will take care of them and keep their comfort as the priority.</li></ul><p>Recruitment has not been straightforward. We’ve struggled to find people who could give us feedback on information about benefits for people with a terminal illness.</p><h3>How to talk about death in a testing session</h3><p>Marie Curie’s research found that, with family and friends, most people (65%) are comfortable or very comfortable discussing death and dying in general. With even more people feeling comfortable or very comfortable talking specifically about:</p><ul><li>end of life wishes for treatment and care (72%)</li><li>end of life wishes around death (74%)</li><li>funeral arrangements (74%)</li><li>financial affairs (75%)</li></ul><p>As a person, I am comfortable talking about death and dying. But I’ve been told in the past that I can be quite blunt because I talk about it using ‘dead’, ‘death’ and ‘died’. So, I was expecting people to be less comfortable talking about it than they turned out to be. As a researcher, it was a new topic to me, and I knew the language would affect the experience the participant had during the session.</p><p>An important part of <a href="https://www.scope.org.uk/about-us/house-style-guide/">Scope’s house style</a> is that we respect other people’s language choices. And as a team we are moving to a trauma-informed approach to user research, where principles of empowerment, voice and choice are central. So, this is the approach we took during testing sessions, with participants deciding and guiding what language we should use.</p><p>Before a session, we have a little bit of information about a participant’s experience. We used this information to find out how a person would like to talk about death in the session. For example, “The Panel Executive told us that your parent died. Would you prefer us to talk about when your parent died or more generally about when somebody has died?”</p><p>Most people wanted us to talk about their specific situation. But there were a couple of people who wanted to talk about ‘somebody’. We didn’t ask why participants wanted to talk more generally, but one said it ‘felt a bit morbid’ to think about their own death and another person said it was ‘too close’ to speak about the death of their parent.</p><p>Even when people asked to speak about death generally, they often spoke about their personal experience and applied the information to their situation. The important thing for us was that they did this in a way they felt comfortable.</p><p>At Scope we try to use Plain English. But when talking about death, lots of euphemisms are used. One of the first questions we asked in the sessions was for people to share a little bit about their experience. This let us find out what language people used and reflect this during the session. For example, if people said a person died, we would say ‘died’. But if they said a person ‘passed away,’ we would use ‘passed away’.</p><h3>What we learned from testing sessions</h3><p>1. When people are looking for information about what they need to do when somebody dies, or their rights for housing and financial support, they want their emotions to be acknowledged. Participants told us that recognising their situation is emotional and not just procedural shows that you understand. And that they were more likely to trust the information if they felt it understood them.</p><p>2. Reassuring people that there is no right or wrong response to somebody dying. Participants thought that it was important to say that people react differently when somebody dies and to reassure people that having different emotions or behaviour to somebody else is OK.</p><p>3. Language is important, but it is also personal. In testing sessions, we were able to tailor our language to each participant. But in the content we were testing, we had to find a shared language. There was a mixed opinion on some phrases.</p><ul><li>‘Dead’ and ‘died’ sometimes felt jarring to participants but was also seen as clear.</li><li>‘Has lost someone’ and ‘passed away’ felt softer to some people but were seen as confusing to neurodivergent people and parents explaining death to children.</li><li>’Is no longer alive’ was seen as a clear way of saying died by people who found it emotionally hard to read ‘dead’.</li></ul><p>4. Autonomy and choice were important in testing sessions.</p><ul><li>Giving people choices over how the sessions would happen and what they needed to feel safe and comfortable.</li><li>Sharing the content in advance so people could look at it before the session if they wanted to.</li><li>The environment. For example, who was there or if cameras should be on during videocalls.</li><li>The language used, what we would or wouldn’t ask questions about, sharing only what participants felt comfortable with.</li></ul><p>5. Content needs to offer autonomy and choice.</p><ul><li>Planning for death and dealing with somebody dying are personal. If there are options, tell people about them. Participants felt that it gave them more control in the situation and helped them to be more objective.</li><li>Participants felt that giving options removes the pressure from people so that they do not feel like they are making the wrong decision.</li><li>People wanted a choice of different tools they could use to help them explain death to somebody else. Parents of disabled children said that different options would help them to explain death using something that their child was already familiar with, that was appropriate for their age and abilities. Parents suggested:<br>- words and phrases<br>- videos<br>-storybooks</li><li>Finally, participants said that when somebody has died it can make it more mentally challenging to read information and understand what they need to do. People wanted actions to be presented in a clear way, and often requested formats that would help them to remember what they need to do. For example, a checklist. People also wanted to be able to access a human if they needed help or to check they were doing something properly. But participants wanted to be able to contact people in different ways depending on how they were feeling. For example, some people wanted a phone number so they could speak to a person and get reassurance. Whereas other people wanted an email address or text function as they did not want to get upset speaking to a person on the phone. So, providing a choice of contact methods was preferred.</li></ul><p>I’ll leave you with the words of 2 participants who summed up my experience of testing content on death perfectly:</p><ul><li>“Nobody teaches you about what you need to do when somebody dies. And by the time you need to know it feels too late.”</li><li>“Death is sad, but we need to normalise it.”</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98ecb0f56911" width="1" height="1" alt=""><hr><p><a href="https://medium.com/content-at-scope/testing-content-about-death-98ecb0f56911">Testing content about death</a> was originally published in <a href="https://medium.com/content-at-scope">Content at Scope</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>