<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Martin Ford-Downes on Medium]]></title>
        <description><![CDATA[Stories by Martin Ford-Downes on Medium]]></description>
        <link>https://medium.com/@martin.ford-downes?source=rss-79a914e48bc1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VYw7OxuANCOTxlljs6QOUw.jpeg</url>
            <title>Stories by Martin Ford-Downes on Medium</title>
            <link>https://medium.com/@martin.ford-downes?source=rss-79a914e48bc1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:25:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@martin.ford-downes/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What are the AI skills service designers need to develop now?]]></title>
            <link>https://medium.com/@martin.ford-downes/what-are-the-ai-skills-service-designers-need-to-develop-now-bd0c19ef2972?source=rss-79a914e48bc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd0c19ef2972</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 08:39:47 GMT</pubDate>
            <atom:updated>2026-02-10T09:13:51.371Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The impact of AI on service design</strong></h3><p>Like many people, I have been thinking about how AI will impact the future of my career. As a service designer working on digital public services, AI assistants are already part of my daily toolset. Solutions with AI features are being deployed, and the <a href="https://www.gov.uk/service-manual/service-standard">service standard</a> has just been updated to include AI considerations.</p><p>Also like many people I have opinions about the benefits and risks of AI. But whether you are positive about AI or not, this is our current reality - and service design has a role to play in it. In fact, I think we have an especially important role to play in it. AI is changing both how we do our job and the solutions we need to design, both requiring new skills. Thankfully, many of our existing skills remain suitable (the things AI is less likely to replace), and others will remain relevant with adaptation. Our profession can also play a key role in balancing the risk and reward of AI solutions, informing how we ideate and present ideas with AI elements to users and stakeholders.</p><h3><strong>AI learning outcomes for service designers</strong></h3><p>Over the past few months, I’ve been working on a set of ‘learning outcomes’ for service designers (published at the bottom of this blog), particularly for those designing digital public services. My thanks go to Julene Aguirre (Senior Service Designer, Ministry of Justice), Becky Mallaband (Head of Design School, NEC Digital Studio) and Tom White (Head of Research &amp; Service Design, NEC Digital Studio)<em> </em>who have collaborated with me to create this.</p><p>Our intention is not to promote or discourage the use of AI. Rather, this is intended as a pragmatic response to our current reality and the likely direction of our profession. I will be using this as a framework to plan my own learning priorities over the next few years, and I hope it will be of use to others too.</p><p>The outcomes are organised by five themes:</p><blockquote>A. AI foundational knowledge<br>B. AI to assist core service design tasks<br>C. Designing services that include AI components<br>D. AI to expand multidisciplinary capabilities<br>E. Skills AI is unlikely to replace</blockquote><p>Each section contains a high-level starting point for learning. Each outcome can be broken down further, some are more complex than others, and each individual will need to assess their own starting point and priorities. It is not intended that all service designers should become experts in all areas. In a future iteration we will include indicators for those we consider ‘essential’ and ‘advanced’ (your feedback is welcome here too). Also, as AI continues to evolve, it’s likely that these learning outcomes will need to change to keep pace.</p><p>Learning outcomes only take you so far and so the next step is to collate a set of recommended learning materials that will help you fulfil the outcomes. We’d like those to include a variety of options such as formal courses, books, podcasts, videos and communities.</p><p>I’d love to hear your feedback on the outcomes themselves and receive any recommendations you have for learning materials that could help us meet them! You can comment here, contact me via linked in, or add comments to this <a href="https://docs.google.com/document/d/1mVVXDPqypHXHgokUbYnx8a1kGPJwnS8GzZlkYiTMODI/edit?usp=sharing">google doc version</a>. <a href="https://drive.google.com/file/d/1xygt_CWu3OSVBQKmCgEKIxHjQ9g_46uv/view?usp=sharing">A PDF version is also available here</a>.</p><h3><strong>AI learning outcomes for service designers creating digital public services</strong></h3><h4><strong>A. AI foundational knowledge</strong></h4><p><em>This theme builds core AI literacy for service designers, focusing on how AI works, its limits, and its role within complex public services, both as a tool to develop services and as part of the infrastructure of services. It supports confident, ethical judgement about where AI is appropriate, how risks should be managed, and how AI can enhance, rather than replace, professional decision-making in justice contexts.</em></p><p>A1. Explain how different types of AI systems function and how they differ in capability and limitation.</p><p>A2. Distinguish between things AI can realistically support in service contexts and those it cannot, identifying common misconceptions or overclaims.</p><p>A3. Describe at a high level how AI systems interact with data, other digital infrastructure, and organisational systems, including where dependencies and constraints typically arise.</p><p>A4. Describe the current landscape of AI use across government and comparable organisations, identifying relevant patterns and lessons.</p><p>A5. Apply UK government service design standards for AI, including ethical guidance and AI as part of the service standard.</p><p>A6. Identify and articulate key ethical, legal, and operational risks associated with the use of AI in public service contexts.</p><h4><strong>B. AI to assist core service design tasks</strong></h4><p><em>This theme focuses on using AI to responsibly accelerate core service design work; improving speed, clarity, and consistency without reducing quality, rigour, or accountability.</em></p><p>B1. Summarise research materials (transcripts, notes, findings) using AI while checking for missing nuance, bias, or misinterpretation.</p><p>B2. Cluster insights into themes and opportunities using AI, then validate and refine them through human judgement.</p><p>B3. Generate early drafts of service design artefacts (journey maps, service blueprints, personas, storyboards) using AI.</p><p>B4. Translate rough sketches into clearer visuals or diagrams using AI-assisted tools.</p><p>B5. Produce draft briefs, problem statements, rationales, and presentation content using AI, strengthening them through critical review.</p><p>B6. Explain where and how AI contributed to design outputs.</p><p>B7. Evaluate and monitor for AI created risks, including hallucinated evidence, oversimplification, or loss of design intent.</p><h4><strong>C. Designing services that include AI components</strong></h4><p><em>This theme enables service designers to responsibly conceive, test, and critique service ideas that include AI components. It focuses on identifying genuine opportunities, recognising risks early, and applying strong service design judgement to decide when AI adds value and when it should be avoided.</em></p><p>C1. Identify and evaluate opportunities where AI could meaningfully improve (or degrade) services.</p><p>C2. Map and explain AI touchpoints within journey maps and service blueprints.</p><p>C3. Critique AI-enabled concepts against government principles such as safety, transparency, accountability, and human oversight.</p><p>C4. Articulate and defend decisions not to use AI, using evidence, service context, and ethical reasoning.</p><h4><strong>D. AI to expand multidisciplinary capabilities</strong></h4><p><em>This theme explores how service designers can use AI to expand their capabilities. This could be using AI to compliment or enhance an existing skill or using AI in place of having certain skills. It emphasises informed use, critical judgement, and knowing where AI-supported work must stop or be validated by specialists.</em></p><p>D1. Can use AI appropriately in early-phase or low-risk contexts, to complete tasks that traditionally sit with other professions in multidisciplinary teams.</p><p>D2. Can use AI appropriately to translate sketches, journeys, and user flows into working prototypes.</p><p>D3. Explain the benefits and limitations of prototypes, ensuring prototypes are not mistaken for production-ready solutions.</p><p>D4. Assess the quality and limitations of AI-generated outputs, identifying where human review, iteration, or specialist input is required.</p><p>D5. Apply clear boundaries to avoid overstepping into sensitive or high-risk professional domains, focusing on effective partnership working.</p><h4><strong>E. Skills AI is unlikely to replace</strong></h4><p><em>This theme reinforces the uniquely human skills that remain central to high-quality service design, particularly in complex, sensitive, and high-stakes contexts. It focuses on relational, facilitative, and judgement-based capabilities where human presence, trust, and contextual understanding are essential, and where AI can offer limited support but not meaningful replacement. </em><strong><em>Each topic in this section is a high-level starting point only. It is not expected that all service designers should become experts in every section below.</em></strong></p><p><strong>E1. In-person facilitation and collaborative design<br></strong>E1A. Plan and facilitate in-person workshops that respond in real time to group dynamics, power imbalances, and emotional cues.</p><p>E1B. Create psychologically safe spaces for collaboration, particularly in sensitive justice or public service contexts.</p><p><strong>E2. Sense-making, judgement, and interpretation<br></strong>E2A. Synthesize complex, messy, or conflicting inputs into coherent service narratives using professional judgement.</p><p>E2B. Recognise when AI-generated insights lack context, nuance or lived experience and intervene to correct or reframe them.</p><p><strong>E3. Ethics and responsibility<br></strong>E3A. Hold accountability for design decisions affecting users, staff, and the public, rather than deferring responsibility to AI outputs.</p><p>E3B. Model responsible behaviour in multidisciplinary teams by setting clear expectations about human oversight and challenging inappropriate or harmful uses of AI.</p><p><strong>E4. Relationship-building and influence<br></strong>E4A. Build trust with users, colleagues, and stakeholders through presence, listening, and credibility.</p><p>E4B. Influence decision-makers through storytelling, facilitation, and persuasion grounded in human impact.</p><p><strong>E5. Agile Delivery<br></strong>E5A. Operate effectively within agile delivery environments, using judgement rather than rigid process to respond to uncertainty and change.</p><p>E5B. Balance user needs, delivery constraints, and organisational priorities through ongoing negotiation and trade-offs.</p><p><strong>E6. Design leadership<br></strong>E6A. Provide clear design direction and decision making in ambiguous or contested spaces, where values, evidence, and stakeholder perspectives may conflict.</p><p>E6B. Coach and support other designers, using empathy, experience, and situational awareness.</p><p>E6C. Set and uphold design quality standards, intervening when AI-accelerated outputs risk lowering rigour or coherence.</p><p>E6D. Model responsible AI use, shaping team norms and expectations through behaviour, not just guidance.</p><p><strong>E7. Strategy and long-term thinking<br></strong>E7A. Frame service design work strategically, connecting day-to-day decisions to long-term organisational and societal outcomes.</p><p>E7B. Anticipate second- and third-order impacts of design and technology choices that AI cannot reliably predict.</p><p>E7C. Integrate political, ethical, and human considerations into strategic design thinking.</p><p><strong>E8. Commercial awareness and supplier engagement<br></strong>E8A. Apply commercial judgement when working with suppliers, recognising incentives, constraints, and risk transfer.</p><p>E8B. Assess AI-related supplier claims critically, identifying over-promising, hidden dependencies, or misaligned incentives.</p><p><strong>E9. Working with Data Science<br></strong>E9A. Collaborate effectively with data scientists and analysts, clearly framing service problems, asking informed questions, and interpreting analytical outputs with appropriate caution.</p><p>E9B. Balance quantitative evidence with qualitative insight, avoiding false confidence or over-reliance on data in decision-making.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd0c19ef2972" width="1" height="1" alt="">]]></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-79a914e48bc1------2</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 11:05:09 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[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-79a914e48bc1------2</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>Mon, 28 Jul 2025 16:25:40 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-79a914e48bc1------2</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>Wed, 19 Mar 2025 09:58:58 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[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-79a914e48bc1------2</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>Mon, 16 Sep 2024 16:30:13 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[Service Patterns: Part 1 - History, Opportunity and Challenges]]></title>
            <link>https://medium.com/share-reuse/service-patterns-part-1-history-opportunity-and-challenges-bfd3989a845a?source=rss-79a914e48bc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd3989a845a</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[service-patterns]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Martin Ford-Downes]]></dc:creator>
            <pubDate>Fri, 30 Aug 2024 14:57:42 GMT</pubDate>
            <atom:updated>2025-03-20T15:18:19.641Z</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><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>Service Patterns at the Ministry of Justice</h3><p>Over the last 12 months, myself and other designers at the Ministry of Justice have been investigating Service Patterns as a tool to create consistent high quality user experiences across our different services. This short series of blogs will take you through our work to date and our plans for the future. Part 1 will look at our research into the history of Service Patterns, the opportunity they present, and some of the challenges we’ve encountered.</p><h3>What are Service Patterns?</h3><p>If you work in or near digital design you are probably familiar with the idea of design systems that contain reusable components and patterns. These are typically used by Interaction Designers to create consistent digital experiences, specifying anything from the design of a button, a date picker, or multi-page experiences for things like signing into an account.</p><p>Service Patterns take this a step further by considering complete user tasks, or the stages of a service, that get built repeatedly across organisations — for example the ability to ‘apply for something’ or ‘book an appointment’. A library of Service Patterns would act as design guides to build these capabilities in repeatable and consistent ways across multiple services. The library entries would deal with what that task means as a digital service, but they would also include consideration of non-digital channels and touchpoints, and their relationship with other tasks, to help you build a complete end-to-end service.</p><h3>History and Opportunity</h3><p>The idea of Service Patterns has been floating around UK public sector design for about 10 years. If you’ve ever gone looking for information on the topic, you’ve probably found the same blogs as we have — e.g. <a href="https://gds.blog.gov.uk/2016/02/29/lets-talk-about-service-patterns/">this one</a> by Lou Downe from 2016 introducing the topic, <a href="https://designnotes.blog.gov.uk/2018/05/17/10-principles-for-service-patterns/">this one</a> from 2018 that takes it a little further, or <a href="https://www.tpximpact.com/knowledge-hub/blogs/design/service-patterns-strategic-approach-digital-transformation/">this more recent one</a> from TPXImpact who worked with the Department of Work and Pensions (DWP).</p><p>As an approach, especially for Service Designers, it seems incredibly appealing. They are a route to creating consistent user experiences, based on tested designs, that act as a solid foundation to your service. They free up design time to focus on the elements of the service that are new or unique or interesting, instead of designing from scratch the same elements over and over again. It intuitively makes sense to Service Designers how and why this could be a powerful approach to designing better services.</p><p>From our research there are a number of organisations that have successfully defined a framework for their Service Patterns, identifying the categories and names of the patterns they would require to describe the services they provide. Some have also been able to catalogue their existing services using that framework — for example <a href="https://patterns.wearefuturegov.com/">at Essex County Council</a>. Some are making links to the work by Kate Tarling on how we should <a href="https://katetarling.com/2018/08/09/a-common-language-to-understand-services/">define and organise our services</a>. At the Ministry of Justice, we’ve also defined the potential service patterns we would like to pursue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UIh7e_x2rtw8d5Ub" /><figcaption><em>A draft of our service patterns titles and categories at the Ministry of Justice.</em></figcaption></figure><h3>The Challenges</h3><p>There is a problem however — in our research we have struggled to find examples of organisations that have a) built out the detailed guidance that would sit under each potential service pattern and b) successfully used service patterns to build better services. We are hopeful that there are examples out there we just haven’t found yet (please do get in touch if that is you!), but this challenge has forced us to consider whether Service Patterns are likely to be a practical approach that delivers meaningful benefits. There are other questions to answer too, such as what is the difference between a pattern in a typical design system, and a service pattern as we’ve defined it here? We’re also considering whether service patterns as an abstract concept is the right approach, or whether they need to be more closely aligned to repeatable products, representing a complete vertical stack of design and code for a given function.</p><h3>Our Approach</h3><p>Part 2 of this blog series will share more details on our approach, but for now here is a summary:</p><p>Within the Ministry of Justice we started with a ‘bottom up’ approach, looking at our existing services, and asking the responsible teams to describe in their own words what common actions and tasks are completed by users of those services. From there we identified roughly 30 potential patterns covering things like applying for things and booking appointments (see the image above for the rest). We’ve experimented with taking existing services and retrospectively converting them into service patterns, and with building service patterns in parallel with the development of new services. Both approaches have had challenges — it’s been difficult to reverse engineer completed services into easy-to-use repeatable guidelines, and it’s been difficult to identify a new service at the right stage of the development lifecycle to build a new pattern in parallel. We are continuing to experiment with approaches and hope to make more progress soon.</p><p>We’ve also been collaborating with colleagues in other UK Government departments, in particular with Lindsey Stephens from DWP, to prototype a potential cross-government service pattern for ‘apply’. Lindsey and the team at DWP have done some great work on defining their own service patterns, and crucially, have managed to fully define the guidance that would form one of their own service patterns. Along with colleagues from the Department for Education, DEFRA, HMRC, and the Home Office, we have used DWP’s work as a starting point to create a prototype service pattern that could be used across all government departments. We hope to share that prototype for feedback soon.</p><h3>Next Steps</h3><p><a href="https://medium.com/@martin.ford-downes/service-patterns-part-2-developing-our-own-service-patterns-228355f8bb27">Part 2</a> looks at what we’ve been doing in more detail. In the meantime, if you’d like to talk more about this topic, please get in touch via <a href="/service/mailto:martin.ford-downes@digital.justice.gov.uk">email</a>, <a href="https://www.linkedin.com/in/martin-ford-downes/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd3989a845a" width="1" height="1" alt=""><hr><p><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> 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>