<?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 Richard Payne on Medium]]></title>
        <description><![CDATA[Stories by Richard Payne on Medium]]></description>
        <link>https://medium.com/@theboypayne?source=rss-9d0bed36ebc0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HuQSgOn0ukzd09cDdZSx7A.jpeg</url>
            <title>Stories by Richard Payne on Medium</title>
            <link>https://medium.com/@theboypayne?source=rss-9d0bed36ebc0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:14:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@theboypayne/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[Integrating NHS Digital’s new Design System into NHS Jobs Beta]]></title>
            <link>https://medium.com/@theboypayne/integrating-nhs-digitals-new-design-system-into-nhs-jobs-beta-aa7ada10522?source=rss-9d0bed36ebc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa7ada10522</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[nhs]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[nhs-job]]></category>
            <dc:creator><![CDATA[Richard Payne]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 20:52:17 GMT</pubDate>
            <atom:updated>2019-06-10T08:59:19.393Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-gdRVYfoD2oH2BxhvY25dg.png" /><figcaption>The <a href="https://beta.nhs.uk/service-manual/">NHS Digital Service Manual</a></figcaption></figure><h4>So we all know the benefits to Research, Design and Development of an active and well-maintained Design System (especially across national Public Sector organisations).</h4><p>Well, not necessarily. For those new to the conversation, consider <a href="https://uxdesign.cc/design-systems-62f648c6dccf">starting here </a>— we all like to preach to the converted (or is that just me?!).</p><p>Where to start? Well, here on <a href="https://twitter.com/nhs_jobs">NHS Jobs</a> (part of <a href="https://twitter.com/NHSBSA">NHSBSA</a>) we decided to be one of the first services outside of NHS Digital to use their <a href="https://beta.nhs.uk/service-manual/">new design system</a>. A risky business you might think? Thankfully not! Let’s see why…</p><p>Firstly — some context. The design system being used previously at NHSBSA by the digital teams was a hybrid of <a href="https://design-system.service.gov.uk/">GOV.UK</a> and NHSBSA patterns and components, which caused challenges in terms of rapid prototyping, consistency and future-proofing.</p><p>We’d prototyped an Alpha MVP for NHS Jobs using this old design system, which had passed a GDS Assessment and so Beta development had started. <br>We wanted our Development team to migrate this Beta front-end over to the NHS Digital design system while our UX Designers also used it to create, test and iterate other areas of the service.</p><p><em>Confused? We were!</em></p><p>Thankfully, we’ve come up with a process to make the transition as smooth as possible. We’re still in the process of working through this, but I wanted to capture our progress now before this post gets too out of hand!</p><h4><strong>1. Brainstorming.</strong></h4><p>At <a href="https://twitter.com/nhs_jobs">NHS Jobs</a>, we like our brainstorming sessions to be lively, creative affairs — just like this (very!) loosely related music video from 1985 entitled <a href="https://www.youtube.com/watch?v=wsA7rdZelLc">(Design) System Addict.</a> Bleeding edge work, I think you’ll agree. <br>Anyway, back to 2019 (thankfully) — the brainstorming session between our Designers and User Researchers produced the following perceived benefits and process:<br>— <em>Consistency</em>: taking advantage of the benefits of a maintained design system with an active backlog and wide community of teams and organisations using and extending it; <br> —<em> Efficiency</em>: rapid prototyping for ideation, hypothesis driven user testing and further iteration. <br> — More effective and persuasive <em>stakeholder communication</em> — <a href="https://uxplanet.org/why-investing-in-ui-design-saves-costs-increases-revenue-and-retains-customers-c762b78c0526">subconsciously an audience trusts</a> a clean, well-designed user interface which means they’ll also be more likely to trust our team’s approach to solving a particular service challenge.<br> —<em> Scale</em>. Quicker development at scale during Beta because the <a href="https://beta.nhs.uk/service-manual/frontend-library">front-end build library</a> uses the same CSS classes as the <a href="https://beta.nhs.uk/service-manual/prototyping-tools">NHS Digital prototyping toolkit</a> we’re using during our design sprints. <br> — Potentially extending the components and patterns with the design system for our colleagues in the wider NHSBSA and NHS Digital communities.</p><h4>2. Involve wider team and stakeholders</h4><p>We also involved other stakeholders in this process to understand their needs, for example <a href="https://twitter.com/DeanVipond">Dean Vipond</a> at NHS Digital and our Front-end Developers working on the Beta production code for NHS Jobs. <br>With our Front-end Developers, we agreed the leanest and least confusing way of migrating elements such as html code and css classes over, out for pitfalls which could bloat the somewhat arduous task further.</p><h4><strong>3.</strong> Focus on grids, patterns and components</h4><p>We decided to use the NHS Digital design system to replicate <strong><em>only key pages </em></strong>of the existing build with layouts, patterns or components not yet featured in the pattern library. <br>This meant that developers would have access to <strong><em>every HTML and CSS component needed</em></strong> in order to migrate the front-end of the production code over to the new design system (regardless of whether this came as standard from the NHS Digital code, or from this own migration work). <br>For example, this job advert page from the Alpha MVP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ILXlBGjF1XhvWy2qC0KAFw.png" /><figcaption>‘Under the bonnet’ during migration work onto the NHS Digital digital system</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXcnM4ij-nfyM4c-c8wxvw.png" /><figcaption>The finished job advert on NHS Jobs Beta</figcaption></figure><h4><strong>4.</strong> Share the work and check our backlog</h4><p>The next stage is to feed our ‘candidates’ and testing findings back into the NHSBSA Digital design system (created with love, blood sweat and tears by our tireless Service Design Lead <a href="https://uk.linkedin.com/in/helen-spires-6b786854">Helen Spires</a>) backlog for discussion and potentially further testing. <br>The 3 stage process at NHSBSA for this is:<br> — Sharing the work. Talking about the pattern or component to the NHSBSA Design community is the best place to start, as other service teams might be working on the same thing. Gathering feedback and potentially other examples from this community is the most effective first step.<br> — Then checking the backlog (see screenshot below). If the pattern or component is already on the backlog, comment and post screenshots of the example.<br> — Raising a new issue. If the idea has been discussed and is not on the backlog, we raise an issue. It’s important to <em>provide context</em> by explaining why it should be included in our own design system — therefore we include screenshots and research notes.</p><h4><strong>5. </strong>Raise an issue on our own Design System backlog</h4><p>We add any unique components, or components (used in a context not yet considered by the pattern library) onto the NHSBSA design system backlog. <br>If a standard component (such as an NHS Jobs header) or a non-standard component, pattern or unique context is tested and approved, then an NHSBSA Front-end Developer will build our ‘quick and dirty’ prototype component with more elegant and secure code.<br>These may naturally includes elements from the GOV.UKdesign system such as the <a href="https://github.com/alphagov/govuk-design-system/wiki/Character-count-testing-and-user-research">character count component</a> which need to be modified (usually visually, less so functionally). <br><em>We‘re not reinventing the wheel</em> and duplicating the hard work already done on either the GOV.UK or NHS Digital Design systems. It’s about catering for the <a href="https://beta.nhs.uk/service-manual/design-principles"><em>task context</em></a> of NHS Jobs users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ii5ZM0aDh5-SlPQil3UMTQ.png" /><figcaption>The NHSBSA Design System backlog</figcaption></figure><h4><strong>6.</strong> Create some internal guidelines</h4><p>It’s become clear from this process that we need some brief internal guidelines and examples to help the NHS Jobs team maintain visual consistency. <br>For example, defining how to use different heading styles across different contexts — for example transactional tasks versus summaries of information — for the most efficient visual hierarchy. <br>This was needed because we found that using too many variants of the <a href="https://www.england.nhs.uk/nhsidentity/identity-guidelines/fonts/">core NHS font ‘Frutiger</a>’ increased <a href="https://www.nngroup.com/articles/minimize-cognitive-load/">cognitive load</a>, which is detrimental to users’ content comprehension and task completion rates.</p><h4>7. Contribute to the community</h4><p>Finally, we’re also working with our colleagues at NHS Digital to share and discuss any patterns/components/findings we’re working on. <br>They may decide to include some of our components and patterns within the NHS Design System for use across the NHS. Then in turn, some of these backlog items might then be added to the GOV.UK Working Group backlog for use across multiple Government organisations.<br>Therefore, we’re keen to solidify and improve the feedback loop between ourselves, NHS Digital and the GOV.UK Design System team.</p><h4>What’s next?</h4><p>No doubt the experienced reader has noticed that this article is more descriptive than analytical in nature. This is because we’re still in the early days of this process, and so I may write another piece covering lessons learnt.</p><p>For now, we’ll keep sharing the NHS Jobs team’s <a href="https://www.interaction-design.org/literature/topics/ui-design-patterns">common solutions to common problems</a> to this ever-growing community in order to to help other services create consistent, recognisable (and reassuring) designs which build at scale quickly while having the flexibity to meet their own public service-specific needs. Sounds like a win to me!</p><p>If you want to know more about Design Systems, here’s some reading— from lighter articles to ‘get down and dirty’ guides to building your own!</p><h3>Further Design System reading:</h3><h4>Lighter reads —</h4><p><a href="https://blog.prototypr.io/top-20-design-systems-7bf0963318ce">Top 20 Design Systems</a><br><a href="https://www.designsystems.com/">Design Systems</a> (by Figma)<br><a href="https://medium.com/oscar-tech/six-lessons-learned-by-creating-a-design-system-at-a-fast-moving-start-up-30ba8458fa20">Six lessons learned by creating a design system at a fast-moving start-up</a> <br><a href="https://medium.com/design-paperless-post/when-your-design-system-fails-f035041ad6d2">When your Design System fails</a></p><h4>In depth —</h4><p><a href="https://www.smashingmagazine.com/design-systems-book/">Design Systems</a> (a ‘Smashing’ book)<br><a href="https://shop.bradfrost.com/-">Atomic Design</a> (Brad Frost et al, based on <a href="https://patternlab.io/">https://patternlab.io/</a> principles)<br><a href="https://designsystemsrepo.com/books/">List of Design System Books</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa7ada10522" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hitting the ground running in your new UX job]]></title>
            <link>https://uxdesign.cc/hitting-the-ground-running-in-your-new-ux-job-d70846924b96?source=rss-9d0bed36ebc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d70846924b96</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[new-job]]></category>
            <category><![CDATA[nhs]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Richard Payne]]></dc:creator>
            <pubDate>Sun, 21 Apr 2019 13:11:39 GMT</pubDate>
            <atom:updated>2019-04-26T23:21:29.510Z</atom:updated>
            <content:encoded><![CDATA[<p>So, the first days of a new role are always a magical mystery tour of <a href="https://youtu.be/sezc05A4s2g">strange faces, places</a> and challenges (I managed to self-indulgently work a couple of classic musical references into that sentence!).</p><p>Having just finished my first 2 weeks on the NHS Jobs service’s Beta phase in Newcastle, I thought I’d share some reflections on how can we help others to help us during these early days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6s0VLqbK3zocLHraSSTG2A@2x.jpeg" /><figcaption>Our Collaboration Corner: If a post-it note falls in the forest, and nobody hears it, does it make a sound?</figcaption></figure><p>Here’s a few tips that come to mind:</p><ol><li><strong>Learn the jargon! </strong><br>First things first; Terminology, domain knowledge, abbreviations and acronyms. Always ask colleagues to clarify these. You’ll be doing this a lot during month 1!</li><li><strong>Ask <em>“Why?”.</em></strong><br>I know, it’s one of the <a href="https://uxdesign.cc/a-comprehensive-and-honest-list-of-ux-clich%C3%A9s-96e2a08fb2e9">many cliches about UX Designers</a> — but it’s definitely important! One of the most important mindsets we must have is inquisitiveness. Unashamedly ask questions – lots of them! If a colleague is taking you through a user journey on the wall, don’t allow it to become a monologue. <br>Asking ‘Why?’ about the flow, screens or elements of the Service Design will start to give context to your new challenge and perhaps also show where more thought is needed by the whole team if you hear vague or confused answers.</li><li><strong>Make a good first impression.</strong><em><br>“Tell us about yourself!” </em>For some of us, this is a <a href="https://www.youtube.com/watch?v=rPu_d4SSOPk&amp;feature=youtu.be&amp;t=124">truly horrifying moment</a> (and yes, I do personally dread it!). Such a simple request, and yet some of us find it really difficult to answer it in a natural and easy fashion. <br>So – I admit it – I mentally prepared a pre-rehearsed statement and ran through it in my mind a few times. I <em>think</em> the idea is to smile, and tell a few relevant facts about why you’re here and your experience to date without coming across as either a big shot or lacking in confidence!</li><li><strong>Control your own on-boarding.</strong><br>Manage your expectations here (especially if you’re a contractor)! A lot of project teams struggle with on-boarding team members effectively, especially when you’ve joined them in-flight. <br>Proactivity is the key. So don’t be afraid to ask <em>all</em> your colleagues (yes, including Lead Developers and Heads of Service) to spend a few hours with you to provide a plotted history of the project, with emphasis on each of their roles within this narrative. <br>I usually offer to so this with new starters when I’m a more experienced team member, and it provides all-important context. Trust me, it beats sitting by yourself digging through Google Drive looking at Discovery research documentation and old versions of prototypes! <br>For more, see <a href="https://www.hollidazed.co.uk/">Ben Holliday’s</a> excellent article about spending time to ‘<a href="http://www.hollidazed.co.uk/2015/07/28/frame-the-problem/">frame the problem’</a> – you need to do this for your own background knowledge so that you understand the intention and need driving the service. I’ve seen too many folks actually having to start sprint work without understanding the big picture, meaning they don’t know <em>why</em> an Agile story is needed — and of course their work suffers as a result.</li><li><strong>Get to know your users.</strong> <br>I wanted to do this, and quickly add value too, by making some Empathy Boards. They can be especially useful in the NHS <em>(…</em><a href="https://beta.nhs.uk/service-manual/design-principles"><em>take the time to learn about the whole person — their emotional, physical and technical needs”</em></a>) because we’re often designing for people with complicated needs and <a href="https://abookapart.com/products/design-for-real-life">stress cases</a> are quite common. <br>These added a new layer of data onto our existing personas by looking at the more psychological and behavioural aspects of our users. Having done this exercise, I found that I could tell a story about this user in a much clearer and more confident manner because I could conceptualise this board in my mind while doing so. I personally can’t do this from reading a Confluence page! <br>In terms of process, I imported <a href="https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a">this excellent template</a> by <a href="https://medium.com/@davegray">David Grey</a> into the <a href="https://miro.com/">Miro app</a> (formerly known as RealtimeBoard) and quickly added post-it notes of insights from the interviews onto the relevant segments. It now just remains for me to pin these boards on the wall of our Collaboration Corner, pictured above.</li><li><strong>Visualise the big picture to get the small details right</strong><br>We didn’t have any user flows for the more complex areas of the service which we’ll be designing next, so I used <a href="https://medium.com/@charlesrt">Charles Reynolds-Talbot’s</a> excellent <a href="https://medium.com/sketch-app-sources/designing-flows-with-gov-flow-749da31944ca">Sketch GOV.UK flow kit</a> to see where I could apply <a href="https://medium.com/@jonyablonski/designing-with-occams-razor-3692df2f3c7f">Occum’s razor</a> (constantly hypothesising and testing where efficiencies could be made, either in the page flow or interactions themselves) before further iteration work begins. <br>It also goes without saying that time invested here in <a href="https://medium.com/sketch-app-sources/user-journey-maps-or-user-flows-what-to-do-first-48e825e73aa8">visualising the user flows</a> pays dividends when it comes to prototyping, working with Developers and ultimately releasing the most efficient product possible. Have you ever held a team conversation where you’re trying to discuss a complicated process in the abstract without a visual reference? How did it go? I think I can guess…! <br>Again, get these flows up on the walls to facilitate conversation between team members and also for wider stakeholders — you never know who might walk past and feel reassured or informed by seeing these visual indications of your thinking and progress.</li><li><strong>Collaborate.</strong> <br>Quickly form an internal and external network of collaboration. This means attending internal Design community meetings as a matter of course, and also understanding where engaging with other organisations can have mutual benefits. <br>For example, we’re particularly excited about plans to make NHS Jobs a case study for the adoption of the <a href="https://beta.nhs.uk/service-manual/">NHS Digital Design System</a>. <br>We met with <a href="https://twitter.com/DeanVipond">Dean Vipor</a>, Lead Designer at NHS Digital, to discuss using and potentially extending the <a href="http://nhsuk-prototype-kit.azurewebsites.net/docs">prototyping kit</a>. The key process is effective feedback of our findings around new components and patterns (based on usability testing) from our use cases which haven’t yet been incorporated into the Design System. These might include administrative and reporting tools for NHS staff such as Hiring Managers.</li></ol><p>So there we go. Some sensible suggestions for starting your new UX role and getting to grips with the challenge, based on my first 2 weeks on the NHS Jobs service. I’ve included screenshots and links below of the assets I’ve mentioned, and links to the templates for them.</p><p>If you’re starting a new UX role soon, I wish you every luck and success.</p><h4>Empathy boards</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2VU9ajY2TABeFiNf2Mxrw.png" /><figcaption>One of the Empathy Boards I produced using <a href="https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a">David’s template</a> and Miro (blurred out intentionally).</figcaption></figure><h4>User flows</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4UgGf7aq1kKG_HshT2GTA.png" /><figcaption>One of the NHS Jobs user flows I produced using <a href="https://medium.com/sketch-app-sources/designing-flows-with-gov-flow-749da31944ca">Charle’s Sketch kit</a>. I produced around 10 of these for this particular Epic (based on key tasks) so that I didn’t end up with a huge overly complex flow.</figcaption></figure><h4>NHS Design System</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loy9yR8El1dFNRw6_VV46A.png" /><figcaption>The <a href="https://beta.nhs.uk/service-manual/">NHS Design System</a> which NHS Jobs will be prototyping with and (hopefully) extending through testing and collaboration to include components and patterns for use cases such as administrative and reporting tools for NHS Hiring Managers and Analytics staff.</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d70846924b96" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/hitting-the-ground-running-in-your-new-ux-job-d70846924b96">Hitting the ground running in your new UX job</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learnt as an Interaction Designer in the public sector — Part 1]]></title>
            <link>https://uxdesign.cc/lessons-learnt-as-an-interaction-designer-in-the-public-sector-part-1-e7df56365569?source=rss-9d0bed36ebc0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7df56365569</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Richard Payne]]></dc:creator>
            <pubDate>Sat, 30 Mar 2019 11:06:43 GMT</pubDate>
            <atom:updated>2019-04-26T23:21:03.172Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons learnt as an Interaction Designer in the public sector — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*6HbflLLXpCMQSP65VQ6upw.jpeg" /></figure><p>I thought I’d share some lesson learnt from working as an Interaction Designer across 4 services within 2 Governmental Departments.</p><p>Prior to this, I’d spent 15 years in similar roles within the Private Sector, and so these are lessons which I think particularly apply to Governmental digital delivery, but of course not exclusively so.</p><p>I’ll write a second list soon, but here’s what springs to mind as I write this:</p><ol><li><strong>It’s going to be complex. </strong><br>Make your peace with this early on. Edge cases (or ‘stress cases’ as described in the excellent <a href="https://abookapart.com/products/design-for-real-life"><em>Design for Real Life</em></a>) should be your playground. Ignore those lazily quoting the 80/20 rule to only explore the ‘happy paths’ While we’re on the topic of lazy thinking, also politely challenge people who say, “<em>It’s MVP, we’ll come back to it</em>” to force through a substandard solution to an Interaction Design challenge. <br>We always do the hard work so that the user doesn’t have to. The back-end of the system has equal responsibility in this matter.</li><li><strong>Use your Design skills to influence others. </strong><br>Make the team space about your users. Assets on a Google Drive or Confluence won’t influence your team in the same way. Shamelessly acquire wall-space and display your Service Blueprints, prototype screenshots, Personas and so on. <br>Use these as a focal point for collaboration and keeping your team focused on the big picture intention (see point 3) behind your service while also getting the small details right within user journeys.</li><li><strong>Stay positive. </strong><br>Remember the intention (for more about ‘Design being the rendering of intent, read this <a href="https://blog.mattedgar.com/2018/10/17/the-promise-of-understanding-a-talk-at-interact-2018/"><em>excellent article by Matt Edgar</em></a><em>,</em> Head of Design at NHS Digital) behind your work. <br>Remember — your responsibility to your end users is to meet their needs.</li><li><strong>Think like a Service Designer. </strong><br>Produce Design assets like Service Blueprints to visually communicate the big picture (including all touchpoints online and offline) to your team. A huge part of the challenge is ‘building the right thing’. <br>Spend enough time framing the problem space correctly by asking the right questions in Discovery. <br>Don’t underestimate how easy it can be for the fundamentally wrong direction to be taken at the end of Discovery, or for new digital user journeys to simply repeat the same old Service Design problems as before.</li><li><strong>Collaborate. </strong><br>Always collaborate! Within, and outside of, your team. Again, the value of this can’t be underestimated. I’d be surprised if your service/design challenge is unique. Reach out to your community, share your work, and great advice/examples from people who’ve worked on similar services will come through. Join<a href="https://design-system.service.gov.uk/community/design-system-working-group/"> <em>Design Pattern Working Groups</em></a>, go to meet-ups (even if you have to travel), ask lots of questions on Slack channels.<br>Oh, and give something back — mentoring less experienced Designers is a great way of consolidating your own knowledge and raising the maturity of the Design function within your Delivery Centre.</li><li><strong>Influence the delivery culture. </strong><br>It may be a new Digital Delivery Centre which needs your help in shaping. It might begin life too Development focused and be pressuring services to skip straight to Beta (the “<em>Build it and they will come”</em> mentality or the <em>‘</em><a href="https://www.youtube.com/watch?v=sHTsQ9qePrQ"><em>Field of Screams</em></a><em>’</em> as some might call it!). <br>Don’t be afraid to present and drive best practice by demonstrating the tools, methodologies and design outputs which you’ve found to be successful in your particular Delivery Centre and are aligned with GDS practice as defined in the <a href="https://www.gov.uk/service-manual">Service Manual</a>.</li></ol><p>I’ll write a second part to this article soon, and am happy to go into more detail about some of these areas if requested.</p><p>To finish for for now, it’s important to say that these are lessons I’ve learnt along the way over the last 4 years and of course, some are necessities while others are ideals to work towards should circumstances allow.</p><p>Some of the above ‘wisdom’ has been gained by <strong><em>not</em></strong> doing these activities and then seeing how my outcomes could have been better if I had!<br>That’s okay, but only as long as I learn from it and remember these lesson for the next service I work on.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7df56365569" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/lessons-learnt-as-an-interaction-designer-in-the-public-sector-part-1-e7df56365569">Lessons learnt as an Interaction Designer in the public sector — Part 1</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>