<?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 Paul Smith on Medium]]></title>
        <description><![CDATA[Stories by Paul Smith on Medium]]></description>
        <link>https://medium.com/@paulmsmith?source=rss-1eeb5f8a238c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uK7wDJArM3D31Ato6X5a8g.jpeg</url>
            <title>Stories by Paul Smith on Medium</title>
            <link>https://medium.com/@paulmsmith?source=rss-1eeb5f8a238c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:44:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulmsmith/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 design: Prototyping]]></title>
            <link>https://medium.com/doing-service-design-at-the-national-lottery/prototyping-at-nlhf-705ff3b88c67?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/705ff3b88c67</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Fri, 27 Sep 2019 14:01:35 GMT</pubDate>
            <atom:updated>2019-09-27T15:27:06.192Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the first in a series of blog posts about “how we design” at the National Lottery Heritage Fund.</p><p>At the time of writing (September 2019) we are moving from a broad discovery phase of work to an ‘<a href="https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works">Alpha’ phase</a> for our primary service which enables people to “<strong>Get funding for a heritage project”</strong>.</p><p>This is the time we try out different solutions to the problems we learnt about during discovery.</p><p>This where prototypes come in,<strong><em> </em></strong><em>they help us to learn by doing</em>.</p><h3>What is a prototype?</h3><p>A prototype is an experimental version of a product or service that allows us to explore our ideas.</p><p>Prototypes can be anything, so long as they do a good enough job of representing the thing we intend to test.</p><h3>Why do we use prototypes?</h3><h4>They help us to learn what the right solution is (or is not!)</h4><p>We create prototypes to help us learn about a problem we want to solve and potential solutions to it.</p><p>They turn our ideas into testable things we can use to show the intention of a design concept to our users. We do this with user research to gain insights by watching what people do and listening to what they tell us when using the prototype.</p><h4><strong>They save time, energy and money</strong></h4><p>The quicker and easier they are to produce and change, the better. Prototypes should be something design teams are happy to throw away.</p><p>The sooner you learn something isn’t working the better. It saves time and effort which costs money.</p><p>Often teams using prototypes make progress quicker when the opposite feels like it would be true. The speed does not come by working flat-out with no breaks though.</p><p>The speed of progress comes from it taking much less effort to go down dead-ends in a prototype, which means we can do more in the same amount of time which ultimately gets us closer to our destination faster. Decision makers have more assurance that the team is delivering the right thing and sooner.</p><p>If you have invested time, energy and money into creating something you are less likely to accept that it is not working.</p><p>Testing ideas cheaply and quickly with prototypes gives us the space to get it wrong when it is easy to correct, so that we get it right when it counts. That also means it’s more reassuring for the people in charge of budgets.</p><blockquote>I have not <strong>failed</strong>. I’ve just found 10,000 ways that won’t work. — <strong>Thomas</strong> A. <strong>Edison</strong></blockquote><h3>The types of prototype</h3><h4>Low fidelity prototypes</h4><p>Low fidelity (often referred to as Lo-fi) prototypes are simple and low-tech concepts.</p><p>We use them so we can spend more energy on our ideas rather than technical details.</p><p>Low fidelity prototypes lower the barrier to participation which is important. It means people who do not see themselves as designers can take part in the design process.</p><p>Everyone can doodle and everyone can learn to use a simple prototyping tool within a couple of hours. Pen and paper or tools like Microsoft Powerpoint can be used to create simple prototypes.</p><p>Being simple often enables real-time iteration. For example, during a research session, we can quickly redo part of a design based on a user’s comments in real time.</p><p>Low fidelity prototypes avoid being confused for a real service by users and stakeholders. This helps to keep the focus on higher level things we are trying to learn rather than the minor details.</p><h3>High fidelity prototypes</h3><p>This type of prototype is more realistic and closer to what an actual solution will look and feel like to users.</p><p>High fidelity prototypes are more detailed, they help us add extra functionality, whilst still not being fully functioning software.</p><p>That might be things like making buttons clickable, adding in logic so that different user responses lead to different paths through the prototype, or enabling users to populate text fields during their research session, so we can learn what they’d input, and how.</p><p>This helps us to better understand how people will use and feel about the services we are designing.</p><p>High fidelity prototypes for digital services are often written in code.</p><p>Reusable prototypes written in code can be quicker to write than graphics are to create. After a while there is no point creating a picture of the thing if you can build it with code in less time.</p><p>This is especially true if the team want to make regular changes in response to research.</p><h3>What have we done so far?</h3><p>So far we are creating low-fidelity prototypes using good old-fashioned pen and paper as well as digital mockups.</p><h4><strong>Pen and Paper</strong></h4><p>We started on paper, in the same room as part of a group workshop known as a ‘design sprint’.</p><p>This was deliberate. Communication is in real time, it’s fast, it’s fun and at the start, the free flow of ideas and debate is best when done in person.</p><p>We analysed the existing live application form as a team. We invited members of our policy team to provide guidance and expertise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sIPGYqqzmNcVIakEC6Dyug.jpeg" /><figcaption>The team reviewing our existing online application forms</figcaption></figure><p>Inspired by <a href="https://designnotes.blog.gov.uk/2014/05/22/gov-uk-sketching-templates/">Ben Terrett’s GOV.UK Sketching templates</a>, I created some sketch sheets for our team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8yqVU3b2ZLVllPR-5wOeg.jpeg" /><figcaption>Photo of a sketch sheet and sketching pens</figcaption></figure><p>We used those to create a paper prototype of a redesigned application form, from the start to when a user clicks submit. Drawing out the content and flow of the questions onto the sketch sheets.</p><p>We took photographs of the sheets and then used a tool called <a href="https://www.invisionapp.com/">Invision</a> to make a ‘clickable’ prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0WRtofIaBqK4aSKnY1d9g.png" /><figcaption>Screen shot of our paper sketches being used with Invision</figcaption></figure><h3>Digital ‘Mockups’</h3><p>Pen and paper works well when you are in the same room but we are a distributed team.</p><p>The other drawback to prototyping on paper is that it eventually it does take longer. A mistake means redrawing a whole page or using fiddly bits of paper and glue which is fun but time consuming.</p><p>Once sketches are finished it then takes time to ‘stitch’ them together in Invision so we decided to try <a href="https://balsamiq.cloud/">Balsamiq Cloud</a> as our low fidelity prototyping tool to enable faster remote collaboration.</p><p>Balsamiq has a hand-drawn look that reminds us to stay lean and leave the little details for later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uqTEzkgfvgWADuX0EdtuNA.png" /><figcaption>Screenshot of a mockup in Balsamiq</figcaption></figure><p>The individual screen designs I call ‘digital mockups’. Some people refer to them as ‘wireframes’ but I try not to because ‘wireframe’ is a long standing industry term which can mean different things to people.</p><h3>Where are we now (Sept 2019)</h3><p>For two sprints we have used Balsamiq to turn digital mockups into prototypes that we have shown to our users. We have analysed the research and then iterated our prototype based on that.</p><p>We have kept copies of each version to refer to because an audit trail of those changes will be useful. Perhaps in conversation with stakeholders as evidence of what worked and what didn’t.</p><p>We are working fast to get to a version we feel confident about. At that point we will discuss investing time in either; making it a higher fidelity prototype or even a going straight to building a ‘beta’ service.</p><p>It is working well so far. All our team have sketched ideas and contributed to the prototype.</p><p>We have learned a lot and have been able to validate some of our ideas, and discard others. We can feel and show tangible progress every sprint, and we’re building confidence as a team that we almost have something that will do the job.</p><p>I am very pleased other members of the team (not just myself as official designer) have used Balsamiq to update prototypes.</p><p>They have learnt new skills and there is not such a dependancy on the person with ‘designer’ in their job title. After all, design and user research is a team sport!</p><h3>What next?</h3><p>In this third Alpha sprint we will conduct another round of research with users next week and analysis to follow up, and then we’ll discuss as a team whether we still have things we need to test and learn with this part of the journey, and whether our next steps should be a brand new prototype for the next part of the journey, or a higher fidelity or beta-ready version of this part.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=705ff3b88c67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doing-service-design-at-the-national-lottery/prototyping-at-nlhf-705ff3b88c67">How we design: Prototyping</a> was originally published in <a href="https://medium.com/doing-service-design-at-the-national-lottery">Doing Service Design at the National Lottery Heritage Fund</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Walls, what are they good for?]]></title>
            <link>https://medium.com/@paulmsmith/agile-walls-9313e49cbeac?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9313e49cbeac</guid>
            <category><![CDATA[agile-working]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 23:25:03 GMT</pubDate>
            <atom:updated>2018-11-19T07:07:51.106Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some thoughts and resources for design teams using physical wall space.</h4><p>I have been working within agile delivery teams for quite a few years now and have often been nominated, asked or took it upon myself to help my teams establish their ‘physical wall-space’.</p><p>Below are some thoughts about why Agile Walls <em>can</em> be really valuable and hopefully some inspiration for when you create your own.</p><h3>Walls are a team’s vital signs</h3><p>Walking around a team’s work area is usually a good way to establish the status of a team and the work they’re doing.</p><p>Browsing a team’s wall-space should give you key information about the situation at hand in much the same way that a patient-chart and health monitor at the end the bed, can give a doctor or passer by the key information they need while a patient is sleeping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9C5FSDpww9ctowF2.png" /><figcaption>Image of at-a-glance information useful to passers-by.</figcaption></figure><p><strong>The vital signs for an agile delivery team might be:</strong></p><ul><li>What are they striving to achieve? (<em>and how will they know if they <br>have done so?)</em></li><li>What are they currently doing? (<em>What and how many things are in-progress?, what is planned?)</em></li><li>Who are the team?</li><li>Who are they doing it for? (and who is involved)</li><li>What is blocking them from getting stuff done?</li><li>What metrics are they using?</li><li>What insights have they uncovered?</li><li>Are they generally happy?</li><li>What is important to them about how they work together?</li></ul><p>Of course, there is no set way that teams should be using their workspace but as a general rule:</p><p>If you can’t answer those questions from a team’s physical space then I’d say that the walls are probably not working hard enough for them or their organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pw-Yd0tMcesNkRmZeld-9A.png" /><figcaption>A wall within Well Digital for a store transformation team</figcaption></figure><p>Leisa made an excellent point in her post “<a href="http://www.disambiguity.com/what-walls-are-for/">What walls are for</a>” when she said that:</p><blockquote>Sometimes the walls are not for you but for other people.</blockquote><h3>Walls are a team’s campfire</h3><p>I heard this analogy for something else recently and I really like it when thinking about a team’s agile walls.</p><p>People gather around Campfires to have conversations and tell stories. They’re not formal and you don’t need to build any serious infrastructure to support them.</p><h3>Tips for using agile walls</h3><h4>Make them clear</h4><p>They are supposed to be rough and ready, the lack of polish is what makes them quick and easy to use but they should be clear and make sense the following day and to fresh eyes.</p><p>Don’t overcomplicate your wall, take some time to design it upfront which is usually best on paper.</p><p>I sketch a rough layout of any wall I want to create prior to getting out the postIt notes and Blutack. This might seem like overkill but it is the work that enables good work. It will help you make the best use of space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SMDyyV6u_lXtKoF2ziF_DA.png" /><figcaption>Rebekah Cooper, Jen Pye and Kim Morley discussion the team wall design</figcaption></figure><h4>Make them easy</h4><p>If a team is combining a physical wall with digitals tools (like Trello, Notion, Jira, etc), then that could be why the information you’d expect to see is not visible on the physical walls.</p><p>If it becomes too much effort to maintain the physical walls then I’d say they are being over utilised.</p><p>To make them easier for people (and better for for a wider audience) my advice is to use the walls to display higher level information that answers the above questions. Put the detail into digital tools.</p><h4>Don’t break the magic string</h4><p>When using digital tools, I think the information from digital tools should bubble up and out to the walls.</p><p>Rather than a live feed, I try to make the physical wall is more like the highlight reel.</p><p>That way it is less arduous to maintain parity between the physical and the digital. The information on a physical wall should be a little more permanent and necessitate less frequent change.</p><p>This helps people working remote, they can update the physical wall whey they are present or ask for less changes from a colleague who is.</p><p><a href="https://twitter.com/@arunzachariah">Arun Zachariah</a>, an excellent agile coach I worked with on a government service, had a great expression, he’d say to the team:</p><blockquote>“Don’t break the magic string!”</blockquote><p>He asked us think of an imaginary ‘magic string’ connecting the physical and digital walls and that we should not put anything on the digital delivery management tools (Trello, Jira, etc) that was not also some how represented on the physical wall.</p><p>If you didn’t do that, you would be breaking the magic string that was joining the two and he would fine you actual cash-money that he put in a pot towards charity.</p><p>If your team does use both physical and digital walls, my advice is to think carefully about how to use and maintain them so not to let one of them stagnate. Play to their strengths.</p><h4>The whole team should own their walls</h4><p>One or two people updating and using a physical wall will likely lead to the rest of the team being disengaged. It needs to be just as much their wall as it is yours.</p><p>It is everybody’s responsibility, you should encourage each other to contribute as all team members will have valuable things to share.</p><h4>Print headings (and constants), handwrite the rest</h4><p>Lastly, I think it is important to make the walls inviting to others and to feel like some effort has gone into them.</p><p>Handwritten headings on scraps of paper or PostIt notes are fine to get going but if they are up more than a week, get them printed.</p><p>I have found that stakeholders and outsiders to the team are far more likely to ‘walk your wall’ if they think it is more than just your latest workings-out on the wall, make it so they can clearly see headings and which items relate to each other.</p><p>As <a href="https://medium.com/@MrAlanCooper/know-whiteboards-know-design-eb3a362df684">Alan Cooper says</a>, throwaway drawings, discussions and notations are what whiteboards are for.</p><h3>White-label wall templates</h3><p>So to help you with some of the above tips and suggestions. I’ve made available some agile wall templates I’ve done for my friends and colleagues at <a href="https://blog.well.co.uk/">Well Digital</a>.</p><p>I have written a separate post to describe them and their use. Head over to <a href="https://medium.com/@paulmsmith/white-label-wall-templates-1cdec749dae6"><strong>White-label agile wall templates</strong></a>.</p><h4>Further reading</h4><ul><li><a href="http://www.disambiguity.com/what-walls-are-for/">What walls are for</a> by Leisa Reichelt</li><li><a href="https://gds.blog.gov.uk/2012/12/19/the-agile-wall/">The role of the Agile Wall</a> by Emily Webber</li><li><a href="https://medium.com/@eleanor.mollett/the-anatomy-of-our-kanban-board-93f694b603e0">The Anatomy of our Kanban board</a> by Eleanor Mollett</li><li><a href="https://medium.com/@MrAlanCooper/know-whiteboards-know-design-eb3a362df684">Know whiteboards, Know Design</a> by Alan Cooper</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9313e49cbeac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[White-label agile wall templates]]></title>
            <link>https://medium.com/@paulmsmith/white-label-wall-templates-1cdec749dae6?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cdec749dae6</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[template]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 23:23:50 GMT</pubDate>
            <atom:updated>2019-05-01T07:51:22.976Z</atom:updated>
            <content:encoded><![CDATA[<h4>A starter kit for your team’s physical wall-space</h4><p>In “<a href="https://medium.com/@paulmsmith/agile-walls-9313e49cbeac"><strong>Agile walls what are they good for?</strong></a>” I wrote about the value of physical “agile walls”.</p><p>However I often find a barrier to teams using them (and staying engaged with them) is the work needed to create and regularly update them.</p><p>So in the spirit of Alice Bartlett’s ‘<a href="http://alicebartlett.co.uk/blog/how-to-do-ok-at-slides"><strong>A white-label slide deck</strong></a>’, I have created a set of white-label agile wall templates. Hopefully as a kind of starter kit to help get your physical wall-space up and running.</p><h3>Getting started</h3><p>If you want to jump straight in, the following link is to the <br><a href="https://docs.google.com/presentation/d/1G67t_-inCkEVZUcn0prbnFg17WEHd7xVSg6SUaBFbAM/edit?usp=sharing"><strong>White-label agile wall templates on Google Slides</strong></a></p><p>I have designed them in Google Slides because other than a web-browser you don’t need any other software to be able to use or customise the templates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQPmHMTd1rtEj4Td1MPMTg.png" /><figcaption><a href="https://docs.google.com/presentation/d/1G67t_-inCkEVZUcn0prbnFg17WEHd7xVSg6SUaBFbAM/edit?usp=sharing"><strong>White-label agile wall templates on Google Slides</strong></a></figcaption></figure><p>To edit the templates, you will need to “Make a copy” of my master google slides file. <em>(Which might mean you need to create a google account if you don’t have one)</em></p><p>I know some of us are on locked-down computers behind particularly inflexible corporate IT policies. If so you can <a href="https://drive.google.com/file/d/1IbrO6EQeKkHfOX4batQ11R1Q1dMUUoEK/view?usp=sharing">download a PDF</a> of the templates should your IT department block google applications.</p><h3>Templates overview</h3><p>The following is a break down of V1 of my white-label agile wall templates.</p><p>I have deliberately not branded these with my name or that of Well (My current employer) because I know that sort of thing just serves to confuse or even annoy teams and their stakeholders.</p><p>They should all work nicely when printed at A4 or A3 and should work out of the box quite well on a greyscale printer.</p><h4>Wall labels</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNicj60Jzt1NoEv7UnV8KA.png" /></figure><p>Above is a set of wall labels that most of the design teams I’ve worked in have needed at one time or another. I’ve used these as column headings or just as labels for large sections of a wall.</p><p>Using the google slides template you can reword them. For example if you prefer “users” instead of “personas” or “In-progress” instead of “Doing” and so-on.</p><h4>Your basic Kanban/Story Card</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mewyagcn1Wlzow4E732xqw.png" /></figure><p>Hopefully a format you’re used to, if not, feel free to edit or adapt this design.</p><p>Out-of-the-box it allows for a title at the top, perhaps a bit of detail in the centre and has placeholder for people assigned to the card and the option to add a “size” for example “XL” if t-shirt sizing or perhaps a number for story points.</p><h4>Hypothesis cards (handwritten)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmnCPWcsLf5m-ZtbjWGGog.png" /></figure><p>I often work in teams that use some form of “Hypothesis Driven Design” (HDD) process. This template is for printed card templates you can use to quickly hand write them as part of workshops or group discussion (notice the cut line down the middle to separate).</p><p>Here are some good blog posts and slide-decks about the Hypothesis Driven Design process:</p><ul><li><a href="https://grillopress.github.io/2017/12/10/hypothesis-driven-design.html">Hypothesis Driven Design</a> by Andrew Duckworth</li><li><a href="http://www.hollidazed.co.uk/2015/07/16/everything-is-hypothesis-driven-design/">Everything is hypothesis driven design</a> by Ben Holliday</li><li><a href="https://speakerdeck.com/tsmorgan/hypothesis-driven-design-17th-may-2018">Hypothesis Driven Design (Presentation)</a> by Tom Morgan</li></ul><h4>Hypothesis Sheets</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qn9Mqp9K-vC7vLi-MBkvsQ.png" /></figure><p>These are for higher level hypothesis that have been formulated by the team, it helps to type these up and print them larger (ideally A3) and place them above lower level hypotheses.</p><p>These are good for stakeholders and outsiders to see the general problems you and your team are looking to address.</p><h4>Insight sheets</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0051q_vEP4G_pQ2borU4Ww.png" /></figure><p>An insight sheet is to get visible the things you have uncovered that help you and your team make decisions or take action. I urge you to read Leisa Reichelt’s excellent post <a href="http://www.disambiguity.com/from-insights-to-actions-or-what-should-we-do-with-this-research/"><strong>From Insights to Actions, or What should we do with this research?</strong></a><strong> </strong>and this template will be fully explained.</p><h4>Objectives and Key Results</h4><p>If you are familiar with Objectives and Key Results (OKRs) then I have created some templates for printing them out big and clear for people to see. If you have not used OKRs yet, then this post</p><blockquote><a href="https://dwpdigital.blog.gov.uk/2018/03/16/setting-community-goals-using-objectives-and-key-results/"><strong>“Setting community goals using objectives and key results</strong></a><strong>” </strong>by Ryan Hewitt (a previous colleague of mine) gives a great explanation and real world example.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kziGAfC5Gqwu1XjiDOC4jw.png" /></figure><p>I advise that they be printed and placed horizontally across the top of your wall (if you have the space) otherwise they stack in columns quite neatly.</p><h4>Sprint Goals</h4><p>If you work in ‘sprints’ then you should be setting clear and shared sprint goals. These templates are to make them easy to read and obvious. Quickly type them up and print them at the end of your planning session.</p><p>This might be a personal thing but these are important, I switch off if referring to these and they are on a scrap of paper in somebody else’s bad sharpie hand writing.</p><p>I’ve made them bright and readable with a clear heading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIqBdxIa7Plg_y0_WstuVg.png" /></figure><p>Printing these should make it easier for people visiting your wall to see what you’re doing and are good to keep each other focussed in conversations as things to point at.</p><p>I tend to place these near the top of the wall, ideally below Objectives and Key Results but above the Kanban section part of the wall.</p><h3>Using the Google Slides templates</h3><p>Most of us are familiar with viewing Google Slides presentations but you may not have used the authoring aspect of the Google slides service, which is how you edit and use the white-label slides I’ve created.</p><p>Hopefully these are relatively straightforward to use, you might want to view thIs hastily recorded 5 minute screencast to get an audio-visual overview.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7co8Z-ORa2k%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7co8Z-ORa2k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7co8Z-ORa2k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/da1e6bb0a31a1dda8fa4f85f36349fc4/href">https://medium.com/media/da1e6bb0a31a1dda8fa4f85f36349fc4/href</a></iframe><h4>Creating a new card or sheet</h4><p>In the Google Slides document, I have created some examples that you can edit or copy.</p><p>This might help you use those templates as intended but you can also use the <em>New Slide</em> button (CTRL + M) to create one from the underlying templates I’ve created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*ngmtVqEo12wCZaNFdqtYCg.gif" /></figure><p>Sometimes with some of my prepared examples it is easier to create a copy of the slide you want, you can do that by right clicking on the slide and clicking duplicate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43wK9TlUVa2RpIqiRNBnHQ.png" /><figcaption>Early versions of these templates being used by my team at <a href="http://blog.well.co.uk/">Well Digital</a></figcaption></figure><p>All feedback, questions or comments welcome on twitter to <a href="https://twitter.com/paulmsmith"><strong>paulmsmith</strong></a> or you can comment here on medium.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cdec749dae6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems — the means, not the end]]></title>
            <link>https://medium.com/@paulmsmith/design-systems-the-means-not-the-end-fc840c21b51e?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc840c21b51e</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 19:54:29 GMT</pubDate>
            <atom:updated>2018-10-23T07:19:01.889Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Design Systems — the means, not the end</h3><h4>Reusable patterns work a treat, except when they don’t</h4><p>When I bought my first house, it was a busy time, I just needed to get stuff done and quickly! Not unlike the teams a lot of us now work with.</p><p>I’d run around stores like Ikea with a list of things I needed for example: bathroom cabinet, shelving units, kitchen cabinets and so on…</p><p>They looked good in the store, I’d check the material, open and close the doors, etc and then I’d load up the car and be on my way home.</p><p>I’d drag the boxes into the house and start building. Unfortunately there was more than one occasion that I’d nearly built the things before I realised they didn’t fit or would not work as I’d intended once they were actually in my particular room.</p><p>If before-hand I had taken the time to think about what I needed and the context that those things would be used, I would have realised that the units were too big and the cabinet doors opened the wrong way for them to be useful in my kitchen and so on.</p><p><strong>I tell this story because it is not unlike the way some teams have been using design systems.</strong></p><h4><a href="https://twitter.com/ermlikeyeah/status/1051015310290104320">Simon Wilson recently tweeted</a>:</h4><blockquote>“It’s not the “commoditisation” of design through things like design systems that gets me TBH, more people thinking “ah yeah design system! grab that and plough on!” with no semblance of process, no rigour. A v real danger”</blockquote><p>I too have seen what Simon described but I’d also argue that perhaps we <em>(the proponents of design systems)</em> are the reason this is happening.</p><p>Is it the result of how design systems have been positioned or ‘sold’ to their audience?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WfFgIIviPDhLihoK.jpg" /><figcaption><strong>Photograph of sweets in a Pick ’n’ Mix display</strong></figcaption></figure><p>In trying to get design systems recognised as a valuable <em>thing</em> to invest in (which I believe they<em> can </em>be) we have described them and their contents with phrases like:</p><ul><li><strong>The “single source of<em> truth</em>”</strong></li><li><strong>Designed to <em>meet user needs</em></strong></li><li><strong><em>Already working</em> as part of a live service</strong></li><li><strong>“Represent what good looks like”</strong></li><li><strong><em>Been through</em> X rounds of <em>user research</em></strong></li><li><strong>“Battle tested”</strong></li><li><strong>Passes automated and Cross browser tests</strong></li></ul><p>So with that in mind, I don’t blame design teams for believing that the patterns and associated components in a design system are some-how a ‘solved problem’ as they grab them <em>off the shelf</em>.</p><p>After-all, that is the aspiration of a design system is it not?</p><p>Josh Clark wrote an excellent post on what should be the aspiration of a design system, Josh says the <a href="https://bigmedium.com/ideas/boring-design-systems.html"><strong>most exciting design systems are ‘boring’</strong></a></p><blockquote>When the design system absorbs mundane problems, designers and developers are freed to pursue new science and higher-order problems.</blockquote><p>I completely agree that is the goal of a design system but I think that it also depends on the scale and variety of needs that the design system is serving.</p><p>So I think it is incumbent upon the teams using a design system to fulfil their side of the deal, which I suspect we as a community have not have spelt out clearly enough, so here are some thoughts on how design systems should be used.</p><h3>Design systems are a starting point</h3><p>For most things in life, we don’t ever really want to have to ‘start from scratch’ and design is no different.</p><p>Institutional knowledge packaged up as a more easily consumable set of ‘things’ with guidance is great but it is less about simply taking and more about evaluating and then trying.</p><p>The <a href="https://design-system.service.gov.uk/">GOVUK Design System</a> stipulates:</p><blockquote><strong>“The contents of the Design System must be of a high quality and meet user needs</strong>”.</blockquote><p>However it would be wrong to use the contents whimsically or ignorantly.</p><p>Generally teams should know the following three things before using a pattern from a design system:</p><ol><li><strong>When to use a pattern</strong><br><em>The scenario this pattern should be employed</em></li><li><strong>Why they should use a pattern</strong><br><em>The needs the pattern meets and how it does so</em></li><li><strong>How to use a pattern</strong><br><em>The way the pattern should be used and implemented</em></li></ol><p>Even then, knowing those things, design teams should also consider the pattern as part of the wider service design because sometimes what works in isolation will not work as part of a bigger (or perhaps different) user journey.</p><h3>Design System general advice</h3><p>What consumers/users of a design system should know about using a design system, or put a different way, what most design systems should perhaps do a better job of emphasising.</p><h4>Know your problem before you look for a solution</h4><p>Before you trawl a design system for what you think you’ll need. Like the story of the Ikea woes of my younger days, take the time to be confident that know the problem you are trying to solve <em>in detail</em> so you can make a better judgement about the things on offer.</p><p>Armed with the knowledge of the problem you are trying to solve, a Design System should make it clear what needs it meets and in what circumstances it does so which should tell you the <strong><em>when and why </em></strong>questions for a pattern.</p><h4>Read the manual</h4><p>So you have a pattern or component that does appear to meet your needs, don’t let it down by incorrectly employing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_YqHxlE-03xGzapuCVSjQ.png" /><figcaption><strong>The instructions and guidance for Flatpack are there to help you do it right.</strong></figcaption></figure><p>Just because what your team has done looks the same does not mean it will perform the same if they skipped past any guidance telling them <strong>how</strong> to use it.</p><p>A lot of hidden effort will likely have gone into ensuring accessibility, performance, responsiveness and service design so ensure that those things are not missed.</p><p>Not using part of a design system as intended could undo all that hard work and mean users will not get the benefit.</p><h4>Prototype the thing</h4><p>To torture the flat-pack analogy, wise advice is ‘<strong>Do not tighten screws before fully assembled</strong>’.</p><p>When using design systems, my advice is always to prototype with the components and patterns from a design system. Don’t rush straight to production, no matter how simple that might be to do with the off-the-shelf things you now have access to.</p><p>It is still much less effort to spin up a prototype and research it properly than it is to put most things in production. Prototypes don’t need code tests, releases (and release notes) and so on.</p><h4>Do your own research</h4><p>As I’ve said, the efficiency and beauty of a well crafted design system is that you get a leg up and don’t have to start from a blank sheet of paper <strong>BUT</strong> you should not take for granted that it will ‘just work’ for your users who may well be in a very different context.</p><p>There are trade-offs in the design and implementation of a pattern that would be hard to document completely.</p><p>A good design system will attempt to make the context clear but that also relies upon a user of the design system to take the time to familiarise themselves with it or understand the context and wider service design of what they are working on.</p><p>If a designer does (as<a href="https://medium.com/u/7f3b4e9622da"> Simon Wilson</a> says) just “grab that and plough on” then they might well be doing something bad for their users. So it is important to do user research to validate it is working as expected in your product or service.</p><p>Design systems are a means to an end. They should give teams a head-start in achieving the outcomes they want but will not always do that out of the box.</p><p>So before you use a pattern, <strong>consider if the way you plan to use it (why, when, how) matches the way the design system expects it to be used</strong>.</p><p>If you do choose to use the pattern, do your own research to avoid false assurance and If find issues in your context then go one step further by taking the opportunity to make the design system better by feeding your insight back to the community.</p><p><em>Thanks to the very generous </em><a href="http://twitter.com/cjforms"><em>Caroline Jarrett</em></a><strong><em> </em></strong><em>for helping me say what I meant to say and to </em><a href="http://ermlikeyeah/"><em>Simon Wilson</em></a><em> for the excellent food for thought as always.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc840c21b51e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taming my inner Lumbergh]]></title>
            <link>https://medium.com/@paulmsmith/taming-my-inner-lumbergh-898d5afe1e9c?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/898d5afe1e9c</guid>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Wed, 23 May 2018 21:05:42 GMT</pubDate>
            <atom:updated>2018-05-24T06:15:45.464Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learning to stay focussed and prevent burnout.</h4><p>I have a voice in my head that I have trouble ignoring. He’s a potent mix of my imposter syndrome, anxiety, my ego and my inner do-gooder/try-hard.</p><p>I have joked in the past that I have an inner <a href="https://youtu.be/YYFO5qPpM_I">Bill Lumbergh</a>.</p><p><em>Lumbergh is a fictional character from the 1999 film Office Space, who regularly asks employees to do unreasonable things and a lot more than they should be expected to do.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/0*wCS0IVk_pk2eXMXs.jpg" /><figcaption>Gary Cole as Bill Lumbergh in the 1999 film <a href="https://www.imdb.com/title/tt0151804/">Office Space</a></figcaption></figure><p>My inner Lumbergh tells me that I need to go ahead and work over the weekend to make something that little more slick or impressive.</p><p>Or to go ahead and solve some annoyance or oversight that is not directly related to my task at hand.</p><p>For example to fix the broken office WIFI, printer, or that poorly designed slide deck I’ve seen being shared around the office.</p><p>The other thing my inner Lumbergh tells me is that I shouldn’t take a day off.</p><p>I shouldn’t have time off because look at the state of your Trello ‘to-do’ column, or because some meeting <em>(no matter how small)</em> is scheduled in my calendar for that week.</p><p>Generally he says I shouldn’t have time off because something <em>might</em> happen that might be good for me to be involved in.</p><p>Those who know me won’t be surprised to hear that this week (21st May 2018) is the first real holiday/vacation I’ve taken since I joined <a href="http://digital.well.co.uk/">Well Digital</a> just over 9 months ago <em>(excluding a few days at Christmas).</em></p><blockquote>This is not me bragging, going so long without a proper break is daft and not healthy.</blockquote><p><strong>I’ve taken myself to the point where I <em>needed</em> a break which is not good.</strong></p><p>In the same way that thirst is a sign you are already dehydrated, getting to the point where colleagues or loved ones can recognise that you are not quite yourself is a sure sign that you should have taken a break by now.</p><h4>Why share this publicly?</h4><p>I have learnt a lot from the insights others have shared about their work-life balance, their habits, working practices, their mental health and their general outlook, so this is my attempt at doing the same.</p><p>I try to take my work seriously but not myself. After-all, we are all just sacks of meat bouncing around this planet of ours in the hopes of doing our best.</p><p><strong>So the following are a few things I’ve learnt recently about staying focussed and avoiding burn-out.</strong></p><h3>1. Add in a breakpoint</h3><p>In software development, a ‘breakpoint’ is an intentional stopping or pausing place in a program, put in place for debugging purposes.</p><p>More generally, a breakpoint is a means of acquiring knowledge about a program during its execution, which I think is a good analogy for what I’ve been doing this week during some much needed time off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_G0zsLjYSdrbtdjOpgiNQ.png" /><figcaption>My calendar for this week. I forced myself to take this week off.</figcaption></figure><p>At the start of the year or as early as you can, <strong>pick a date to have some time off and get it officially planned in.</strong></p><p>I am also going to take smaller breakpoints as and when I can, for example by manufacturing long weekends such as booking a Friday and the following Monday off work.</p><p>I’m no longer going to see time off as ‘nice to have’ or somehow a lower priority than the items in my to-do list. That list will never be empty.</p><p>So It will need to be something absolutely critical to stop me booking or get me to cancel or change those breakpoints in future.</p><p>People say when you take some time off you should forget about work but I’m deliberately using the breakpoint analogy because I will only be able to forget about work if I’ve sat down and thought about (debugged) what’s been happening and arrived at a way to move forward when I return to work.</p><p>Which is partly why I’m writing this blog post. It has helped me decompress the last few months of personal learning.</p><h3>2. Go easy with those good intentions</h3><p>I think we all do this, at a milestone point in our lives (such as new year or starting a new job), we say to ourselves that we are turning over a new leaf and we have such good intentions for the future.</p><p>We believe we might now have a better chance of changing things because we are about to radically change the context and/or the routines which surround them.</p><p>Lots of us will arbitrarily decide upon the things we want to change.. For example, I remember saying to myself:</p><blockquote><em>“</em>Im going to make more homemade lunches and take them into the office”</blockquote><blockquote>“I’’m going to cycle into the office more”</blockquote><blockquote>“I’m going to make sure I always have an empty inbox at the end of the week”</blockquote><blockquote><em>“</em>I’m going to log off at the end of the day and not check Slack and emails”</blockquote><blockquote>“I’m going to remember not every problem needs me to solve it”</blockquote><p>The list went on and on.</p><p>I set out with a whole heap of these good intensions but it was too much change for me to manage, too much to be mindful of and when properly considered, most were not really within my direct control.</p><blockquote><strong>What I should have done was critically examine my recent work/life experience and find the most important thing to change.</strong></blockquote><p>As you might guess, my inner lumbergh pipes up quick with how I’ve failed or generally under-performed as a colleague or loved-one, which is not healthy.</p><p>If this all sounds familiar then you don’t need to wait for a new job or some identifiable milestone... Ask yourself right now, today:</p><p><strong>What three things should I start or stop doing?</strong> What they are depends on what your goals are or what is important to you. However don’t just think them up, make a tangible plan to achieve them. Trello is the tool I’ve gone with.</p><p>I also suggest that you find a way to help stay mindful of them. Post-It notes on the fridge perhaps? A reminder in your calendar, you could set them as your desktop wallpaper…You get the idea.</p><h3>3. Speak up more.</h3><p>Be honest with yourself and others. If you’re feeling nervous about a project, meeting or any aspect of your work, speak up and stop ignoring those feelings. <strong>Expressing your trepidation about something doesn’t make you weak; it makes you a human being.</strong></p><p>I recently spoke up in a meeting and it helped the team to voice their concerns as well. It derailed the agenda quite a bit (which I felt guilty about) but it was productive and helped build more understanding between us. In agile this is what retrospectives are for but sometimes there is value in not waiting for the correct ceremony.</p><p>Sometimes the hard bit is doing it in the right way, especially if you’re feeling stressed and care deeply about the work you’re doing.</p><p>Be positive and be kind. Open up with how you feel and why but do so constructively and then listen to what people say in return as It might give you needed perspective and calm your nerves or doubts.</p><h3>4. Learn to internalise any external verification.</h3><p><a href="http://www.craigabbott.co.uk/what-is-normal-anyway">Craig Abbott said this</a> and he is so right.</p><blockquote>When somebody compliments you, believe it and take it on board. Very few people hand out lies as compliments, so if they tell you they like your work, it’s likely that they do. Say thank you, pat yourself on the back, and don’t always discuss what you felt you could have done better.</blockquote><p>We should take satisfaction in the recognition before moving on. We all want to be respected and appreciated so when it happens take a moment to acknowledge it to yourself as well as to them.</p><h3>5. Say NO more often.</h3><p>When asked to do something I’ve had to start assessing if it adds genuine value to my personal progression, to the team or projects I am responsible for. If it doesn’t then more times than not the answer should be a polite <strong><em>no</em></strong> or at least a <strong><em>no not right now</em></strong>.</p><p>This is how I plan to be more focussed and effective for the work I’ve been assigned or the team are relying upon me to deliver.</p><p>Even reading that back just now, it sounds very selfish but to avoid burnout and stay focussed you need to do it more than you probably do.</p><p>I have learnt this only very recently. It’s constructive feedback I’ve had from people I respect and admire.</p><p>That said, growing up I’ve also heard conflicting advise on this, for example <strong>The law of reciprocity says:</strong></p><blockquote>“If you happily help people first, others automatically will feel a sense of obligation to return the favour,”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGVhCbvvp1qvFYoH-DThvQ.png" /><figcaption>PostIt note I put on the wall here at Well Digital (credit <a href="https://medium.com/u/d9a06cb30f4b">Lawrence Kitson</a>)</figcaption></figure><p>For me it’s less about gaining trust or some kind of favour in my back-pocket.</p><p>Its more that I genuinely like to help people, I enjoy doing things for other people. It makes me feel useful and valuable.</p><p>Unfortunately always saying yes doesn’t scale. Your own work does eventually suffer, you end up doing things out of hours and wander onto an unsustainable path.</p><p>Almost sadistically it gets worse the more you help people because they come back for more or others do in their place. A phrase I really like is “Stop starting, Start finishing” and boy do I need to heed that advice myself.</p><p>So with that in mind, I am starting to guard my time and my energy a little more closely so that where I really can add a lot of value, I can do so to the very best of my ability.</p><h3>6. Choose Kindness</h3><p>Treating people fairly and with respect <a href="https://www.forbes.com/forbes/welcome/?toURL=https://www.forbes.com/sites/jacquelynsmith/2012/10/03/10-ways-to-get-your-colleagues-to-work-with-you-better/2/&amp;refURL=&amp;referrer=#40e7636b6696">encourages collaboration</a> and, as a result, boosts productivity but most importantly, you will feel better about yourself and your life.</p><p>As Seth so brilliantly put it <a href="http://sethgodin.typepad.com/seths_blog/2017/12/kindness-scales.html">Kindness Scales</a>:</p><blockquote><strong>It scales better than competitiveness, frustration, pettiness, regret, revenge, merit (whatever that means) or apathy.</strong></blockquote><blockquote><strong>Kindness ratchets up. It leads to more kindness. It can create trust and openness and truth and enthusiasm and patience and possibility.</strong></blockquote><blockquote><strong>Kindness, in one word, is a business model, an approach to strangers and a platform for growth.</strong></blockquote><blockquote><strong>It might take more effort than you were hoping it would, but it’s worth it.</strong></blockquote><h3>Thanks for reading</h3><p>There are many great posts and articles worth reading of a similar nature. Some of these are just a few that have helped me in recent years:</p><ol><li><a href="https://medium.com/u/f1b87a5eb00e">Leisa Reichelt</a>’s “<a href="https://the-pastry-box-project.net/leisa-reichelt/2012-december-26">Don’t give up</a>”</li><li><a href="https://medium.com/u/1c19cb911141">Kit Collingwood</a>’s “<a href="https://medium.com/@kcollingwood/curating-our-mental-health-146e1374a01f">Curating our Mental Health</a>”</li><li><a href="http://www.craigabbott.co.uk/">Craig Abbot</a>’s “<a href="http://www.craigabbott.co.uk/what-is-normal-anyway">What is normal anyway</a>”</li><li><a href="https://medium.com/u/42c29151c49a">Gavin Elliott</a>’s “<a href="http://www.gavinelliott.co.uk/2017/11/impostor-syndrome/">Imposter Syndrome</a>”</li><li><a href="https://medium.com/u/a4185685cb11">Giles Turnbull</a>’s “<a href="https://gds.blog.gov.uk/2016/05/25/its-ok-to-say-whats-ok/">It’s ok to..</a>”</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=898d5afe1e9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Joining Well Digital]]></title>
            <link>https://medium.com/well-digital/joining-well-digital-134ad67fcfb0?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/134ad67fcfb0</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[pharmacy]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Mon, 02 Oct 2017 16:27:16 GMT</pubDate>
            <atom:updated>2017-10-04T07:50:21.584Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<h4>My first month as Senior Digital Designer at Well, the UK’s largest independent Pharmacy.</h4><p>Since I wrote that I was <a href="https://medium.com/@paulmsmith/leaving-dwp-digital-8daf587a0a0f">Leaving DWP Digital</a>, I received some lovely messages wishing me well. Some said they would like me to write ‘<a href="https://weeknot.es/about">weeknotes’</a> for the new role.</p><p>Week-noting is a popular practice of people writing a day-by-day account of their working week. As you might guess though, my time became spoken-for rather quickly.</p><p>Instead, I decided to keep detailed notes of my first three days, followed by a round-up of what the month had to offer.</p><h3>Day 1 — Digital Healthcare kick-off</h3><p>Day one arrived. It’s Tuesday 29th August 2017. Having met some of the team at the <a href="https://www.manchesterdigital.com/events/manchester-digital-bbq-0">Manchester digital BBQ</a> earlier in the year, I was ready to get straight to work.</p><p>In the morning I joined a kick-off meeting between <a href="http://ustwo.com/">UsTwo</a> &amp; <a href="http://digital.well.co.uk/">Well Digital.</a> It is for a discovery project that will focus on ‘Digital Healthcare’.</p><p>It was a great way to meet the team and to start learning about how pharmacies and the UK healthcare system operate.</p><p>It was quite an intensive day. We covered our goals for the project, the assumptions, we did a dive into the existing business, NHS regulations as well as what is happening in the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GDlXmsvi_Fg-gyCGW9P5_w.jpeg" /><figcaption>Outside Well HQ with Dan Sheldon and the UsTwo discovery team [Photo credit: <a href="https://medium.com/u/a83992e90748">ustwo</a>]</figcaption></figure><p>Well have set a wide brief for UsTwo so it will be interesting to see what insights and potential opportunities they uncover.</p><p>Alongside the kick-off meeting, I did some general HR type things, setup my email and collected my new work machine. Lots of hellos, a tour of the building and my first day was complete. 🎉</p><h3>Day 2 — Services Discovery, a growing to-do list &amp; lots of acronyms</h3><p>It is <a href="https://digital.well.co.uk/@sheldonline">Dan’s</a> last day in the office for two weeks, so we make time to catch up and talk about some early priorities before a new project kick-off, this time its a discovery to focus on ‘Services’.</p><p>It’s quickly apparent that I’m going to be busy, there will be no shortage of work but more importantly that <a href="https://digital.well.co.uk/@chrisellett">Chris</a>, Dan and the Well board have a bias for action, they’ll be moving fast and intend to learn by doing.</p><p>Initially the services discovery will be the project I will focus most of my time on. I‘ll be working with <a href="https://common-good.co/">Common Good</a>, a strategy-led design studio based in Manchester that are already partnered with Well, having worked on the new <a href="http://finder.well.co.uk/">Store finder</a>.</p><p>To kick things off <a href="https://twitter.com/meachinC">Charlie</a> (designer and co-founder of Common Good) started the day with a <a href="http://toolbox.hyperisland.com/project-point-of-departure">Project Point of Departure</a> workshop which is a nice way to get things moving and to establish our first steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NJAK8sbZwU5YFAAUstuJA.jpeg" /><figcaption>The services discovery team outside Well Digital HQ</figcaption></figure><p>We defined a mission for the project as a whole, a mission for our first sprint and identified key people from across Well that will be able to help us along the way.</p><p>From there we started a session to understand what services Well currently offer, why, any business drivers and associated regulations.</p><p><a href="https://twitter.com/PopUpStory">Hinrich</a> (Content Designer) lead this and grouped our findings. I knew Well offered a lot of services but I was still surprised at just how many and at the complexity of <a href="https://www.nhscc.org/ccgs/">commissioning</a> some of them.</p><p>I wasn’t the only one drowning in pharmacy and healthcare related acronyms, as I looked across the table, <a href="http://twitter.com/radinadoneva">Radina</a> and <a href="http://twitter.com/meachinC">Charlie</a> had beaten me to starting a glossary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*wykklzDYn8mOn4WLz6wp7Q.jpeg" /><figcaption>Screenshot of an internal ‘Jargon Buster’</figcaption></figure><p>The kick-off takes up most of the day, I finish by continuing to set up the new work machine and wading through some more email.</p><p>I can see that it’s going to be fast paced, interesting and meaningful work<em> </em>that matters to Well as business and to a lot of people (customers and colleagues) who operate or reply upon Well services.</p><h3>Day 3 — First ‘Show &amp; Tell’</h3><p>Thursday is <a href="https://www.gov.uk/service-manual/agile-delivery/agile-tools-techniques#team-review-show-and-tell">Show &amp; Tell</a> day at Well, first of all, it’s great to see them being taken seriously (not <em>just another ceremony</em>).</p><p>Chris Ellett starts things off and I’m introduced to people, I talk a little bit about my role, what I’m going to be doing at Well and then it’s over to Charlie to talk about the work he and the team had been doing for the <a href="http://finder.well.co.uk/">new Store Finder</a>.</p><p>The services discovery we kicked off yesterday is introduced and I talk about some of the objectives the team have set as part of our mission for the project.</p><p>This week there are questions about the data used for the store finder, this is excellent, I’m really happy to see this happening because it is very much the point of a Show &amp; Tell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*M4v3b0SbD-20o6YJuoUgMQ.jpeg" /><figcaption>A show &amp; tell at Well HQ</figcaption></figure><p>I’m told the attendance is steadily growing. In a fast paced, agile environment, a bunch of lengthy emails specifying what’s happening would soon be at the bottom of everybody’s inbox by 10:00am.</p><p>Show &amp; Tells ask people to unplug and give their attention so they can find out what’s happening in an open forum, ask questions which importantly, others can hear and respond to.</p><p>After a good conversation we wrap up the in-person event and I stay behind to help record a summary version to camera which get’s shared on the company intranet for people that are unable to attend.</p><p>It’s great we’re being inclusive and not forgetting from our base in the Manchester head-office that what we’re doing impacts lots of colleagues in stores across the country.</p><p>I’m very happy to see that the team publishing the recordings have taken the time to caption (subtitle) the video, making it as accessible as they can for all members of Well staff. I’ll talk more about accessibility in the round-up below.</p><p>Finally, in the afternoon we get a cup of tea and get together to divide up the work over a shared <a href="http://trello.com/">Trello</a> board. Doing this I can see already that there is a really positive, friendly and supportive team dynamic.</p><p>The day ends and my first three days are over. I’m tired but feel energised about the challenge ahead.</p><h3>Four weeks later..</h3><p>As I write this it’s the end of my fourth week with Well Digital, time feels like it has gone remarkably quickly, which I see as a good sign. So what else have I been doing since day three?</p><h4><strong>Design is a good idea</strong></h4><p>Part of my role is to help us establish design principles and practices here at Well but it is not something any one person can do overnight by themselves, nor should it be.</p><p>I’ve begun by trying to get an understanding of the design work that is currently happening here.</p><p>The discovery project has been a good place for this because we’ve been mapping user journeys for a lot of Well services.</p><p>We’re gaining a detailed understanding of the things people do with us, for example:</p><ul><li>getting a Flu-jab for winter.</li><li>being vaccinated to ensure they are safe when traveling.</li><li>Having their medicines (and how they use them), reviewed by our colleagues in store.</li><li>Seeking advice about their sexual health.</li></ul><p>This is vital because ‘digital’ doesn’t simply start and end with websites or mobile Apps. Journey Mapping is a start towards us gaining real insights about our users and their needs .</p><p>These ‘<a href="https://userresearch.blog.gov.uk/2015/05/28/we-need-to-talk-about-user-needs/">user needs</a>’ help us to better reason about the things we need to do when designing end-to-end services.</p><p>When thinking about design, we should remember that people outside the digital team are also making significant design choices that affect our customers in meaningful ways.</p><p>To me, this means that as part of their job, they too are <em>designing </em>our products and services. In other words, every one of us is a designer, officially or not.</p><p>As <a href="https://medium.com/ux-immersion-interactions/the-power-of-experience-mapping-212ba81e5ee">Jared Spool points out</a>:</p><blockquote>When someone influences the experience of the user, they, in that moment, become a user experience designer.</blockquote><p>I think this is already recognised here at Well. As people officially calling ourselves ‘designers’, our role is about being stewards for good design.</p><p>As a way to help some early discussion, I’ve started mocking up some posters to visualise some of my thoughts about our possible design principles and ways of working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7YZOO8uKtReCR9Dpp-cDA.jpeg" /><figcaption>Some of the ‘ways of working’ poster designs</figcaption></figure><p>I saw the <a href="https://www.gov.uk/government/organisations/government-digital-service">Government Digital Service</a> and my colleagues at DWP do this well and I will be referencing a lot of <a href="http://govdesign.tumblr.com/">their wisdom</a>.</p><p>We will be getting people together to discuss our principles soon. I learnt in government that posters of things like values and principles should not be used to enforce a culture, instead they should be a reflection of a shared culture and understanding. So for the time being, these are just my ideas and pieces of inspiration.</p><h4>Accessible and Inclusive Design</h4><p>I decided that as part of the services discovery, I’d start with an ‘expert review’ and audit of the existing Well website. This is usually a good way to highlight the things that will be crucial for us as we start to design and build new services.</p><p>The key areas I looked at were:</p><ul><li><strong>Design<br></strong>Is the current visual language consistent? Is the content legible and readable? Has the site been built to be responsive or adaptive to various devices? and how does the design and user interface perform in certain contexts of use?</li><li><strong>Accessibility<br></strong>Does the current website present any barriers to our users? Given our business, our services are for people from all walks of life and we should strive to make our services accessible to all, no matter what their health condition, impairment, background or disability.</li><li><strong>Web performance<br></strong>How fast does the site respond to our users? Does it load in an acceptable time that will keep people happy and able to do what they need? What are the key performance and user experience metrics for the current site? <a href="https://developers.google.com/web/tools/lighthouse/audits/first-meaningful-paint">Time to first meaningful paint</a>? What is the homepage <a href="https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index">SpeedIndex</a>? (not just Time to first byte or the time to document complete).<br>Are we being considerate with people’s bandwidth? (mobile data bills are expensive!)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtmzIT9hkzEIMLb4uS-ERA.jpeg" /><figcaption>Board used to present back some of my findings</figcaption></figure><p>I wrote up the detailed findings, shared them with the discovery team and at Show &amp; Tells. If you are not sure what some of the above means, follow <a href="https://medium.com/u/cdc6092eb8ab">Well Digital</a> as future blog posts will explain more.</p><p>I will quickly focus on accessibility because I was super happy to see the Show &amp; Tells videos were already being captioned. It is one small example of good accessibility practice.</p><p>I asked about this and people knew it was important for people that are deaf or hard-of-hearing.</p><p>However I want us to go further and to <strong>think about more than just physical impairments</strong>.</p><p>It is crucial to know that where, when and how our products are being used can present barriers to all us that can be avoided by good design and accessibility choices.</p><p>The Show &amp; Tell videos for example, might be accessed by staff on computers with no speakers or in the store environment where headphones or playing sound is not appropriate, those people will be included simply by the use captioning in the videos.</p><p>We will be blogging and sharing more about accessible and inclusive design here at Well you can also <a href="http://twitter.com/well_digital">follow Well Digital on twitter</a> to keep up to date.</p><h3>Summary</h3><p>Its been a busy and exciting month. I’ve learnt a lot, I’ve been trusted to get on and do the right things and already made new friends.</p><p>I’m grateful to Dan Sheldon and Chris Ellett for the opportunity to join Well at this point in its history, I hope to make a contribution because its work that really matters, to our customers, colleagues, to Well as an organisation and perhaps to the NHS and the industry as a whole.</p><h4><strong>Footnotes</strong></h4><ul><li>Like the sound of the work we’re doing? <a href="/service/mailto:digital@well.co.uk">Email us</a>.</li><li>You can <a href="https://github.com/welldigital/design/tree/master/posters">download posters from our github repository</a>.</li><li><a href="http://twitter.com/paulmsmith">Follow me on twitter</a> to ask questions or challenge things I’ve said here.</li><li>Big thank you to Sam Schofield, Edith in HR, Gary &amp; Zoey in Front-of-house, and to Ben Lingard &amp; Matt Lindop of IT. All of whom I’ve pestered multiple times for assistance. 👏</li><li>Printers really are a pain <em>everywhere</em>.</li><li>Start with a cup of a tea and go from there.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=134ad67fcfb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/well-digital/joining-well-digital-134ad67fcfb0">Joining Well Digital</a> was originally published in <a href="https://medium.com/well-digital">Well Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leaving DWP Digital]]></title>
            <link>https://medium.com/@paulmsmith/leaving-dwp-digital-8daf587a0a0f?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8daf587a0a0f</guid>
            <category><![CDATA[dwp-digital]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[well-digital]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Mon, 14 Aug 2017 06:46:33 GMT</pubDate>
            <atom:updated>2017-08-14T06:46:33.041Z</atom:updated>
            <content:encoded><![CDATA[<p>At the end of August I will be leaving The Department for Work and Pensions (DWP) having been there almost two years.</p><p>It is not a decision I took lightly, I’ve been asked quite a few questions as to why I’m leaving and what I’m doing next so I thought it was worth sharing some of the detail.</p><h4><strong>Too long, didn’t read (TL;DR)</strong></h4><p>The DWP Digital User-centred design team is great. I really enjoyed working there and love the people. They do great work, put up with a lot and are on the road to benefitting citizens with the work they’re doing. I’m proud to have been part of it and would go back in the future.</p><p>I’m joining <a href="http://digital.well.co.uk/">Well Digital</a> as their Senior Digital Designer. I’ll be part of the founding team of Well Digital. I’m looking forward to playing a role in shaping their principles, priorities and design approach. I’ll be helping to make user centred design part of the way they do things.</p><h3>My time at DWP Digital</h3><h4>Why I joined DWP</h4><p>Firstly to be hired by <a href="http://benholliday.com/">Ben Holliday</a> as a Front-end Developer to join the design community he was striving to build was an opportunity not to be missed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3JHD7mF5Sj-v6c2sR-eKA.jpeg" /></figure><p>I was a ‘freelancer’ when the chance to talk to Ben came along. Having worked at the BBC and for various prominent digital agencies I managed to carve out a good reputation and a consistent flow of work. I was happy, the work was challenging, pressured but financially and emotionally rewarding.</p><p>I remember commenting to my family, the only thing that would make me consider going ‘full time’ again would be the type of work I’d been admiring from afar, that was the work of the Government Digital Service (GDS).</p><p>Reading the blog posts of people like <a href="https://gds.blog.gov.uk/2013/05/01/govuk-in-pictures/">Tom Loosemore</a>, <a href="https://gds.blog.gov.uk/2012/07/05/a-few-notes-on-typography/">Ben Terrett</a> and friends. It felt like government had awoken from it’s slumber and not only that, they had started doing the kind of thinking that my part of the digital industry wasn’t (at the time).</p><p>GDS were focussing on users and really understanding their needs, failing fast by prototyping, working agile and making decisions that were based on evidence (<em>both data and research with users</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbiOmjrRrOE9erceoiB3Tw.jpeg" /></figure><p>Those ways of working, combined with the scale of the challenge felt like ‘work that matters’ and worth taking a drop in salary for.</p><p>The chance to do work that helps everybody, even family members that depend on (or have to use) government services is what I wanted.</p><p>I kept an eye on what was happening in government and <a href="http://twitter.com/hashtag/govdesign">#govdesign</a> in general. Eventually I spoke to Ben, I was interviewed and Ben took a chance on hiring me.</p><h4>Being a civil servant</h4><p>One of the first things I learned about being a civil servant is that although the majority of things take time, occasionally change happens very fast and with little or no warning. I naively thought DWP and government would be the picture of a stable working environment but it has actually been quite turbulent.</p><p>The section of DWP I joined (the Business Transformation Group) was disbanded after my first six months, senior leaders left (or changed roles), teams of contractors were let go and whole services, live or in development were ‘paused’ or retired.</p><p>When Ben hired me, it was to be based in a Manchester office that he was told would be opening very soon (end of 2015). This turned out to be a complicated saga, with slated offices falling through and the move being off and then on again multiple times. This made getting a design team established in the North West rather difficult and affected the work I had the opportunity to do.</p><p>A lot of these things are normal in large enterprise organisations but perhaps not in such a compressed time frame, if you factor the EU referendum (‘Brexit’) and general elections into the mix, they all go towards demonstrating that <strong>civil servants need to be very resilient and resourceful people</strong>.</p><p>I learnt quickly that I needed to be the same. I wanted to do as much as I could to help Ben and the design team, as well as the DWP service teams I was working with.</p><h4>Highlights</h4><p>20 months working in government has given me the opportunity to work with some truly brilliant people. It would be unfair to name individuals (and a rather long list) so I’ll just say a huge thank you to everybody I’ve worked with.</p><p>The following is a list of things I’ve done and achieved whilst in gov:</p><ul><li>Conducted accessibility testing and audits for my service teams. Meeting users with various assistive technologies to understand how they work and the barriers presented to them (and importantly what we could do about it). Meeting some remarkable people around the country in the process.</li><li>Part of a design sprint for DWP at the treasury building in conjunction with PolicyLab <a href="https://openpolicy.blog.gov.uk/2016/11/21/bringing-together-policy-and-digital-design-teams/">that brought together policy and digital design teams</a> to see if we could prototype and learn about the potential affect of work &amp; health related policy.</li><li>Being part of the Cross Government Design Systems Working Group, helping to define standards for better collaboration between departments on building reusable design patterns, components and front-end code.</li><li>Working with the Stockport based, ‘Prove you can apply’ service team. A small team lead by Rachel Woods that is doing an excellent job of assisting the rollout of Universal Credit, saving citizens time and the government money.</li><li>A committee member for “One Team Gov”. I built <a href="http://oneteamgov.uk/">the website</a> and helped to make a one day unconference event become a global public service movement.</li><li>As a front-end developer I was an early pilot user that helped GDS to develop an <a href="https://designnotes.blog.gov.uk/2017/04/20/were-building-an-autocomplete/">accessible and reusable ‘Autocomplete’ component</a> that links with open ‘register’ data. (Well done Theo, Ed and team!).</li><li>Wrote for the GDS Design Notes blog about ‘<a href="https://designnotes.blog.gov.uk/2017/03/24/doing-the-hard-work-to-make-things-open/">Doing the hard work to make things open</a>’ where I make the case for teams giving the space and time for designers and developers to contribute to the open source projects they use within government.</li><li>I was nominated by my colleagues for ‘Developer of the year’ at the <a href="http://events.computing.co.uk/digitalleadersawards/static/shortlist">2017 Computing Digital Leaders Awards</a>.</li><li>Gave a talk to fellow designers and developers about the need for a DWP Design System (<a href="https://docs.google.com/presentation/d/1RVebi1INBCDcyyB1r4Wo_LwX35oIHQJFey-7IhYqgB8/edit?usp=sharing">see slides</a>) that aligned with the efforts of others within government.</li><li>Contributed <a href="https://github.com/alphagov/govuk_prototype_kit/pull/200">code</a> and <a href="https://github.com/alphagov/govuk_prototype_kit/pull/219">documentation</a> to the <a href="https://govuk-prototype-kit.herokuapp.com/docs/about">GOV.UK Prototyping Kit</a> used by designers and developers across gov.</li></ul><p>There were many more great things I feel very fortunate to have been a part of in my short but busy time in Gov.</p><p>You will note from the list that I’ve also had the opportunity to work with wider government and the Government Digital Service. This was brilliant, I loved that I could look sideways and not to be confined to the landscape of DWP. We’re all <a href="http://oneteamgov.uk/">One Team Government</a> after all.</p><h3>Why am I leaving?</h3><p>As a friend of mine put it, when an opportunity arises most people will take it if there is a bit of push <em>away from their current role</em> and a decent amount of pull <em>towards the new role</em>.</p><h4><strong>The push</strong></h4><p>In all honesty there is very little, the senior design leaders Ben has put in place are picking up the baton to continue getting things changed and I’m confident they will. (<a href="http://www.hollidazed.co.uk/2017/05/30/leaving-dwp-digital/">Ben is leaving as well</a>). Briefly here are the things that were push factors for me.</p><p><strong>‘Front-end Developer’ is not officially recognised as a specialist role<br></strong>The government is currently undergoing ‘digital transformation’, as part of that a ‘Digital, Data &amp; Technology’ skills framework (known as DDAT or ‘<em>Dee-Dat’</em>) is being developed for the ‘<a href="https://www.gov.uk/government/publications/functional-model-for-more-efficient-and-effective-government">civil service functional model</a>’.</p><p>The DDAT doesn’t specifically recognise the role of front-end developer in their <a href="https://www.gov.uk/government/publications?departments%5B%5D=digital-data-and-technology-professions">list of published distinct specialist roles</a>.</p><p>This to me, meant an uncertain path of career progression and personal development. It affects the ability to move off a ‘digital allowance’ scheme and onto a ‘specialist pay’ scale. I’ve never been comfortable with the digital allowance scheme, it meant somebody had to put together a business case for part of my salary every year and I didn’t like that.</p><p>However even more importantly, it limits the chance to form a real cross government community of practice in the same way that content designers, user researchers and so-on have started to do.</p><p>I’ve spoken to people in government about it and it’s quite a thorny issue. Front-end Development as a practice is often misunderstood, partly because as the digital industry has matured it’s been known under several aliases such as web designer, client-side developer, UI engineer, user experience developer and many others.</p><p>It’s further complicated because the practice of front-end development sits between both design and software engineering, which means it needs a combination of both digital design and software development skills. Some people are closer to design and others feel closer to software engineering.</p><p>I’ve written this up in more detail, in ‘<a href="https://medium.com/@paulmsmith/building-for-everyone-e8194fdc99af"><strong>Building for everyone</strong></a>’, I make the case for specialist user-centred front-end developers in government.</p><p>I joined DWP because it was great to see front-end development’s place in design <a href="https://frontendne.co.uk/talks/making-where-design-and-front-end-development-meet">being taken seriously by Ben Holliday</a>, there are many great front-end developers in Gov and I hope this get’s resolved soon but the uncertainty was a push factor for me.</p><p><strong>Being on the slow train</strong><br>I could detail other push factors that many people across gov would probably recognise when trying to do their jobs, things like getting access to the right equipment &amp; assistive technologies, the choice about technology we use and how locked down it is, etc.</p><p>However I feel positive those issues will get resolved, it’s important to remember that it’s still early days in the DWP ‘transformation’ journey and that things move very slow when dealing with such scale but if the people still there #keepgoing with collective small practical actions then I’m confident these things will change.</p><p>However for myself, a great opportunity came along in the meantime which leads me on to <em>the pull </em>and what’s next.</p><h3>I’m joining Well Digital</h3><p>‘Well’ is the UK’s largest independent pharmacy chain, and the third largest overall, employing over 7,000 people with over 750 pharmacies across the country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*raG6OGqg3Z0XOZtQu5oMfg.png" /></figure><h4>What will I be doing?</h4><p>I’ll be working with <a href="http://www.sheldonline.com/">Dan Sheldon</a> and <a href="https://digital.well.co.uk/@chrisellett">Chris Ellett</a>, as part of what is effectively the founding team of a digital start-up within Well.</p><p>I will be helping to shape their principles, priorities and design approach, I’m excited that my day-to-day will include things like:</p><ul><li>Designing end-to-end, cross-platform services (web, Android, iOS, emails).</li><li>Working in a multi-disciplinary agile team alongside software engineers, product managers and user researchers</li><li>Defining Well’s approach to design and advocating for design across the business</li><li>Creating their unified design system</li><li>Helping to build the Well Digital team, supporting recruitment, identifying good practices to adopt and sharing experiences, e.g. through blog posts, tech talks at conferences etc.</li><li>Making a positive contribution to the Manchester technology community.</li></ul><p>Chris, Dan and the team have already got started and have been working in the open by <a href="https://digital.well.co.uk/">blogging their work</a>. Please follow along and <a href="/service/mailto:digital@well.co.uk">get in touch</a> if you want to know more.</p><p><strong>Thank you,<br>- Paul</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8daf587a0a0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building for everyone]]></title>
            <link>https://medium.com/@paulmsmith/building-for-everyone-e8194fdc99af?source=rss-1eeb5f8a238c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8194fdc99af</guid>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Paul Smith]]></dc:creator>
            <pubDate>Fri, 11 Aug 2017 09:54:47 GMT</pubDate>
            <atom:updated>2022-09-22T10:53:51.718Z</atom:updated>
            <content:encoded><![CDATA[<h4>The case for specialist user centred Front-end Developers within Government and beyond.</h4><p>Recently the Government Digital Service published it’s work on the <a href="https://www.gov.uk/government/collections/digital-data-and-technology-job-roles-in-government">Digital, data and technology career framework</a> (DDaT), which is a common set of roles, skills and career paths, that every government department can use.</p><p>In summary it aims to bring consistency to the multitude of technical roles that exist in the public sector. Many of these roles have a number of different titles, but in reality, the scope and skills are the same.</p><p>I applaud this effort, however the beta version of the framework does not recognise what I believe is a specialist role of ‘Front-end Developer’, instead it has a catch-all role of ‘<a href="https://www.gov.uk/government/publications/software-developer-role-description/software-developer-role-description">Software Developer</a>’</p><p>So this is my feedback and the case for ‘Front-end Developer’ to be recognised as a specialist role and to be part of the user centred design ‘cluster’ of the framework, alongside roles like ‘Content designer’, ‘Technical writer’, and so on.</p><p><strong>UPDATE: </strong><a href="https://www.gov.uk/guidance/frontend-developer"><strong>Frontend Developer is a specialist DDaT role</strong></a><strong> now! Well done to all who made it possible.</strong></p><h3>Why? Some soul searching</h3><p>The first question I asked myself when reading the DDaT Framework is how did this get missed? or did it, was it a conscious choice not to split this out as a specialty? if so, why?</p><p>Before I went knocking on doors, it lead me to question my own perspective for the reason why this didn’t feel right.</p><h4>Is it my background?</h4><p>I come from a digital agency and commercial media production background, where those businesses need specialist front-end developers to achieve high fidelity designs that create immersive customer/audience experiences.</p><p>One of the last things I worked on prior to joining government was the relaunch of lexus.eu with my last project being to create a <a href="https://www.lexus.co.uk/car-models/rx/rx-house/">Virtual video tour of the new model Lexus RX</a>.</p><p>If you asked a ‘full stack’ software developer in my previous places of work to do that, to stop writing ASP.NET and start working with the HTML5 media element api, they would point to a front-end developer and say that they are better placed to do that work, do it well, on budget and within a given timescale.</p><p>Of course I’m not saying that a full stack developer isn’t capable of doing that type of front-end development but it’s a level of mastery that takes deep knowledge and experience which is maintained over time. It’s not something you can effectively ‘dip into’ as and when the need arises.</p><h4>Are my expectations for the practice of Front-end development within government too high?</h4><p>Browsers bugs, quirks, accessibility, debugging tools, client-side performance, a multitude of devices and assistive technologies are hard issues to keep up with, a person with broad but not very deep working knowledge of front-end development would struggle in my previous world <em>but</em> is that the level required in the public sector?</p><p>I think that depends on what we want to to achieve and where in the process the Front-end Developer is placed, we might not be building highly interactive or immerse user experiences like Lexus but upon reflection my expectations for ‘front-end’ are not too high and I believe our challenges are far greater.</p><h3>This is for everyone</h3><p>When I thought about it more, I arrived at why I joined DWP in the first place. I joined because if there is one place I should be able to truly do what’s right for the user then surely it’s when I’m developing for public services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*GhEps_dk7LNtQgDsRzWwjQ.jpeg" /></figure><p>In the commercial world, users are often divided into target markets or demographics. Limited time and resources mean it doesn’t make business sense to cater for people that are unlikely to want your products or to use your services.</p><p>As a front-end developer this often lead to difficult conversations about the degree to which something could or should be accessible or which browsers and platforms did we ‘care about’.</p><p>Progressive enhancement to some people (thankfully becoming less over time) became synonymous with being ‘boring’ , ‘safe’ and even ‘avoiding work’.</p><p>However in government our users often don’t have a choice about interacting with us but more importantly <em>those people can be anybody, from any walk of life</em>. They can be people on old computers, new computers, phones, disabled people with Macs, Linux machines, games consoles, in public libraries, even Fridges! You get the point, the list is endless.</p><p>So in government we should never write-off a proportion of our users as not warranting consideration. This in my opinion instantly deepens the level of knowledge and experience required for a front-end developer in government.</p><h3>Software Pioneering to Front-end Town Planning</h3><p>I realise that the DDaT framework is not asserting there is no such thing as a ‘front-end developer’ specialism and I work in a section of DWP lead by Ben Holliday, which very much recognises front-end specialists.</p><p>In 2016 the lead developers at GDS blogged <a href="https://gdstechnology.blog.gov.uk/2016/05/12/our-approach-to-frontend-and-backend-development/">their approach to frontend and backend development</a>, making some great points but I feel their primary concern was to ensure departments can be ‘agile’ which leads me to Simon Wardley’s excellent notion of Pioneers, Settlers and Town Planners (<a href="http://blog.gardeviance.org/2015/03/on-pioneers-settlers-town-planners-and.html">#1</a>, <a href="http://blog.gardeviance.org/2012/06/pioneers-settlers-and-town-planners.html">#2</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*xs_A0H7CMMT3tBikKVGoxw.png" /></figure><p>Simon’s model is a powerful tool for helping individuals find their purpose and working agile means you need those ‘pioneers’ who have broad skills and are good at exploring, good at implementing the organisational needs to make things work together.</p><p>But that’s an entirely different (but equally valuable) mindset to that of what I see as a <em>user centred</em> ‘front-end developer’, who are more of settler and town planner.</p><p>I think given how important a skill front-end development is to the delivery of services, I’m concerned that the front-end ‘town planner’ will, in practice, not get the chance to exist.</p><p>People with that deep practical experience will lose their opportunity for continued mastery as a practitioner, they will be swept along because, as the GDS post says, they want the ability to ‘<em>re-assign developers to different projects as the need arises</em>’.</p><p>It’s not just about the level of quality and accessibility we want to deliver to our users. It’s about fostering a community that can implement those things in a way that they become consistent best practice across government and hopefully influence the wider web development community.</p><p>We talk about user needs but we must not forget that other developers and designers within government are users and have needs too. User centred Front-end developers can write code that makes it quicker and easier for full-stack or back-end developers to reuse design or interaction patterns, which makes it faster and easier to create accessible services of a consistent standard.</p><p>I’d like to see government taking the lead on things that the private sector simply doesn’t have the motivation or resource to invest in.</p><p>We should be propagating best practice not just in what we deliver but in how we deliver it.</p><p>After all, specialist front-end developers are the people that ultimately build the result of the other user centred designer’s hard work. Front-end developers create the interfaces our citizens (and civil servants) use, read and click through.</p><h3>Across the pond</h3><p>Lastly it’s worth looking at what others are doing, the best comparison I can see is the US Digital Service and their counterpart 18F.</p><p>Modelled on GDS (the UK’s Government Digital Service). 18F is an office within the US Government’s <a href="https://www.gsa.gov/">General Services Administration</a> (GSA) that collaborates with other agencies to fix technical problems, build products, and improve how government serves the public through technology.</p><p>18F is promoting team best practices across speciality areas they call ‘guilds’. These guilds support their members in whatever way deemed most appropriate by those members themselves.</p><p>So not only do 18F recognise Front-end Developers as specialists, under what they call the ‘Front-end guild’, they have began fostering sub-specialities of <a href="https://pages.18f.gov/frontend/">‘Front-end Designer’ and ‘Front-end Developer’</a>.</p><p><a href="https://github.com/18F/frontend/wiki">Their list of guild outcomes and metrics</a> are great and example of what we in the UK government need to be doing, which is why we should recognise ‘front-end development’ as specialist role and community.</p><blockquote>Thank you for reading. I deliberately didn’t include a ‘TL;DR’.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8194fdc99af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>