<?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[Share + Reuse - Medium]]></title>
        <description><![CDATA[Reuse by Design — Making the Case for a Share + Reuse Infrastructure in Government and how to implement Reuse by Design - Medium]]></description>
        <link>https://medium.com/share-reuse?source=rss----e3d7c1b0aafd---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Share + Reuse - Medium</title>
            <link>https://medium.com/share-reuse?source=rss----e3d7c1b0aafd---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:33:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/share-reuse" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reuse by Design: Unlocking Reuse to Accelerate Transformation]]></title>
            <link>https://medium.com/share-reuse/reuse-by-design-unlocking-reuse-to-accelerate-transformation-9472b7de9299?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/9472b7de9299</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[reuse]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[components]]></category>
            <dc:creator><![CDATA[Nikola Goger]]></dc:creator>
            <pubDate>Fri, 28 Nov 2025 10:37:36 GMT</pubDate>
            <atom:updated>2025-11-28T10:37:34.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_J9K3x7tLyhAIoCV7jee0w.png" /></figure><p><em>This is the last part of the write-up of the talk </em><a href="https://govservicedesign.net/programme/share-and-reuse-design"><em>“Share &amp; Reuse by Design”</em></a><em> by Nikola Goger, Rob McCarthy and Martin Ford-Downes at the “SD in Gov” conference on 18.9.2025.</em></p><p>Part 1: <a href="https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb"><strong>Breaking Down Silos:</strong> Why Share and Reuse Matters in Government</a><br>Part 2: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff"><strong>Design System: </strong>Doing design systems in government, differently.</a><br>Part 3: <a href="https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653"><strong>Service Patterns</strong></a><br>Part 4: <a href="https://medium.com/@nikolagoger/common-components-and-the-gov-reuse-library-building-the-infrastructure-for-reuse-3bf0d2c1faed?postPublishedType=initial"><strong>Building the Infrastructure for Reuse</strong>: Common Components and the X-Gov Reuse Library</a><br>Part 5: <strong>Reuse by Design</strong>: Unlocking Reuse to Accelerate Transformation</p><h3><strong>What Do We Need to Make Reuse Work?</strong></h3><p>Reuse doesn’t happen by accident. It needs intentional design. Here’s what we’re focusing on:</p><p><strong>1. Infrastructure</strong></p><p>We need centralised, accessible spaces where reusable assets live. Not just design systems, but libraries of patterns, principles, and components. Think of it like a box of LEGO — teams should be able to grab what they need and start building.</p><p><strong>2. Culture</strong></p><p>We also need to embed “sharing our work so people can find it again” into our workflows and that goes beyond show&amp;tells and documentation. That means:</p><ul><li>Making it easy to contribute work.</li><li>Bringing “share” time into our sprints</li><li>Celebrating reuse as a success metric.</li><li>Thinking cross-government by default.</li></ul><p>We also need to develop completely <strong>new ways of working for our teams</strong>, so instead of “building one service that can do a specific thing” we need to start looking at “what is the reusable core of the service — and what are the layers on top of that that are the unique parts of a service”. That’s not something we’ve done before so we’ll have to work our way through how to do that in an efficient and scaled up way. ​</p><p><strong>3. Collaboration Models</strong></p><p>We can’t rely on one central team (like GDS) to do all the heavy lifting. Departments need to be empowered — and incentivised — to contribute to a shared ecosystem.</p><p>Imagine a model where:</p><ul><li>Departments share backlogs transparently.</li><li>Local champions help curate and maintain reusable assets.</li><li>A cross-government board helps steer priorities.</li></ul><p>This isn’t just about tools. It’s about trust, relationships, and shared purpose.</p><p><strong>A Vision for the Future</strong></p><p>What if every team building a service could reuse 60% of their work — components, patterns, knowledge — and focus their energy on the 40% that makes their service unique?</p><p>That’s not just a productivity boost. It’s a transformation accelerator.</p><p>We’re already seeing glimpses of this future in our work at the Ministry of Justice. But we know we can’t do it alone. That’s why we’re inviting others to join us — to share, reuse, and build together.</p><p><strong>Let’s Build the Future Together</strong></p><p>Reuse isn’t just a technical fix. It’s a mindset shift. It’s about recognising that we’re part of something bigger — that the best way to serve the public is to collaborate.</p><p>So here’s our ask:</p><ul><li>If you’ve built something useful, share it.</li><li>If you’re starting something new, look for what already exists.</li><li>If you believe in this vision, help us shape it.</li></ul><p>Together, we can build a government that works smarter, faster, and better — for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9472b7de9299" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/reuse-by-design-unlocking-reuse-to-accelerate-transformation-9472b7de9299">Reuse by Design: Unlocking Reuse to Accelerate Transformation</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Components and the GOV Reuse Library: Building the Infrastructure for Reuse]]></title>
            <link>https://medium.com/share-reuse/common-components-and-the-gov-reuse-library-building-the-infrastructure-for-reuse-3bf0d2c1faed?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/3bf0d2c1faed</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[reuse]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[components]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Nikola Goger]]></dc:creator>
            <pubDate>Fri, 28 Nov 2025 10:37:24 GMT</pubDate>
            <atom:updated>2025-11-28T10:37:23.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LISGPFiSybKgqB2quVWbvg.png" /><figcaption>A laptop with the GOV Reuse Library displayed</figcaption></figure><p><em>This is a write-up of the talk </em><a href="https://govservicedesign.net/programme/share-and-reuse-design"><em>“Share &amp; Reuse by Design”</em></a><em> by Nikola Goger, Rob McCarthy and Martin Ford-Downes at the “SD in Gov” conference on 18.9.2025.</em></p><p>Part 1: <a href="https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb"><strong>Breaking Down Silos:</strong> Why Share and Reuse Matters in Government</a><br>Part 2: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff"><strong>Design System: </strong>Doing design systems in government, differently.</a><br>Part 3: <a href="https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653"><strong>Service Patterns</strong></a><br>Part 4: <strong>Building the Infrastructure for Reuse</strong>: Common Components and the X-Gov Reuse Library <br>Part 5: <a href="https://medium.com/@nikolagoger/reuse-by-design-unlocking-reuse-to-accelerate-transformation-9472b7de9299?postPublishedType=initial"><strong>Reuse by Design</strong>: Unlocking Reuse to Accelerate Transformation</a></p><p>After discussing the first 2 initiatives, our Design System and Service patterns in the last 2 blog posts, this blog is about the next 2 initiatives: Common Components and the GOV Reuse Library.</p><h3><strong>Initiative 3: Common Components: Engineering Reuse from the Ground Up</strong></h3><p>While design systems and service patterns help us reuse design and delivery knowledge, we also need to tackle reuse at the <strong>engineering level</strong>. That’s where our third initiative - <strong>Common Components -</strong> comes in.</p><p>This is our <strong>least mature workstream</strong>, but it’s also one of the most exciting. It’s about building reusable technical building blocks that can be shared across services and departments.</p><p><strong>The Opportunity: Scaling Reuse in Engineering</strong></p><p>We’re currently exploring two key areas:</p><ul><li><strong>scaling up the DS </strong>and moving stronger into the engineering space</li><li>building an <strong>engineering portal </strong>that helps with publicizing shared tooling &amp; guardrails that agencies across MOJ can use</li></ul><p>Hopefully a lot more on this in 2026!</p><h3>Initiative 4: <strong>The GOV Reuse Library: Building the Box</strong></h3><p>You can find the Library here:<a href="https://dev.reuselibrary.service.justice.gov.uk/about.html"> https://dev.reuselibrary.service.justice.gov.uk</a></p><p>Please have a look around and give us feedback! We are very interested to hear about other content you’d like to see there and things you have that should go into the Library.</p><p>If components are the Lego bricks, the <strong>GOV Reuse Library</strong> is the box they live in.</p><p>It is a cross-government initiative lead by the Ministry of Justice in collaboration with other departments like the Department for Education and the Government Digital Service. We are also currently onboarding more departments.</p><p>Over time, the MoJ Design System has accumulated a variety of resources, including patterns, principles, and ethics guidance. It’s become clear we need a <strong>new level up</strong>: a central space where all reusable assets can sit side by side.</p><p><strong>What Is the Reuse Library?</strong></p><p>It’s a <strong>cross-government platform</strong> that brings together:</p><ul><li>Design systems</li><li>Service patterns</li><li>Standards and manuals</li><li>Reusable products and components</li><li>Etc.</li></ul><p>You can filter by <strong>department</strong>, <strong>content type</strong>, and <strong>profession</strong>. It’s live now in its first iteration, and we’re actively collecting feedback.</p><p><strong>Why Are We Doing This?</strong></p><p>Because we need to make reuse <strong>easy, visible, and collaborative</strong>.</p><p>“In my head, all of this is like a box of LEGO… but we don’t even have a box yet.”</p><p>The reuse library helps us:</p><ul><li><strong>Spot duplication</strong></li><li><strong>Surface opportunities to collaborate</strong></li><li><strong>Enable new ways of working</strong></li></ul><p>It’s not just about content — it’s about <strong>culture</strong>.</p><p><strong>What’s Next?</strong></p><p>We’re working on:</p><ul><li>Collecting feedback and ideas</li><li>Iterating the MVP</li><li>Developing a governance model</li><li>Onboarding more departments</li><li>Building new content (e.g. profession sites, engineering portal)</li></ul><p>This is all very new, but the momentum is growing. We’re building a framework that can scale across government and we want you to be part of it!</p><p><strong>Join Us</strong></p><p>We’re doing much of this in our spare time. Imagine what we could achieve with proper funding, focus, and support.</p><p>Sharing and reuse shouldn’t be left to small teams or GDS alone. The opportunity is too big. The scale is too vast. We need <strong>everyone</strong>.</p><p>Let’s build the future of reuse — together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bf0d2c1faed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/common-components-and-the-gov-reuse-library-building-the-infrastructure-for-reuse-3bf0d2c1faed">Common Components and the GOV Reuse Library: Building the Infrastructure for Reuse</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write-up: Service Patterns - Part 3 of “Share and Reuse” from Service Design in Government 2025]]></title>
            <link>https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/573b29506653</guid>
            <category><![CDATA[user-centred-design]]></category>
            <category><![CDATA[uk-government]]></category>
            <category><![CDATA[service-patterns]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 14:41:50 GMT</pubDate>
            <atom:updated>2025-10-23T08:05:56.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_TXbYgk6ewiwx-SYrRdfg.png" /><figcaption>Martin Ford-Downes standing at a lectern, presenting at the SD in Gov conference 2025.</figcaption></figure><p><em>This is a write-up of the talk </em><a href="https://govservicedesign.net/programme/share-and-reuse-design"><em>“Share &amp; Reuse by Design”</em></a><em> by Nikola Goger, Rob McCarthy and Martin Ford-Downes at the “SD in Gov” conference on 18.9.2025.</em></p><p>Part 1: <a href="https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb"><strong>Breaking Down Silos:</strong> Why Share and Reuse Matters in Government</a><br>Part 2: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff"><strong>Design System: </strong>Doing design systems in government, differently.</a><br>Part 3: <a href="https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653"><strong>Service Patterns</strong></a><br>Part 4: <strong>Building the Infrastructure for Reuse</strong>: Common Components and the X-Gov Reuse Library {coming soon}<br>Part 5: <strong>Reuse by Design</strong>: Unlocking Reuse to Accelerate Transformation {coming soon}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*YnoZZuD4iNrOAAm2PcEAHg.jpeg" /><figcaption>A screenshot with the definition of service patterns</figcaption></figure><h4>Defining service patterns</h4><p>We define service patterns are a structured way of describing repeatable user tasks that can be combined to build or shape end-to-end services. They can be used to understand and organise the services you offer and support you in building new services.</p><p>Design systems are a proven way to create more consistent and accessible user experiences, in an efficient way. Some of the patterns we find in them are quite complex, involving multiple pages or branching paths. From there it is reasonable to ask whether we can define patterns for more complex tasks — this is what service patterns aim to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*QG0CWMD90dFdVzJB7nf0JA.jpeg" /><figcaption>A screenshot showing examples of UK government apply services, like apply for a visa</figcaption></figure><p>The opportunity seems obvious. If you take “applying for things” as an example of a complex task, there are hundreds of these services in the UK public sector. In many cases those services have similarities thanks to the government design system. However, we haven’t defined anywhere what “applying” ought to look like as an end-to-end experience. We believe service patterns could be used to do that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*QsBKq13Km2hFgRKyecCR0A.jpeg" /><figcaption>A screenshot describing the differences between components and patterns</figcaption></figure><p>How would these service patterns differ from the patterns in design system today? Components and patterns in design systems focus on digital interactions for specific user actions. However these components and patterns do not normally describe the complete end to end journey a user would go on to complete their goal.</p><p>Service patterns look at entire tasks, like applying for something or booking an appointment. They’re multi-channel, considering steps beyond the screen. Their scope is broader and so they’re likely to be less specific as they need to work across different contexts. Whilst many parts of services can be standardised, bigger patterns will mean they need to support more complexity and variations. Applying to be a foster parent should probably be different and more complex than applying for a parking permit.</p><p>Service patterns therefore sit at a medium level of zoom. Not so low that they are too restrictive, but not so high that they don’t provide any value. Just the content that we are most confident is common and shared across all services of a certain type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*l4jvaOZyahQZvKr9OaVFWg.jpeg" /><figcaption>A screenshot listing the 9 service patterns we have identified</figcaption></figure><h4>Identifying our service patterns</h4><p>At the Ministry of Justice, we started by identifying our potential service patterns. Teams were asked to describe the user tasks their services facilitated, in their own words. We then sorted, categorised and iterated on those findings to identify our pattern needs. That led to 9 potential service patterns: Record, Understand, Inform, Request, Apply, Book, Evaluate, Decide and Pay.</p><p>This list may change. Other organisations working on service patterns have similar but not identical lists. It’s an open question whether we could or should standardise these. Regardless, we’ve found that these 9 tasks cover the majority of things users need to do when interacting with public services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4XdAT34e2yCEL4we5q2lbg.jpeg" /><figcaption>A screenshot showing the different parts of a service pattern</figcaption></figure><h4>The parts of a service pattern</h4><p>Let’s now break down the parts of a service pattern that you could document in a library. The example used here is applying for a passport.</p><p>If getting a passport is an end-to-end service, then we can break that down into several parts. You will need to apply for the passport. You may need an appointment to prove your identity. A decision will be made about your application, and you will be informed of the outcome.</p><p>Within each part, there are sub-patterns or steps. For example, “apply” could include preparing to apply and submitting the application. These are not 100% prescriptive. Each service decides which parts, in what order, work best.</p><p>Then under those sub-patterns we can define tasks like finding the right form and checking eligibility.</p><p>We could also include supporting guidance. For example:</p><p>· User needs — what do we already know about users applying for things<br>· Scenarios — the happy and unhappy paths through a service<br>· Recommended digital components<br>· Demos or prototypes<br>· Case studies<br>· Relevant policies, goals or business metrics</p><p>This is not a definitive or exhaustive list of the things that could be in a service pattern library, but they’re the ones our research has shown so far to have potential to be useful. You may notice the nature of these assets are largely about guidance and context setting, and less about code and screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*yyvf5CWakKNKwYMqG1CRHg.jpeg" /><figcaption>A screenshot of an example service pattern, for people requesting things</figcaption></figure><h4>Examples</h4><p>An example from the Ministry of Justice are the services for requesting things in prisons. People in prison need to request all sorts of things — access to healthcare, information about their sentence, or changes to their cell. Different teams provide these services and the outcomes differ, but the core request process has repeatable elements. We’ve documented them as a service pattern, to create a blueprint for any team working on a request service in prisons. We then expanded the pattern to any type of request service in the Ministry of Justice.</p><p>Beyond the Ministry of Justice we’re involved in a grass roots cross-department project to explore service patterns at a whole-government level. We have identified that we mostly share the same service patterns needs, and we agree on the sort of content that would be useful in a service patterns library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*koPynsbpzNJP24casfBtng.jpeg" /><figcaption>A screenshot of the ‘apply’ service pattern proof of concept</figcaption></figure><p>We have also built two ‘proof of concept’ service pattern for applying and booking appointments, taking a collaborative approach involving multiple departments and other public sector organisations. For each we focused on a subset of the elements that could make up a service pattern; user needs, sub-patterns and user scenarios. <a href="https://design-patterns.service.justice.gov.uk/service-patterns/">The patterns available online here and we welcome your feedback on them.</a></p><h4>Benefits</h4><p>Why do service patterns? We think there are several potential benefits (that still need to be proven):</p><p>· <strong>Service patterns can help you to organise and understand the services you offer.</strong> Start simply by understanding what you do today, in categories like “apply” and “book appointment.” You may have hundreds of services but you will probably find that at a fundamental level you do fewer things, with many variations. Documenting this can be a powerful tool for talking to stakeholders about duplication in your organisation, paving the way to make the case for improvement through more consistent and repeatable design approaches.</p><p>· When you commission new work, <strong>service patterns can be a framework for scoping</strong>. If a new need can be defined by its service patterns, you can immediately identify what you already know and can reuse.</p><p>· They <strong>avoid repeating research </strong>into things you already know, creating more time to discover fresh new insights.</p><p>· They can <strong>guide you to reusable assets and components</strong>, particularly for digital services.</p><p>· Access to research and reusable components can mean <strong>faster delivery</strong>.</p><p>· Users will have more <strong>consistent experiences</strong> across all your services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*SRRDVfPgn8j21GqnKiqqRA.jpeg" /><figcaption>A caption that says ‘service patterns do not replace design’</figcaption></figure><p>One final important note. <strong>Service patterns do not replace the need for design.</strong> Every service will still have unique elements that require thoughtful research and a user-centred approach. But with service patterns, we can do that more effectively, freeing up time to focus on more valuable work.</p><p>In summary:</p><p>· Service patterns are a framework for describing complete user tasks.<br>· They enable consistent user experiences, designed and built efficiently.<br>· We’d love your feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=573b29506653" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653">Write-up: Service Patterns - Part 3 of “Share and Reuse” from Service Design in Government 2025</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing design systems in government, differently.]]></title>
            <link>https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/71bb6a2579ff</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[reuse]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Rob McCarthy]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 10:39:20 GMT</pubDate>
            <atom:updated>2025-10-23T08:08:06.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Me, Rob McCarthy, standing behind a podium and a laptop giving a talk at SDinGov. Behind me is a large screen showing the slides for my talk. The slide has black text on it which says “The big question. Can we do design systems in a more intentional, connected, and joined up way across government?”" src="https://cdn-images-1.medium.com/max/1024/1*kWUFzspZaCa9sek5w0tNgQ.png" /></figure><p><em>This is a write-up of the talk </em><a href="https://govservicedesign.net/programme/share-and-reuse-design"><em>“Share &amp; Reuse by Design”</em></a><em> by Nikola Goger, Rob McCarthy and Martin Ford-Downes at the “SD in Gov” conference on 18.9.2025.</em></p><p>Part 1: <a href="https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb"><strong>Breaking Down Silos:</strong> Why Share and Reuse Matters in Government</a><br>Part 2: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff"><strong>Design System: </strong>Doing design systems in government, differently.</a><strong> </strong><br>Part 3: <a href="https://medium.com/share-reuse/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653"><strong>Service Patterns</strong></a><br>Part 4: <strong>Building the Infrastructure for Reuse</strong>: Common Components and the X-Gov Reuse Library {coming soon}<br>Part 5: <strong>Reuse by Design</strong>: Unlocking Reuse to Accelerate Transformation {coming soon}</p><p>Last month I spoke at <a href="https://govservicedesign.net/">Service Design in Government</a> (SDinGov) alongside my colleagues <a href="https://medium.com/u/f0ee59a3d7a2">Nikola Goger</a> and <a href="https://medium.com/u/79a914e48bc1">Martin Ford-Downes</a>. Our session, <a href="https://www.linkedin.com/posts/nikolagoger_thanks-everyone-who-came-to-listen-to-our-activity-7374727528252481536-ZT3T?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAVm18YBlBMTe6ewsXnlaBHg3o0C-gTX1s8"><em>Share and reuse by design</em></a>, looked at how government could work better if reuse was at its core.</p><p>This blog post is a write-up of the talk I gave at that session, and it’s a continuation of something I’ve been thinking and writing about for a while.</p><p>Previously, I’ve written before about <a href="https://medium.com/share-reuse/why-do-we-need-a-design-system-dd15ca8b2361">why departments like the MOJ need their own design systems</a>. In that piece, I ended with a reflection that shaped my talk at SDinGov:</p><blockquote>“A connected government with underlying and centralised digital infrastructure, created and maintained through a participatory model with all departments, is the future that I think we need. But, it’s not our reality now.”</blockquote><p>I still think that’s the future we need to be working towards. And it’s the reason I keep asking this question:</p><p><em>If we have lots of design systems across government, can we do them in a more intentional, connected and joined up way?</em></p><h3><strong>Why the MOJ has its own design system</strong></h3><p>At SDinGov, I began by asking the audience a simple question:</p><blockquote>“Who’s heard of the GOV.UK Design System?”</blockquote><p>Almost every hand went up. No surprise there. It’s well known, widely used, and rightly celebrated. Over the years it’s saved government tens of millions of pounds and will continue to do so long into the future.</p><figure><img alt="Screenshots of the home pages of 12 design systems across government. The design systems included are GOV.UK, Ministry of Justice, Home Office, Intelligence Community, Department for Education, Office for National Statistics, Department for Work and Pensions, HM Revenue and Customs, Land Registry, Royal Navy, and the Ministry of Defence." src="https://cdn-images-1.medium.com/max/1024/1*-ia5Pp37m5DLve0Jks6v8Q.png" /></figure><p>But it isn’t the only design system in government. Departments like the <a href="https://design.homeoffice.gov.uk/design-system">Home Office</a>, <a href="https://design-system.dwp.gov.uk/">Department for Work and Pensions</a>, <a href="https://design.education.gov.uk/design-system/">Department for Education</a>, <a href="https://design-system.service.mod.gov.uk/">Ministry of Defence</a>, and even the <a href="https://design.sis.gov.uk/">MI5/MI6</a> have their own.</p><p>The <a href="https://design-patterns.service.justice.gov.uk/">Ministry of Justice</a> does too.</p><p>But why?</p><p>The <a href="https://design-system.service.gov.uk/">GOV.UK Design System</a> is brilliant for public-facing, transactional services. Things like renewing a passport or paying a fine. But a lot of products delivered by departments are internal-facing. They’re used by caseworkers and operational staff doing complex, task-based work all day, every day.</p><p>A case manager processing a lasting power of attorney or a prison officer recording an incident has very different needs from someone renewing their passport once a decade.</p><p>And then there’s the practical side. The GOV.UK Design System can’t cover everything. It would need unlimited time and money to do that. Departments need to fill in the gaps for their own products.</p><p>That’s why we have the MOJ Design System. And even though I can explain it, it still doesn’t sit entirely comfortably with me. If every department is doing the same thing, in slightly different ways, it starts to feel very inefficient.</p><p>That’s what led me to the big question I can’t stop thinking about.</p><p><em>If we have lots of design systems across government, can we do them in a more intentional, connected and joined up way?</em></p><p>After posing that big question to the audience about whether we can do design systems in a more intentional and connected way, I brought it to life by talking through two experiments we’ve been running at the MOJ.</p><p>Both experiments set out as a way to improve our own design system. But as we’ve tested and learned, I’ve started to think about how these ideas could work at a bigger scale, and in turn, help design systems across government become more intentionally connected and joined up.</p><h3><strong>Experiment one: </strong>Easier, faster, and ​more open contributions</h3><figure><img alt="A diagram using squares and diamond shapes of different colours to illustrate a contribution model. The image represents something being contributed into a design system which can then be used by lots of people and teams." src="https://cdn-images-1.medium.com/max/1024/1*c4BpG51eQbXDMemzRJ2VXA.png" /></figure><p>The first experiment was about making contributions easier and more open.</p><p>In my post <a href="https://medium.com/@robertjmccarthy08/are-design-systems-too-slow-27c8092cd34f"><em>Are design systems too slow?</em></a>, I wrote about what I called the “chasm of invisibility”. This is the time between when someone contributes something to a design system and when others can actually reuse it.</p><h4>The problem</h4><p>Let’s say someone creates a useful component, like a time-out warning which has a use where people are using an authenticated product on a shared computer, like they might do in a library, or in a prison. In the past, the contributor would share it on Github, and from there it could take months, often longer, before it made it into the design system.</p><p>During that time, the work wasn’t easy to find or reuse. And the work ultimately became invisible. And this is how reuse fails, and when reuse fails, duplication wins.</p><p>What made this worse was how contributions were being shared. Everything living inside a GitHub discussion quickly became noisy and hard to follow. For some people, GitHub is fine. But for many others, it’s overwhelming.</p><p>During research, one developer said:</p><blockquote>“It’s like the wild west. There’s lots of views and opinions, when what people want are simple facts.”</blockquote><p>What should have been a simple way to share work had become a chasm of invisibility.</p><figure><img alt="A diagram using squares and diamond shapes of different colours to illustrate a contribution model that doesn’t work very well. The image represents a time out warning component being contributed into a design system which then sits on Github where lots of people are adding to it, which can be confusing and overwhelming for those wanting to reuse the contribution." src="https://cdn-images-1.medium.com/max/1024/1*W-UikUStvOoY6JWZVxcltg.png" /></figure><h4>The solution</h4><p>We created a simple form on the MOJ Design System site where contributors only need to provide a few things:</p><ul><li>a name of the component they are contributing,</li><li>a short description of what it is and what it does,</li><li>an image of the component.</li></ul><p>That’s enough for it to be published as an <a href="https://design-patterns.service.justice.gov.uk/design-system-statuses/#:~:text=Archived-,%E2%80%98Experimental%E2%80%99%20status,-Experimental">experimental building block</a>.</p><p>Contributions can include more if it’s available, and this could include code, links to Figma, and accessibility reports. But, these aren’t essential for the early stages of a contribution. Our research showed that something was better than nothing when it came to reuse.</p><h4>The result</h4><p>The time between a contribution being made and someone else being able to reuse it has gone <strong>from months and years to just 10 days</strong>.</p><p>The chasm of invisibility has gone and the MOJ Design System has 3 experimental components (as of October 2025). These include an <a href="https://design-patterns.service.justice.gov.uk/components/inset-text-highlighted/">inset text (highlighted)</a> component, a <a href="https://design-patterns.service.justice.gov.uk/components/new-features-banner/">new features banner</a> component, and a <a href="https://design-patterns.service.justice.gov.uk/components/progress-tracker/">progress tracker</a> component.</p><p>It makes me wonder what might happen if this model existed across government.</p><p>Could we have a single way to contribute to design systems, so that everyone benefits from shared work earlier? Could we create a single space for experimental building blocks that later mature into official ones?</p><p>It feels like a small but meaningful step towards doing design systems in a more intentional and connected way.</p><h3><strong>Experiment two: </strong>A squad operating model</h3><figure><img alt="A diagram using squares, diamond shapes, and circles of different colours to illustrate a team setup. The image represents 3 teams which are similar but slightly different in their focus and what they deliver." src="https://cdn-images-1.medium.com/max/1024/1*VcIvmQ8v95ItcjFjIADqaA.png" /></figure><p>This second experiment was about team setup and the reach of the design system.</p><p>The MOJ is big. It includes prisons, probation, courts and tribunals, legal aid, the Office of the Public Guardian and many arms length bodies.</p><p>One small central design system team can’t possibly cover all of those needs. And when that happens, divergence starts to creep in.</p><p>We saw this clearly when we looked at our header component. The MOJ Design System has one standard header, but across our products we found many versions with each being slightly different in layout or functionality.</p><figure><img alt="A screenshot of the header component from the MOJ Design System is on the left of the image. On the right is 11 screenshots of header components across different products within the MOJ." src="https://cdn-images-1.medium.com/max/1024/1*HHq5ER0ce0b0niZOVnP1oQ.png" /></figure><p>It’s easy to see how it happens. Teams are working fast and solving problems locally. But those small differences add up over time and create inconsistency.</p><p>To tackle this, we’ve been trying a squad model.</p><p>We merged the central MOJ Design System team with a team from Probation to form a joint squad.</p><p>The central squad focuses on consistency, standards and reusable building blocks, and the probation squad focuses on relevance for their area, creating new building blocks or adapting existing ones when needed.</p><p>For example, the probation squad recently released a header variant that meets their specific needs but stays connected to the main component.</p><p>It’s a variant, not a divergence.</p><figure><img alt="A diagram using squares, diamonds and triangles of different colours to illustrate a two squad model. One squad is a large diamond and the other squad is a large triangle." src="https://cdn-images-1.medium.com/max/1024/1*ZeWVHNM4Ef4wuDxgJxO_6w.png" /></figure><p>The early results are promising. We’re seeing fewer inconsistencies and stronger alignment. The plan is to expand this model to other parts of the MOJ, creating a network of connected squads that share the same direction and purpose.</p><p>Now imagine this at a government-wide level. A central design system team made up of departmental squads, all working to a shared direction and funded across departmental boundaries.</p><p>That would be a major shift, but it could make design systems across government much more connected and much more efficient.</p><h3><strong>Back to the big question…</strong></h3><p>I mentioned earlier that it doesn’t sit comfortably with me that we have so many design systems across government.</p><p>And, I keep coming back to that question of whether we can do design systems in a more intentional, connected and joined up way.</p><p>With the experiments we’ve been running at the MOJ, I think we’re starting to do exactly that.</p><p>By changing how people contribute and by rethinking how our teams are structured, we’re finding ways to connect and join up the work we’re doing — not just within MOJ, but in ways that could scale beyond it.</p><p>Could this grow into something bigger? Could we have a single contribution model, a shared team structure, and maybe even one design system that connects government?</p><figure><img alt="A diagram using squares different colours to illustrate a joined up design system model. The image shows blocks with different government departments names in, and they’re connected within a larger block. There is a large blue square to represent one design system, and lots of smaller squares which represent contributions into the design system." src="https://cdn-images-1.medium.com/max/1024/1*nerfn0_CsJTINlcBlsu8Bg.png" /></figure><p>If we could do that, we’d be a step closer to the future I wrote about before — a connected government with shared digital infrastructure, built and maintained together.</p><p>So, if you work on, use, fund or have just heard of design systems in government, I’d like to leave you with the same question that I keep wrestling with:</p><p><em>Can we do design systems in a more intentional, connected and joined up way across government?</em></p><p>If you think we can, like I do, then I’d love to talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71bb6a2579ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff">Doing design systems in government, differently.</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write-up: “Share & Reuse by Design” — Talk at SDinGov 2025]]></title>
            <link>https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/ce2ac43dd5bb</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[reuse]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Nikola Goger]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 12:11:07 GMT</pubDate>
            <atom:updated>2025-11-24T10:35:39.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPAAjz0qTPz5GPnsn4g1nA.jpeg" /><figcaption>Rob, Nikola and Martin at SDinGov 2025</figcaption></figure><h3>Write-up: “Share &amp; Reuse by Design” — Talk at SDinGov 2025</h3><p><em>This is a write-up of the talk </em><a href="https://govservicedesign.net/programme/share-and-reuse-design"><em>“Share &amp; Reuse by Design”</em></a><em> by Nikola Goger, Rob McCarthy and Martin Ford-Downes at the “SD in Gov” conference on 18.9.2025.</em></p><p>Part 1: <strong>Breaking Down Silos:</strong> Why Share and Reuse Matters in Government <br>Part 2: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff">Doing <strong>design systems </strong>in government, differently.</a> <br>Part 3: <a href="https://medium.com/@martin.ford-downes/write-up-service-patterns-part-3-of-share-and-reuse-from-service-design-in-government-2025-573b29506653"><strong>Service Patterns</strong></a><br>Part 4: <a href="https://medium.com/@nikolagoger/common-components-and-the-gov-reuse-library-building-the-infrastructure-for-reuse-3bf0d2c1faed?postPublishedType=initial"><strong>Building the Infrastructure for Reuse</strong>: Common Components and the X-Gov Reuse Library</a><br>Part 5: <a href="https://medium.com/@nikolagoger/reuse-by-design-unlocking-reuse-to-accelerate-transformation-9472b7de9299?postPublishedType=initial"><strong>Reuse by Design</strong>: Unlocking Reuse to Accelerate Transformation</a></p><h3>Part 1: Breaking Down Silos: Why Share and Reuse Matters in Government</h3><p><strong>Introduction: A Familiar Frustration</strong></p><p>When I joined the Civil Service, I kept thinking: <em>“Surely someone has done this before?”</em> — but finding earlier work was so difficult and time-consuming that I eventually gave up and built the thing from scratch. This experience isn’t unique, it’s a systemic issue. We’re working in silos, duplicating effort, and missing opportunities to build on each other’s work.</p><p>This post explores why that matters, what’s at stake, and how we can start to change it.</p><h4><strong>The Scale of the Challenge</strong></h4><p>Let’s start with some numbers:</p><ul><li><strong>UK Civil Service</strong>: ~550,000 people</li><li><strong>IBM</strong>: ~270,000</li><li><strong>Meta</strong>: ~75,000</li><li><strong>Google</strong>: ~185,000</li></ul><p>The Civil Service is larger than all these tech giants combined. And that’s not even counting the NHS. The Ministry of Justice alone has nearly 100,000 staff. We’re not short on talent or scale. But we are short on connection.</p><p>We have 465 departments, each with their own services, teams, and ways of working. That’s thousands of services being designed, built, and maintained — often in isolation.</p><figure><img alt="We are not harnessing our large crowd of talented people enough! We need to start working as ONE organisation!" src="https://cdn-images-1.medium.com/max/1024/1*yHIt60UxzHQ6geb-65fHwg.png" /></figure><h4><strong>Building Blocks for Change: What We Mean by “Share and Reuse”</strong></h4><p>In government, we often talk about transformation — about making services simpler, faster, and more accessible. But transformation isn’t just about what we build. It’s about how we build it. And one of the most powerful levers we have is <strong>reuse</strong>.</p><p>Reuse isn’t just a technical or design principle. It’s a cultural shift. It’s about working in ways that make it easier to share, find, and build on each other’s work. It’s about unlocking the collective skills of thousands of public servants across hundreds of departments.</p><p>So what do we mean when we say “share and reuse”? Let’s break it down.</p><h3><strong>Three Categories of Reuse</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9yJaXbTtUT5AkSU4u6_ohA.png" /></figure><p>We’ve found that reusable work tends to fall into three broad categories:</p><p><strong>1. How to build a thing — The tangible building blocks</strong></p><p>This includes things like:</p><ul><li><strong>Design systems</strong>: Component libraries, style guides, and interaction patterns.</li><li><strong>Common components</strong>: Reusable code modules, UI elements, and backend services.</li><li><strong>Case management systems</strong>: Platforms that support internal workflows across departments.</li></ul><p>These are the things we physically build and use to deliver services. They’re the nuts and bolts — often technical, but not exclusively so.</p><p><strong>2. How to find &amp; share things — The knowledge layer</strong></p><p>This is about surfacing and distributing what we already know:</p><ul><li><strong>Service histories</strong>: How a service evolved, what decisions were made, what worked and what didn’t.</li><li><strong>Onboarding guides</strong>: Helping new team members understand how things work.</li><li><strong>Service information</strong>: All the information building up in a service team</li></ul><p>This layer is about <strong>knowledge management</strong> — making sure that valuable insights don’t get lost in the shuffle.</p><p><strong>3. How we do things — The ways of working</strong></p><p>This includes:</p><ul><li><strong>Templates</strong>: Roadmaps, service blueprints, business cases.</li><li><strong>Standards and principles</strong>: For AI, ethics, security, and more.</li><li><strong>Common rituals</strong>: Show &amp; tells, retros, user research practices.</li></ul><p>These are the cultural and procedural elements that shape how we work. They’re often invisible, but they’re critical to enabling reuse and linking our work up across areas.</p><h3><strong>Why Reuse Matters</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fEirc-j6n60-2W87a_D-w.png" /></figure><p>Let’s be honest: working in silos can be fast. If you’re under pressure to deliver, it’s tempting to just build something from scratch. But that speed is deceptive. It’s short-term gain for long-term pain.</p><p>Here’s what happens when we don’t reuse:</p><ul><li><strong>Duplication of effort</strong>: Multiple teams solving the same problem independently.</li><li><strong>Inconsistent user journeys</strong>: Services feel disconnected and confusing.</li><li><strong>Wasted resources</strong>: Time, money, and energy spent reinventing the wheel.</li><li><strong>Burnout</strong>: Teams constantly firefighting instead of innovating.</li></ul><p>Now imagine the alternative:</p><ul><li><strong>Efficiency</strong>: Teams build faster by starting with proven solutions.</li><li><strong>Quality</strong>: Reused components are tested, accessible, and secure.</li><li><strong>Consistency</strong>: Users experience seamless journeys across services.</li><li><strong>Motivation</strong>: Teams focus on the unique, high-impact parts of their work.</li></ul><p>Reuse isn’t just a nice-to-have. It’s a strategic imperative.</p><h4>The Case for Reuse — Tailored to Your Audience</h4><p>When making the case for reuse, it helps to tailor your message to different stakeholders:</p><ul><li><strong>For teams</strong>: Reuse means less grunt work and more time for creative problem-solving.</li><li><strong>For users</strong>: Reuse leads to smoother, more predictable experiences.</li><li><strong>For organisations</strong>: Reuse drives efficiency, reduces risk, and improves service quality.</li></ul><p>And yes, working in silos might seem faster. But it’s a false economy. The real value comes from thinking long-term — building infrastructure and culture that supports reuse by default.</p><h3><strong>Four Workstreams Driving Reuse</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vh8bHXWrZePgjfi_hmieMQ.png" /></figure><p>To move from vision to reality, we’ve launched <strong>four interconnected initiatives</strong>, each tackling a different aspect of reuse. These aren’t just design experiments; they’re strategic efforts to build infrastructure and culture that support reuse by default.</p><ol><li><strong>Design System</strong></li></ol><p><strong>Focus:</strong> Team setup, contribution strategies, scaling</p><p>The MoJ Design System is our most mature workstream. It’s been running for years and now includes two dedicated teams. Through this, we’ve learned a lot about what a sustainable “business model” for reuse looks like: how to structure teams, enable contributions, and scale across domains.</p><p><strong>2. Service Patterns</strong></p><p><strong>Focus:</strong> Identifying reuse opportunities, measuring impact</p><p>Service patterns help us understand repeatable user tasks and how they can be reused across services. This workstream is both cross-government and embedded in service teams, helping us scope opportunities in the wider reuse space and think critically about how to measure reuse impact.</p><p><strong>3. Common Components</strong></p><p><strong>Focus:</strong> Engineering reusable building blocks</p><p>This is our newest initiative, focused on the engineering side of reuse. We’re exploring how to build shared components that can be used across services and tech stacks. It’s early days, but we’re already identifying key opportunity areas and working closely with engineering leadership.</p><p><strong>4. Cross-Government Reuse Library</strong></p><p><strong>Focus:</strong> Enabling collaboration and discoverability</p><p>The reuse library is creating a central space where reusable assets (design systems, patterns, standards, and more) can live side by side. It’s about making things easy to find, reducing duplication, and sparking collaboration across departments.</p><h3><strong>How These Workstreams Connect</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GMwpVOYKsbWj5TImLxr7VA.png" /></figure><p>Each initiative plays a different role in the reuse ecosystem:</p><ul><li><strong>Design System</strong> and <strong>Common Components</strong> are the <strong>building blocks:</strong> they help teams construct services faster and more consistently.</li><li><strong>Service Patterns</strong> are the <strong>touchpoints for sharing:</strong> they help teams identify reuse opportunities and align on best practices.</li><li>The <strong>Reuse Library</strong> is the <strong>discovery layer:</strong> a place where all reusable assets can be surfaced and shared.</li></ul><p>Importantly, these aren’t just for designers. They’re for <strong>whole teams</strong> — delivery managers, developers, researchers, and policy colleagues. Reuse is a team sport.</p><h4><strong>A Cultural Shift</strong></h4><p>Reuse isn’t just about tools and systems. It’s about culture.</p><p>We need to move from “my team, my service” to “our work, our ecosystem.” That means:</p><ul><li><strong>Making work visible</strong>: So others can find and build on it.</li><li><strong>Lowering barriers to contribution</strong>: So sharing is easy and rewarding.</li><li><strong>Thinking cross-government by default</strong>: So we design for scale, not just for our corner.</li></ul><h4><strong>A Call to Collaborate</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNggTlfyNrlFzv2Ivn487A.png" /></figure><p>Everything we’re sharing is a work in progress. Some initiatives have been running for years; others are just beginning. Nothing is set in stone. We want your feedback, your ideas, your examples.</p><p>This isn’t something we can do alone. Let’s build a culture of sharing and reuse — together.</p><p>READ THE NEXT PART: <a href="https://medium.com/share-reuse/doing-design-systems-in-government-differently-71bb6a2579ff"><strong>Design System</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce2ac43dd5bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/write-up-share-reuse-by-design-talk-at-sdingov-2025-ce2ac43dd5bb">Write-up: “Share &amp; Reuse by Design” — Talk at SDinGov 2025</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Patterns: Part 4 — new patterns and productive collaboration]]></title>
            <link>https://medium.com/share-reuse/service-patterns-new-patterns-and-productive-collaboration-3ae587ad697b?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ae587ad697b</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[uk-government]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[service-patterns]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 10:34:27 GMT</pubDate>
            <atom:updated>2025-07-29T12:19:36.647Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOwwAIprasLa9Sj6W-gm5w.png" /></figure><h3>Service Patterns: Part 4 - new patterns and productive collaboration</h3><p>It’s been a while since I blogged, so here are a few updates on what’s been happening over the last few months.</p><h3>New cross-gov service pattern</h3><p>My last blog highlighted the ‘proof of concept’ for a cross-government service pattern to design services that involve ‘applying’ for things. <a href="https://design-patterns.service.justice.gov.uk/service-patterns/apply/">You can view the apply pattern here</a>. It was created with input from 5 UK government departments and facilitated by myself, Lindsay Stephens (DWP) and Gareth Thomas (DEFRA).</p><p>Since then we’ve produced another proof of concept pattern for services involving ‘appointments’. This time more than 30 government departments, arm’s length bodies (ALBs), and other public sector organisations collaborated to create the pattern during Services Week 2025. <a href="https://design-patterns.service.justice.gov.uk/service-patterns/appointment/">You can view the appointments pattern here</a>. Thank you to everyone who participated! Please take a look — we’d love your <a href="https://forms.office.com/Pages/ResponsePage.aspx?id=KEeHxuZx_kGp4S6MNndq2ML_UAYVtf1Jv53R4CVxx1hURFpPVDhUQVJVNkQxMzQyODRON0kzVVpKUi4u">feedback</a> on both patterns.</p><figure><img alt="A screenshot of the ‘appointments’ service pattern, listing common user needs for people using this type of service." src="https://cdn-images-1.medium.com/max/958/1*PP49EGqJeb_4Sr_zeBDFvA.png" /></figure><p>We are yet to determine if the right place for service patterns is at a cross-government level, organisation level, or a combination of both - but we hope these two service patterns support and encourage discussions about the value, place and purpose of service patterns. Lindsay, Gareth and I are currently discussing what to work on next. We think that’s going to be a focus on creating a business case for service patterns to quantifying the value of their benefits (if you have any ideas for that <em>please</em> let me know!)</p><h3>Service pattern collaboration</h3><p>Active collaboration on service patterns continues. More departments and organisations are investing resources into exploring them. A few weeks ago colleagues from six organisations with active service pattern works streams came together to share their progress in more detail, which I found really inspiring.</p><p>Familiar topics of conversation continue to crop up. How many service patterns do we need? At what level of zoom or fidelity should they be defined? Where is the line that separates patterns that you find in today’s digital design system, and service patterns as they are understood here? Are services patterns primarily about reusable digital prototypes for screens and flows, or guides to common steps, insights, and scenarios? Whilst its reassuring we’re all asking the same questions, defining service patterns precisely, across industry, remains challenging.</p><p>On the point about service patterns as digital flows vs guidance, the cross-government examples above lean heavily into the ‘guidance’ understanding of service patterns. Focusing on that was mostly a practical decision based on the resources we had. The answer, like most things, is probably somewhere between the two extremes. On a more screens and flows view of things I like the work Liam Collins is doing at the Welsh Government. He has created some compelling visual prototypes of what that approach might look like, <a href="https://digitalpublicservices.gov.wales/blog/our-work-so-far-service-patterns">which you can read about here</a>. I hope to explore that approach further in the work we are doing internally at the Ministry of Justice.</p><h3>Useful links</h3><p>I’d like to recommend this <a href="https://benholliday.com/2025/03/28/everything-service-patterns/">blog post by Ben Holliday</a> from a few months ago. It’s a great summary of the story of Service Patterns in UK Government (and beyond) over the past 10 years, with links to the all useful blog post and other assets that tell the story of our progress to date.</p><h3>Coming up next</h3><p>If you’re going to <a href="https://sdingov.net/">SDinGov 2025</a> I’m pleased to see there are a few sessions touching on service patterns or adjacent topics, including one from the Ministry of Justice looking at our wider approach to ‘<a href="https://sdingov.net/programme/share-and-reuse-design">share and reuse</a>’ components and patterns. I’ll be there all three days so please also say hello and introduce yourself!</p><p>There’s also a new <a href="https://publicpolicydesign.blog.gov.uk/2025/07/14/join-our-first-global-public-design-conference/">Public Design Conference</a> in London on 11th September that will be focused on global public design patterns, including (but not limited to) service patterns.</p><h3>Keep in touch</h3><p>If you have access to the UK cross-government Slack workspace, you can join the conversation there in our channel <a href="https://ukgovernmentdigital.slack.com/archives/C064FK6C718">#service-patterns</a>. You can also get in touch with me via ServicePatterns@justice.gov.uk. If you have an active work stream developing or using service patterns I’d especially like to hear from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ae587ad697b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/service-patterns-new-patterns-and-productive-collaboration-3ae587ad697b">Service Patterns: Part 4 — new patterns and productive collaboration</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Patterns: Part 3 - working across government]]></title>
            <link>https://medium.com/share-reuse/service-patterns-part-3-working-across-government-6b2e3421e99d?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/6b2e3421e99d</guid>
            <category><![CDATA[user-centred-design]]></category>
            <category><![CDATA[uk-government]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[service-patterns]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Thu, 20 Mar 2025 15:59:41 GMT</pubDate>
            <atom:updated>2025-03-20T15:59:41.103Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VeiTk7NJIWY7VPxop8MhlQ.png" /></figure><p><em>This is an abridged version of a blog originally published at </em><a href="https://services.blog.gov.uk/2025/03/19/developing-service-patterns-reusable-designs-for-building-government-services/"><em>https://services.blog.gov.uk</em></a><em> on March 19, 2025.</em></p><p>Over the past year a working group has developed a service pattern that could be applied across all UK government departments. It contains recommendations on how to build a user-focused service that involves ‘applying’ for something.</p><h3>What are service patterns?</h3><p><a href="https://medium.com/share-reuse/service-patterns-part-1-history-opportunity-and-challenges-bfd3989a845a">Part 1</a> of this series explains what we mean by service patterns, but as a brief reminder: service patterns describe replicable pieces of services that can be combined to build or shape end-to-end services. For example patterns for ‘apply for something’ and ‘book an appointment’ could be used to create services to receive a new benefits payment, get a new passport, and many others. A library of service patterns would act as design guides to build services in repeatable and consistent ways.</p><h3>Service patterns across government</h3><p>Designers from Ministry of Justice (MOJ), Department for Work and Pensions (DWP) and Department for Environment Food and Rural Affairs (Defra), had all been thinking about service patterns. A working group was formed to share experiences. Whilst slightly different approaches were being taken, it was apparent that the names of the patterns themselves (things like ‘apply for something’ and ‘book an appointment’) were largely consistent across departments.</p><p>In order to validate this a workshop was held to compare and contrast our pattern names which included representatives from 5 departments. The workshop proved that most departments shared the same pattern needs. We also agreed that the type of content we expected to find in a service pattern library was largely similar. Five patterns stood out as having the greatest potential for shared needs — ‘apply’, ‘appointments’, ‘get a decision’, ‘pay’ and ‘evaluate’.</p><p>A second workshop was held to identify what type of content could be reusable across departments, using ‘apply’ as a test case for a service pattern. Participants mapped their service pattern needs against each other’s to identify similarities and variations. <a href="https://design-patterns.service.justice.gov.uk/service-patterns/apply/">The outcome of that workshop is now available as a prototype for review and feedback.</a> The prototype includes user needs, internal business needs, journey stages and steps, and typical user scenarios. We expect a full pattern library to contain other types of information such as recommended digital components and patterns, case studies, and any relevant accessibility concerns.</p><figure><img alt="a laptop screen showing the  prototype service pattern for apply" src="https://cdn-images-1.medium.com/max/620/0*3oCsBcWPOTPzS7fm.jpg" /></figure><p>We do not believe service patterns replace the need for design. Different departments and services will have their own unique challenges and opportunities to address. However by providing a shared starting point, we hope they can enable more efficient, consistent, and scalable designs.</p><h3>What next?</h3><p>We’d love your feedback on our <a href="https://design-patterns.service.justice.gov.uk/service-patterns/apply/">prototype</a> to inform the next stages of our work. You can do that by completing the <a href="https://forms.office.com/Pages/ResponsePage.aspx?id=KEeHxuZx_kGp4S6MNndq2ML_UAYVtf1Jv53R4CVxx1hURFpPVDhUQVJVNkQxMzQyODRON0kzVVpKUi4u">apply pattern prototype survey</a> by the end of April 2025. You can also email questions or comments to <a href="/service/mailto:servicepatterns@justice.gov.uk">servicepatterns@justice.gov.uk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b2e3421e99d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/service-patterns-part-3-working-across-government-6b2e3421e99d">Service Patterns: Part 3 - working across government</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do we need a design system?]]></title>
            <link>https://medium.com/share-reuse/why-do-we-need-a-design-system-dd15ca8b2361?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd15ca8b2361</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Rob McCarthy]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 11:09:24 GMT</pubDate>
            <atom:updated>2024-10-07T11:15:43.755Z</atom:updated>
            <content:encoded><![CDATA[<h4>Having the GOV.UK Design System negates the need for any other UK Government design systems. Or does it?</h4><figure><img alt="A diamond shape with a thick blue outline sits at the top of a tree diagram. This is meant to represent the GOV.UK Design System. Arrows come from the top diamond down to five smaller diamonds with different coloured outlines. These are meant to represent different UK Government department design systems. The fifth diamond includes a question mark symbol in the centre. An arrow comes down from each of the smaller diamonds to 4 smaller rectangles representing products in each department." src="https://cdn-images-1.medium.com/max/1024/1*Hq46YQhLTYfpnU_pq1MVtA.png" /></figure><p>My colleagues at Ministry of Justice, <a href="https://medium.com/@nikolagoger">Nikola Goger</a> and <a href="https://medium.com/@martin.ford-downes">Martin Ford-Downes</a>, have recently written about <a href="https://medium.com/share-reuse">share and reuse</a>, and more specifically <a href="https://medium.com/share-reuse/reuse-by-design-1fc69d93c917">how government could work better if it had reuse at its core</a>. Many points across the writings resonated with my work leading the MoJ Design System, so much so, I thought it would be a good starting point for my entry into the world of writing right here on Medium.</p><p>Over the last 12 months I’ve successfully made the case for a centralised team to work on and maintain the <a href="https://design-patterns.service.justice.gov.uk/">MoJ Design System</a>. Whilst I was making the case, a question that persistently come up was: <em>why do we need a design system when we already have the GOV.UK Design System?</em></p><p>So that’s where I’m starting: <strong>Why do I think government departments need their own design systems when there’s already the well established and internationally heralded </strong><a href="https://design-system.service.gov.uk/"><strong>GOV.UK Design System</strong></a><strong>?</strong> <a href="https://designnotes.blog.gov.uk/2019/02/14/how-the-gov-uk-design-system-can-work-alongside-other-government-design-resources/">I’m not the first person to think about this</a>.</p><p>Before I get too far in, it’s really important to say that any reasons I think there are for departments to have their own design system is not a criticism of the GOV.UK Design System, or anyone that has worked on it. The work that has been done, and the outcomes achieved, have been hugely transformational for the UK Government and beneficial to so many people, especially the general public who are using, needing, and often relying on the digital services hosted across the <a href="https://www.gov.uk/">GOV.UK website</a>. I’m a fan-boy for sure, through-and-through.</p><h3>So, if there’s nothing wrong with the GOV.UK Design System, why do departments need their own?</h3><p>The GOV.UK Design System provides styles, components, patterns and pages for reuse by teams that are creating digital services hosted on GOV.UK. These reusable building blocks help teams create digital services that are accessible, usable, and consistent.</p><p>Examples of these digital services would include <a href="https://www.gov.uk/renew-adult-passport/renew">renewing a passport</a>, <a href="https://www.gov.uk/pay-parking-fine">paying a parking fine</a>, or <a href="https://www.gov.uk/state-pension-age">checking your state pension age</a>.</p><p>Many of the digital services hosted on GOV.UK are transactional and follow a linear-ish path from start-to-finish. Also, many of these digital services are used by people infrequently. Of course there are exceptions to both of these statements.</p><p>Whilst this public-facing work is going on, there are also many teams across government departments who aren’t creating digital services to go on the GOV.UK website. Instead, they’re creating digital products (a fancy name for software) that are used internally by administrative or operational staff.</p><p>Examples of these digital products could include probation staff updating a person’s licence arrangements, administrative staff processing a lasting power of attorney, or prison staff checking a list of visitors for the upcoming day.</p><p>Many of these digital products have multiple and interweaving journeys rather than being transactional and linear. Administrative or operational staff may need to search for a record, view that record, edit that record, link that record to another, and archive or delete that record. All of those tasks may be present within a single part of a digital product, and that digital product may contain many other parts that contain many other tasks.</p><p>This means that lots of teams across government are making platforms, products, tools, software (whatever you want to call it) so that administrative and operational staff can work more easily, more accurately, and more efficiently.</p><p>Another difference between the services on GOV.UK and the products used internally by administrative and operational staff are that these users are often doing these tasks all day, every day. The needs of someone renewing their passport every 10 years are very different from the needs of a super-user that’s using a piece of software to do their job.</p><p>I think the GOV.UK Design System provides a lot of the necessary user-interface components that teams need to create accessible, usable, and consistent digital services that are hosted on the GOV.UK website. I don’t think the GOV.UK Design System provides the necessary user-interface components that are needed to create the software used behind the scenes in government.</p><p>At this point, I do think it’s worth pondering the question of <em>why would the GOV.UK Design System contain components for internal digital products?</em> After all, the design system is prefixed by GOV.UK to quite literally represent <a href="https://who.is/whois/gov.uk#:~:text=Domain%20name%3A%0A%20%20%20%20%20%20%20%20gov.uk">the domain</a> it’s used for, and this focussed scope is likely one of the reasons for the success of the GOV.UK Design System.</p><p>To expect the GOV.UK Design System to contain everything that teams across government could need would mean it needs to be financed and supported to do that.</p><p>Most products aren’t backed by unlimited time and money, and that’s why Product Managers are so valued — they prioritise and carve out the most impactful and valuable path that a product can take. And that’s what the GOV.UK Design System has done so well over the past 6 years. It’s been focussed on what it can do to offer the most value. Where it’s not been able to do everything (<em>I feel ridiculous even writing that, like it’s realistic to expect ALL THE THINGS</em>), government departments like the <a href="https://design.homeoffice.gov.uk/">Home Office</a>, <a href="https://design.education.gov.uk/design-system">Department for Education</a>, <a href="https://design-system.dwp.gov.uk/">Department for Work and Pensions</a>, and the <a href="https://design-patterns.service.justice.gov.uk/">Ministry of Justice</a> have all setup their own design systems. It’s been out of a necessity to create the reusable building blocks that their teams need in order to deliver accessible, usable and consistent digital products for use by their administrative and operational staff.</p><h3>Sounds like we’re headed for silo-topia. Right?</h3><p><a href="https://medium.com/share-reuse/reuse-by-design-1fc69d93c917">Nikola’s writings on reuse by design</a> talks about the utopia of a connected government where digital infrastructure is centralised, but uses a participatory model of dedicated and incentivised people or teams within departments. When making the case for a centrally maintained MoJ Design System, this utopia has stuck firmly with me. I’m aware of the irony about believing in the vision of a more connected government with underlying digital infrastructure whilst having made the case for what could be viewed as a disconnected and siloed design system.</p><p>I’m using the words ‘disconnected’ and ‘siloed’ intentionally here as it’s a view that could understandably be held when asking the valid question: <em>why do we need a design system when we already have the GOV.UK Design System?</em></p><figure><img alt="A diamond shape with a thick blue outline sits in the middle of a tree diagram. This is meant to represent the GOV.UK Design System. Arrows come from five smaller diamonds into the larger blue diamond. These are meant to represent different UK Government departments. Arrows go to 20 or more smaller rectangles which represent products across government." src="https://cdn-images-1.medium.com/max/1024/1*MEQ6vWsvjlnJHtRg7l1xXA.png" /></figure><p>A connected government with underlying and centralised digital infrastructure, created and maintained through a participatory model with all departments, is the future that I think we need. But, it’s not our reality now (<a href="https://www.gov.uk/government/news/tech-experts-to-shape-government-digital-vision-to-drive-innovation-and-boost-public-services">or maybe it is closer than I think with an emerging ‘digital centre’</a>).</p><p>Whilst it’s not our reality now, we must make tracks towards this future where silos are broken down — and I think the case I’ve been making for a centrally supported and maintained MoJ Design System means we can do some of that work which will take us there. Rather than create our own silo and only concentrate on what we’re doing, we will have a team that can work with other departments, contribute to a digital centre, and in some cases, hold up a torch and light the way.</p><p>In my next post, I’m going to look at the <a href="https://bigmedium.com/ideas/design-system-pace-layers-slow-fast.html">speed of design systems</a> in government versus the speed of product development. I’ll dig into what problems I think we have, and show what we’re doing on the MoJ Design System to try and solve them.</p><p><a href="https://medium.com/share-reuse"><strong>Reuse by Design</strong></a> is a series of blogs making a case for a share + reuse infrastructure in government and how to implement reuse by design.<br><strong>Read all blogs: </strong><a href="https://medium.com/share-reuse">https://medium.com/share-reuse</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd15ca8b2361" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/why-do-we-need-a-design-system-dd15ca8b2361">Why do we need a design system?</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Patterns: Part 2 — Developing our own Service Patterns]]></title>
            <link>https://medium.com/share-reuse/service-patterns-part-2-developing-our-own-service-patterns-228355f8bb27?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/228355f8bb27</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[service-patterns]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 08:32:56 GMT</pubDate>
            <atom:updated>2025-03-20T15:18:59.336Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A logo that says ‘Design by Reuse’ illustrated by building block toys being placed on a table." src="https://cdn-images-1.medium.com/max/1024/1*XAM-7Pknx9uzhdfkbms9xw.png" /></figure><h3>Service Patterns: Part 2 — Developing our own Service Patterns</h3><p><em>This blog is part of a series from designers at the Ministry of Justice who are making the case for ‘share + reuse’ infrastructure across government. Find out more about that </em><a href="https://medium.com/@nikolagoger/reuse-by-design-18510ac35dc8"><em>here</em></a><em>. If you’d like to get involved please get in touch via </em><a href="/service/mailto:martin.ford-downes@digital.justice.gov.uk"><em>email</em></a><em> or </em><a href="https://www.linkedin.com/in/martin-ford-downes/"><em>LinkedIn</em></a><em>.</em></p><h3>Building our patterns</h3><p>In <a href="https://medium.com/share-reuse/service-patterns-part-1-history-opportunity-and-challenges-bfd3989a845a">part 1</a> of this series I talked about how we define service patterns at the Ministry of Justice, the research we did into the recent history of the idea, and our initial reflections on the opportunities and challenges. The two key themes that emerged were a) what is the effort required to produce and maintain service patterns and b) how to prove the benefit of service patterns. Part 2 below focuses on our work to build service patterns at the Ministry of Justice, with part 3 to follow on our other collaborative efforts to produce cross-government service patterns.</p><h3>Addressing a need</h3><p>Service Patterns at the Ministry of Justice emerged in response to a need — how could user centred designers enable and assure consistency of design across the dozens of digital product teams building and maintaining 100s of services? While it is not a perfect measure of scale and complexity, the Ministry of Justice is one of the largest UK government departments with over 90,000 staff and an annual budget in the region of £10bn. With that size and scale comes predictable risks around design consistency. We could easily spot instances of deviation in our digital interfaces that could be addressed with a traditional design system, but we could also see duplication of a broader type, concerning the overall tasks and activities our users needed to complete.</p><h3>Identifying our pattern categories</h3><p>We took this idea to the community of user centred designers working in HM Prison and Probation Service (HMPPS), and asked them to describe, in their own words, the fundamental task and activities users of their services undertook. More than 50 designers contributed their ideas, which were then affinity mapped and given draft title categories or themes to describe each grouping. These themes and categories were iterated upon, leading to our first set of service pattern definitions, which we grouped by category.</p><figure><img alt="A screenshot of a miro virtual whiteboard showing different coloured post it notes, with the names of digital services sorted into categories by the type of action the user takes in that service — in this case, booking an appointment." src="https://cdn-images-1.medium.com/max/1024/0*ptBspKNpjuJUM5Jx" /></figure><p>This was a relatively quick and painless exercise, although the categories and names went through several versions. We made two observations at this point; the first was that some patterns were potentially far larger and more complex than others (e.g. apply for something vs record information), but it wasn’t clear yet if that was a problem. Secondly, some patterns could both exist on their own (e.g. provide information) and be sub-elements of the more complex patterns (e.g. provide information as a sub-element of the book an appointment pattern). This could lead to some complexity in the information architecture of the eventual pattern library.</p><figure><img alt="A screenshot of a miro virtual whiteboard showing the names of our proposed service patterns." src="https://cdn-images-1.medium.com/max/1024/0*Pr4MghexVdSo_-kf" /></figure><h3>Prototyping a pattern library</h3><p>From our research we knew that several other organisations had reached this point, and many of them went on to catalogue their existing services under these headings. But as noted in our previous blog, evidence of people getting further than this point was limited. However, inspired by the relative ease of reaching this point, we moved straight to attempts at documenting design guidance for our patterns. Our intent was to create a tool for designers that would kick-start their designs, with guidance covering the common, predictable and repeatable elements of a service. This in turn would create more time and space to explore the aspects of the new service that were different or unique. We identified potential information categories for these library entries, things like a description of the scope of the pattern, examples of existing implementation, relevant research, links to reusable design artefacts, and other useful considerations, like the happy and unhappy path scenarios to consider to prevent dead ends in your service. We also wanted to make recommendations for digital components and patterns, linking to our existing Design System. A mockup of a pattern using dummy information was created to support this.</p><figure><img alt="A screenshot of our mock-up service pattern, giving examples of the sort of information we expect to find within a service pattern library, such as the description and scope of the pattern." src="https://cdn-images-1.medium.com/max/1024/0*1--q-wgxNH1W2vk8" /></figure><p>Our first attempt at this was to ask for volunteers among our product teams to select one potential pattern from a recently developed service, and to retrospectively create a service pattern from it. The success criteria was that the information had to be sufficiently generic to be applicable for multiple services, but not so generic that it was of limited value when applied. This first attempt was only partially successful. While the teams could identify content for the different categories of information we wanted, reverse engineering their very specific designs into more generic ones was difficult, and likely could have benefited from more dedicated time and effort.</p><p>We decided to park this approach whilst we explored a few other ideas. One was to use our service patterns as a way of blocking out user flows when scoping new pieces of work. This received positive feedback from designers as a quick and simple method to outline the different aspects that would be needed for a new service. We also spent some time thinking about a submission process and publication standards for service patterns which was aligned to our existing design system.</p><figure><img alt="A screenshot of a miro virtual whiteboard showing service patterns being used to map our a user flow." src="https://cdn-images-1.medium.com/max/1024/0*f4JoMT_Hwk3LFjeF" /></figure><h3>Next steps and reflections</h3><p>Following the above, work at the Ministry of Justice then moved to a collaboration with other government departments to create a cross-government service pattern prototype. This will be the focus of the next blog, but by way of a preview, the collaborative approach taken there has worked well, and learnings from it are going to be applied to our next attempt at creating Ministry of Justice in-house service patterns. We are also going to use our <a href="https://medium.com/rocketships/the-rocketship-files-x-1-year-in-space-5627f01ab44d">Rocketships model</a> to give it the time and space we now think it needs to be successful. We will share progress on this in the future.</p><p>Finally, some additional observations we’ve made over the past year;</p><ul><li>Building and maintaining patterns is not something that can be done as a ‘side project’. Existing design systems require teams to maintain them, it is likely Service Patterns will need something similar.</li><li>We are still looking for good examples of proving the benefit. The scale of service patterns means that the elapsed time from creating a pattern through to at least one more service being developed using that pattern is greater than creating a simple component and measuring its reuse.</li><li>Our initial ambition was to create a full library of patterns, but our focus going forward is going to be on fewer higher value contributions. Earlier in this blog we noted that some of our patterns were quite small compared to others, and on further reflection, are likely very close to what you’d expect of a pattern in an existing design system. Therefore our focus is going to be on the more complex patterns such as ‘apply’ and ‘book an appointment’.</li><li>As part of our broader thinking on <a href="https://medium.com/share-reuse/reuse-by-design-18510ac35dc8">share and reuse in government</a>, we want to test whether service patterns in abstract are the best way to deliver the value we are aiming for, or if a “productification” approach may be better. What we mean by this is whether whole bundles of components including fully coded capabilities may be a better approach.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=228355f8bb27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/service-patterns-part-2-developing-our-own-service-patterns-228355f8bb27">Service Patterns: Part 2 — Developing our own Service Patterns</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reuse by Design]]></title>
            <link>https://medium.com/share-reuse/reuse-by-design-1fc69d93c917?source=rss----e3d7c1b0aafd---4</link>
            <guid isPermaLink="false">https://medium.com/p/1fc69d93c917</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[public-sector]]></category>
            <dc:creator><![CDATA[Nikola Goger]]></dc:creator>
            <pubDate>Mon, 16 Sep 2024 14:52:44 GMT</pubDate>
            <atom:updated>2024-09-17T12:23:21.129Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reuse by Design - Chapter I</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UDzzVf9twKCHFO_BKi0MNw.png" /></figure><h3>A greenfield Utopia — How would government work and deliver if we built it from scratch?</h3><p>Read the <a href="https://medium.com/@nikolagoger/reuse-by-design-18510ac35dc8"><strong>intro to Reuse by Design here</strong></a></p><p>We have seen some great work in countries like <a href="https://e-estonia.com/story/">Estonia</a>, Ukraine, Italy, or India that show how governments can build efficient and user-centred services. Could those be blueprints for us? How can we stop solving the same problems over and over again? How can we design more like Lego? What could a <a href="https://www.publictechnology.net/2024/07/09/education-and-skills/gds-and-cddo-set-to-move-from-cabinet-office-to-dsit/">new digital centre</a> look like?</p><p>I’d love to see an urban planning approach. Imagine a government <strong>town square</strong> (Meet other citizens and have a chat!) with a <strong>store</strong> (“Locally produced components!”), a <strong>library</strong> (Find all information about past/existing work), a <strong>university</strong> (Learn new things, develop standards, experiment), a <strong>market</strong> to showcase local produce (Discover current work) and a <strong>utilities provider</strong> to link everyone into the same tech and data infrastructure. This would cover a lot of common needs — and too many of them are currently developed in silos.</p><p>So what would we need to build better shared infrastructure that makes it easier and faster for the wider government to build better services?</p><ul><li><strong>Components: </strong>libraries, share infrastructure and a new participation model</li><li><strong>Collaboration:</strong> new ways of working and enabling tech</li><li><strong>Culture: </strong>a culture of reuse and &amp; incentives for departments</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6ze2CbKCTrUbgejVniJ9w.png" /></figure><h3><strong>Components</strong></h3><p><em>Libraries, share infrastructure and a new participatory model</em></p><p><strong>What do we have?</strong></p><p>Quite a lot of good stuff! We have the GOV.UK design system, we have GOV.UK components like Pay, Notify etc.</p><p><strong>What do we need?</strong></p><p>A lot more of this. A LOT.</p><p>There are many more types of things we should share. I’ll talk about it in <strong><em>Chapter 2: Taxonomy and Productifiction</em></strong><em> — What are the things we can share + reuse?</em> of this series and you can already read about <a href="https://medium.com/share-reuse/service-patterns-part-1-history-opportunity-and-challenges-bfd3989a845a">Service Patterns: Part 1 — History, Opportunity and Challenges</a> in the blog by <a href="https://medium.com/u/79a914e48bc1">Martin Ford-Downes</a></p><p>The issue with building shared components from the centre only is that it currently covers a relatively small part of the work that is happening. And the current model<strong> </strong>doesn’t scale well to be able cover more of the needs of all of the departments. We could do with a warehouse instead of a small store.</p><p>How can we get central share infrastructure that covers a lot more ground by providing the urban planning and will allow the departments to focus on the unique work their services require? The answers is a <strong>participatory model</strong>.</p><h3>C<strong>ollaboration</strong></h3><p><em>New ways of working and enabling tech</em></p><p><strong>What do we have?</strong></p><p>A lot of smart people and great work happening everywhere. People are willing to share and reuse but it is hard.</p><p><strong>What do we need?</strong></p><p>A way to harness all this potential: A functioning pipeline so departments can feed work into the centre much more easily.</p><ul><li><strong>New ways of working</strong></li></ul><p>In our departmental Design System (That a lot of departments have one already makes the point that it’s not currently easy to share into the centre) we are currently developing service models on how the teams in our different departmental areas can run ahead and build things and share them back into the Design System. We are experimenting with the idea of a community-owned sandbox that significantly lowers the hurdles to contributing and offers transparency on the work that is happening. A similar model could be used to work cross-government.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cbR-LB7Q6WDRb3rhwpkjw.png" /></figure><p>More about this in <strong><em>Chapter 3: Building new Infrastructure </em></strong>and in a blog on the MoJ Design System team by <a href="https://medium.com/u/b56ba66f4bce">Robertjmccarthy</a> soon.</p><ul><li><strong>Technology that enables collaboration</strong></li></ul><p>We are lacking a town square. We are not currently set up to easily collaborate and share between departments. I’ve learned this the hard way when I set up a Sharepoint collab space for the cross — gov Heads of Design to share documents and collaborate. Even though a lot of departments are moving over to MS, this is still a clunky and very manual process that doesn’t scale well and has a difficult user experience. And a lot of people still can’t access it. The result is <em>very</em> low engagement.</p><p>We need technology that makes it easy to work together instead of putting up hurdles.</p><h3>C<strong>ulture</strong></h3><p><em>A culture of reuse and &amp; incentives for departments</em></p><p><a href="https://medium.com/u/566d3f4726bc">Richard Pope</a> makes a good point in Platformland (p114):</p><p><em>“Common components are an achievable aspiration that can transform public services, but experience shows that they are unlikely to emerge organically from government agencies. The institutional incentives are not strong enough.”</em></p><p>I couldn’t agree more — but this a problem we really need to solve. To significantly raise the amount of shareable material we need to find ways to enable it to emerge from departments . And we need incentives.</p><p><a href="https://gds.blog.gov.uk/2013/01/06/digital-transformation-in-2013-the-strategy-is-delivery-again/"><strong>The strategy has been delivery</strong></a><strong> for quite a while now. We are very focused on delivering fast </strong>— and working in a silo enables us to deliver fast. Of course this is short-sighted since in the long run we could deliver a lot more quality work in much shorter time if we reused instead of reinventing the wheel. So we need to shift the focus more long-term and cross-cutting.</p><p><strong>What do we have?</strong></p><ul><li>A lot of willingness to reuse — as shown in the success of the available components and the gov design system. Also in how missed the GDS Academy is.</li><li>It’s even in the Service Standards! <a href="https://www.gov.uk/service-manual/service-standard/point-13-use-common-standards-components-patterns"><em>13. Use and contribute to open standards, common components and patterns</em></a></li><li><a href="https://labour.org.uk/change/mission-driven-government/">Mission-driven government</a> specifically aims to drive joined up working between departments where so far “too often different parts of the government have pursued their own narrow goals rather than working together.”.</li></ul><p><strong>What do we need?</strong></p><ul><li>Bake sharing and reusing into our <strong>ways of working</strong>. If you have interesting examples of teams integrating it into sprints / product lifecycles I’d love to hear them!</li><li>Departments need their own <strong>local reuse infrastructure </strong>to efficiently reuse and share their own components back into the centre. We need people in all departments who’s fulltime job it is to make it happen. We can’t just hope it will happen — and we can’t just rely on the centre.</li><li><strong>Incentives for departments </strong>to develop components and share them into the centre need to happen on a budget level. And by central and departmental leadership 100% buying into it and all sides enabling it in their departments via <em>love</em> (it’s in the strategy and in the goals and is celebrated) and <em>money</em> (there is actual investment into it).</li></ul><h4>Final thoughts that keep me up at night</h4><p>We still act and build services like a herd of small private sector start-ups and don’t really utilise our massive advantage: That we are at heart one giant public sector network that would be able to work incredibly efficient if we just had the infrastructure and the ways of working to do so.</p><p><strong>What have I missed so far? How does your Utopia look like? I’d love to hear your thoughts.</strong></p><p>Coming soon: <strong><em>Chapter 2: Taxonomy and Productifiction</em></strong><em> — What are the things we can share + reuse?</em></p><p><strong>Reuse by Design</strong> is a series of blogs by Nikola Goger collaborating with various smart brains working in the public sector.</p><p><strong>Read all chapters here </strong><a href="https://medium.com/share-reuse"><strong>https://medium.com/</strong>share-reuse</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fc69d93c917" width="1" height="1" alt=""><hr><p><a href="https://medium.com/share-reuse/reuse-by-design-1fc69d93c917">Reuse by Design</a> was originally published in <a href="https://medium.com/share-reuse">Share + Reuse</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>