UX London 2017: Leading Service Design workshop with Kate Tarling

Slide 1

Slide 1 text

Kate Tarling and Ben Holliday UX London UX London Leading Service Design

Slide 2

Slide 2 text

Kate Tarling and Ben Holliday UX London Hello! Kate Tarling Home Office (immigration, passports, borders) Ben Holliday Department for Work and Pensions (DWP)

Slide 3

Slide 3 text

Kate Tarling and Ben Holliday UX London What we’re going to talk about Service design? Starting with users Framing the problem Orienting around services Setting long term goals and vision for services Communicating service design Getting senior level buy in

Slide 4

Slide 4 text

Kate Tarling and Ben Holliday UX London [pic - gov.uk]

Slide 5

Slide 5 text

Kate Tarling and Ben Holliday UX London

Slide 6

Slide 6 text

Kate Tarling and Ben Holliday UX London

Slide 7

Slide 7 text

Kate Tarling and Ben Holliday UX London Service design?

Slide 8

Slide 8 text

Kate Tarling and Ben Holliday UX London

Slide 9

Slide 9 text

Kate Tarling and Ben Holliday UX London

Slide 10

Slide 10 text

Kate Tarling and Ben Holliday UX London Service design or user experience design?

Slide 11

Slide 11 text

Kate Tarling and Ben Holliday UX London This is the real challenge: An organisation that delivers services, organising itself around the needs of its users

Slide 12

Slide 12 text

Kate Tarling and Ben Holliday UX London Always look at outputs before job titles http://bit.ly/ux-and-service-design

Slide 13

Slide 13 text

Kate Tarling and Ben Holliday UX London …understanding user needs as part of the full end to end service experienced by an end-user. This means working across multiple channels, not excluding administrative or ‘back end’ systems and processes

Slide 14

Slide 14 text

Kate Tarling and Ben Holliday UX London What service designers do Design services Choreograph work across teams Stop bad projects, shape good ones Facilitate shared understanding Help others make good decisions

Slide 15

Slide 15 text

Kate Tarling and Ben Holliday UX London Services exist because someone wants to do something

Slide 16

Slide 16 text

Kate Tarling and Ben Holliday UX London Study Travel Buy a house Stop working Use my money

Slide 17

Slide 17 text

Kate Tarling and Ben Holliday UX London Hmm, but what about... Internal systems and applications? Internal services like data analytics? Being arrested - surely that’s not a service?

Slide 18

Slide 18 text

Kate Tarling and Ben Holliday UX London Services exist because people want them

Slide 19

Slide 19 text

Kate Tarling and Ben Holliday UX London Services exist because someone needs to do something

Slide 20

Slide 20 text

Kate Tarling and Ben Holliday UX London They want to do something where an organisation has a goal, intent, or something of value to offer

Slide 21

Slide 21 text

Kate Tarling and Ben Holliday UX London The best service is one where no one has to do anything

Slide 22

Slide 22 text

Kate Tarling and Ben Holliday UX London Verbs not nouns Good Get something Check something Stay somewhere Bad e-form digital portal quote builder

Slide 23

Slide 23 text

Kate Tarling and Ben Holliday UX London Lets people check what their State Pension could be worth when they reach retirement age so that they can plan for their retirement

Slide 24

Slide 24 text

Kate Tarling and Ben Holliday UX London Lets people get a new passport so that they can travel to other countries and in and out of the UK

Slide 25

Slide 25 text

Kate Tarling and Ben Holliday UX London Most services provided by large organisations were made before the internet even existed

Slide 26

Slide 26 text

Kate Tarling and Ben Holliday UX London Making things digital ≠ making digital things

Slide 27

Slide 27 text

Kate Tarling and Ben Holliday UX London

Slide 28

Slide 28 text

Kate Tarling and Ben Holliday UX London Making things digital Employing the culture, mindset, practices, processes, skills and technologies of the internet era

Slide 29

Slide 29 text

Kate Tarling and Ben Holliday UX London

Slide 30

Slide 30 text

Kate Tarling and Ben Holliday UX London So what does good look like for services made in the internet era?

Slide 31

Slide 31 text

Kate Tarling and Ben Holliday UX London Westpac Get a new credit card 5 days 5 minutes Example via Sense & Respond by Jeff Gothelf & Josh Seiden

Slide 32

Slide 32 text

Kate Tarling and Ben Holliday UX London Tesla

Slide 33

Slide 33 text

Kate Tarling and Ben Holliday UX London Problem solved in 7 days Example via Sense & Respond by Jeff Gothelf & Josh Seiden

Slide 34

Slide 34 text

Kate Tarling and Ben Holliday UX London Amazon The process becomes the proxy for the result you want. You stop looking at outcomes and just make sure you’re doing the process right. Jeff Bezoz in annual letter to shareholders (2017)

Slide 35

Slide 35 text

Kate Tarling and Ben Holliday UX London What we can learn Have a useful and usable vision Ambition to re-think fundamentally Focus on outcomes & learn what works Make it faster to change in future

Slide 36

Slide 36 text

Kate Tarling and Ben Holliday UX London Starting with users

Slide 37

Slide 37 text

Kate Tarling and Ben Holliday UX London Handling challenges like: “They don’t have to like it. They just have to do it”

Slide 38

Slide 38 text

Kate Tarling and Ben Holliday UX London It’s not about what users prefer

Slide 39

Slide 39 text

Kate Tarling and Ben Holliday UX London What people need to do at a fundamental level is less likely to change than organisation design, technology, policy or process. It’s more future proof.

Slide 40

Slide 40 text

Kate Tarling and Ben Holliday UX London The difference between what we want people to do and what they actually do is where services become inefficient. Failure demand: avoidable contact, time spent on incomplete or unlikely things, fixing problems, manual processing, guiding people through complexity, hours wasted, opportunity cost.

Slide 41

Slide 41 text

Kate Tarling and Ben Holliday UX London Users Citizens Customers Front line staff Back office users Service providers Friends and family of users Stakeholders Policy SMEs Other service teams

Slide 42

Slide 42 text

Kate Tarling and Ben Holliday UX London We distinguish between: ● the end user trying to do something ● people delivering a service ● what it’s like to use an internal system ● what actually needs to happen

Slide 43

Slide 43 text

Kate Tarling and Ben Holliday UX London And we talk about: ● user needs ● the intent of policy, law or regulation ● the goals of an organisation ● desired outcomes

Slide 44

Slide 44 text

Kate Tarling and Ben Holliday UX London Use the wrong words and you focus on the wrong problems at the wrong level

Slide 45

Slide 45 text

Kate Tarling and Ben Holliday UX London Service design starts with user needs

Slide 46

Slide 46 text

Kate Tarling and Ben Holliday UX London Functional need The practical things people need to do Emotional need Feeling stressed or anxious, needing peace of mind or to feel confident about something

Slide 47

Slide 47 text

Kate Tarling and Ben Holliday UX London Finding a job is practical, the fear of getting sick and losing your job is emotional

Slide 48

Slide 48 text

Kate Tarling and Ben Holliday UX London User needs are about understanding the problem space not the solution space

Slide 49

Slide 49 text

Kate Tarling and Ben Holliday UX London Research to understand real life stages and context, not user needs that IT projects create

Slide 50

Slide 50 text

Kate Tarling and Ben Holliday UX London Adapted from @naintaraland and sketch by @ayeshamoarif Research here... doesn’t help us to understand this

Slide 51

Slide 51 text

Kate Tarling and Ben Holliday UX London Life stages and context (planned and unplanned events) eg. retiring, or bereavement Things people have to do eg. check or get their State Pension

Slide 52

Slide 52 text

Kate Tarling and Ben Holliday UX London Help people prepare for retirement vs Get your State Pension

Slide 53

Slide 53 text

Kate Tarling and Ben Holliday UX London Work in the UK vs Apply for Tier 2 visa

Slide 54

Slide 54 text

Kate Tarling and Ben Holliday UX London It’s easy to conflate needs with design decisions. These are things we make people do, not what people need: - prove your address - verify who you are - apply for a credit card

Slide 55

Slide 55 text

Kate Tarling and Ben Holliday UX London The test of a good user need: If you showed it to a user, would they recognise it as their need? Is it written with words real users use? Does it describe the problem rather than a solution? Will it stay the same regardless of changes to technology, policy, and existing services? Does it help you organise and prioritise work? By @leisa

Slide 56

Slide 56 text

Kate Tarling and Ben Holliday UX London Good needs Bad needs Need to know if I can or can’t go to the UK Need to know exactly what I can and can’t do while here, so I’m not thrown out of the country Need to complete an application and send documentary evidence of my eligibility Need to read latest guidance on policy changes

Slide 57

Slide 57 text

Kate Tarling and Ben Holliday UX London Framing the problem

Slide 58

Slide 58 text

Kate Tarling and Ben Holliday UX London We should be able to trace anything we do to a clear user need, policy or organisational objective. We must be able to measure progress when working towards these goals.

Slide 59

Slide 59 text

Kate Tarling and Ben Holliday UX London Framing the problem 1. Why are we doing this work? 2. Who are our users? 3. What outcome will users get from this service? 4. What outcome are we looking for? 5. What are our key metrics? http://bit.ly/frame-the-problem

Slide 60

Slide 60 text

Kate Tarling and Ben Holliday UX London 1. Why are we doing this work? What is our motivation for building this product or service?

Slide 61

Slide 61 text

Kate Tarling and Ben Holliday UX London 2. Who are our users? Who do we think would need to use this product or service?

Slide 62

Slide 62 text

Kate Tarling and Ben Holliday UX London 3. What outcome will users get from this service? What problem will it solve for people?

Slide 63

Slide 63 text

Kate Tarling and Ben Holliday UX London 4. What outcome are we looking for? What problem will it solve for our organisation?

Slide 64

Slide 64 text

Kate Tarling and Ben Holliday UX London The problem in both hands User Get something done Faster decision Not waste time Faster payment Clear content and signposting Public sector Reduced costs Increased automation Increased effectiveness Increased efficiency Reduce error and support required

Slide 65

Slide 65 text

Kate Tarling and Ben Holliday UX London Simpler, clearer, and faster services so good people prefer to use them

Slide 66

Slide 66 text

Kate Tarling and Ben Holliday UX London 5. What are our key metrics? What do we need to measure against these outcomes?

Slide 67

Slide 67 text

Kate Tarling and Ben Holliday UX London Find the right level of focus for a team to organise their work around the needs of users, understanding constraints and key measures

Slide 68

Slide 68 text

Kate Tarling and Ben Holliday UX London ‘We need a digital form so that applicants can self serve more’

Slide 69

Slide 69 text

Kate Tarling and Ben Holliday UX London ‘We need a digital form so that applicants can self serve more’ Who is ‘we’? What are users really trying to do? Why this? How else? Why now? Or else? What does this data tell us? What does this allow us to do? How would this be different? See more at http://bit.ly/2mRZkj8

Slide 70

Slide 70 text

Kate Tarling and Ben Holliday UX London Decide solution Question everything ‘We need a mobile app’ ‘Why do people even need to study…’

Slide 71

Slide 71 text

Kate Tarling and Ben Holliday UX London Decide solution Question everything ‘We need a mobile app’ ‘Why do people even need to learn…’ Agree outcomes Know... Decide... Record… Take action… Feel confident… Do the right thing...

Slide 72

Slide 72 text

Kate Tarling and Ben Holliday UX London Orienting around services

Slide 73

Slide 73 text

Kate Tarling and Ben Holliday UX London How we introduce end to end service design in large organisations that understand and structure work in different ways eg IT portfolios, technology programmes, projects, enterprise architecture

Slide 74

Slide 74 text

Kate Tarling and Ben Holliday UX London Write or rewrite all project descriptions using simple and clear language, so that everyone understands what it is doing and where money is going

Slide 75

Slide 75 text

Kate Tarling and Ben Holliday UX London Un-pick solutions Check suitability Check eligibility Check identity Make a decision ‘Case work system’

Slide 76

Slide 76 text

Kate Tarling and Ben Holliday UX London Describing a service ● start with a verb ● describe the activity the service lets the user do and reflect the policy intent ● be made of words the people using the service use ● be the only way the service is referred to http://bit.ly/helping-teams-define-their-focus

Slide 77

Slide 77 text

Kate Tarling and Ben Holliday UX London ‘Electronic aviation reporting transformation project’ Fly a small aeroplane to the UK Check if someone is allowed to land

Slide 78

Slide 78 text

Kate Tarling and Ben Holliday UX London Frame the work in terms of the end to end service, to help you see where there is cohesion, and to align teams

Slide 79

Slide 79 text

Kate Tarling and Ben Holliday UX London Common types of services Start Stop Check or share Register/provide info Get or apply Claim Move Become Learn

Slide 80

Slide 80 text

Kate Tarling and Ben Holliday UX London Having a way to understand services helps align different groups by using the same language for all the different parts

Slide 81

Slide 81 text

Kate Tarling and Ben Holliday UX London Get or apply for something e.g. passport, driving licence, permission to study in the UK

Slide 82

Slide 82 text

Kate Tarling and Ben Holliday UX London

Slide 83

Slide 83 text

Kate Tarling and Ben Holliday UX London A service Sub-services Activities Capabilities Technology Data What someone is trying to do e.g. work in the UK Key stages e.g. applying The things that need to happen e.g. finding out how or verifying something The ability or capacity to do these things Systems and tools that support this service The actual data e.g. name, address

Slide 84

Slide 84 text

Kate Tarling and Ben Holliday UX London Finding out Routing & action Make a decision Meeting rules Enforcing rules

Slide 85

Slide 85 text

Kate Tarling and Ben Holliday UX London Patterns and standards help us scale better service design across a large organisation

Slide 86

Slide 86 text

Kate Tarling and Ben Holliday UX London

Slide 87

Slide 87 text

Kate Tarling and Ben Holliday UX London

Slide 88

Slide 88 text

Kate Tarling and Ben Holliday UX London https://projectsbyif.com/ideas/we-should-know-whats-made-a-decision

Slide 89

Slide 89 text

Kate Tarling and Ben Holliday UX London Identify desired service outcomes to help guide all the work across a large service

Slide 90

Slide 90 text

Kate Tarling and Ben Holliday UX London Theme 1: Finding out Theme 2: Routing & action Theme 3: Make a decision Theme 4: Meeting rules Theme 5: Enforcing rules

Slide 91

Slide 91 text

Kate Tarling and Ben Holliday UX London Theme 1: Finding out about something Outcome People know the right thing to do and what to do next. Or they know they don’t have to do anything. Measure - Comprehension - Likelihood of doing the right thing - Proportion of people who need help

Slide 92

Slide 92 text

Kate Tarling and Ben Holliday UX London Theme 3: Make a decision Outcome Organisation has the data it needs to make a decision to grant something Measure - Ratio of positive to negative decisions - Ratio of those refused who are subsequently accepted - Time someone is waiting from start to end

Slide 93

Slide 93 text

Kate Tarling and Ben Holliday UX London What people are trying to do usually doesn’t neatly align with one team or one organisation, it cuts across them. It changes how we need to work together.

Slide 94

Slide 94 text

Kate Tarling and Ben Holliday UX London ‘Get permission to do something’ service overall service owner Finding out sub service owner Routing & action sub service owner Make a decision sub service owner Meeting the rules sub service owner

Slide 95

Slide 95 text

Kate Tarling and Ben Holliday UX London Setting long term goals and vision for services

Slide 96

Slide 96 text

Kate Tarling and Ben Holliday UX London A mission statement is an ideal future state or vision for the service that we’re working to deliver. It describes what we’re trying to achieve

Slide 97

Slide 97 text

Kate Tarling and Ben Holliday UX London The challenge is to imagine something that asks the right questions

Slide 98

Slide 98 text

Kate Tarling and Ben Holliday UX London Emotional: Is there a compelling emotional component? Tangible: Is there a clear enough picture to work towards? Open: Is this vision of the future adaptable to change?

Slide 99

Slide 99 text

Kate Tarling and Ben Holliday UX London Good example (Co-op Funeral Service): Give time back to Funeral Directors to spend with clients digital.blogs.coop/helping-funeralcare-rethink-how-we-deliver-our-at-need-funeral-service/

Slide 100

Slide 100 text

Kate Tarling and Ben Holliday UX London Good example (government): A way for people to share medical information with government that’s instant, transparent and trusted

Slide 101

Slide 101 text

Kate Tarling and Ben Holliday UX London Good example (government): Same day decisions for permission for people applying to do something

Slide 102

Slide 102 text

Kate Tarling and Ben Holliday UX London Good example (local authority): Give time back to carers travelling to visit people in their homes

Slide 103

Slide 103 text

Kate Tarling and Ben Holliday UX London Bad example: A fully digitised customer experience by 2020

Slide 104

Slide 104 text

Kate Tarling and Ben Holliday UX London Bad example: Customers fully self serve which cuts support costs

Slide 105

Slide 105 text

Kate Tarling and Ben Holliday UX London Bad example: More intelligent and smarter use of data across the end to end service

Slide 106

Slide 106 text

Kate Tarling and Ben Holliday UX London Bad example: Leverage cutting edge technology like blockchain, AI and VR to deliver modern services

Slide 107

Slide 107 text

Kate Tarling and Ben Holliday UX London A good mission statement should: ● be a single sentence ● start with a verb ● focus on a real problem people have ● not refer to a solution ● be possible to measure ● be big enough to aim for ● be adaptable to change

Slide 108

Slide 108 text

Kate Tarling and Ben Holliday UX London Communicating service design

Slide 109

Slide 109 text

Kate Tarling and Ben Holliday UX London Scenario How something is now

Slide 110

Slide 110 text

Kate Tarling and Ben Holliday UX London Scenario How something could work in future

Slide 111

Slide 111 text

Kate Tarling and Ben Holliday UX London Journey What users actually do - or what they could do

Slide 112

Slide 112 text

Kate Tarling and Ben Holliday UX London Picture of whole service* Reality. Spot gaps and opportunities to align *Don’t start here

Slide 113

Slide 113 text

Kate Tarling and Ben Holliday UX London What we believe we need to do, generally speaking

Slide 114

Slide 114 text

Kate Tarling and Ben Holliday UX London Which team could do which part

Slide 115

Slide 115 text

Kate Tarling and Ben Holliday UX London When might each part happen But work to reduce dependencies between teams

Slide 116

Slide 116 text

Kate Tarling and Ben Holliday UX London Roadmap of problems to solve Not solutions to be delivered

Slide 117

Slide 117 text

Kate Tarling and Ben Holliday UX London Test and learn about riskiest assumptions, not ‘minimal viable products (MVPs)’

Slide 118

Slide 118 text

Kate Tarling and Ben Holliday UX London What is our riskiest assumption? How can we test it?

Slide 119

Slide 119 text

Kate Tarling and Ben Holliday UX London Prototypes for how might we check if someone can do something? eg. drive, work, care for children List of prototypes Create a check code Send link in an email Show digital proof Request proof from someone

Slide 120

Slide 120 text

Kate Tarling and Ben Holliday UX London Prototype (fake) the end to end service, not just the digital interface part of it

Slide 121

Slide 121 text

Kate Tarling and Ben Holliday UX London Summary of things we typically use: Scenarios User journeys Picture of a whole service Choreographing the work of other teams Prototype parts of a service or patterns Prototype the whole service (fake it)

Slide 122

Slide 122 text

Kate Tarling and Ben Holliday UX London Getting senior level buy in for good service design

Slide 123

Slide 123 text

Kate Tarling and Ben Holliday UX London 1. Get top cover support 2. JFDI: Make good examples and publicise 3. BE the top cover support 4. Reality distortion 5. How to win friends and influence people 6. Allies and alliances 7. Embed with decision makers and budget holders 8. Be willing to see this change over 2 - 5 years 9. Keep going

Slide 124

Slide 124 text

Kate Tarling and Ben Holliday UX London Thank you kate@katetarling.com holliday.ben@gmail.com