<?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 Kate Ivey-Williams on Medium]]></title>
        <description><![CDATA[Stories by Kate Ivey-Williams on Medium]]></description>
        <link>https://medium.com/@kateiveywilliams?source=rss-3baa50daa2fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*b1F6VpYz89VwCgM6.</url>
            <title>Stories by Kate Ivey-Williams on Medium</title>
            <link>https://medium.com/@kateiveywilliams?source=rss-3baa50daa2fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:55:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kateiveywilliams/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[Improving government services: step by step]]></title>
            <link>https://medium.com/the-service-gazette/improving-government-services-step-by-step-29ebfcb47e92?source=rss-3baa50daa2fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/29ebfcb47e92</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Kate Ivey-Williams]]></dc:creator>
            <pubDate>Tue, 11 Jun 2019 20:49:15 GMT</pubDate>
            <atom:updated>2019-06-24T09:45:45.302Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving government services</h3><h4>Step by step</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MrrBqpr3rq4h3H2V5tOxow.png" /><figcaption>The “Learn to drive a car: step by step” seen here in the side bar of a content page to show where you are in the journey, and the overview seen here on mobile.</figcaption></figure><p>After <a href="https://medium.com/the-service-gazette/death-by-double-diamond-f79e43f9e753">my frustrations of service design consultancy work</a> — never getting close enough to implementation to do the real design work, I moved to the <em>Government Digital Service</em> in the hope of getting my hands dirty. It’s <em>almost</em> like working in-house, but not quite.</p><p>Rather than designing government services, <em>GDS</em> helps government design better services.</p><p>When trying to get government to do this, we face 3 major barriers:</p><p>Firstly, government is really old. In fact the UK government is one of the oldest in the world, and most of the services it provides were never “designed” but rather emerged out of policy built on policy and archaic systems and processes.</p><p>Secondly, there are a lot of people in government (often unwittingly) designing services. From policy to operations, people are responsible for critical aspects of a service, but they are not always working in a joined-up way.</p><p>Thirdly, government organisations rarely own a whole end-to-end service, because the user needs we want to frame services around cut across organisational boundaries. Take starting a business as an example — to reach that end goal users may have to interact with up to 12 different government organisations, but these organisations aren’t necessarily working together.</p><p><em>GDS</em> is a bit like a service design agency within government. We sometimes directly help departments redesign services on a case by case basis, but this approach doesn’t scale at the rate we need to fix services. We don’t have an army of service designers to deploy on the 100s of government services that need work. And work doesn’t stop just because a service designer isn’t there to facilitate the process. So how do we scale service design in government? We need to give government the means to make services better, in an ongoing and iterative way that cuts across functions and organisational boundaries.</p><p>I’m service design lead for the gov.uk programme at <em>GDS</em>. My work focuses on two main things: how gov.uk improves the experience of using government services for citizens, and what the gov.uk team is providing to government to help them improve those services.</p><p>The work I’ve been doing over the last few years has focused on achieving these goals. The very tangible piece of work we’ve done is to introduce a new feature on gov.uk called step by step navigation.</p><p>This navigation pattern was developed to help users through end-to-end services on gov.uk. It gathers together and organises all the pages on gov.uk that help users with each task they need to complete to achieve an overarching goal, like learning to drive or visiting the UK.</p><p>This makes services easier to understand and use — but improving the user experience of an as-is service is only the first step. The real value is in how the step by step supports government to work better to improve services long term. It’s about changing the way government works.</p><p>Step by step helps government to scope services from the user’s perspective. It cuts across what each organisation delivers, and it gives those organisations something tangible to collaborate around.</p><p>Through facilitated workshops to build step by steps, gov.uk is helping departments to map out the as-is journey through a service. In some cases, these workshops are the first time the people responsible for different parts of a service have interacted. The mapping process helps them understand the ordering of steps in a user’s journey, where those steps are broken, who owns what in the service and how it connects to other government services.</p><p>From these workshops, departments have gone on to improve the content in their services to make it easier for users to understand each task they need to complete. And where the service is too complex to explain in a simple way, they’ve started to address the underlying service design and policy.</p><p>As we scope and build more step by steps with organisations we have an emerging list of government services being validated by the cross-government teams who own them. This list will help government by giving them something to orientate around. When doing any improvement work they could ask: What service am I working on? Who are the users and what are they trying to achieve? What step am I working on and how does it join up with the other steps? How does this service connect to others? What other departments do I need to collaborate with?</p><p>Gov.uk is where most of government’s services live. It’s the only place where we can aggregate information about services onto a single platform, agnostic of organisational boundaries. We have a unique opportunity to build this list of services with the organisations who deliver them, so it becomes the single source of truth about what services government provides and how they connect.</p><p>Step by steps also provide a structure upon which we can aggregate end-to-end service performance data from across the whole service, so it can be used to diagnose sources of failure demand and iterate in an ongoing way. A single data point doesn’t give us the context we need to see what’s going wrong, but through the context of the step by step, we can start telling meaningful stories about how users are experiencing a service and make strategic decisions about how to improve things.</p><p><em>GDS</em> is like a service design agency working on the inside, but through gov.uk we also own one of the main citizen interfaces with government. We’re in a unique position to make end-to-end services better by helping the organisations that provide those services to understand them. Through step by step, we can help government understand, visualise, collaborate on and improve the services it provides.</p><p>———<br><a href="https://medium.com/@kateiveywilliams"><em>Kate Ivey-Williams</em></a><em> is the service design lead for </em>GDS<em>’ gov.uk programme. She has worked with dozens of UK government departments to create 42 step by step service navigations.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29ebfcb47e92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-service-gazette/improving-government-services-step-by-step-29ebfcb47e92">Improving government services: step by step</a> was originally published in <a href="https://medium.com/the-service-gazette">The Service Gazette</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Death by double diamond]]></title>
            <link>https://medium.com/the-service-gazette/death-by-double-diamond-f79e43f9e753?source=rss-3baa50daa2fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f79e43f9e753</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[digital-government]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Kate Ivey-Williams]]></dc:creator>
            <pubDate>Tue, 03 Jan 2017 23:44:14 GMT</pubDate>
            <atom:updated>2017-01-06T16:51:54.976Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to stay in service</h4><p>I’ve been lucky enough to work as a service designer both in a consultancy and now in-house with <em>Government Digital Service </em>in the UK. Working in these two very different environments has taught me a lot about the challenges service design faces and what we need to do to actually get well-designed services delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBmBRmUsJtvQNn17FKboZQ.jpeg" /></figure><p>The challenge is in implementation. The service design industry has mastered methodology. We understand what a well-designed service should look like. We know what needs to be done to get there. We can even build prototypes that help us simulate and test the user experience. But something seems to happen before implementation. Service designers are rarely involved in actually implementing a service. This means that when the service actually goes live, it often isn’t the shape you’d so carefully crafted on the page and handed over to the client.</p><p>A lot of this is because of the waterfall nature of the commonly-followed double diamond process. What tends to happen after the final ‘deliver’ stage of the double diamond is that the service designer will hand over a set of instructions to the client and leave them to implement it themselves. This can take years. And no matter how good the stakeholder engagement, the service can come out looking very different to how it was originally designed.</p><p>It’s pretty demotivating for service designers to work in this way, where their designs get thrown over a wall without any certainty that they will ever get implemented in a way that aligns to the original vision. This is also a massive problem for the service design industry. It means we don’t have much in the real world to point at and say “we designed that”, which makes it hard to sell the value of our work based on the quality of our designs. So instead we sell it on methodology, not real-world examples. And this methodology doesn’t include implementation. When it comes to implementing a service, each challenge is different. It’s hard to create a template for this.</p><p>But service design is not a methodology — it’s the design of services. Just like graphic design is about designing graphics, and product design about designing products.</p><p>Some service design organisations have been trying to influence implementation by selling training. They see this as a way to help clients keep the thread of service design once they’ve handed over the designs and gone away. An unfortunate side effect of this is that it can be seen as service design consultancies making themselves redundant. And, while it’s obviously great for as many people as possible to understand service design, a week of training isn’t the same as years of study or industry experience.</p><p>So rather than teaching organisations to follow the double diamond process and use service design methods, we need to build our own capabilities as services designers to help organisations get services delivered. And we need to stick around during implementation to make that happen.</p><p>Waterfall doesn’t work. But what I’ve seen — both in-house and in consultancies — is service design organisations increasingly moving to agile.</p><p>There are several ways in which agile can help service designers get closer to implementation. First and foremost, agile helps service designers design for the real world — because they’re working in the real world right from the start. They’re not just creating a proposal and handing it over at the end.</p><p>Agile is an iterative process. This means you can flex and change the service design throughout the process — right through to implementation. You can work out how to get to the best-designed service, one that responds to the way things actually work.</p><p>And agile is less tied to methods and ‘deliverables’. You can choose and change how to approach each stage of the project based on what the challenge is and what you need to get out of it.</p><p>Clearly it’s easier to use agile as an in-house designer where you are, in effect, both designer and client. But consultancies can and are starting to move in this direction too. Before I moved in-house, the consultancy I was working with started to build more account-like relationships with clients. This meant they could move away from the ‘discover-define-develop-deliver’ sales pitch towards more flexible contracts and budgets. This let them plan projects in a more agile way, and work with clients from strategy through to piloting services at a pace that worked for the organisation. We had a service designer on-site with the client almost full time, working with their senior stakeholders, making sure they were ready and willing to deliver the services we had designed.</p><p>Service design doesn’t stop at delivery. It shouldn’t even stop at implementation. A service is an ever-evolving, iterating thing. For service designers to influence that, they have to be involved at every stage.</p><p>—</p><p>Kate Ivey-Williams is a service designer at <em>Government Digital Service</em> in the UK. Prior to this, she worked as a service designer for <em>Engine Service Design </em>in London.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f79e43f9e753" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-service-gazette/death-by-double-diamond-f79e43f9e753">Death by double diamond</a> was originally published in <a href="https://medium.com/the-service-gazette">The Service Gazette</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>