<?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 Sophie Dennis on Medium]]></title>
        <description><![CDATA[Stories by Sophie Dennis on Medium]]></description>
        <link>https://medium.com/@sophiedennis?source=rss-f75503ab734------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NU0NTt6LxJSIhqRo.jpeg</url>
            <title>Stories by Sophie Dennis on Medium</title>
            <link>https://medium.com/@sophiedennis?source=rss-f75503ab734------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:14:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sophiedennis/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[No one is reading your emails that carefully – so stop obsessing about them]]></title>
            <link>https://medium.com/@sophiedennis/no-one-is-reading-your-emails-that-carefully-so-stop-obsessing-about-them-46767f82a57b?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/46767f82a57b</guid>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sat, 25 Feb 2023 17:38:04 GMT</pubDate>
            <atom:updated>2023-02-25T17:38:04.579Z</atom:updated>
            <content:encoded><![CDATA[<p>If I could go back in time and give my younger self some advice, I would definitely tell her this: stop obsessing over your emails; no one is reading them that carefully. Just send the damned thing.</p><p>We were putting together some comms for senior leaders today. The team gave some really good feedback on the draft.</p><p>Which I ignored.</p><p>Not because it wasn’t good feedback. It added richness and colour to what we were saying. It made some good extra points which may be useful to land. But honestly, no one who gets these emails is going to read them that carefully. We just didn’t need to wordsmith this stuff that much. We just needed to get it clear, make sure they could quickly grasp what we wanted them to do and GET IT SENT.</p><p>Once upon a time I would have spent hours on this kind of email. Especially for sending to someone senior. I would have obsessed over every sentence, carefully crafting it to be Just Right. Reflecting on every word. I’d have got several people to check it for me, and gone through several rounds of revisions.</p><p>(I blame 4 years spent over analysing sentences for an English Literature degree, and 2 years as an early-career editor.)</p><p>What I’ve learned – not least now I’m myself the typical busy senior leader with way too many emails – is that people just aren’t reading your emails that carefully. They may not even be reading it themselves at all. Their PA is reading it, or they are forwarding it on to someone else in their team.</p><p>Be clear on what the message is about. Be clear what you want them to do about it. So long as you nail that you’re good.</p><p>What’s more, carefully crafting every sentence is not going to stop people misreading your email. Cos they are just not going to read it that carefully. They’re going to skim it over coffee, or while multi-tasking during a boring video call, or while ploughing through the 50 messages that have built up in their inbox while they were in the non-boring meeting that are now standing between them and getting to finish for the day at a non-stupid hour. And you know what? If they do misread it, it’s not the disaster you think it is. If they’ve not quite grasped your point or got the wrong end of the stick then you’ll probably get to find that out. And then you can correct it. This isn’t your only chance. You can follow up! You can reply to their reply! You can fix it in the meeting! You can send the email that says “Hi, a few people have pointed out that I wasn’t quite clear in my last email…”.</p><p>Most of the time it’s much more important to get the damn thing sent, than to express it all perfectly.</p><p>Especially if you’re asking someone to do something. The sooner you ask them to do it, the sooner it’ll be done. Velocity beats perfection every time.</p><p>My younger self would be horrified at how quickly I bash out emails these days.</p><p>I’d tell her: You can spend hours carefully crafting every sentence so your meaning and intent is perfectly expressed. But they’re just not going to read it that carefully. Spending hours carefully drafting and redrafting isn’t worth it. There are so much more valuable things you could be doing with your time. Just get it Good Enough. And hit “send”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46767f82a57b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What we’re looking for at Service Design in Government 2019]]></title>
            <link>https://medium.com/@sophiedennis/what-were-looking-for-at-service-design-in-government-2019-df8308f42d67?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/df8308f42d67</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[public-speaking]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Fri, 21 Sep 2018 17:09:24 GMT</pubDate>
            <atom:updated>2018-09-21T17:09:24.170Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m Programme Chair for the international Service Design in Government conference next year. Now in its sixth year, it’s a hands-on, practical event for anyone involved in designing and delivering better public services. It remains probably the leading event of its kind, and draws people from around the world.</p><p>I’m on a mission to get you to come speak at it.</p><p>People often ask “I’m doing X, I’m not sure that’s what you’re looking for?”. Usually my answer is “yes it is!”. So I thought I’d dispel a few misconceptions that come up about the conference, and share a bit more about some things we’re particularly looking for for 2019.</p><p>I’ve also shared <a href="https://medium.com/@sophiedennis/how-to-find-something-interesting-to-share-at-a-conference-and-how-to-pitch-it-to-me-ff32907fdf27">my top tips for deciding what to talk about</a> if you don’t know what to talk about, the kinds of sessions that tend to work well, and how to write a good proposal.</p><h3>It’s not just “government”</h3><p>Don’t be put off by the “government” bit of “service design in government”. It’s for anyone designing and delivering better public services, regardless of whether the organisation doing it is “of the government”. So not just central government, but also:</p><ul><li>Healthcare</li><li>Arts and cultural institutions</li><li>Local and regional government</li><li>Charities</li><li>Community organisations</li><li>Non-profits</li><li>Arms-length bodies</li></ul><p>Think broad ‘tech for good’ type stuff. Only not just tech.</p><h3>It’s not just for “service designers”</h3><p>You also don’t have to be a service designer! Designing better services involves lots of people in lots of different roles. If you are doing that in a way that’s user-centred, thinking about systems, and making an impact, we’d love to have you.</p><h3>Where next for service design?</h3><p>This is sort of the underlying theme for Service Design in Government 2019.</p><p>I particularly want to see more about <strong>asset-based approaches</strong> next year. Shout out to Steve Lee for his great workshop on asset-based community development at this year’s conference. I really believe this is the next step for service design. Delivering change <em>with</em> communities not just <em>for</em> communities. Genuine co-production (not just co-design workshops!). Listening over consultation, etc… If you have a case study to share on this, PLEASE SUBMIT IT!</p><p>Good sessions tend to fall into three main types:</p><ol><li>solid tutorials on core skills</li><li>case studies</li><li>cathartic problem-sharing</li></ol><p>Tutorials can be solid “[subject] 101” stuff, or things that help established practitioners deepen their practice with a deep dive into a particular area we could all get better at.</p><p>I also always love the opportunity to practice a technique or learn a new workshop method. It’s all very well reading about a particular workshop technique or analysis approach in a book, it’s another thing to have the confidence to actually do it — and practicing in a safe environment really helps.</p><p>For case studies what’s come out really strongly in the feedback over the last couple of years is that people aren’t interested in yet another “hey we did some prototyping and codesign and here’s the pretty service blueprint” case study.</p><p>A lot of our participants are experienced practitioners who already know all about prototyping, and service blueprints, and the double diamond. What they want is time to reflect and chew on “where next?” with their peers, and to deepen their practice in ways that will help them affect actual change on the ground. And we all appreciate the reassurance of learning we’re not the only ones finding this hard.</p><p>We want case studies — and tutorials and workshops — that talk about how we turn all this lovely service design-y stuff into actual delivery. All the prototypes and codesign and blueprints in the world are useless if they don’t translate into actual change in how services are delivered, and actual change in the real-world outcomes for people. Doing that is hard. It doesn’t matter if you’re not quite there yet or it hasn’t all gone swimmingly. Just sharing the challenges is useful.</p><p>Though if you can bring evidence of impact then so much the better.</p><p>There’s still room to share your awesome, interesting discovery work of course. But I expect we’ll be more interested if you’re sharing:</p><ul><li>deep insight into the problem space. So not the methods, but what you learned about users, organisations and what’s really going on with them and what they need that would be useful to other people working on a similar problem</li><li>how you adapted common methods or deliverables to the particular problem space, or people you were working with, in ways other people can learn from</li><li>some kind of evidence of outcome or impact — or at least how you are working to get the discovery work taken forwards</li></ul><p>Finally cathartic problem-sharing. You don’t have to have all the answers. Some of the best sessions are where someone facilitates a workshop where people just get together to share how they’re trying to tackle a particular problem. Where else will you get over 300 of your peers in the same place to all help each other figure out how to do this stuff?</p><h3>Still room for basics</h3><p>We still want some solid “service design 101” talks that teach core methods to product managers, content designers, policy makers and others who want to use more service design techniques in their work. Not everyone who comes is a world-leading expert. We get plenty of people for whom service design is part of their role, but not actually their job, and who want to learn more about how to use the methods in their work. We have lots of people who are just getting started.</p><p>People are generally working in larger teams — there’s not so much “UX team of one” (though there is in some smaller organisations), and the message to “start with user needs” and idea of agile ways of working is pretty well established, if not always practiced.</p><p>So don’t get too basic. In your day to day work you may spend a lot of time explaining basic concepts of user-centred design, agile ways of working, discovery/alpha/beta and ‘being digital’ to your colleagues. You don’t need to spend time explaining these things at Service Design in Government. I’ve made this mistake myself in the past. These are Your People! Yes please share how you are getting these ideas embedded in your organisation, or great ways you’ve found to explain them simply to other people. But you don’t need to spend time explaining core concepts.</p><h3>What you’ll get, expenses, code of conduct, etc…</h3><p>Full details of what you get as a speaker — which most importantly includes a full pass to the whole three day conference, as well as travel expenses if you don’t have an employer who’ll cover them — is in the <a href="https://govservicedesign.net/2019/submitter-information/">information for submitters</a>.</p><p>If you’re still not sure what you can talk about, or what to include in your proposal, then my other post on <a href="https://medium.com/@sophiedennis/how-to-find-something-interesting-to-share-at-a-conference-and-how-to-pitch-it-to-me-ff32907fdf27">how to find something interesting to share at a conference — and how to pitch it to me</a> will help.</p><p>The call for speakers is open until 28th Sep — though I have it on good authority that the form will keep working until midnight on Sunday 20th September. You can <a href="https://ureview.firebaseapp.com/proposesession/sdingov2019">submit your session here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df8308f42d67" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to find something interesting to share at a conference — and how to pitch it to me]]></title>
            <link>https://medium.com/@sophiedennis/how-to-find-something-interesting-to-share-at-a-conference-and-how-to-pitch-it-to-me-ff32907fdf27?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff32907fdf27</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Fri, 21 Sep 2018 17:03:43 GMT</pubDate>
            <atom:updated>2020-09-24T13:36:42.788Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As Programme Chair for both </em><a href="https://2020.manchester.uxinthecity.net/"><em>UX in the City: Manchester</em></a><em> and </em><a href="https://2020.govservicedesign.net/"><em>Service Design in Government</em></a><em> I hear from lots of people that they aren’t sure sure what they could speak about, what would make a good session, or what to include in their proposal. So here is my collected advice on how to pick a good talk topic, and what I look for when reviewing submissions.</em></p><p>This post was originally written during the open call for speakers for the 2019 conferences.</p><h3>Trust me, you have something to share</h3><p>Lots of people tell me they’d like to try speaking at a conference, but don’t think they have anything interesting to share. Every time, within five or ten minutes we’ve found at least one really useful thing they could talk about — if not several.</p><p>There’s this belief that everyone at the event will be either as or more experienced than you. This isn’t true! There will always be people who are further behind on their journey than you are. We’re all learning all the time, and love to hear about how other people have dealt with the kind of situations we find ourselves in.</p><p>Here’s how to get over this hump:</p><ol><li><strong>Think back to a year ago. What do you know now that you wish you’d known then?</strong> There’s your talk. There will absolutely be people in the audience who are where you were a year ago. <br>This does not need to be ground-breaking. Share how you’ve taken a technique or method from someone else and made it work, and what you learned in doing that which wasn’t obvious from the stuff you’d read or heard.</li></ol><p>If you’re a bit more experienced, another way to think about this is:</p><ol><li><strong>What advice are you often asked for or do you often give to people you work with?</strong> There’ll be lots of other people keen to learn from you too, and lots more people who have exactly the same questions.</li><li><strong>What issues do you talk about most with your peers and what tips and advice do you share with them</strong>, or have you found most useful? There will be lots more people just like you at the event who will be in a similar position and will value your perspective. If nothing else it’s always reassuring to learn we’re not the only ones finding something hard!</li></ol><h3>It doesn’t have to be for everyone</h3><p>These are multi-track conferences. That means your session doesn’t have to be suitable for everybody. If it’s not right for someone they can just go to one of the two or three other sessions that are on at the same time.</p><p>Better your session is really relevant to a specific section of the audience, than vaguely interesting to all of them.</p><p>For both events, we get a mix of experience levels.</p><p>At UX in the City: Manchester we have a core group of ‘UX professionals’. They may be in a specialist research/design/content role, or a generalist “UXer”. We also get quite a lot of the “UX curious” — people who are developers, designers or whatever, who are passionate about making things work well for users, but don’t have formal responsibility for UX design. Some people are working in mature organisations with large, dedicated design teams, but there are also lots of people struggling with the challenges of being a UX team of one. Not everyone is working “agile”.</p><p>Much of this also applies to Service Design in Government. Yes I want sessions that speak to experienced service designers who want to deepen and extend their practice. But we also get plenty of people for whom service design is part of their role, but not actually their job, and who want to learn more about how to use the methods in their work. People are generally working in larger teams — there’s less “UX team of one”, and the message to “start with user needs” and idea of agile ways of working is pretty well established, if not always practiced.</p><h3>Types of session</h3><p>For both conferences I’m looking for:</p><ol><li>solid tutorials on core skills</li><li>case studies</li></ol><p>Tutorials can be solid “[subject] 101” stuff, or things that help established practitioners deepen their practice with a deep dive into a particular area we could all be better at. The latter are particularly useful and well received.</p><p>I also always love the opportunity to practice a technique or learn a new workshop method. It’s all very well reading about a particular workshop technique or analysis approach in a book, it’s another thing to have the confidence to actually do it — and practicing in a safe environment really helps.</p><p>For case studies, these are best when they share:</p><ul><li>how to apply and adapt a technique to work in the ‘real world’</li><li>what you learned about a particular kind of user, design problem or technology, and how it’s applicable to other people and organisations</li><li>how doing all this great user-centred digital service design-y stuff has made an impact on your end-users or your organisation’s bottom line. Stuff people can point to with their bosses to say “look! I am not a crazy person! This stuff actually works!”</li></ul><p>You don’t have to do all three.</p><p>Here’s some more advice on <a href="https://medium.com/@sophiedennis/what-were-looking-for-at-service-design-in-government-2019-df8308f42d67">what we’re looking for at Service Design in Government in 2019</a>. Tl;dr: if you’re wondering if what you are working on is relevant, the answer is probably “yes”.</p><h3>Writing your proposal</h3><p>Eventually your session description will end up in the programme, but right now I and my fellow session reviewers are your audience. So write your proposal for us — you can always amend it later for participants.</p><p>The questions I’m asking myself when reviewing your session are:</p><ul><li>Will anyone be interested?</li><li>Will they learn something useful?</li><li>Does this person know what they are talking about?</li></ul><p>The last one is really hard. We blind review. That means I don’t see your name or bio when marking your session. I don’t know anything about your background or experience. The only thing I have to go on is the title and description. So that session description has to demonstrate that you know the subject matter and that the insight you have to share is robust and valid. The best way to do that is to tell me exactly what that insight and advice is going to be.</p><p>Top tips for your proposal:</p><ol><li>Don’t be coy! Clever titles and ‘I’ll share my top 3 secret tips’ might work in the programme, but when blind reviewing your submission the more detail you can give me the better. Be specific. I want to know what those top 3 tips actually are.</li><li>It doesn’t have to be most perfectly crafted marketing copy. Just be really clear, coherent and straightforward about what you’ll cover.</li><li>Try writing “People will learn:” and then follow it with 3 to 5 bullet points that simply set out what people will take away from the session. Keep it practical and clear.</li><li>If you find yourself writing something that sounds a bit like “people will learn how awesome I / my agency / my product is and why they should pay me all the money” then you have a sales pitch, not a conference session. We’ll probably pass.</li><li>You can always revise the description before it’s published if you worry the description is too long or gives too much away that you want to save for your Big Reveal.</li><li>Longer is better than shorter. Unlike some events we don’t have any word limit on the long form of your session description. We want as much detail as you can give us about what you’ll talk about. While I don’t hugely appreciate wading through a 1000 word case study, that’s better than getting a single paragraph.</li></ol><h3>Picking a session type and length</h3><p><em>The following is a bit specific to the session types offered by the UX, Service Design and Agile conferences run by Software Acumen, but may be relevant to other events as well.</em></p><p>Don’t sweat it. No really. I used to agonise over which session type was the best fit, or whether my session really fitted into the types described. Don’t worry about it too much. I’ve discovered this is the least important piece of information as far as I’m concerned. What we really need to know is whether to put you in a room with chairs in rows (“theatre style”), or with people sat around tables (“cabaret style”). So just pick the one that seems best. ‘Case study’ and ‘tutorial’ are probably the simplest defaults. If none of them fit that’s fine. We’re always open for people wanting to do something a bit different.</p><p>We have four session lengths:</p><ul><li>45 minutes</li><li>60 minutes</li><li>90 minutes</li><li>3 hours (150 minutes, with a half hour break)</li></ul><p>45 minutes is great for a talk or a tutorial with one or two really quick exercises.</p><p>60 minutes is fine for talks as well, and will let you really go deeper into a subject. It’s also perfect for a short workshop or hands-on session. A good 60 minute workshop format is a 15 minute introductory talk-y bit, then two 10–15 minute group exercises that get people to apply what they’ve learned, then a wrap up. It’s good for something focused on a specific skill, or as a taster session.</p><p>The 90 and 150 minute slots are both for more in-depth workshops. We don’t ask our participants to sit through 90 minutes of someone just talking. 90 minutes gives you time to include a longer exercise. The 150 minute slot is basically a 3 hour half-day session with a break in the middle.</p><p>If your session could suit a couple of different lengths — for example if you could present it either as a talk, or as a more interactive workshop — then mention that in the description. Once all the sessions are reviewed and we’ve got a shortlist, myself and our Event Producer sit down and play tetris with the schedule, trying to work out how to fit everything in to the slots we have. So it’s always useful to know if something might suit a shorter or longer slot. I’d suggest you submit it once in your preferred format, but clearly say that you’d be happy with a different length slot. But if you’d rather submit it twice — perhaps to give more detail on what a workshop version would cover — then that’s fine too.</p><p>Phew! I think that’s my collected advice on submitting to conferences done. Let me know in the comments or on <a href="https://twitter.com/sophiedennis">Twitter</a> what other questions you have. But most importantly…</p><h3>Submit your ideas!</h3><p>UX in the City Manchester<br><a href="https://2020.manchester.uxinthecity.net/">https://2020.manchester.uxinthecity.net/</a></p><p>Service Design in Government<br><a href="https://2020.govservicedesign.net/">https://2020.govservicedesign.net/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff32907fdf27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to run a regular design team meeting]]></title>
            <link>https://medium.com/@sophiedennis/how-to-run-a-regular-design-team-meeting-b67b8fe2a8be?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/b67b8fe2a8be</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 12:19:38 GMT</pubDate>
            <atom:updated>2019-03-28T17:14:02.469Z</atom:updated>
            <content:encoded><![CDATA[<p>Holding a weekly team meeting is a common tactic for building a community of practice. Booking a room and picking a time each week to get together for an hour with others working in the same discipline is a pretty low-friction way to get started.</p><p>But having attended and run a lot of these meetings, I’ve found there is a big difference in how purposeful and productive they are. A talking shop and forum to air problems is definitely better than nothing. But if you really want to grow and develop as a professional community, you need to introduce aspects of deliberate and reflective practice into your sessions.</p><p>I thought I’d share the structure I came up with for the weekly design team meetings when I was interim Head of User-Centred Design at Land Registry, in case it helps other teams get more from their get-togethers. I doubt it’s perfect. But it is simple and easy to remember (and hence to use). And we definitely found our meetings were a lot more productive when we followed the pattern than when we didn’t.</p><h3><strong>A simple formula for a more productive design team meeting</strong></h3><p>The meeting splits into 3 parts:</p><h4><strong>1. Updates</strong></h4><p>2 mins for each person to share:</p><ul><li>what they did last week</li><li>what they’re doing this week</li><li>have they got any work to share and show</li></ul><p>Use a timer — if you don’t you’ll over run.</p><p>Capture anything that might need more discussion on a post it and stick it up on the wall (or use a whiteboard, flip charts or virtual equivalent). Just write the topic. Don’t discuss yet. Try to group as you go to save time at step (2).</p><h4><strong>Review topics</strong></h4><p>Quickly recap the topics that came up in step 1. Check if there’s anything else anyone wants to throw into the pot. If you have a big team or a lot of topics you could dot vote on what to discuss and what you’ll leave to a later meeting.</p><p>But don’t get sucked into discussion now, leave that until after…</p><h4><strong>2. Show The Thing (critique)</strong></h4><p>This is a chance for anyone to share what they are working on. To make best use of the time I recommend one person share one thing each week, rather than everyone sharing. But a couple of things can also work.</p><p>Sometimes there won’t be anything anyone wants to share and that’s OK. Just try not to go more than 2 weeks without someone sharing something.</p><p>Most important though: show work in progress. The real value of sharing work with your peers is to get feedback and support. Encourage people to bring the things they are really stuck on and struggling with, not just the things they’ve finished and are really proud of (though do that too).</p><p>This session should be about critique, and learning to give and receive constructive feedback on designs. Keep the meeting a safe environment where people can be open and honest about problems, and get constructive help.</p><p>Although I’ve called this “show the thing” don’t just show’n’ tell. Practice presenting the problem you need to solve, and how you are seeking to tackle it. Encourage people to use the session to get help on a design problem or something they are stuck on. You’ll find this is a great way to quietly grow your skills as a team.</p><p>This is important for everyone whatever their level. But I’ve found it particularly helpful for making sure juniors are getting the support they need, especially when they are largely working on their own (which they shouldn’t be, but we all know it happens). You’ll spot where perhaps someone needs extra help from someone with more experience to tackle a problem or have a difficult conversation with stakeholders. This can be missed when juniors are embedded on a team on their own.</p><h4><strong>3. Discuss</strong></h4><p>Refer back to the list you made in step 1. What issues do people want to discuss? Pick a few to talk about in more detail. This is an opportunity to air problems and discuss as a group how you’re going to respond to situations that affect the whole team.</p><p>This is also where you can mention stuff like events coming up, or anything else that needs a bit longer than the 2min initial update.</p><p>Leave this until the end, as otherwise it’ll take up the whole meeting — and the critique part is more important…</p><h3><strong>Tips</strong></h3><h4><strong>1. Stick to the plan</strong></h4><p>Sometimes I’d relax and not follow the formula so exactly. I’d forget to bring the timer. I wouldn’t capture themes. We’d spend twenty minutes going round and round a problem none of us could actually fix. But I noticed that the meetings weren’t as productive when that happened compared with when we stuck to the formula.</p><p>That said…</p><h4><strong>2. It’s OK to mix it up</strong></h4><p>I think the initial quick go round is essential so you pick up if someone has a major problem. And encouraging someone to have something to show each week, however small, is important for developed a culture of reflection and critique. But sometimes we’d devote the rest of the meeting to a different activity. For example at Land Registry one week we looked at the GDS skills matrix for designers, and where we each thought we were on it. And another time we reviewed the post-it notes we’d written when I first joined, setting out the team’s hopes, fear and goals for design at Land Registry. It turned out we’d made more progress than we thought.</p><h4><strong>3. Celebrate wins and successes</strong> however small</h4><p>Encourage applause and cheers. Give out silly badges and awards (one team member used to draw sheriff badges on post-its with whatever ad hoc award they thought someone deserved that week).</p><h4><strong>4. If it’s turned into a moan-fest…</strong></h4><p>End with a quick round robin where you ask people to call out something good or positive that’s happened. There’s always something. Even if it’s really trivial it will lift the mood, get everyone pulling together and hopefully send people away in a slightly more positive frame of mind.</p><h3><strong>Why it works</strong></h3><p>I did a bit of reflecting on why I think this formula works in writing this post. I think it’s because:</p><ol><li>It makes sure everyone gets a chance to celebrate successes, air concerns and show a bit of what they were working on.</li><li>It helps stop meetings either getting dominated by one person or issue, or turning into moan fest.</li><li>But most importantly: the structure includes time for “<strong>reflective practice</strong>”.</li></ol><p><a href="https://twitter.com/mrbootle">Jason Bootle</a> introduced me to the concepts of deliberate and reflective practice at UX Cambridge 2016 in his talk <a href="https://www.slideshare.net/mrbootle/building-a-reflective-practice-what-we-can-learn-from-elite-sports-ux-cambridge-2016">Building a Reflective Practice: what we can learn from elite sports</a>. Reflecting on his talk, I realised why this formula works is that it turns the meeting into a forum for the team to reflect on their work and how to improve it, not just a talking shop.</p><p>A lot of design team meetings waste this opportunity. They easily become rambling and unfocused. Things descend into a moan-fest about how, yet again, design isn’t being taken seriously. Or one person’s update dominates the whole meeting because they’re tackling a really gnarly problem.</p><p>But having a time to get feedback from your peers is really important when designers are spread across multiple teams in an organisation. They spend most of their time getting critique and feedback from non-designers, rather than the informed peers who can really help them grow. Your regular time together is a precious opportunity for you all to develop your design practice. Don’t squander it.</p><p>So whatever format you use for your design team meetings, if you do nothing else, make sure you <strong>build time for reflective practice into your time together.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b67b8fe2a8be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e14: be kind to the tortoises, dear hares]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e14-be-kind-to-the-tortoises-dear-hares-dbac71344b0e?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbac71344b0e</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[digital-health]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sun, 16 Apr 2017 12:03:26 GMT</pubDate>
            <atom:updated>2017-04-16T12:06:20.907Z</atom:updated>
            <content:encoded><![CDATA[<h4>10 to 16 April 2017</h4><p>A short work week due to Easter was made shorter by spending Monday trying to shake off a migraine. I got a full-on aura on Sunday night which I haven’t had in ages. My usual tactic of taking some soluble aspirin as soon as it came on seemed to do the trick, and I made it to bedtime OK. But when I woke up the migraine was clearly still there. Staring at a computer screen is the thing most guaranteed to bring on a migraine for me — closely followed by stressful meetings. I decided it was better to avoid both, take the day off, and hope that settled everything down.</p><p>Tuesday I went back to work for ceremony day. The migraine still hovered in the background but I made it through. Thankfully it was a light day for me. I had hoped to share some of the survey findings at show and tell but taking Monday off put paid to prep time. I’m off most of next sprint so didn’t have much to do in planning either. My goals for this one are to finish off reviewing the video of last week’s research, analyse and collate insights, playback to the team, and do a summary of that and the survey findings for next show and tell.</p><p>Wednesday I worked from home watching research videos, and seeing feedback from the newly ‘live’ GP profiles roll in. My goal was to rewatch all the session videos from last week. We’re looking at almost the ‘microinteration’ level — exactly how do people interact with elements of the page? is there particular heading or sentence that isn’t clear? That can involve quite subtle cues that are difficult to pick up on in the moment, and patterns that are difficult to spot when the people taking notes change during the day.</p><p>I got through 2 videos last week, got 3 more done on Wednesday and finished the last one off on Thursday back in the office. I’d decided to take the opportunity to also make a kind of rough transcript — timestamped verbatim quotes so I could easily find video examples of interactions later. In all it was a pretty time-consuming process. Probably a couple of hours for each 45 minute session. I think it was worth it as by the end I’d found patterns and findings I wouldn’t have got to just from my own memory of the session and my colleagues rough notes from the day. But I wouldn’t recommend it if high-level findings are sufficient for what you need.</p><p>With hindsight also if I did this again — re-watching all the videos — I’d stick to transcribing onto post-it notes. Having everything in a typed document is handy for some future person wanting to review the sessions, but it made analysis awkward. I did end up doing the last session on post-its, as I didn’t have a second monitor to work on in the office on Thursday. It <em>felt</em> like the note-taking process was also quicker that way. I’m not entirely sure, though if you’re not a quick typist it certainly would be. In the ended I added lots of headings and highlighting to make it easier to scan through the transcript for patterns. I could have printed all the transcripts out, cut them up, and clustered that way. But it would have been quicker and easier to have everything atomised on post-it notes in the first place, and to stick them up on print-outs of the prototype screens as I went.</p><p>All the same I got the insights pulled together in time for Thursday afternoon. The Book a GP Appointment journey is looking good — we just need to make a couple of the ‘next actions’ clearer. Our two low digital skills participants both struggled on the search results page, and were tempted to go back and re-run their search even though they could see there own surgery in the list. One even did exactly that, in one of those unbeatable “<a href="https://medium.com/@IanAmes/user-research-is-the-most-frustrating-thing-ever-a817252014d4">just click the button!</a>” moments you sometimes get in research. It turns out the copy at the top of the page wasn’t clear what they should do next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*o6LyrCXlMQOtm7kaUcDbPg.png" /><figcaption>Jean Luc Picard saying ‘Just click the button!’ courtesy of memegenerator.net and Ian Ames</figcaption></figure><p>On the GP Profiles things are a little more muddy. I think it confirmed that we will need some kind of navigation to orient people with what’s on the page, but it’s not needed urgently as the page is currently fairly short. We have some copy tweaks to make. Then there are the needs people have that we can’t meet with the data and information we currently have. If you’ve worked on ‘digital transformation’ in government you’ll be familiar with that problem. This is where the transformation bit comes in. Good news is that there is a team already working on improving the data. We’ll need to work with them to find better ways to help hard-pressed GP surgeries provide us with relevant, accurate, up-to-date info for patients.</p><p>The basic profile pages are now ‘live’ on the beta site. If you <a href="http://www.nhs.uk/service-search/GP/LocationSearch/4">search for a GP surgery on nhs.uk</a> you should get a yellow strip at the bottom of the page inviting you to view a new version of it. That’ll take you through to a simple version of the new pages we’ve been working on. We’d love your feedback.</p><p>A bit like with the survey the feedback is a bit of a double-edge sword. The pages are so high traffic that we got 200 pieces of feedback left in just 2 days after launch. So brilliant for getting lots of feedback from real users but quite a bit of work to process. Good news though is that from the looks of it so far most of the things people have told us they can’t find are things we know we haven’t included yet. That’s good, because it means our research, and especially the survey we ran in February, has basically been valid. It’s not so good as it confirms we still have a lot of work to do to properly meet the very diverse needs of the people who visit these pages.</p><p>We also spent some time on Thursday looking at ‘what next’ for our team, and I got to spend a bit of time this week on what’s next for me. Hopefully some interesting, more strategic work for NHS Digital. But that does mean I need to focus on finishing things off rather than launching into new research avenues over the next few weeks.</p><p>The migraine continued to bob up and down through the week. Wednesday was mostly OK, but Thursday took its toll. The twin weapons of aspirin and Paramol got me through. I’ve now got over a week off. The long Easter weekend, to finish packing the old house and getting the new one ready for our arrival. Then I’m in Oxford for a couple of days, attending the UX in the City full day workshop on Org Design for Design Orgs with Kristin Skinner, co-author of <a href="https://orgdesignfordesignorgs.com/">the book with the same name</a>. Then we move into our new house on Friday.</p><h3><strong>Metrics</strong></h3><p><strong>Blog posts published:</strong> 1. YTD: 11.</p><p><strong>Country miles walked:</strong> 0</p><p><strong>Meditation:</strong> 3 day run-streak, back on the wagon.</p><p><strong>Reading/listening/watching:</strong> <em>Rogue One</em> of course. Good. Personally I think suffered from the modern blockbuster disease of too much non-stop action and not enough storytelling or character development. I read a review that said the big problem with <em>Rogue One</em> is that it makes <em>New Hope</em> seem sluggish and boring. I felt rather the opposite. Oh for a half hour of droids wandering the desert. I also wish they hadn’t gone for CGI Tarkin &amp; Leia. The tech is still in uncanny valley territory. I think I would have found recasting with new younger actors — as they did with Mon Mothma — personally less disruptive of the ever fragile suspension of disbelief.</p><p>Work wise Dan Hon’s very good post on the <a href="http://tinyletter.com/danhon/letters/s4e10-stages-of-transformation">Stages of (Digital) Transformation (Grief)</a> resonated, reminding us to tread gently if we want to bring the wider organisation with us:</p><blockquote>There will be people who will feel a combination of angry and ashamed and guilty. Angry because they were on a path and it’s being closed off… Ashamed because now they feel their work wasn’t up to what “everyone else” expected. Guilty because they now might see how things could be different and they’re holding themselves up to new standards.</blockquote><blockquote>What I try to remember in times like this is that I’m going to transformation war with the army that I — that the organization — has. No-one is coming to fix it. The team has to own it. But that *they did the best in the environment they had*.</blockquote><p>It reminded me strongly of Dan Barrett’s ‘<a href="https://medium.com/@dasbarrett/being-the-tortoise-38f33a6a7959">Being a Tortoise in a land of Hares and Rocks</a>’. Be kind to the tortoises, dear hares, they’re on your side and making them feel stupid and ashamed isn’t going to get you anywhere.</p><p>On the listening front, to survive the migraine haze driving home on Thursday I cracked open my Harry Belafonte. If I were ever to be on Radio 4’s <em>Saturday Live</em> then Harry Belafonte would be my inheritance track — the one my parents passed down to me. While ‘Matilda’ and ‘When the Saints Go Marching In’ from <em>Live at Carnegie Hall</em> hold a special place in the Dennis household’s collective hearts neither featured on the CD I had in the car. So I’ll leave you with his 1954 version of ‘John Henry’ — one man’s tragic determination to beat the onrushing tide of technological innovation:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYqAfSqY1cig%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYqAfSqY1cig&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYqAfSqY1cig%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6bc662c1b592fe4768050f36f9173674/href">https://medium.com/media/6bc662c1b592fe4768050f36f9173674/href</a></iframe><p>Remember folks: it’s only digital transformation. No need to hammer yourself to death.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbac71344b0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e13: lab, lab, lab… and wild horses]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e13-lab-lab-lab-and-wild-horses-137961170ce3?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/137961170ce3</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sun, 09 Apr 2017 12:39:07 GMT</pubDate>
            <atom:updated>2017-04-09T12:39:07.632Z</atom:updated>
            <content:encoded><![CDATA[<h4>3 to 9 April 2017</h4><p>Monday was my birthday. We totally failed to take the day off from house stuff, so I spent much of it in Ikea and B&amp;Q. Andy bought me an Echo, so at some point I’ll be able to turn off the lights without having to get out my mobile phone. Like living in the future already.</p><h3>Lab, lab, lab</h3><p>The rest of the week was Lab Week — a full-day of user research in a local user research lab on Wednesday, with Tuesday all about prepping for that, and Thursday and Friday all about review and analysis.</p><p>This is the third lab day we’ve run since I joined the team. A rhythm of monthly lab-based research, with field and pop-up research in between seems to be suiting us. Lab research is expensive to run — not just the cost of hiring the facilities and recruiting participants, but also the time it takes from the researcher and the rest of the team. Alternating it with leaner, faster research methods is getting us a good balance of rapid feedback and the more time-intensive benefits of a full day in the lab, like extra time with each person, an unobtrusive observation area for the team, video recording, and targeted participant recruitment.</p><p>The team at Research Helper — the facilities arm of Simple Usability in Leeds, whose lab we often use — also handled participant recruitment for us this time. We had not one but two people pull out at the last minute — one on the day itself. But thanks to their efforts juggling the schedule and finding replacements we still got to talk to a full complement of six users which was brilliant. In my experience some recruiters aren’t that pro-active about checking people are coming and finding replacements, so this earned them a big gold star from me.</p><h4><strong>Book a GP appointment</strong></h4><p>Our focus for this lab was checking whether the changes we’d made since the last lab we ran at the beginning of March had delivered the improvements we were hoping for.</p><p>It was generally pretty good news on that front. The ‘book a GP appointment’ journey was much better. The work the devs have done to help people find their GP surgery first time has really paid off, with everyone successfully finding their own surgery. We’ve also stripped the journey right back to the absolute minimum number of steps, and reduced the amount of explanatory copy. In the last lab the whole flow was clearly much too long. Pretty much every user said they’d have given up and just picked up the phone well before the end. It’s much better now we just get you to your destination as fast as possible. Who knew?</p><p>There’s still work to do on the search. Including generic terms like “medical centre” gives a long list of results, and we’ve also discovered that some people — mostly older users, 50+ — will search for the name of their doctor, not the name of their surgery. We have the data to search by doctor, but will need to figure out the best way to return useful results when someone searches for a “Dr Smith”.</p><p>There was also a little confusion from our low digital skills users. People who are don’t use the web that often don’t necessarily recognise cues for what’s a link, or what to do with a set of search results. We need to make the actions more explicit in a couple of places.</p><p>Book a GP Appointment is now live in Beta (a beta is a trial, or pilot, of a service, but which is nonetheless fully working and ready to be used in anger by people) and you can try it for yourself at <a href="https://beta.nhs.uk/book-a-gp-appointment/">beta.nhs.uk/book-a-gp-appointment</a>. The aim is to provide a clear, simple journey from getting information about a health problem, to suggesting you should consult your GP, to booking that appointment. You can see the full journey in practice on the new <a href="http://beta.nhs.uk/conditions/hand-foot-and-mouth-disease">Hand, Foot and Mouth Disease beta page</a>.</p><h4><strong>GP Profiles</strong></h4><p>We’re still finishing off a few things on the GP practice profiles, but they should be fully public in the next week or so. Again we’ve been stripping them back since the lab in March, and the shorter more concise pages definitely worked better — while still getting comments like “comprehensive” from users.</p><p>We’ll be going ‘live’ with a simple version of the pages, while continuing to work on some of the new IA and navigation concepts as we scale up the amount of information and services they offer. We need to finish analysing what we saw in the lab to decide the best combination of content to use — we tested 3 variations of the page, and each had some strengths. But it shouldn’t be too difficult to combine the best of all 3 into the live page.</p><h3><strong>Team</strong></h3><p>Team wise it’s been a bit of an unsettling time. A lot of colleagues on the team in London left the project at the end of March, including several of the people I was most excited about working with before I joined: Mat Johnson, reviving a small part the old University of Surrey team; Tim Allan and Dom Smith who I <em>very nearly</em> got to work with a couple of years ago and was excited to finally join forces with; Tara Land, former Head of Research at GDS, who I’d never met or worked with before, but proved as true and wise an ally as I’d hoped. I’m really sorry to see them and others go, though with a lot of contractors on the team it was probably inevitable at some point.</p><p>The consolation is, however, the strength of our team up in Leeds. Most of them I didn’t know before I joined, but they’ve proved almost universally to be smart, dedicated, welcoming and collaborative colleagues who it’s a pleasure to work with.</p><p>In particular I probably haven’t given enough weeknote love to our devs before. They continually impress me not just with their dev skills, but also their commitment to taking a user-centred approach to our work — even when what users need makes their work more difficult. They’re always there in the lab or the pop-up research we do, taking notes, badgering me to know when we’re getting together for group analysis, complaining in retro when the pressure to deliver means they don’t get to spend as much time with the research as they want. So big love to Eve, Neil, Steve, Mark and Alex T.</p><p>Even so, we are losing a couple of people from our Leeds team as well. That means we’ll need to take time to adjust our ways of working a little, and build up a larger team again.</p><h3><strong>Metrics</strong></h3><p><strong>Blog posts published:</strong> 1. YTD: 10.</p><p><strong>Country miles walked:</strong> 0. Despite the sunny weather, I took Saturday off to read a book on the sofa.</p><p><strong>Meditation:</strong> no, but I’m not sleeping all that well with everything going on, so need to get back into it.</p><p><strong>Reading/listening/watching:</strong> we watched <em>Fantastic Beasts and Where to Find Them</em> on Monday though we were both a bit zonked and probably need to re-watch it. Overall a lot of fun, though I found the plot-twists a bit predictable.</p><p>I got two books for my birthday: <em>Turn the Ship Around</em> which I’ve only just started, and Clover Stroud’s <em>The Wild Other</em> which I unexpectedly devoured in a single sitting on Saturday.</p><p>It was beautifully written, with the kind of sharp, evocative descriptions of events and places that I love. And lots of horses. But I was left feeling a bit ambivalent about it, for I think several reasons. Firstly I’m unsure whether Stroud is respecting her family and friends’ privacy, or just deeply self-absorbed. She seems to breeze in and out of people’s lives with barely a backward glance, thinking almost entirely of herself. There is little sense of how the people around her might be experiencing events or her presence in their lives. She might, as she suggests in the acknowledgements, just be mindful that this is a personal perspective and is being careful not to ascribe any interpretation or experience to others. But it comes across as uninterested and unaware.</p><p>Then there’s the wild outlandishness of it all. If this was a novel you’d dismiss it as an over-the-top fantasy which couldn’t possibly happen to anyone in real life. The idyllic middle-class childhood in the country. The tragedy that ends it. The sister who runs a circus. The other sister with the best-selling pottery empire. Travelling round Ireland in a horse-drawn cart, raves, drugs, becoming a cowboy in Texas, touring war-torn Ossetia with a Cossack horseman, five children.</p><p>Finally there’s the weirdness of reading such an outlandish and deeply personal account from someone whose life touches your own. That this strange and turbulent life is that of the kind of person I grew up with heightens the sense of the unreal. I was at primary school with Stroud’s sister Nell — the one who went on to start a circus. I have sharp memories of halloween parties in the garden of their rambling house in Oxford, with proper apple bobbing and costumed children shrieking through the bushes. And we both have parents who’ve suffered severe brain damage — though my father’s motorbike accident came when I was in my late twenties, and he was left less impaired than Clover’s mother. I think that also may have made me more judgemental of Clover at times than is perhaps fair.</p><p>Overall I would recommend it, but perhaps not if you are the kind of person who is easily wound up by the unconscious privilege of #middleclassproblems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=137961170ce3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e12: OMG we bought a house!]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e12-omg-we-bought-a-house-1ea5498aa3e3?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ea5498aa3e3</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sun, 02 Apr 2017 22:18:15 GMT</pubDate>
            <atom:updated>2017-04-02T22:18:15.583Z</atom:updated>
            <content:encoded><![CDATA[<p>27 March to 2 April 2017</p><p>Another busy but bitty week.</p><p>I’m noticing a pattern where, when I settle down to write these weeknotes I think nothing much has happened, then when I look back over my calendar and remind myself what I was doing each day, I realise <em>lots</em> has happened.</p><p>Writing that up is a bit trickier. I’ve mostly stuck to the simple day by day structure I adopted when I started these in January. I’m not sure how well that works when there are multiple storylines developing over the week. Perhaps I just need to work out how to channel my inner Aaron Sorkin (if I have one). Re-watching <em>The West Wing</em> there’s always a lot of “oh, this is the episode where that happens… and that… <em>and</em> that”. That’s what my week often feels like. Only with less sass and fewer neat end-of-episode resolutions.</p><p>But let’s give it a go…</p><h3><strong>In this week’s episode</strong></h3><p>At the end of last week I was offered the interim Head of Design role I had <a href="https://medium.com/@sophiedennis/weeknotes-s01e07-viable-or-just-minimal-a20059b11224">applied for a while back</a>. I had some conversations with NHS Digital as a result, and spent the weekend deliberating about what direction to take. So some of Monday — and indeed the rest of the week — was spent continuing those conversations.</p><p>I’m eager to get back into a leadership role. The challenge of building up a design/UX team and helping shape digital strategy for a large organisation is extremely attractive. At the same time there are serious challenges to be tackled at NHS Digital, working on something I’m passionate about. I know I could make a real difference if we can just find the right place for me.</p><p>And this particular Head of Design role would involve a LOT of travelling. Realistically I’d be away 3 or more likely 4 nights a week. Did I really want to do that? After all one of the reasons we left our beloved Dartmoor for Yorkshire last year was to cut the amount of travelling I was doing — design leadership and strategy roles being a bit thin on the ground in West Devon.</p><p>So that was all rather dominating my headspace this week, vying with the anxiety of hoping at any minute to exchange on the house we’re buying. We’d expected it to be last Thursday. Then last Friday. Now today (Monday). Was it all about to somehow fall through at the last minute?</p><h4><strong>Monday</strong></h4><p>Had a few conversations about what a more meaty role for me in NHS Digital might look like. Prepped for show and tell the next day. Lunch with former DWP colleague, Mel Cannon, who’s Head of Content over there. She’s published some great stuff recently which is all collected in her post <a href="https://medium.com/@melanie.cannon/starting-conversations-about-content-design-55443063aea1">starting conversations about content design</a>. I’ve found her advice on <a href="https://dwpdigital.blog.gov.uk/2017/02/28/helping-teams-define-their-focus/">helping teams define their focus</a> by writing clear service names, descriptions and mission statements particularly helpful.</p><p>In the evening I went to the NUX (“Northern UX”) Leeds meetup. Barry Briggs from the BBC UX&amp;D team gave a really good and interesting talk on information architecture. <a href="https://nuxuk.org/2017/03/13/nux-leeds-27-march-2017-desperately-seeking-something/">Barry’s slides are here</a>. They don’t really do the talk justice, so if you get the chance to hear him do this talk somewhere go. He talked about <a href="http://boxesandarrows.com/four-modes-of-seeking-information-and-how-to-design-for-them/">Donna Spencer’s four modes of information seeking</a> and examples of how the BBC websites support each one. If you’ve read <a href="https://medium.com/@sophiedennis/weeknotes-s01e11-design-tactics-design-strategy-addf2b646f76">last week’s weeknotes</a> you’ll know that this was very timely.</p><p>I reflected on how different information seeking around healthcare and health services is from the ‘fire and forget’, quick answers to known questions, one-off transactions model GOV.UK has been based on. With healthcare there’s a lot more “berry picking”. A lot more not even knowing what it is you’re looking for. Repeated returns to a topic to understand it in more detail as the user’s needs change over the course of an illness or condition. Tim Allan, who’s been working on the NHS.UK Beta down in London, wrote an interesting article on this just a few weeks ago: ‘<a href="https://medium.com/@thebottlerocket/users-in-health-a-uk-perspective-1f30345ef128">Users in health — A UK perspective</a>’.</p><h4><strong>Tuesday</strong></h4><p>Ceremony day. Again.</p><p>My other task Monday afternoon was putting together our little team’s show and tell slot. It covered findings from the last lab session on 6th March and the design changes we’ve made as a result. This was supposed to be a joint slot with our interaction and content designer. But with one thing and another both got held up that morning so I ended up doing it on my own. It wasn’t my best show and tell presentation. To be honest the subject matter was a little dull. The changes we shared are minor — though important — tweaks. The more interesting stuff is the wider IA and nav approach, but with only had 5 minutes I dropped that discussion. This is “show and tell” not “reflect and ruminate” after all, and we don’t have anything concrete to show from the IA work just yet.</p><p>At lunchtime the news came from the solicitor that we’d exchanged on the house purchase and that completion date was set for Friday. We just needed to transfer the balance of the deposit, and hope nothing went wrong.</p><h4><strong>Wednesday</strong></h4><p>We reviewed some variations Alex had developed for the header area of the GP profiles. The answer to my rhetorical “how long can it take to discuss a header design?” proved to be “a long time”. Part of the problem is that changing one thing on the page has a knock-on effect on other parts of the page. So there was a bit of “if we change thing A about the header, what do we do about section Y down there?”. Also heated debates about our differing perspectives on what users want and need. These should be resolved by putting things in front of users, but we couldn’t agree what we wanted to put in front of them or in what form (lab? pop-up? A/B test?). In the end I suggested we separate out the question of what designs we wanted to explore from how we could validate them with users. Looked at that way it turned out we really had only two options to explore (albeit some with knock-on implications) which simplified things a lot.</p><p>In the afternoon I did some prep for Wednesday’s lab, and sorted out some final bits and pieces I needed to do for the first version the new GP profiles going ‘live’ on beta.nhs.uk at the end of the week.</p><p>Back home Andy sent a large sum of money to our solicitors, ready for completion on Friday.</p><p>A special treat was also waiting for me: a copy of <a href="https://www.amazon.co.uk/Designing-UX-Prototyping-Ben-Coleman/dp/0994347081"><em>Designing UX: Prototyping</em></a> by Dan Goodwin and Ben Coleman, two of the talented team behind South West digital design agency <a href="https://fffunction.co/">fffunction</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gE-E_d9b8tZEJa1tvX0fqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dyLrBidJayICbJVIRmcU0w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VBzsa57flHefwEopLvKWKQ.jpeg" /><figcaption>Designing UX: Prototyping by Dan Goodwin and Ben Coleman. Technical Editor: yours truly.</figcaption></figure><p>I’ve had the privilege to be technical editor for the book, casting an expert eye over each chapter as it was written. Ben and Dan were super to work with, and the resulting book is something they can be really proud of. The book covers the whys, whens and hows of prototyping digital products and services, from mocking things up on paper right through to full HTML prototypes. It’s particularly aimed at people new to UX, but there’s good stuff in there for anyone wanting to up their prototyping game, or experiment with different tools and approaches. It’s available as an <a href="https://www.sitepoint.com/premium/books/designing-ux-prototyping">ebook direct from Sitepoint</a> and in <a href="https://www.amazon.co.uk/Designing-UX-Prototyping-Ben-Coleman/dp/0994347081">print from Amazon</a>.</p><h4><strong>Thursday</strong></h4><p>We had a team workshop to look at another option for the new IA. I talked through the “top tasks” that have emerged from the user survey on the current GP profiles and we sketched out ideas for how multi-page profiles might work. There was then the challenge of how to share the workshop outputs with Alex our interaction designer, who’s had to go to Canada for a few weeks. I kicked myself when our lead dev suggested we make a video. Doh! <a href="http://www.sophiedennis.co.uk/post/33236859856/predict-the-sky">I’ve used video in the past to talk remote teams through prototypes and sketches</a>. You can record a video of you talking through a prototype or sketch so much faster than you can write up your ideas into a coherent email. It took Joe and I just 10 minutes to make a couple of videos talking through the sketches and concepts behind them. This is why the agile manifesto favours face to face communication over written documentation — it’s often the quickest way to communicate ideas between both parties. But it doesn’t necessarily have to be physically face to face, and it doesn’t even necessarily have to be synchronous.</p><p>We also talked about priorities for the user research we’re running next week. We’ve been working on a lot of divergent concepts. If you put them all together we could easily have a dozen variations. That’s far too many to put in front of one person in one session. We settled on testing our iterations of the current structure and design, rather than the more radical changes to the IA. How well the iterations test next week will help us decide how much of a priority developing and validating a different approach is.</p><p>Then there was last minute house-buying drama. Turns out there are a number of bankrupt Andrew Robinsons around. Quite why this only came to light at 5pm on the day before completion is something I’ll leave anyone who’s ever dealt with a solicitor with an insufficient sense of organisation and urgency to ponder. Anyway, Andy had a ‘fun’ half hour trying to find our scanner so he could print and sign a piece of paper confirming none of them were him.</p><h4><strong>Friday</strong></h4><p>OMG WE BOUGHT A HOUSE!</p><p>As a pair of lifelong renters this was a pretty big day in both our lives.</p><p>I distracted myself in the morning by trying to get the video Joe and I recorded off my phone and up on the Internet. This was, I think, mainly hampered by having my phone and Mac set up to do all sorts of automatic photo syncing, which meant I was simultaneously uploading and downloading several copies of over a gigabyte of video. Or possibly it was just my phone being cranky about uploading large files to Dropbox. Anyway I eventually got that sorted.</p><p>The call from the estate agent came about 11.30. We were officially home owners!</p><p>The new house is over an hour away, so by the time we’d got keys and stuff it was mid-afternoon. The seller had left the house spotless, albeit stripped of curtain poles and — bizarrely — toilet roll holders. The spotlessness was a relief. I know how much dirt and dust moving kicks up and had been braced for a weekend spent scrubbing. The items she’s taken we did know about in advance, but I’m still a bit baffled. Who is so attached to their toilet roll holders they bother unscrewing them and taking them with them? And now we have to get opinions about toilet roll holders, which is just something we’d both rather not waste time and headspace getting opinions on.</p><p>Still. WE OWN A HOUSE!</p><p><strong>Weekend</strong></p><p>DIY shops. Curtain poles. Getting opinions about toilet roll holders. The Great Flooring Replacement Debate. Such, it seems, is the heady life of a British home owner.</p><p>Did you know you can easily spend £30 or more on a single toilet roll holder? Perhaps that explains why people take them with them when they move. If I’d blown £90 or more on toilet roll holders I might well keep them so I didn’t have to spend another £30 a pop on them at my next place.</p><p>If you’re in need of toilet roll holders, btw, check out these <a href="https://www.ebay.co.uk/itm/222454735740">fun</a> <a href="http://www.ebay.co.uk/itm/NEW-BLACK-DRAGON-BATHROOM-WALL-MOUNTED-TOILET-ROLL-HOLDER-FANTASY-GOTHIC-50048-/311812653774?hash=item48997b82ce:g:Ui8AAOSwzvlW9FHm">gothic</a> <a href="http://www.ebay.co.uk/itm/Toilet-Paper-Holder-Gothic-Dragon-Wall-Mounted-Home-Bathroom-Tissue-Accessory/131577047258?_trksid=p2045573.c100508.m3226&amp;_trkparms=aid%3D555017%26algo%3DPL.CASSINI%26ao%3D1%26asc%3D20160706105120%26meid%3D936925d8e09840b9aec54784a183ac59%26pid%3D100508%26rk%3D1%26rkt%3D1%26">ones</a> on eBay. I especially like this <a href="http://www.ebay.co.uk/itm/182228776917">Grim Reaper writing his list on the roll</a> as it turns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvH0Az6ZrHyX_F2SGCDBSw.png" /><figcaption>He’s making a list. He’s checking it twice…</figcaption></figure><p>And now alongside the headspace I’ve had to devote to them, I’ve taken up valuable week note space discussing toilet roll holders as well.</p><p>It’s my birthday on Monday, and I’m hoping to have a day off from future-of-work worries, house worries, DIY, packing and toilet roll holders. I’m not sure that’s going to happen.</p><h3><strong>Metrics</strong></h3><p><strong>Blog posts published:</strong> 1. YTD: 9. With the first quarter of the year done I’m some way behind on a target of 50 for the year.</p><p><strong>Country miles walked:</strong> Zero. Roll on new house in the country and long, light, sunny evenings.</p><p><strong>Meditation:</strong> none. I probably need it too.</p><p><strong>Reading/listening/watching:</strong> best April fool has to be <a href="https://www.nationaltrust.org.uk/news/second-chalk-figure-discovered-near-uffington-white-horse">the National Trust’s white horse hill duck</a> discovery.</p><p>This one from NNGroup on <a href="https://www.nngroup.com/articles/ideation-chumps/">why you shouldn’t bother with “ideation”</a> would have been funny if it hadn’t been something I could totally imagine someone writing in absolute seriousness.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ea5498aa3e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e11: design tactics, design strategy]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e11-design-tactics-design-strategy-addf2b646f76?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/addf2b646f76</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sun, 26 Mar 2017 16:29:33 GMT</pubDate>
            <atom:updated>2017-03-26T18:09:17.456Z</atom:updated>
            <content:encoded><![CDATA[<h4>20–26 March 2017</h4><h3><strong>Exploring nav and IA for GP profiles</strong></h3><p>This week we’ve been thinking about how to improve wayfinding and IA on the new NHS.UK pages we’re creating for GP practices. We have been pursing a long scrolling page design: basically everything about a practice on a single page, with clear headings for each section.</p><p>But unlike the information on symptoms and conditions our London colleagues have been working on, the information we’re presenting doesn’t have a natural linear order. There is no narrative to follow, or obvious hierarchy. People come to practice pages for lots of different discrete tasks — from checking what time they can call for an appointment, to leaving feedback, or finding out what their rights are when they’re having trouble registering with a new doctor. There also is some information that is totally irrelevant to most people, but extremely important to a few — like wheelchair access, facilities for people who are deaf or hard of hearing, or information to help people with poor English find a doctor who speaks a language they’re more fluent in.</p><p>So we thought we should review whether a long scrolling page was the best approach. In particular we had been using anchor links at the top of the page to help people quickly jump to the information they needed rather than having to scroll. We found in testing that people assumed the links took them to a new page. They then became disoriented by the scrolling and had difficulty spotting specific bits of information — like whether there as a car park.</p><p>So from our previous research lab we had a few things we wanted to look at:</p><ol><li>user interface design — what I call the navigation mechanics — tabs, top menus, sidebar menus, sticky nav, category pages etc… etc…</li><li>information architecture — how do we group information into sections and what are those sections called (labelling)?</li><li>information design — within those sections, is the information presented in a way that’s easy to understand and scan?</li></ol><h4><strong>Finding patterns</strong></h4><p>I spent some of the week hunting down and collating example of sites tackling similar navigation challenges — thanks to everyone on Twitter who sent suggestions. We’ve been looking at hotels, which similarly need to collate a lot of information about a service (an individual hotel) some of which is only relevant to some guests. I also looked at patterns from the BBC, GOV.UK and local councils. Common patterns were:</p><ol><li>‘Sticky nav’ — where the navigation remains visible as the page scrolls (<a href="https://www.airbnb.co.uk/rooms/272282?s=7FAz94e3">AirBnb</a>, <a href="http://www.sacoapartments.com/serviced-apartments/uk/london/saco-the-cannon/">SACO</a>, <a href="https://www.gov.uk/service-manual/agile-delivery/agile-government-services-introduction">GOV.UK</a>)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*L_BEe5fdEeA1pdn0yRutTA.gif" /><figcaption>Sticky tabs and call-to-action sidebar on AirBnB</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*aeTjqt-WYjKkpVMe5XR-Dw.gif" /><figcaption>Sticky sidebar on GOV.UK pages</figcaption></figure><p>2. Making the page visibly scroll rather than jump when using navigation links, so it’s clear to people they have gone to a different point on the same page, and not to a new page (<a href="https://www.airbnb.co.uk/rooms/272282?s=7FAz94e3">AirBnb</a>, <a href="http://www.sacoapartments.com/serviced-apartments/uk/london/saco-the-cannon/">SACO</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*XSH0SuQ8OYsGdUQzEPSUsQ.gif" /><figcaption>On the SACO website if you click on the navigation tabs the page visibly scrolls down, rather than just jumping to the section as it does with native anchor links. The GOV.UK page above is an example of the native ‘jump’ interaction.</figcaption></figure><p>3. Creating a ‘hub’ page primarily made up of links to sub-pages and tasks — particularly good if most people are interested in one task or topic at a time (<a href="http://www.bbc.co.uk/education/subjects/zyg4d2p">BBC Bitesize</a>, <a href="https://www.bristol.gov.uk/bins-recycling">Bristol City Council</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQTLSa1oi_PVqnhSQha9CA.png" /><figcaption>Hub page for bins &amp; recycling on bristol.gov.uk, including clear ‘top tasks’ at the top.</figcaption></figure><p>I had some fun capturing the videos of these interactions using <a href="https://giphy.com/apps/giphycapture">GIPHY Capture</a>. I wanted animated gifs as they’re dead easy to share in Slack or Trello. GIPHY capture is a super-simple app that captures what’s happening on any section of the screen and saves the video as an animated gif. You can set it to show or not show the cursor, and there’s a few controls for framerate, image size, and trimming the start or end of the clip. A nice example of a simple app that does one thing really well.</p><h4><strong>Rapid user research</strong></h4><p>Wednesday afternoon we went off to a couple of local coffee shops for some pop-up guerrilla testing (we tend to use “pop-up” rather than guerrilla in government circles). Pop-up research is a good way to assess individual interactions and quick tasks like this — anything you can get feedback on in 5 minutes or less. We wanted to see the kind of terms people might use to look up their own GP, and also how the long practice pages worked without any links at the top at all — did people naturally scroll, and did they still get a bit lost?</p><p>We structured our questions so we could learn something useful whether people had two minutes or 10. We spoke to about 20 people over the course of an hour and half, and got some useful if unsurprising feedback. It was interesting how different the customers were between the two coffee shops though. The one on the ground floor of our own office building had a largely 30–40 year old professional clientele. The one in the city centre shopping centre had mostly older shoppers, many with low or non-existent digital skills. Going to both was good as it prevented us making assumptions based on insights from a limited user group.</p><p>We’re pretty lucky to be working on something as universal as GP surgeries, which means almost everyone we speak to can relate to the task we’re investigating. Checking our assumptions with ‘normal people’ in this way stops us getting bogged down in arguments about our own opinions. I reckon that’s a good return on the investment of a few hours of four team members’ time.</p><h4><strong>An expert view</strong></h4><p>I was also lucky enough to be able to tap into the big brain and many years of experience of <a href="https://twitter.com/cjforms/">Caroline Jarrett</a> this week.</p><p>Shock news for all of us in the design/UX community was that, hard on the heels of her husband coming out of hospital following a kidney transplant, <a href="http://www.effortmark.co.uk/taking-time-off-due-leukaemia/">Caroline herself has been diagnosed with leukaemia</a>. She is currently in hospital receiving treatment, and will be isolated in a hospital room for several weeks.</p><p>In her announcement on her website she asked us all to please keep asking her questions about forms and surveys. So I did, and she generously gave me an hour of her time, both for a good gossip, and to give me the benefit of her wisdom on various nav and IA patterns. It was particularly good to see our work through her eyes. After almost 3 months I’m too close to both the problem and our solutions. Caroline’s enthusiastic endorsement helped me see how far we’ve come, and that the page as it is today is nothing like as long and confusing as it maybe was a few weeks ago. Testament to the continual iteration and improvements the team have been making.</p><p>As I say Caroline is marooned in hospital for some weeks to come. She tells me she often has some hours each day to do with as she likes, and as you know one of the things she likes best is chatting about forms. If you have questions about form design, survey design, or wider interaction and information design please do send them her way. Just be aware that anything her medical team needs to do takes priority, and she may not always be able to answer quickly.</p><h4><strong>Design workshop</strong></h4><p>We tied this all off with a design workshop on Thursday afternoon, identifying two or three options to work up over the next week and a half before another round of lab-based user research on 5th April.</p><p>Highlight of the afternoon though was surely using our new Surface Pro screen to capture notes as we went. Things I love:</p><ul><li>Pens that never run out of ink</li><li>Including images, screenshots and photos of paper sketches on the whiteboard</li><li>Live annotating and sketching on top of a web page</li><li>Getting a high-res image of the final whiteboard</li></ul><p>The built-in whiteboard app is still a little basic — I really want it to do handwriting recognition, and fake sticky notes would be a nice addition. But it was incredibly useful to be able to share a really good quality version of the notes from the session with the team, and most importantly the product manager who couldn’t be there with us. The image it exported was vastly superior to the usual smartphone photo of a whiteboard, with faded whiteboard pens and scribbled post-it notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zb5s8pxDILPd8wAWi1uynA.jpeg" /><figcaption>Surface Pro whiteboard app with notes from our design workshop</figcaption></figure><h4><strong>Top tasks</strong></h4><p>My other job this week has been first pass analysis of the survey we ran recently. We’ve just about got all 1,150 responses categorised now. I spent Tuesday wrangling Excel functions and cursing pivot tables. I love a good spreadsheet as much as the next former delivery manager and content strategist, but this has frankly taken it all a little far.</p><p>Still we’ve got some useful high-level insights from it. In particular we’ve confirmed a major top task we’ve currently dropped from our pages — reading and leaving reviews. I suspect a good chunk of response bias here — if your intent is to leave feedback, then you are going to be more inclined to fill in a survey asking for feedback than someone who is just after a phone number. But we clearly do need to dig into people’s need and motivations around reviews, feedback and complaints in more detail at some point, and hook up with the work already done by NHS England and other colleagues on this.</p><h3><strong>Old friends and colleagues</strong></h3><p>As well as Caroline, I also got to catch up with various former DWP colleagues. I swapped nearly but not quite buying a house stories with Mel and Rebecca from the content team, raised a glass to Eddie Shannon as he heads off to his next adventure in government design, had a cathartic lunch with fast-streamer Hannah Roe, and caught up properly with Ben Holliday at last.</p><p>It was good to hear that the strategic piece I was working on before I left is bearing fruit. Even better, it’s enabled Ben to make the case to <a href="https://dwpdigital.blog.gov.uk/2017/03/13/designing-services-with-service-designers/">hire a permanent, senior service designer</a> to work on that programme long term.</p><h4>Making the case for service design and design strategy</h4><p>A big lesson from my time at DWP is that, when you are trying to make the case for service design to an organisation, there is nothing quite like having someone in there and doing the job to convince people of its value.</p><p>It is surprisingly tough to make the case for service design — and more particularly ‘service designers’ and why you should hire them — to people who don’t already understand what it is. Partly it involves a leap in perception and understanding of the role of design and user research in an organisation. Design and research are still perceived as largely tactical, delivery functions. Whereas service design — certainly at senior level — is primarily a strategic one. We’ve successfully got design and research embedded in the day-to-day delivery of digital services — the <em>are we working in the right way</em> level. They’re not yet well embedded at the <em>are we working on the right things</em> level, where they can actually make the most impact.</p><p>But also when you try to describe the kind of tasks a service designer might do — end to end journeys, identifying pain points, future vision — people reply that those are things their user researchers, business analysts, technical architects and above all product managers, are (or should be) doing. Why do they need this extra ‘service designer’ person in there?</p><p>I think the service designer is there, not because these aren’t things the people you’ve already got can do, but because when tackling big, broad problems having someone who covers all those things and can look at the whole from a ruthlessly user-centred perspective is invaluable.</p><p>My thinking on this is similar to David Bland’s three circles. At a product strategy level you want a balance of three perspectives:</p><ul><li>desirable</li><li>feasible</li><li>valuable</li></ul><p>with leadership around all three.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9T6zZNsAWXROU1wfCU3NYQ.png" /><figcaption>Great products and services come from a combination of what’s desirable, what’s feasible, and what’s viable. Your product needs leadership around all three: a design lead focused on what’s desirable, a product lead focused on what’s viable, and a tech lead (if it’s a digital product/service) focused on what’s feasible. From ‘Introduction to Assumptions Mapping’, David Bland <a href="https://www.slideshare.net/7thpixel/introduction-to-assumptions-mapping-agile2016/49">https://www.slideshare.net/7thpixel/introduction-to-assumptions-mapping-agile2016/49</a></figcaption></figure><p>Your service designer — or design lead, experience strategist, UX architect or whatever job title we’re using this year — fills the ‘desirable’ function. Of course, in government services ‘desirable’ isn’t the right word. But nonetheless I think the core trio here of product/business, tech/ops and design/user experience is valid.</p><p>Importantly, of course, your design lead, tech lead, and product lead must all value and understand the importance of the other circles. The point is not that your product manager doesn’t understand users, or your design lead is incapable of making trade offs between user needs and business goals. If these people don’t understand the importance of all three perspectives I’d question their fitness to lead at this level. The point is to bring together experts on those three areas, and in the healthy tension that will inevitably arise from the particular view you’ve asked each to take of the problem, to identify the very best approach.</p><h3><strong>Metrics</strong></h3><p><strong>Blog posts published:</strong> 2. Year to date: 8.</p><p><strong>Country miles walked:</strong> 11 miles. <br>Wooooot! Spring has well and truly sprung so Saturday we headed to our usual spot at Langsett Reservoir. We made it nearly to the top of Cut Gate, which accounts for 8.7 of the 11 miles. We turned back before the top in case our legs weren’t as up to going 10 miles as our liberated brains were, but we’re determined to make it to the top and the views over Derwent some day soon though. The final 2.3 miles were an early Sunday evening stroll in celebration of the clocks going forward. It being light past 7 is definitely a bonus when trying to get the miles up.</p><p><strong>Meditation:</strong> been really lax this week. Need to get back into it properly.</p><p><strong>Reading/listening/watching:</strong> Luke Jones shared this good piece from The Atlantic on <a href="https://www.theatlantic.com/magazine/archive/2006/06/the-management-myth/304883/">The Management Myth</a> (2006) about management ‘science’ and whether you can, in fact, learn just as much about management from reading Descartes and Shakespeare. We tried the original <em>John Wick</em> as part of our 9 mile walk recovery programme. I can confirm that the reviews saying it’s very stylish, very silly, and within those parameters really rather good are pretty much spot on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=addf2b646f76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e10: very nearly but not quite a homeowner]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e10-very-nearly-but-not-quite-a-homeowner-b9cb403bd8a6?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9cb403bd8a6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 23:22:44 GMT</pubDate>
            <atom:updated>2017-03-20T23:22:44.284Z</atom:updated>
            <content:encoded><![CDATA[<h4>13 to 19 March 2017</h4><p>Sitting down to write this I realised last week is a bit of a haze, even though it’s just a week ago at most. Perhaps the previous two weeks - which I haven’t written weeknotes for yet - just loomed too large, with lots of big stuff happening with the NHS Digital team, some intense user research and then speaking at <a href="http://govservicedesign.net/2017/">Service Design in Government</a>. Or perhaps the fact it’s the week when we <em>very nearly finally</em> bought a house - our first ever, ssshh don’t jinx it - is crowding out everything else. Nonetheless let’s give it a go...</p><p><strong>Monday</strong> I went down to London and spent a productive day with three of the User Research Sisterhood, fleshing out the primary care patient experience map they’ve been chipping away at. We also met with the Head of Insight at NHS England. They do what I call &quot;proper social science research&quot; - large scale attitudinal surveys, working out robust performance satisfaction measurements and so forth. I think it’s possible he was as excited about the possibilities of enriching their sometimes dry data with our &quot;voice of the user&quot; stories to, as we were about having their large-scale robust analysis to backup our small sample insights.</p><p><strong>Tuesday</strong> was ceremony day. Quiet one for me. As I’d been off quite a bit of last sprint with SDinGov the team were better placed than I to talk about what we learned on the user research. And planning was rightly very focused on making sure the dev work is on track to deliver for end March.</p><p><strong>Rest of the week</strong> was a bit of a mix of bits and bobs.</p><p>We pushed on with categorising the survey we ran on the GP pages on NHS Choices. It’s definitely revealing some clear top tasks people actually come to the GP pages on the NHS website for. By week’s end we had 600 of the 1150 replies categorised. So it’ll need a push next week to get it finished off. And then I get to have &quot;fun&quot; with spreadsheet formulas. Remind me never to volunteer to run a quant research piece again.</p><p>I caught up with the detailed analysis the team had done of the lab research we’d done last week. Alex (interaction design) and Dean (content design) did a cracking job on the write up, very focused on actions and recommendations for design. Yay! for whole team being engaged in research. Our big challenge is around navigation and IA. Users are getting rather lost and disoriented on our long scrolling page. We’d love to talk to anyone with experience and user insights they can share (even off the record) on designing effective long scrolling pages vs tabs/accordions/multiple pages. Especially ones which need to cover a lot of different tasks and scenarios.</p><p>I also started planning another lab day, this time with the luxury of a 3 week lead time. Bliss.</p><h3>Metrics</h3><p>Big fat zeros all round.</p><p>I maybe did a bit of meditation. But no blog posts, no country miles walked and not really watching much of note either.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9cb403bd8a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknotes s01e07: viable, or just minimal?]]></title>
            <link>https://medium.com/@sophiedennis/weeknotes-s01e07-viable-or-just-minimal-a20059b11224?source=rss-f75503ab734------2</link>
            <guid isPermaLink="false">https://medium.com/p/a20059b11224</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[user-story-mapping]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sophie Dennis]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 23:46:06 GMT</pubDate>
            <atom:updated>2017-02-26T23:46:06.745Z</atom:updated>
            <content:encoded><![CDATA[<h4>20–27 February 2017</h4><p>The theme of the week has definitely been about putting the “viable” into Minimum Viable Product (MVP). Especially in the context most non-startups mean when they say ‘MVP’, which is “what’s the first version we should release widely to customers?”, rather than the true Lean Startup concept of “what’s the smallest, quickest, simplest thing we can build to find out whether we actually have a viable business here?”.</p><p>It was the theme of a workshop I ran on Monday for a new client, and then ended up as a thread through a number of discussions and debates back at NHS Digital.</p><h3><strong>Sunday/Monday</strong></h3><p>I headed to Newcastle on Sunday, and spent a lovely evening catching up with two separate sets of old friends who happen to live within 10 minutes walk of each other in Whitley Bay. The bracing sea winds of Whitley reminded me a lot of Dartmoor — always windy, always a couple of degrees colder than everywhere else.</p><p>Monday I ran a story mapping workshop for a new client. Two of their team came to my talk on “<a href="https://2016.nuxconf.uk/videos/#sophie">The Art of Doing Less</a>” at NUX5 in Manchester last Autumn, and asked if I could run a workshop for their wider team. In the morning I ran an extended version of the workshop on which the talk was based, which I’ve run at UX Cambridge, UX London and other events, and in the afternoon we built a story map for a potential new product they’re considering. It was a really rewarding day. They’re largely a team of developers with minimal in-house UX and design, but they are all passionate about producing software that really works for their users. I was struck as ever by how powerful story mapping is, and how you can use it to build clarity and consensus in a very short space of time, in a format that is incredibly simple and easy to understand and communicate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Glpey3MmljuGZECrrNx-tQ.jpeg" /></figure><p>The workshop focuses on how to use story mapping to define a Minimum Viable Product (in that “first release to customers” sense) that emphasises the viable and not just the minimum — a minimum viable experience, rather than minimum viable product if you will. This means combining story mapping with ways of understanding what really matters to customers and users. The workshop is at least as much about understanding the Kano model and the power of identifying, and then eliminating, pain points in the existing user journey, as it is about how to arrange post-it notes in rows and columns.</p><p>I’m keen to run more workshops and facilitate story mapping and product prioritisation with teams, so get in touch if you’d be interested in learning more about it.</p><h3><strong>Tuesday to Friday</strong></h3><p>Back in Leeds with the NHS Digital team I found myself on the sharp end of ‘responding to change over following a plan’.</p><p>My plan for the week had been to spend it analysing a “true intent” survey we’ve been running on the existing NHS Choices pages for GP surgeries. However, the team really wanted to bring forward our next lab-based research session to 6th March, which was less than two weeks away. That meant instead of a nice clear week to focus on the survey, I spent much of it rapidly booking labs, drafting a recruitment brief and getting quotes from agencies to find us participants (as they normally need at least a week for recruitment, preferably two). Lots of bitty tasks and admin that made settling down to anything else difficult.</p><p>Happily I still managed to make a decent start on the survey analysis. Our true intent survey is mainly free text questions (along the lines of “what made you come here today?…. what were you looking for?… Did you find it?”) so the responses have to be manually coded (categorised) to extract patterns. To do that you have to read what each person has written in answer to the questions to decide which categories it fits into. We’ve had over 1,100 valid replies which is kind of one of those good problems because it gives us a good-sized sample on which to base our findings, but even if it only takes a minute to read each reply it’s going to take over 18 hours to do the coding.</p><p>Anyway I managed to do a first pass coding of 250 responses, using categories (“codes”) from a couple of smaller surveys run last year. The previous categories didn’t quite work on their own, but that enabled me to come up with a refined set of codes for us to use. I tested the codes on a second pass through about 30 responses and they seem to be holding up fairly well. The idea now is to get the whole team to help review and code responses. I’ve imported the raw data into a Google Spreadsheet so we can work on it collaboratively. Having 13 people contributing will certainly make lighter work of those 18 hours, and it’s belatedly occurred to me that an hour spent reading replies must surely count as <a href="https://articles.uie.com/user_exposure_hours/">Exposure Hours</a>. Possibly that means team-coding is the plan I should have had all along. But better to come late to the party than never to show up at all.</p><p>We also had some sometimes heated debates about MVPs and the state of what we’re likely to deliver in March. I gave the team some fairly tough feedback — which is always difficult both to give and to receive — but which I hope will lead to a better finished product in the end.</p><h3><strong>Weekend</strong></h3><p>Saturday we got my desk at home set up. Our current house is a temporary rental and we unpacked as little as possible knowing we’d just have to re-pack it all again in 6 or 9 months. So for the last 6 months my home office has mainly been a pile of boxes. At NHS Digital we have a team commitment to enable remote working, which means I am getting to work from home a lot more than when I was at DWP (or Land Registry before it), as they very much stuck to the Gov digital orthodoxy that teams must be physically co-located to be effective. At NHS Digital all our team meetings are “remote by default” if possible, with lots of use of Trello and Slack for asynchronous communications. This week I worked from home Wednesday to Friday, partly to try to get some clear time to concentrate on the survey, partly to avoid Storm Doris. While it was great to have the freedom to do that, it cruelly exposed the shortcomings of working at the dining table or squatting at Andy’s desk (3 days is a bit long to deprive him of his work space). It’s been great to get my proper desk back and, more importantly, my big external monitor, it’s height adjustable monitor arm, and my ergonomic office chair.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k79F5gcpiXEl2WxMJ6EHgQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOWHQ8SGeE-6XAlApBfy3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NPeeKpkSaQsXKuhy93YlyQ.jpeg" /><figcaption>L-to-R: clearing space for the desk; the finished product (it was only this freakishly minimalist for about 5 minutes, don’t worry!); the other half of the office, still mostly boxes. Several of my Twitter followers were also rather taken by our landlord’s animal curtains.</figcaption></figure><p>Once that was set up I tidied up some loose ends from Monday’s workshop, sending a copy of the slides and speaker notes to the team, and fleshed out my talk on ‘Adventures in Policy Land’ which I’m giving at <a href="http://govservicedesign.net/2017/">Service Design in Government</a>. The other bonus of tidying up my office is I now have lots of wall space to play with, so I merrily set about outlining the talk in more detail on post-it notes. That lead to ideas about whiteboard paint which proved perfect displacement activity.</p><h3><strong>Metrics</strong></h3><p><strong>Blog posts published</strong>: 1 (by a whisker!). YTD: 6.</p><p><strong>Country miles walked</strong>: 0. Some serious walking is going to need to be done at some point to make up for all the weekends I’m working. While it only takes about 30 minutes to get to what we consider ‘decent countryside’ from the place we’re renting, that means that when things are busy there isn’t an option to just pop out for an hour or two. We’re so looking forward to getting back to having proper countryside practically on the doorstep, and being able to get in a quick walk no matter how busy things are.</p><p>On which front we inched a crucial step closer to buying a house this week when we got final approval through for the mortgage. We now ‘just’ need to agree the completion date and actually exchange contracts. Everything is crossed and if I’m not talking about it much it’s because I don’t want to jinx it.</p><p><strong>Meditation</strong>: think I managed it about twice.</p><p><strong>Reading/listening/watching</strong>: I finished <em>How to Be a Heroine</em>, which I felt tailed off a bit at the end. Perhaps because it’s never occurred to me to try to model my life on fictional heroines, and also because I actually haven’t read many of the books it features. Also possibly because having come to it late I found <em>Wuthering Heights</em> more ridiculous than romantic. Worth trying though, especially if you are an avid reader of fiction. My ‘to read’ list expanded as one of the friends I met in Newcastle recommended Andrew Marr’s <em>We British</em> as “a well-written and relentlessly interesting history of the British as seen by its poets”. And Jukesie’s post about <a href="https://productforthepeople.xyz/01-the-pick-n-mix-product-manager-698896102a91#.9kqvjg7xm">10 books that made him a better project manager</a> reminded me I keep meaning to read <em>Turn The Ship Around</em> having heard him enthuse about it before, the art and science of forging high-performing teams being one of my passions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a20059b11224" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>