<?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 Chris Bush on Medium]]></title>
        <description><![CDATA[Stories by Chris Bush on Medium]]></description>
        <link>https://medium.com/@chrisjbush?source=rss-62d656b60d9a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tSsSYomcr55g33PgrKR0Tg.png</url>
            <title>Stories by Chris Bush on Medium</title>
            <link>https://medium.com/@chrisjbush?source=rss-62d656b60d9a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:27:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisjbush/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[Field notes: Exploring AI transcription services for inclusion]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://chrisjbush.medium.com/https-medium-com-suthen-exploring-ai-transcription-services-for-inclusion-5c4d009f8ac6?source=rss-62d656b60d9a------2"><img src="https://cdn-images-1.medium.com/max/1663/1*AVd1a0CzHD2lFA7z33SWug.jpeg" width="1663"></a></p><p class="medium-feed-snippet">Can AI transcription improve peoples access to content?</p><p class="medium-feed-link"><a href="https://chrisjbush.medium.com/https-medium-com-suthen-exploring-ai-transcription-services-for-inclusion-5c4d009f8ac6?source=rss-62d656b60d9a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://chrisjbush.medium.com/https-medium-com-suthen-exploring-ai-transcription-services-for-inclusion-5c4d009f8ac6?source=rss-62d656b60d9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c4d009f8ac6</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Chris Bush]]></dc:creator>
            <pubDate>Fri, 10 May 2019 10:25:36 GMT</pubDate>
            <atom:updated>2019-05-10T10:25:36.767Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Design principles for pensions and financial services]]></title>
            <link>https://chrisjbush.medium.com/thinking-about-design-principles-for-services-that-span-a-persons-career-or-lifetime-52b8d021f925?source=rss-62d656b60d9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/52b8d021f925</guid>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Chris Bush]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 19:26:44 GMT</pubDate>
            <atom:updated>2024-06-28T20:52:39.358Z</atom:updated>
            <content:encoded><![CDATA[<p>Currently, there are very few digital services that are designed to span a career or lifetime of user interaction.</p><p>Some forward thinking services (like www.MinPension.se – which I’ve had the privilege of working on over the past four years) were quick to realise how significantly their user needs would change over the course of their lifetime, and our team began to research and design tools that were specifically aimed to meet these needs at the different stages of a user’s life or career.</p><p>This got me thinking, currently many digital services focus on singular, recurring needs that a user’s might have and rarely do they explore the wider context of the users situation and seek to find opportunities to add more meaningful value.</p><p>For many current digital services, public or otherwise this is not likely to cause an issue, but as open data becomes more prevalent in society and as our expectations move closer and closer to seeing our personal data joined up in ever more useful and insightful ways, it is highly likely that we will see more services emerging that will aim to be lifelong companion service. These emerging services will look at the separate pieces of data we have in numerous sources, enquire about or evaluate the data and seek to make suggestions that will help us make better or more informed decisions.</p><p>So, taking inspiration from <a href="https://www.gov.uk/guidance/government-design-principles">Government Design Principles</a>, I started to draft a a rough set of design principles for a companion service that could span an individuals career/lifetime, and rather than have them sit on my hard drive gathering dust. It felt much more useful to share them in a public space and see if anybody else has had similar thoughts and considerations.</p><p>PLEASE NOTE: These are not a final set of principles, they are just a collection of thoughts based around the idea of nurturing a user through a complex service over a prolonged period of time.</p><ol><li><strong>Start with the user’s needs (</strong><a href="https://www.gov.uk/guidance/government-design-principles#start-with-user-needs"><strong>GDS</strong></a><strong>)</strong><br>Start by identifying user needs. If you don’t know what the user needs are, you won’t build the right thing. Do the research, analyse data, talk to users. Don’t make assumptions. Have empathy for users, and remember that what they ask for isn’t always what they need.</li><li><strong>Keep it simple (</strong><a href="https://www.gov.uk/guidance/government-design-principles#do-the-hard-work-to-make-it-simple"><strong>GDS</strong></a><strong> — modified)</strong><br>Making something look simple is easy. Making something simple to use is much harder — especially when the underlying systems are complex — but that’s what we should be doing. This applies to everything we create including Task flows, Content and form design, Tone of voice, UI and Visual hierarchy, Consistency, Error messages, Hand over to third-party systems.</li><li><strong>Speak the user’s language.</strong><br>Avoid jargon. We should speak the user’s language with words, phrases and concepts familiar to the user, rather than process-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.</li><li><strong>Understand the context.</strong><br>The processes our users are going through are variable, some are simple and can be achieved in a few minutes, some are complex and can take many months. For each process being designed, look at our existing research to understand the users, their situation and their motivations to provide the support and guidance to help them through to the next stage.</li><li><strong>No dead ends/Cul-de-sacs.</strong><br>Our users will be dipping in-and-out of their service journey whilst dealing with everyday life. If a user is unsuccessful in completing a process always aim to provide guidance on what the next steps might be. For example, if the user cannot achieve their desired goal in their specified time frame, what other options are available to them? We should always guide our users through the process and never leave them saying “What should/can I do next?”</li><li><strong>Understand user motivations (extrinsic and intrinsic) and design for them.</strong><br>Our users will be focused on getting on top of their {service need}, but it is unlikely they will be fully aware of all the steps and requirements they will need to complete to make that journey. It is very likely that some processes will seem daunting and they may not yet fully appreciate their value at the time. When designing for extrinsic motivations try to align them with larger intrinsic motivations and clearly describe the value of completing the task at hand, providing nudges and support when needed.</li><li><strong>Be Inclusive.</strong><br>We want to design and develop our service for the widest possible range of users. Every stage of our processes should conform to WCAG AA as a minimum and AAA where possible. Our content should be easily understandable by those with cognitive challenges such as dyscalculia, dyslexia, or potentially those with English as a second language. <br>The UI should be easily accessed by those with motor impairments and easily distinguishable by those with visual impairments.<br>Accessibility tests should always include manual testing with screen reader across desktop and mobile devices.<br>Always try to recruit at least 1 or 2 users per day of usability testing who have inclusive needs (It might be colour blindness, dyslexia, cultural or a physical impairment).</li><li><strong>Be Transparent.</strong><br>Always openly tell users what we are doing and how we are going to use their data. Users should openly consent to third-party integrations and understand the benefits (or risks if appropriate) that integration provides. For example, Calls-to-action should always be worded in the simplest and clearest way possible.<br>This will ensure that not only are we helping users understand what we are doing, but it will also allow us to provide clearer protections for the vulnerable.</li><li><strong>Learn from the users.</strong><br>User insights are the best way of learning what we need to do to develop our service. User research should be conducted frequently and with members of the wider product team observing. We can all benefit from a change in our perspectives.</li><li><strong>Recognise the need for support</strong><br>Recognise that some users may want or need support from somebody else to help them achieve a given goal. This could be a parent/child, a loved one, or an industry professional. Whilst this may not be core to the service offering, there may be occasion where a by-proxy user may require alternative guidance to that of the user.</li></ol><p>It is also likely, in order to help motivate users to complete difficult tasks, you will need need to inspire them. Often (if taking action for the first time), users won’t know how to formulate their own specific plans, goals and outcomes. So the first step of a given process should always focus on supporting a user take action.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52b8d021f925" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>