<?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 Scott Herrington on Medium]]></title>
        <description><![CDATA[Stories by Scott Herrington on Medium]]></description>
        <link>https://medium.com/@scottd_h?source=rss-393287c2a33a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ex-ng35Vn36QrmK72FW5FQ@2x.jpeg</url>
            <title>Stories by Scott Herrington on Medium</title>
            <link>https://medium.com/@scottd_h?source=rss-393287c2a33a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:40:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scottd_h/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[GOV.UK. A better UX for UK’s citizens]]></title>
            <link>https://medium.com/@scottd_h/gov-uk-a-better-ux-for-uk-s-citizens-34ad19000ec7?source=rss-393287c2a33a------2</link>
            <guid isPermaLink="false">https://medium.com/p/34ad19000ec7</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Scott Herrington]]></dc:creator>
            <pubDate>Wed, 22 Apr 2015 19:05:04 GMT</pubDate>
            <atom:updated>2015-06-10T07:45:23.090Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMsc6Xrw_RYntBLBAVTwng.jpeg" /></figure><p><strong><em>“Making services so good that people prefer to use them.”</em></strong></p><p>This is the UK Government’s guiding vision, as they attempt to revolutionise public services online. This vision kicked off with the launch of GOV.UK in October 2012.</p><p>Recently, <a href="https://www.xing.com/communities/groups/product-tank-hamburg-97c8-1006005">Product Tank Hamburg</a> invited <a href="https://uk.linkedin.com/in/marksheldon">Mark Sheldon</a>, a product manager at GOV.UK, to tell us a little about how he and his team accomplished the mammoth task of migrating hundreds of sites, with thousands of pages of content to one url, with one coherent user experience. He also shared with us a few key lessons he learnt along the way.</p><h3>First a little background…</h3><p>The seeds for an online UK public services revolution were sown in 2010 when Martha Lane Fox, the “UK’s Digital Champion”, led a review of the government’s Directgov website.</p><p>At the time, Directgov served as the government’s main hub for all online services. It became clear however that what was supposed to be a hub, was more of a landing-page for a whole world of online public services chaos. Each service was built and maintained by completely different agencies who worked autonomously, with little attempt at content curation. This meant that there was zero coherency in design, navigation, or content, as visitors tried to find out important information, or use a particular service. The scope of the review therefore quickly expanded, to include the government’s entire online strategy.</p><p>This review culminated in Martha Fox’s letter of recommendation to Francis Maude, the minister responsible for driving the government’s “Digital by Default” approach. “<a href="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/60993/Martha_20Lane_20Fox_s_20letter_20to_20Francis_20Maude_2014th_20Oct_202010.pdf">Directgov 2010 and Beyond: Revolution, not Evolution.</a>”</p><p>The letter’s key recommendation was to:</p><blockquote><strong>“Make Directgov the government front end for all departments’ transactional online services to citizens and businesses, with the teeth to mandate cross government solutions, set standards, and force departments to improve citizens’ experience of key transactions.“</strong></blockquote><p>This she said would only be achieved by centralising publishing, and the necessary decision making powers, so that one coherent online experience could be realised for all the UK’s citizens.</p><h3>Queue Gov.UK…</h3><p>GOV.UK was to be new home for all of the UK government’s online services. To furnish this home, the websites and thousands of pages of content belonging to them were redesigned and migrated. Those sites currently include:</p><ul><li>Directgov</li><li>Business link (services aimed at helping UK businesses)</li><li>24 ministerial departments and</li><li>331 agencies and public bodies</li></ul><p>As of writing this, Mark and the teams at GOV.UK are busy helping an additional 766 websites through the “discovery, alpha, beta and live” pipeline.</p><p>Mark Sheldon and his team were initially responsible for the great lift at the beginning, which saw the migration of the Directgov and business link sites. This took place, from start to finish, in just 9 months.</p><h3>How did Mark and his team achieve this?</h3><h4>1. Set Standards</h4><p>The GOV.UK team set out early on to provide a framework and set of guidelines, to support any agency or public body who wished to design an online service for the GOV.UK platform. Otherwise a coherent user experience would never be realised.</p><p>To drive the efforts of standardisation, key stakeholders were asked to draw up a number of key points and learnings, from their own standardisation efforts. This led to a 26 point “Digital by Default Service Standard”. Every digital public service, whether it be a rebuild of an existing service, or a completely new service, MUST adhere to these 26 points. A panel of which Mark is on judges whether the service meets the requirements before migration. If not — it doesn’t go live.</p><p>You can <a href="https://www.gov.uk/service-manual/digital-by-default">read all 26 points</a> yourself, but just to give an idea of how user focussed they are, point one is “Understand user needs,” and point 26 is “Test the service from beginning to end with the minister responsible for it.”.</p><h4>2. User Research is strictly embedded into the design cycle.</h4><p>Leisa Reichelt, Head of User Research at the Government Digital Service (GDS), says user research is a “team sport.” And she doesn’t just talk the talk. She seems to do a pretty good job of walking the walk too, to the point that “all GDS team members are required to observe at least 2 hours of user testing every 6 weeks”. (So impressed! more on this in my concluding thoughts.)</p><h4>3. Cross functional on-site teams</h4><p>In true Agile style, the GOV.UK teams are comprised of members who represent the entire development chain. And to boot, they’re co-located too. This has helped ensure things move quickly and shared understanding can be built with as little friction as possible.</p><h3>Mark’s key lessons learnt</h3><h4>1. Get a vision.</h4><p>Something which is easy to remember and easy to articulate. This acts as a lens through which all decisions can be looked at.</p><h4>2. If you’re going to make a big splash, get an Umbrella.</h4><p>Ensure you get buy in from the most senior person you can get hold of. They’re support is needed to help sweep aside problems and blockers as they arise. without them you’ll spend far too much time with bureaucracy, and too little on creating awesome services.</p><h4>3. Get Principles.</h4><p>Find out what your team’s fundamental truths are. Get them written down and own them. Some of Mark’s team’s principles include:</p><ul><li>“Don’t do everything yourself. You can’t”</li><li>“Do less — but better”</li><li>“Make things open. This makes things better.” Improvements and ideas will come from places you least expect.</li></ul><h4>4. Have strong opinions, but hold them weakly</h4><p>(credited to Paul Saffo, Stanford Uni)<br>Don’t be afraid to use your knowledge or intuition. when you feel you can take a step forward… take the step forward. Build something. Have an opinion, do something with it but be prepared to change your mind.</p><h4>5. Show the thing!</h4><p>Don’t write it down… build it. Build it in whatever fidelity is required, whether that be Paper, Powerpoint, HTML or whatever. Stick it in front of colleagues or potential users and get real feedback.</p><h3>Concluding thoughts</h3><p>I have to say, I was quite impressed by the whole GDS set-up. Especially considering the fact this is a department born from a government initiative. If “Government” and “bleeding-edge design and development techniques” were a couple in a bar they’d be getting a lot of confused stares. They just don’t traditionally fit. Obviously it does here though. They seem to really get Agile, and are reaping the full benefits. I can’t imagine anything other than an agile approach with co-located cross-functional teams being able to achieve the migration of sites the size of Dirtectgov and Business Link in 9 months… with user-testing!</p><p>Most noteworthy for me was just how ingrained their user-centric design approach was. Many companies claim to be user-focused, but I’ve never heard of management supporting it to the point that they actually insist on all employees taking part in user-testing — and making it a formal requirement. This is really leading by example. Nothing is as powerful at increasing over all quality, along the entire development chain, as watching users actually use (or fail to use) what you’ve built. It’s humbling, it’s eye opening, and most importantly, I feel it gives teams the courage to get their ideas tested early. Not once they’re happy with it, but as soon as they realise an assumption just went into their UI, their flow or whatever. You’re reminded that humans are so spectacularly diverse that no one team, let alone one person, can foresee how their screens will be interpreted, or misinterpreted. Ensuring this realisation is fresh in everyone’s minds is time extremely well spent, and I’ll be taking this as an example to look up to.</p><p>Despite how impressed I am by the entire execution however, I do remain sceptical towards the fundamental approach of GOV.UK. One destination for ALL of the UK’s citizens sounds great from a cost-saving/efficiency perspective, but not so great when it comes to crafting a superior UX.</p><p>Without a doubt, their work over the past 4 years has led to an enormous improvement. You just have to compare screenshots to see that a more centralised approach to design and publishing is reaping benefits for the users. That said, the UK, like an increasing number of countries, has a citizenship comprised of many, many cultural groups. International cultures, religious cultures, national sub-cultures, class cultures, professional cultures and every other cultural sort in between is represented. To try and provide one UX which is effective at delivering relevant information and services, in an engaging manner, to such a diverse group is a nigh on an impossible task, and one can’t help but think many, many people are being left out.</p><p>One major exclusion, straight off the bat, is support for foreign languages. I’m so, so disappointed by this fact considering the UK’s history, our political situation, and our dependence on immigrants to prop up our economy and health services. Doing UX in London, language MUST have been identified as a major barrier to getting information and access to public services in a “simpler, clearer” manner. How can this be missing if the decisions truly are user-centred?!? I know great experiences are realised by learning to focus, and say no more often than yes, but English only seems shortsighted at best considering the aims and audience.</p><p>It will be interesting to see how GOV.UK develops. Judging by their speed so far, I won’t have to wait too long, but if it’s to be the one “preferred” url for all of the UK’s citizens, this centralised approach will only get them so far I feel. It works great for slick coherent design and orderly curation of articles and services. Without a doubt this has improved the experience. At some point though, to elevate the user experience further, GOV.UK will need to start thinking about how they can better cater to more specific groups of citizens, with vastly varying information needs. Otherwise they’ll just end up with a watered down UX that tries to balance the widely-varied needs of everyone, and fails to truly serve anyone.</p><p><em>Originally published at </em><a href="http://www.uxdistillery.com/2015/02/21/gov-uk-creating-a-better-ux-for-uks-citizens/"><em>www.uxdistillery.com</em></a><em> on February 21, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34ad19000ec7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>