<?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 Caroline Finucane on Medium]]></title>
        <description><![CDATA[Stories by Caroline Finucane on Medium]]></description>
        <link>https://medium.com/@carolinefinucane?source=rss-fad4a932721e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EYjF8UEEm4KDil9a95FsKA.jpeg</url>
            <title>Stories by Caroline Finucane on Medium</title>
            <link>https://medium.com/@carolinefinucane?source=rss-fad4a932721e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:33:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carolinefinucane/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[How we responded to the COVID-19 booster confusion]]></title>
            <link>https://medium.com/@carolinefinucane/how-we-responded-to-the-covid-19-booster-confusion-a77ad3cae4f7?source=rss-fad4a932721e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a77ad3cae4f7</guid>
            <dc:creator><![CDATA[Caroline Finucane]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 00:00:30 GMT</pubDate>
            <atom:updated>2025-10-29T06:33:06.728Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>This autumn, as the COVID-19 vaccination programme launched, our digital services team needed to move quickly to respond to confusion around eligibility.</strong></p><p>Many patients turned up at pharmacies expecting to receive a booster, but had to be turned away.</p><p>We needed to act fast to help reduce pressure on community pharmacies and offer clarity for patients.</p><p>Many of the ineligible people coming forward had likely come through our own booking service, which is intentionally designed to let people self-refer if they believe they are eligible.</p><h3>Why this confusion happened</h3><p>This year, the Joint Committee on Vaccination and Immunisation (JCVI) changed eligibility rules for COVID-19 boosters.</p><p>The age threshold rose from <strong>65 to 75</strong>, meaning many people who had qualified last year were no longer eligible.</p><p><a href="https://www.nhs.uk/vaccinations/covid-19-vaccine/">NHS England published guidance on NHS.UK</a> and GOV.UK, but the shift caught many off guard. Here’s what some users told us in the booking exit survey (1 Sept to 5 October):</p><blockquote><em>I do not understand why I do not qualify too, especially as I am 67</em></blockquote><blockquote><em>If something has changed, it would be kind to inform people that they are no longer at significant risk</em></blockquote><h3>What we did</h3><p>We — Vaccination Digital Services — acted quickly to support patients and pharmacy teams, by:</p><ul><li><strong>sending targeted follow-up messages</strong> to around 250,000 people under 75 with upcoming bookings, explaining the updated eligibility rules and setting expectations</li><li><strong>updating confirmation messages</strong> in the booking service to reinforce the change</li><li><strong>working with Community Pharmacy England</strong> to create <a href="https://cpe.org.uk/our-news/c-19-vac-eligibility-resources-to-help-pharmacy-teams/">resources to help pharmacy teams</a></li><li><strong>adding a warning to the</strong> <a href="https://www.nhs.uk/nhs-services/vaccination-and-booking-services/book-flu-vaccination/">flu booking start page</a>, reminding users to check COVID-19 eligibility before booking</li><li><strong>updating national invitations</strong> to make the change in eligibility clearer</li></ul><p>Mindful of the frustration people were feeling, we wanted the tone of our email to reflect that. It was a slight shift from our <a href="https://service-manual.nhs.uk/content/voice-and-tone">usual voice</a> — more empathetic, more human — and it felt right for the moment: <em>We understand this might be confusing, especially if you had the vaccine last year.</em></p><figure><img alt="The follow-up messages we sent, to set expectations" src="https://cdn-images-1.medium.com/max/469/0*eDdAqLYZ7y7bc_1O.png" /><figcaption>The follow-up messages we sent, to set expectations</figcaption></figure><figure><img alt="Our warning on the flu booking start page" src="https://cdn-images-1.medium.com/max/624/0*4rbnvt2zEE4U7brP.png" /><figcaption>Our warning on the flu booking start page</figcaption></figure><h3>What we know</h3><h4>Many people go straight for the green button</h4><p>While the COVID-19 vaccination booking service automatically screens out users who are not eligible by age, the <a href="https://www.nhs.uk/nhs-services/vaccination-and-booking-services/book-flu-vaccination/">flu vaccination booking service</a> allows users to <strong>self-refer</strong> for a COVID-19 booster if they believe they meet the criteria.</p><p>This is needed because many people want the convenience of arranging both vaccinations in one go — ideally to have at the same appointment. We need to make that process as smooth as possible for those who are eligible.</p><p>We made the criteria as clear as possible, using a prominent yellow <a href="https://service-manual.nhs.uk/design-system/components/warning-callout">warning callout</a>. But it’s possible many people simply didn’t read this or understand it, or just clicked through anyway.</p><blockquote><em>“No proper information on eligibility. Just a yes/no question”</em></blockquote><blockquote><em>“I wanted to see more detail on eligibility criteria”</em></blockquote><p>We’re waiting for more data to back this assumption — but this is something researchers see time and again: users skip the content and head straight for the green button — and designers always have to plan for it.</p><figure><img alt="Screen from our flu booking service, asking users if they’d also like a COVID-19 vaccine. We think many ineligible people clicked through." src="https://cdn-images-1.medium.com/max/400/0*yQ9smi-TsOwFr_eO.png" /><figcaption>Our flu booking service asks users if they’d also like a COVID-19 vaccine. We think many ineligible people clicked through.</figcaption></figure><p><a href="https://digital.nhs.uk/blog/design-matters/2022/covid-19-testing-tackling-eligibility">We saw this pattern in the COVID testing service too</a>: once users are familiar with a digital service and have seen an interruption screen before, they’re more likely to ignore it, even if content has changed. They assume they’ve read it before.</p><h4>‘Immunosuppressed’ is a grey area</h4><p>But it’s likely the confusion wasn’t <em>just</em> about age.</p><p>Every season, it seems that some patients self-refer believing they have a weakened immune system that qualifies them for the jab — but in fact they do not, or no longer, meet the criteria. For example, someone who recently came off treatment might not realise they’re no longer eligible.</p><blockquote><em>“I’m asthmatic. Got to the time section. Got thrown off. Filled out details and said not eligible. I’ve had it every year for as long as I remember.”</em></blockquote><blockquote><em>“I have to rank as very [disappointed] as I find I am not eligible despite a number of health conditions including cardiac, respiratory and diabetes.”</em></blockquote><blockquote><em>“Incomplete list of immune conditions left me uncertain as to whether I am eligible or not”</em></blockquote><p>It’s always a challenge to help people determine whether they have a <a href="https://www.nhs.uk/vaccinations/covid-19-vaccine/">weakened immune system because of a health condition or treatment</a>, because this is ultimately determined by a clinician. We can’t publish a definitive list for people to check against.</p><h3>What we’ve learned — and what we’ll do next time</h3><p>But let’s focus on what we can do.</p><p>Now we know: <strong>when eligibility rules change, clarity matters more than ever.</strong></p><p>We’ve learned that:</p><ul><li>people often don’t read content, especially if they’ve seen similar screens before</li><li>even well-placed messaging can be missed or misunderstood</li><li>many people don’t know if they qualify for an NHS vaccination</li></ul><p>And next time, we will:</p><ul><li><strong>make it clear that things have <em>changed</em></strong>, not just what the new rules are</li><li><strong>personalise communications</strong> where possible (e.g. “Because you’re under 75…”)</li><li><strong>align national messaging and digital services</strong> more closely to set expectations</li></ul><p>These lessons will shape how we communicate eligibility in future campaigns, and in the upcoming <a href="https://www.service-catalogue.nhs.uk/services/check-my-vaccination-record">Check and book an RSV vaccination service</a> in the NHS App, currently in alpha.</p><p>We’re constantly learning and improving how we design digital services. As we work to increase uptake of seasonal vaccinations, we also have a responsibility to support those who are no longer eligible — with clear, compassionate communication that helps everyone understand where they stand.</p><p><em>Originally published at </em><a href="https://design-history.prevention-services.nhs.uk/vaccinations/2025/10/how-we-responded-to-the-covid-19-booster-confusion/"><em>https://design-history.prevention-services.nhs.uk</em></a><em> on October 23, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a77ad3cae4f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[COVID-19 testing: 5 things I’ve learnt as content lead]]></title>
            <link>https://medium.com/@carolinefinucane/covid-19-testing-5-things-ive-learnt-as-content-lead-3b129529fe5d?source=rss-fad4a932721e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b129529fe5d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[covid-19-testing]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Caroline Finucane]]></dc:creator>
            <pubDate>Fri, 16 May 2025 08:31:43 GMT</pubDate>
            <atom:updated>2025-05-16T08:37:39.200Z</atom:updated>
            <content:encoded><![CDATA[<p>Date: 20 July 2021</p><p><strong>Over the last 16 months of managing the digital content for the COVID-19 testing programme I have learnt much about how complex, high-priority UK-wide projects are run.</strong></p><p><strong>I’m sharing what I’ve taken away as these principles will be helpful for anyone working on a UK-wide government digital service, even if COVID-19 has brought unprecedented challenges.</strong></p><h3>1. Involve the content team early</h3><p>This may seem obvious, but when the testing programme started, content designers were only aware of new programme requirements when the solution had already been decided and half signed off.</p><p>It didn’t help that services needed to be created at speed and we had all been thrown together with little understanding of each other’s ways of working.</p><p>Six months on, when we were working in a more user centred way and resourced with a team of excellent product managers, things were much better. I was invited to initial discussions when new requirements came in, which meant the content team could have a say in suggestions worth exploring, and those to rule out based on insight we had so far.</p><p>But this early involvement did not happen every time. Even a year on, we are still sometimes asked to approve pre-written copy sent to us at the very last minute.</p><p>It’s awkward asking everyone to rewind so we can design a solution based around user needs, rather than what stakeholders feel we need to convey. It’s frustrating also to the delivery lead who thought we were almost there, and the team who got us to this point, whose work we might not be able to take forward.</p><p>Content leads can be proactive in ensuring this situation does not happen. When you’re first starting on a project, identify who all the project leads are and make sure you’re on the invite list for all the key meetings.</p><h3>2. Beware of content as the ‘quick fix’</h3><p>There were some tricky times when the content team was consulted within hours of an ‘urgent incident’ so we could resolve it that same day. We were never missed off those invites!</p><p>I remember one time in May 2020, when the launch of the NHS COVID-19 contact tracing app was suddenly delayed. We had 2 screens in the registration service for testing that asked the user if they had this app, and if so, asked them to enter their app reference code. These screens were now not appropriate, given the app was not yet available, but could not be removed at such short notice.</p><blockquote>We should at least log design debt and have ringfenced time to systematically address it. This way, we avoid hotfixes bedding in and we do not scale up inadequate solutions.</blockquote><p>I was asked to approve the only feasible solution: a screen that instructed the user who had selected ‘Yes, I have the app’, to go back and select ‘No I do not have the app’ to be able to go forward again. This oddity would not exist for long, but I was concerned that ‘copy changes only’ might set a precedent for resolving issues in what was perceived to be the most efficient way.</p><p>Sometimes a content hotfix was needed as a sticking-plaster until we could deploy something better. But I wondered if, with the constant deluge of new requirements, we’d end up never revisiting that content. Also, because of all the new business priorities, a new design proposal to improve the front-end service might never get a look in.</p><p>We should at least log design debt and have ringfenced time to systematically address it. This way, we avoid hotfixes bedding in and we do not scale up inadequate solutions.</p><h3>3. Put in place a senior-level content lead</h3><p>It worked well to have a team of user-centred design (UCD) leads who met regularly. The team comprised people who headed up interaction design, service design, user research and content.</p><p>I wondered why content was not always represented at this senior level on other programmes. Here’s why it needs to be:</p><p>We (the UCD leadership team) have been collectively devising a strategy to ultimately improve the experience for users of the COVID-19 testing journeys.</p><p>One problem has been that too many people try to use the ‘get a PCR test’ service (mainly for people with symptoms) when they actually need a rapid test (for people with no symptoms). Users do not understand the difference between the 2 test types and they don’t know where to go.</p><p>A content lead’s input has been key to resolving this — not just to work on signposting and wording to explain the tests, but to get agreement and alignment across comms, marketing, and the various other teams and publishers on how we refer to them.</p><blockquote>Let’s recognise the need for a content lead at a senior level. Programmes need more than just a talented wordsmith in charge of approving content.</blockquote><p>It’s also about contributing more generally as a user-centred designer, to solve broader pain points like ‘digital journeys are too long and repetitive’. This might involve, for example, testing a new design pattern that shows the user how far they are into the journey or lobbying for developer time to improve these existing issues.</p><p>The person in this role, just like other UCD leads, would be thinking outside their ‘content design’ box and using their initiative to collaborate with other specialists and senior stakeholders to drive forward big-impact improvements. Being across all the content means they’re well placed to do this — they have that high level understanding of all the services.</p><p>Let’s recognise the need for a content lead at a senior level. Programmes need more than just a talented wordsmith in charge of approving content.</p><h3>4. Co-ordinate across organisations</h3><p>You can imagine how many different government sites and tools publish content on COVID-19. With all the new requirements flooding in every week, it was hard to stay joined up.</p><p>A new testing policy would be communicated to the COVID-19 testing team, and we’d go at top speed to update all the content in the online services — for example, when self-isolation changed from 14 days to 10 days. But the other impacted organisations were sometimes forgotten about until the last hour.</p><p>By the time the request trickled through to, say, NHS.UK or GOV.UK, they did not always have the resource to make major changes at such short notice.</p><p>If you know what’s coming up, you can plan for it and deprioritise to free up resource if necessary. This is impossible to do if you’re not sighted on the roadmap or business priorities, or given a heads up as soon as the requirement comes in.</p><p>On a complex project like COVID-19 testing, there’s a need for a central person who can:</p><ul><li>impact assess across all government websites when a new requirement comes in</li><li>engage with all parties</li><li>coordinate the solution and timing of all the updates (“press publish when our release goes live”)</li></ul><p>Ultimately, there should be someone who ensures we have content alignment across organisations at any one time.</p><h3>5. Consider from the start how we build and manage a UK-wide service</h3><p>Designing a UK-wide service can be incredibly complicated. It needs to meet all the varying requirements of the devolved nations without coming across as ‘England led’.</p><p>However, it’s hard explaining to our service users that the policy or process is different if you live in, say, Northern Ireland. It can also be difficult to meet the wording preferences of the country representatives, and consulting with them or keeping them in the loop with every change.</p><p>It requires a team of highly organised people with diplomacy and patience. It’s also an important consideration for UCD. Content should be relevant to users and personalised whenever possible. For example, we might need to direct Scotland residents to GOV.SCOT , or (who knows) allow them to switch to Scotland-specific content at the toggle of a button.</p><p>But when we do not have a content management system (CMS) and are dependent on releases, we also have to be realistic. Creating a whole Scotland-specific branch of the test booking journey, for instance, would probably not be feasible as it would be too many screens to maintain. If we were to create a dynamic screen that’s different depending on whether it’s England or Scotland it might be 2 variables too many when we already have 6 different versions to accommodate.</p><p>Yet ‘catch-all’ content can be baffling for users. Check out this brainteaser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*MTg5MpO4GZq34FMQ7MQydg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b129529fe5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[COVID-19 testing: tackling eligibility]]></title>
            <link>https://medium.com/@carolinefinucane/covid-19-testing-tackling-eligibility-453d2636055c?source=rss-fad4a932721e------2</link>
            <guid isPermaLink="false">https://medium.com/p/453d2636055c</guid>
            <category><![CDATA[covid-19-testing]]></category>
            <category><![CDATA[eligibility-criteria]]></category>
            <dc:creator><![CDATA[Caroline Finucane]]></dc:creator>
            <pubDate>Fri, 16 May 2025 08:21:29 GMT</pubDate>
            <atom:updated>2025-05-16T08:36:54.177Z</atom:updated>
            <content:encoded><![CDATA[<p>Date: 5 October 2022</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m57mNfZgDSc3V2547fO-vw.jpeg" /></figure><p><strong>At the start of the COVID-19 pandemic, free coronavirus tests were only for key workers so they could continue their critical work. But eligibility for tests would soon change as infection rates started to spike.</strong></p><p><strong>We were ready for the first surge, which came in October 2020. The government swiftly kickstarted the expansion of testing with rapid lateral flow tests. We wanted everyone to ‘Get a free NHS COVID-19 test’.</strong></p><p>But by 1 April 2022, free testing for the general public ended as part of the government’s <a href="https://www.gov.uk/government/news/government-sets-out-next-steps-for-living-with-covid">Living with COVID plan</a>. When this happened, my team faced the challenge of adapting the <a href="https://www.gov.uk/order-coronavirus-rapid-lateral-flow-tests">online ordering service</a> to provide tests only to those who qualified, and to inform users early on in their journey if they were not eligible. Here, I outline the challenges we faced controlling access to tests, and share our solutions.</p><h3>Challenge 1: Simplifying a complex issue</h3><p>The changing eligibility criteria kept us on our toes, but what really challenged us were these 2 things:</p><ul><li><strong>the rules were different </strong>based on where in the UK you lived</li><li><strong>eligibility was self-determined</strong>, and our description of eligible groups could sometimes be misinterpreted; for example, volunteers who were not eligible may have described themselves as NHS workers</li></ul><p>When people visited GOV.UK to request a rapid lateral flow test, they typically did not know the complex eligibility criteria and wanted to know straight away if they qualified. Yet we know from experience that most users will not read lots of information on the start page — they go straight for the green button.</p><blockquote>It’s much easier for people to answer simple questions than try to understand complex eligibility information.</blockquote><p>The GOV.UK solution is asking questions within the service to determine if the user is eligible. It’s much easier for people to answer simple questions than try to understand complex eligibility information.</p><p>But if a user invests time answering questions only to discover at the end they can’t have a test, it can cause frustration and anger.</p><p>Therefore, to manage expectations, we used a ‘gate page’ early in the user journey. This is an alert that interrupts the user flow with important information — in our case, informing the user who is eligible for a test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ajIieKzG4JeJYijTNY8Cg.jpeg" /><figcaption>The gate page gives information about who is eligible for a COVID-19 test</figcaption></figure><p>This type of alert grabs attention after the start page because it looks different and is unexpected. And at around 325 characters, it’s easy to read and understand.</p><p>Testing showed it worked: most people understood who was eligible before they clicked ‘continue’. Then the rules changed.</p><h3>Challenge 2: Conveying that eligibility has changed</h3><p>We found that people only read the interruption screen once. The next time they used the service, they’d skip past the updated screen without reading it; “I’ve read this before”.</p><p>So how, in future, would we convey that eligibility had just changed?</p><p>Changing the H1 heading to state that ‘The rules have changed’ did grab attention, although it would only work until the rules changed again.</p><p>And regardless of this, there would always be some ineligible people who, for whatever reason, would plough ahead.</p><h3>Challenge 3: Telling people they are not eligible</h3><p>The testing service was often used by vulnerable or ill people, and simply ending the journey on an exit page with the standard message ‘you are not eligible based on the answers you gave’ without any further information could cause anger or anxiety.</p><p>That’s why we had to consider the user beyond the end of their digital journey. We offered guidance on what they could do next if they were worried or had symptoms, providing them with links for further help</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*XmKIgZOG5-nMpjz_jfgYCA.jpeg" /><figcaption>Further guidance is given if users are not eligible</figcaption></figure><h3>Challenge 4: Verifying people who are eligible</h3><p>Another challenge we faced is that users who were determined to order a free test could backtrack and answer differently.</p><p>Our solution was to add more questions so that people had to verify the information they had given. So, for example, if someone answers that they need a test because they work for the NHS, they must specify their area of work and their job title.</p><p>There are understandable concerns about adding these extra questions to an already long journey. But for policy teams, it had the desired effect: the number of completed journeys, and traffic, dropped sharply after we deployed it. Tests were no longer needed for most people, because it was now time to live with coronavirus.</p><h3>Conclusion</h3><p>After many iterations, we had a system that was working well. Only a small number of ineligible people were qualifying for tests. We could find a better way to do this, but it would come at a price.</p><p>Validation technology, for example, is technically tricky to deliver. And asking busy, reluctant GPs to order tests on behalf of patients they deemed eligible wasn’t the answer.</p><p>Another argument for a self-determined eligibility system is that users are largely honest. Experience tells us that many people who end up end up in the wrong place in the journey misinterpret the question rather than knowingly lie.</p><blockquote>We cannot soften the coronavirus testing policy, but we can make some pragmatic allowances.</blockquote><p>Also, many ineligible people who get through have an understandable motive. Perhaps they had a health condition ‘not on the list’ and pretended it was, because they were worried and thought they’d been forgotten. Or they did not want to be unknowingly infected while visiting their elderly relative, so they pretended they were in the NHS cohort.</p><p>We cannot soften the coronavirus testing policy, but we can make some pragmatic allowances because any system that controls eligibility will never be 100% accurate.</p><p>The system meant that eligible people could get free lateral flow tests without too much difficulty, while the number of ineligible people getting through was at an acceptably low level.</p><p>It was a balance, and we got the balance about right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=453d2636055c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking siloes with a service catalogue]]></title>
            <link>https://medium.com/@carolinefinucane/breaking-siloes-with-a-service-catalogue-515b41332c9a?source=rss-fad4a932721e------2</link>
            <guid isPermaLink="false">https://medium.com/p/515b41332c9a</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[service-catalog]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[organisational-design]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Caroline Finucane]]></dc:creator>
            <pubDate>Fri, 16 May 2025 05:05:44 GMT</pubDate>
            <atom:updated>2025-05-16T13:24:09.585Z</atom:updated>
            <content:encoded><![CDATA[<p>Date: 16 May 2025</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b01pQm5h7xvfHTuExOdFFQ.png" /></figure><p><strong>In the Digital Prevention Services Portfolio, we’ve created a catalogue of our products and digital services, to help us tackle the problem of siloed working. Siloes are inevitable in any large organisation, the NHS included. The trick is to accept that and come up with tactics for dealing with it.</strong></p><p>The need for this became clear when we surveyed teams working on digital vaccination services about the challenges of meeting the <a href="https://service-manual.nhs.uk/standards-and-technology/service-standard">NHS Service Standard</a> principles. Many people pointed out problems created by siloes, saying things like:</p><p><em>“Being able to collaborate with other teams isn’t easy…”</em></p><p><em>“[We have] difficulties collaborating across teams, departments, operational and portfolio areas.”</em></p><p><em>“[It’s] hard to know who to contact across the wider NHS England.”</em></p><p>These comments made us ask:</p><ul><li><strong>How can we make this easier?</strong></li><li><strong>How can we help colleagues learn where each team sits</strong>, how all the different teams relate to each other and what they’re all working on?</li></ul><h3>A catalogue of services and products</h3><p>That’s why we’ve built a <a href="https://www.service-catalogue.nhs.uk/">catalogue of our digital services and products</a>. This includes all the teams who are making contributions to digital prevention services — regardless of where they sit on the official organisational chart.</p><p>You can see where they are in the organisation, by selecting the “By organisation” tab at the top of the page. You can also browse by status, including discovery, alpha, beta, live, and retired, by platform, by theme and (my favourite) by users.</p><p>The concept is nothing new. <a href="https://digital.nhs.uk/services/service-catalogue">NHS England has a Service catalogue</a>, for external stakeholders, which has useful detail about our technical enablers. With our catalogue, it is designed to meet specific internal needs and helps everyone understand who owns what.</p><p>The catalogue has a single entry for each product or digital service and from there we can add useful links. This includes Slack channels, URLs of prototypes or live start pages, entries from our <a href="https://design-history.prevention-services.nhs.uk/">NHS Digital prevention services design history</a> website and more. The catalogue groups entries in different ways, such as by theme, to show relationships or commonalities, which is essential for collaboration. For example, it can show similar digital enablers or teams working towards the same outcome.</p><p>This version of the catalogue doesn’t yet do things that will take longer to work out. It doesn’t list whole services like “Get a COVID-19 vaccination” because these services are built by many teams across different areas, making ownership complicated. But we think it will be achievable to catalogue these services in a future version.</p><h3>Silo-busting features</h3><p>This catalogue is designed to help teams and leads to:</p><ul><li><strong>clearly articulate their scope</strong> and identify who else they need to work with</li><li><strong>self-organise</strong> to design across organisational boundaries</li><li><strong>discover related services</strong> and <strong>dependencies</strong></li><li><strong>share and reuse </strong><a href="https://service-manual.nhs.uk/design-system/patterns"><strong>design patterns</strong></a> to avoid duplication and unnecessary variation</li><li><strong>understand the wider context</strong></li><li><strong>spot duplication and gaps</strong></li></ul><p>Looking ahead, the potential is huge: what if we could show success metrics? What if we could map entries to needs and show the size and scale of each service?</p><h3>Help us improve</h3><p>This catalogue is a first version and we want to iterate and improve. A small team worked on this, including our colleague <a href="https://vickyteinaki.muchloved.com/">Vicky Teinaki</a>, who died earlier this year.</p><p>Her thoughtfulness and dedication to collaboration inspired all of us. Vicky’s contributions exemplified the very spirit of this project, and her impact will continue to be felt in this work and beyond.</p><p>If you’ve got feedback about the service catalogue beta, the simplest way to send it is by email, to me, at <a href="/service/mailto:caroline.finucane@nhs.net">caroline.finucane@nhs.net</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=515b41332c9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>