---
id: "workshop:human-centered-design-february-21"
type: "InnovateUS workshop"
title: "Human-Centered Design for Public Servants"
url: "https://innovate-us.org/human-centered-design-february-21"
date: "2023-02-21"
duration: "90 minutes"
language: "English"
instructors: ["Virginia Hamilton"]
recording: "https://www.youtube.com/watch?v=ggwy4Qcu6vs"
transcript: "automatic, from the recording"
source: "InnovateUS (innovate-us.org)"
licence: "CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/), as stated on innovate-us.org"
---

# Human-Centered Design for Public Servants

InnovateUS workshop · 21 February 2023 · 90 minutes

Join Virginia Hamilton in this 90-minute virtual training on Human-Centered Design, participants will learn how to use design thinking for public problem-solving. Participants will be given an overview of the five key phases of the human-centered design process - empathize, define, ideate, prototype, and test - and will learn strategies for using human-centered design to improve government services for those who most need them. To watch this recording enter the passcode: xzuFC8Z^

## Learning goals

- Learn how involving "users" can help them better understand the nuances of the problem they are trying to solve
- Learn how to conduct effective interviews

## Speakers

- **Virginia Hamilton**, Senior Fellow, The Burnes Center for Social Change

Recording: https://www.youtube.com/watch?v=ggwy4Qcu6vs

## Transcript

Automatic transcript of the recording: names and terms can be misheard, and the times can be a few seconds off. Each time links to that moment of the video. The transcript alone: https://innovate-us.org/human-centered-design-february-21.txt (plain text) and https://innovate-us.org/human-centered-design-february-21.json (every segment with its start and end second).

**Virginia Hamilton**

[0:00](https://youtu.be/ggwy4Qcu6vs?t=0) I'm delighted to be here to do this intro to human-centered design. Hold on one second. Make sure the technology works. Here we go. As Hannah said, I have been a public servant almost all of my career. I spent 17 years working in California state government. I founded and ran a nonprofit for local government for 15 years, and then spent six years in the Obama administration in the Department of Labor. That's where I discovered and fell in love with human-centered design. Hannah said it was called the Customer-Centered Design Initiative because I was worried that people in the federal government would not want to talk about humans, so we called it customer-centered design. Now I do many different things. I work with the Federation of American Scientists. I work through the Partnership for Public Service in teaching a class called Gov21, which is a program for people in the federal government who want to be change makers and troublemakers. I'm now just starting to teach that class at the state level. I'm piloting something here in California, being funded by Schmidt Futures. I also teach human-centered design. I teach people how to design and facilitate good meetings. That's me with a bag of ideas. When I was at the Department of Labor, I will say I'm very proud that in addition to leading the Customer-Centered Design Initiative, in which we did train 2,000 people around the country, mostly in the workforce development system, I also raised our score out of all the federal agencies. Employees have to do a survey every year called the Federal Employment Viewpoint Survey or something like that. I was leading the team of people that moved us from

[2:04](https://youtu.be/ggwy4Qcu6vs?t=124) 17 out of 18 in all our scores around innovation up to seven in a couple years. We got a lot done. Thank God for Homeland Security. They were number 18. That's who I am. What I'm going to talk about today is both an intro to design thinking, a few things that I've learned about using design thinking in the government context, and give you some examples of the kinds of things that I've done and then hope we have time to have a conversation as well. Assuming I can make all the technology work. First, I want to start with a story about MRIs. If you've had an MRI, can you just write in the chat what that felt like? Now I've got to find my screen again. What did it feel like?

[3:05](https://youtu.be/ggwy4Qcu6vs?t=185) Virginia, I'm having to read some of these. I'm seeing loud, claustrophobic, lots of uncertainty, scary, cold, claustrophobic, right? Yeah. All of those things. I've had one. I've felt all those things too. Many people do. This is a story about a guy named Doug Dietz. He was an engineer at GE Healthcare, and he and his team spent years and years designing and building MRI machines. MRI machines have saved probably millions of lives, diagnosed millions of diseases and conditions. He was actually in a hospital right after this machine had been installed, talking to the technician. He was very proud of the work that he had done. And he, at some point in the conversation, was asked to please leave the room, and he asked why.

[4:10](https://youtu.be/ggwy4Qcu6vs?t=250) The tech said, well, this is when we need to bring in the anesthesiologist. He was a little puzzled by that and went out in the hallway where he overheard a family talking to their child. This was an MRI that was used for pediatric medicine. This father was saying, you've got to be brave. The parents were almost just worried as much about just getting their child through the MRI machine as they were about the diagnosis itself. What he learned, what Doug Dietz learned, was about 80% of the pediatric patients had to be sedated before they went into the machine. He was actually sort of horrified by that and went out and discovered this thing called human-centered design. He worked with a company called IDO, which is a famous international design firm that would probably claim that they invented human-centered design. They didn't, but they certainly have popularized it. He worked with a design team. The design team was full of parents, medical professionals, and children. As a result of the design that they did, they came up with this.

[5:33](https://youtu.be/ggwy4Qcu6vs?t=333) It was really literally a decal that they could just put on top of the MRI machines. In addition to being a decal, it was really about the experience. When children would come into the hospital and they were told they were going to a spaceship or a rocket ship or a pirate ship, it was a pirate ship, it would be like they got a pirate's hat. They were given a sword and they were told, when you go in, you've got to lie down really, really carefully and be super still because pirates are going to come attack you. Just before the whirring and the banging, it was like, okay, it's a spaceship, it's going to shift into hyperdrive, so you got to really be still. They created this beautiful experience for these children and families that included everybody. It was doctors, it was x-ray technicians, it was receptionists, it was the parents themselves. The sedation rate within literally a couple of weeks went from 80% down to 20%. I love this example of human-centered design because, particularly for those of us who work in government, this was a cheap solution.

[6:56](https://youtu.be/ggwy4Qcu6vs?t=416) They, I mean, it was decals and some paint on the wall, but it was also training people on how to create a different kind of experience for the families. I'm going to stop there, I think, and we're just going to show a very quick video, which means I'm going to have to stop sharing my screen. Hold on one second, we can do this. Maybe I can do it. Stop sharing. Hannah is going to show about a four-minute video that I also love as just a beginning way to start talking about design thinking. Can you all see the video? Yeah. Okay, great. Let me just mute. Okay. Oh, we need sound.

[8:00](https://youtu.be/ggwy4Qcu6vs?t=480) Can you stop it? We don't have sound. We don't have sound. Sorry, did you say I should stop it? Yeah, there's no sound. Okay. One second. Jess, do you mind if I send this to you to make sure if you could try it? Here's, I'm going to send you the link. Yeah, I can. I just sent that to you. Sorry, everyone. I'm not sure why the sound didn't come from my screen. Can you guys hear this? No. Okay, let's just skip it. There's always something that's going to go wrong. I would urge you to watch this video later. We'll put the link in the chat. Don't watch it now.

[9:15](https://youtu.be/ggwy4Qcu6vs?t=555) It's a video that just talks about human-centered design and the fact that we design everything. We design doors. We design what clothes we wear. We design what our houses look like. We're always designing, and we can design in ways that are helpful to people, and we can design in ways that are not. So let me, oops, sorry, that's a wrong one. We've got the technology glitches, which we forgot to talk about at the beginning. There we go. Okay. How do I share my screen now? There we go. Sorry.

[10:20](https://youtu.be/ggwy4Qcu6vs?t=620) Okay. Okay. So on to what human-centered design is. It's a method or a process for solving problems, really is at its core. It's just a replicable, scalable way to solve problems in which, instead of focusing first on the law, the regulations, in the case of government, the new appropriation, the new piece of legislation, we're really focusing on people. And there are five steps along the way, or three or four, depending on what company you're looking at or what website you're looking at. This is a classic view of human-centered design, which I'm going to use to step you through this process. We also, in human-centered design, use this magic question when we're trying to generate new thinking, which is, how might we? And how implies that we're going to actually do something.

[11:33](https://youtu.be/ggwy4Qcu6vs?t=693) It's not, can we, will we, should we? Might actually reduces commitment. We're just saying, how might we? Not like, how can we, how will we? And then we implies that we're doing something together, that design thinking and human-centered design is a team sport with radical inclusion of different ideas. And this is one of my very favorite quotes from one of the co-founders of Waze, who said, fall in love with the problem, not the solution, and the rest will follow. We are solution machines. From the time we're little kids, we're raising our hands saying, oh, call on me, I've got the answer. As we go to school, we come up with papers that are solutions to problems. When we get to work, we get promoted because we're the people that have the solutions. You've probably all heard a manager say, don't come to me with a problem, come to me with a solution. And we're just fixated on solutions. And in human-centered design, we resist the urge to immediately start coming up with solutions. And we spend a lot of time really trying to understand what the problem is, because how you frame a problem will actually help frame solutions. And if you want to be innovative and think differently, then you have to really spend some time on problem framing.

[13:08](https://youtu.be/ggwy4Qcu6vs?t=788) So I'm going to go through the steps of design thinking. And the first is to build empathy with your customers. There are a couple of images here. One is this man in a wheelchair. And one of the things that we like to do when we are interviewing people is to interview what we call extreme users, those people who are at one end or another of a particular problem that we're trying to solve. You may have heard of the curb cut effect. It is people who use wheelchairs, lobbied in cities across the country to get curb cuts so that they could navigate the streets. And not only did that curb cut help people who are using wheelchairs, but it also helped people who were using strollers and using roller bags and using carts and using shopping carts. And so that solving for an extreme user solves for a lot of other people.

[14:08](https://youtu.be/ggwy4Qcu6vs?t=848) My other favorite example, and this does come from IDEO, the design firm, they were designing a new kind of pill bottle and asked an extreme user, a woman in her 80s who had a very bad arthritis in her hands, what her experience was with pill bottles. And she said it was fine. And so in addition to listening to people and having empathy interviews with people, you also need to observe them. And so they observed this woman coming back from the pharmacy, and she walked right in the kitchen. She took her pill bottles out of her bag, put them through the deli meat slicer on her counter, and then poured the pills into baby food jars. So she had developed a workaround for her pill bottles. And I suspect that almost everyone who works in government, sooner or later, has developed a workaround around a really stupid rule, regulation, policy, whatever it is, and to the point where they've sort of forgotten that it was a workaround. So the first thing we want to do is we want to build empathy by listening and observing. And I also want to make the point here that it's not just customers, but it's also staff. Our frontline staff, people who work directly with our customers, know a lot about what's going on with customers. And if we don't design for our staff as well as for our customers, they're going to work around it. We can have a beautiful, elegant design for our customers, but if it doesn't work for the staff, they're going to figure out a way to not use it. So I'm always very conscious about including staff in any kind of customer research that I do. Another way to build empathy is to build journey maps,

[16:09](https://youtu.be/ggwy4Qcu6vs?t=969) and here are two different examples. One comes, these both are from government, I believe. One is a disaster survivor. The other is someone who's trying to get more information about grants and benefits and funding from the federal government. And in both cases, there's a couple things going on. One is the moment or the touch point or the activity that's happening along the way. The second is what people are thinking. And the third is what their emotional state is. We understand now through neuroscience and through behavioral science that, I don't know, something like 80 to 90% of any person's decisions are actually unconscious and emotional. And then we go up to our head and think about it. And so in human-centered design, we spend a lot of time thinking about the experience of people, not just sort of what they're thinking. I put this quote up on the top. I'm teaching a class right now for state government, and a very well-meaning person in the class after the first day said, if we could just educate people about all the different agencies in our department and what they do, then they'd have a better and easier time getting to the right place. And it took everything in my body to not say anything because here I am, it's the first day of class, and I don't want to contradict one of my participants. But the truth of the matter is, whether it's a disaster, whether you're looking for a grant or funding, whether you're applying for unemployment insurance, whatever it is, with your experience in government, you do not care what department is going to help you, and you should not. People are people, and we need to figure out as government how to get them what they need without them having to understand that this agency does this

[18:14](https://youtu.be/ggwy4Qcu6vs?t=1094) and this agency does that. I can get on a soapbox about that for a while. So, as we're doing customer research and understanding more about the problem, we're going to define and redefine it a number of different times. This photograph represents a classic situation or story that was in the UK. There were, in an office building, a set of people who lived, who worked there, who kept complaining to the office building owner that the elevators were too slow, and so he started thinking about, oh my god, I'm going to have to add another elevator, I'm going to have to put another, you know, faster machines, I have to change algorithms, and it was all starting to add up to a whole lot of money. And finally, someone said to him, why don't we just ask them what they are, um, what they're complaining about? And as it turns out, they weren't really complaining that the elevators weren't fast enough, they were just complaining that they were bored while they were waiting. And that's a really different solution with a really different set of ideas that you could use to solve that problem than if you actually thought the problem was that your elevators were too slow. And in fact, I stay at a hotel in Washington DC often, and I just love their solution. They have, on certain floors, a map of the area that you're in in Washington DC with all sorts of little pinpoints about where, you know, museums and galleries and other kinds of um, uh, sites are. And sometimes I'm like, oh no, the elevator's too fast, like, I really want to want, like, I want to look at it some more. So defining your problem actually really helps box in what your solution is. So we try to stay big and loose when we're first doing our problem

[20:16](https://youtu.be/ggwy4Qcu6vs?t=1216) solving. And there are lots of different tools to use. First, of course, I've just described uh, trying to empathize with your customer, doing customer interviews, observation, um, using analogous thinking by looking at other systems. And then there are also tools specifically for problem solving. There's the five whys. Some of you may be familiar with that, particularly if you have young children. It's sort of a thing that happens automatically. There's a tool called an abstraction ladder in which you're trying to understand how the world would be a better place if you solved the problem. And then what are the barriers standing in the way and how it can be done. There, there are a number of different specific tools that you can use to help you really land on what you think your problem is. Because you can, you can solve a problem in a very elegant design project and have it be the wrong problem. So we spend a lot of time there. Beth Novick, who maybe some of you know, has a whole course on problem, solving public problems and problem framing. And it's just a very important part of our process that sometimes pushes people.

[21:32](https://youtu.be/ggwy4Qcu6vs?t=1292) They just, it's like, okay, we have enough time with the problem. Like we want to come up with the solution here. But very important. Here's one more example I'll give you. Often in government, your boss, the secretary, the governor, the mayor, the deputy secretary, has a great idea. And you're sitting around wondering what problem they're trying to solve. And this comes from my colleagues here in the California Office of Data and Innovation. The governor went to them during COVID and said, I want you to build an app that will tell people all of the different kinds of services that are available to them and all the benefits that are available to them during COVID that will help them financially. And my colleagues at ODI, instead of just rushing out and building an app to solve the problem, started really understanding better what was already out there and what people really needed and came up with a very elegant solution, which was everyone was applying for unemployment insurance. So how about after people finished their unemployment insurance application, there was just a pointer to more benefits. So tax credits and TANF and help with energy bills and other kinds of benefits that people could be eligible for if they were already eligible for unemployment. So sometimes you have a solution handed to you. And I think this is a wonderful example of sort of taking that solution and just tweaking a little bit so that the solution is easier, faster, and a better one than the boss gave you. Oops, hold on one second. Man,

[23:36](https://youtu.be/ggwy4Qcu6vs?t=1416) I am having technology problems today. Sorry. There we go. So once you've finished your customer research and you've thought about the problem a lot and you have empathized with your customers, you're going to develop some insights, which are going to help you figure out what problem you really want to solve. And this comes actually from work I did with IDEO when I was still at the Department of Labor. It was a time at which there were a lot of long-term unemployed who were coming into career centers around the country. And it was a different kind of customer. They were older, they were more skilled, they had played by all the rules, and they were being discriminated against because they were older. And after doing a number of interviews and better understanding who this group of people were, we developed the insight, which sort of sounds obvious after the fact, but it certainly wasn't at the time, which is that emotional states really matter.

[24:41](https://youtu.be/ggwy4Qcu6vs?t=1481) So when someone's walking through the door of a career center because they're unemployed and they're looking for work, if they're about to lose their house or their apartment or their car, they're panicked. And in fact, they don't need to spend the next hour learning how to use LinkedIn to network with other people. They don't even need a job, they need money. And those people are really different than someone who has sent out a million resumes online and they haven't gotten anything back, and they're just stalled. They have no idea what to do next. And those people are really different from people who might have lost their job because the whole industry or occupation has gone away, and they just have no idea what to do. And so depending on these different emotional states, instead of just doing a one-size-fits-all orientation, which is what typically all the career centers, at least in California, were doing, we experimented- I didn't get that. Could you try again? Sorry, Siri's talking to me. We developed a different way of working with people as they walk through the door in certain areas to experiment and prototype. And one of them was just to triage, like an Apple store.

[25:51](https://youtu.be/ggwy4Qcu6vs?t=1551) So when people walk through the door, instead of just immediately throwing them into a orientation that most of them wouldn't listen to for more than five minutes, we just asked them a quick set of questions, and then we did this sort of speed dating where they would be assigned to the right people to talk to about whatever their issue was. And then once you have an insight, once you've developed some sense of what the problem really is, then it's all about ideation, which is a fancy word for brainstorming. And this was something that I did here in California, I think. This was- we did some- we did human-centered design remotely using a Miro board. And this was once the team design teams had come up with their how might we questions, in this case, how might we improve our virtual services for job readiness training, or how might we provide handoffs of resources to employers, we just come up with as many ideas as we can.

[26:57](https://youtu.be/ggwy4Qcu6vs?t=1617) Lots and lots of research that says that quantity is better than quality. If you have 100 ideas, 10 might be great. If you only have 10 ideas, one might be good. So we really go for quantity when we're first coming up with our ideas. And then we start taking our ideas and creating some prototypes that we can then test. There's a couple of examples here. One comes from the work I did in Detroit a few years ago, where, again, I do a lot of work in the workforce development field. The- they realized that the- there are nine career centers in Detroit, and they realized that they put their brand new staff at the front desk, which was like a really bad idea, because when someone's coming up to the desk, you want someone there who actually knows everything about what's going on in the community. And so they- the design team came up with the idea of having a welcome team academy and a year-long training for people who worked at the front desk.

[28:02](https://youtu.be/ggwy4Qcu6vs?t=1682) Well, they didn't go out and then develop the training and start the class. They literally just wrote on the Word doc, this is what the class is going to be. Here's the format. This is what's going to happen. Here's the schedule. Here's the content. And they showed it to people who worked on the front desk. They showed it to their managers and said, would this be useful? How can we tweak it to make it better for you? And so on. This is also a photograph of people I worked with in Chicago who were doing some prototyping to create a different way of- I'm not remembering now what it was- a different way of doing something, but actually using their hands and doing prototypes, because when you're using a prototype, you really want to show people and not tell them. I've also included here just a little image of the design museum magazine, because this particular issue, which was in the fall of 2022, is all about design and government, and particularly talks about using human-centered design in policy. So you will get these slides, and it'll just be a flag for you to remember to go find that magazine. You can see most of the articles are online for free. These are more examples of testing. We developed- we did a day in Boston a few years ago looking at the future of work and using human-centered design to come up with some new ideas. On the upper left-hand corner, you can see a worksheet that was our idea for what a prototype would be and the kinds of assumptions we wanted to test and the way we would actually go about building out that prototype and testing it. On the right is- Some work I was doing with an organization that was creating a new video for their website.

[30:08](https://youtu.be/ggwy4Qcu6vs?t=1808) And literally, the guy just held up a piece of paper that looked like the front of a screen and read a script. And then along the way, people would stop him and go, no, that doesn't make sense or that's not going to work. The guy in the back is taking notes. So you're prototyping something because you want to make it as rough and scrappy and cheap as possible, so that when you go to actually build it, you've already tested it with your users. The one on the bottom, the photograph on the bottom, was some work we did in Oregon, where when the first thing that people saw when they walked through the door of the Career Center was a big stop, a hand saying stop, and we just prototyped a couple of different messages. Wait, you're up next with a smiley face. We had a couple, I think we had three different versions of this, and we tested them once a week. And then we asked the people who worked at the reception desk what the mood of the customers was, when they walked up to the reception desk and literally just changing the wording on a sign changed the experience of the people walking through the door.

[31:20](https://youtu.be/ggwy4Qcu6vs?t=1880) One of my other favorite examples is I have a friend who ran a center down in Long Beach. And in the parking lot, instead of saying American Job Center this way, it said good people and great jobs this way. So just that tiny little change really changed people's experience of those government services. So you want to prototype and test. It's not something we do in government at all. We tend to have an idea and then have a committee, and then we get in a room together, and we bring in the experts who know something about it, and we write memos and documents, and then they go through clearance for a year, and then they hit the streets, and no one has ever actually been exposed to that idea or that new policy or that new procedure. And often they don't work. So I love this.

[32:26](https://youtu.be/ggwy4Qcu6vs?t=1946) I stole from somebody, sort of. I changed it a little bit. But our customers don't want a product, a website, a program, a workshop. They want to make their lives better. And we have, I think, a moral obligation, frankly, as public servants to make the experience of people who, particularly people who need government, an experience that is as good as possible. So I also want to sort of close this part of the presentation by saying this is a quote from Antoinette Carroll, who runs a creative reaction lab, which is a design firm in St. Louis. It's really focused on community design and co-design and collaborative design. All systems, including systems of oppression, inequality and equity, are by design, and therefore they can be redesigned, which is the good news.

[33:32](https://youtu.be/ggwy4Qcu6vs?t=2012) So how much time do we have? Are we OK? Yes, we're good on time. Awesome. So we're just going to I've been talking a lot. There are a lot of you. We are just going to practice an empathy interview. This, by the way, this image came from Dolly. If you have not started experimenting with open AI and some of the chat GPT and some of these tools, I literally typed in animals and different computer screens talking to each other and got this image. We're going to practice doing an empathy interview and we're going to put three, try to put three people per breakout room. So spend just a few minutes in introducing yourselves. Pick someone to keep time. Most of you have phones that have timers on them. Person one is the is the one with the first name closest to a. So if there were April was in the room, she would go first. If Zelda was in the room, she would go last and just time.

[34:41](https://youtu.be/ggwy4Qcu6vs?t=2081) Talk for two minutes about what intrigues you or concerns you about using human centered design in government. And the other two people just listen. Don't comment. Don't have a conversation. Just listen. And then you'll go to person to person three, each talking for two minutes. And then we'll have a few minutes at the end for for the three of you to be able to comment or ask questions until the time is up. We're going to have it's going to be 12 minutes total. And we'll come back and talk for a few minutes about those experiences. And then I'm going to run through a few more slides about lessons that I've learned about using human centered design and government. So I'm going to now turn this over to Hannah. I'm going to stop sharing. I'm also going to put the instructions in the chat. Okay, I'm just creating the breakout rooms.

[35:45](https://youtu.be/ggwy4Qcu6vs?t=2145) I'm about to send you off into them. It's not working for me. Thank you. So I'd love to hear just a little bit about if people will be willing to come off of mute and just say either something that they talked about that they thought was interesting or what it felt like to just be listened to, which doesn't happen very often in our lives. Anybody willing to also write in the chat. Want to come off mute and just say, let's talk about.

**Audience**

[36:28](https://youtu.be/ggwy4Qcu6vs?t=2188) I'm a trained facilitator I've never asked a question that no one didn't answer for like a half an hour. So, Virginia, Virginia, my name is rich Kilpatrick I'm from New Jersey. I had to superb problems that were presented I'm not talking from the, the listener perspective about you know being able to be listened to I'm talking about, you know, the real problems that the people were, were trying to address it's very interesting.

**Virginia Hamilton**

[36:58](https://youtu.be/ggwy4Qcu6vs?t=2218) And not easy. Definitely not easy. Yeah, I would say. One of the many reasons I love working with government as opposed to in in the private sector is that there are a lot of very difficult wicked problems that are really really important. And I love that you're all trying to work on them.

**Audience**

[37:25](https://youtu.be/ggwy4Qcu6vs?t=2245) I'm a micro was fantastic I want to thank the people who were in it. What was really interesting to me is that we didn't actually get into our own like problems because I don't know about you guys but minor endless at my agency. But instead we focus on some common things that stand between us and human centered design. One of the things that came up is that it's very hard to get by and at the right level. So very often it's the people, people lower down the organization, who are closer to the customers are more aware of how a form should be redesigned or what needs to change but they don't necessarily have the power to implement it. So one challenge is how do you get the buying of the people at the top. You know how do you get a sponsor. Yes. So that you can actually do this. And then one of the people in our group brought up a great idea which she said sometimes she finds. She just has to do it like she'll mock up the form, she'll bring it to somebody, and then we'll say, Oh, that does look better.

[38:31](https://youtu.be/ggwy4Qcu6vs?t=2311) And sometimes it's, you just jump into it you just start producing a solution I hope somebody will care and listen. Another thing we noted is that problem definition design thinking all this stuff can be very threatening, so that sometimes when you mentioned oh there's a problem with this process or a problem with this form, what you get is just the person defending the status quo.

**Virginia Hamilton**

[38:57](https://youtu.be/ggwy4Qcu6vs?t=2337) Yeah, two comments on that one is when I was at the Department of Labor, I, this was not my job to use human centered design, I just did it. And in fact, I was on in California. My boss was in DC, and the. And I had some people saying well we should talk to people in DC about what you're doing and I said do not talk to anyone in DC, because they'll just shut this down. Goofy Virginia and California, and I had to wait until I had enough. I had my two state two of my states were involved in the projects, and they were super enthusiastic so I could go back to the people in DC and go well my customers want this. They have really good stories to tell. And then I found a couple of good. But just a few champions back in DC who were willing to take the risk to fund it and then, and then of course it gains momentum but I was I slid under the radar for quite a while before I started.

[40:03](https://youtu.be/ggwy4Qcu6vs?t=2403) I'd say the other thing to say about the defensiveness is one of the things that I've learned over the years is that. When you're talking to your boss and saying, this doesn't work this form is stupid. This isn't right like this is a problem. They don't want to hear it and they get defensive, but when you go to them and say, I've just interviewed 25 customers, and they said this and they said this and you have direct quotes, and maybe even photographs or you've built some personas and you've done your homework and you're there to present not your opinion, but what the customers are saying. It's still difficult but it's much harder to to just say well that's, I'm not going to worry about that I'm going to ignore it because it's not really coming from you. I love your you probably a lot of you had great conversations I have a few more slides and then we'll go to. We'll go back to q amp a.

[41:07](https://youtu.be/ggwy4Qcu6vs?t=2467) Let me share my screen again. For my last five slides. And wrap up this part about what human centered design is. It is a replicable process, anyone can learn how to use in which you're instead of starting first with a rule of regulation as something that someone tells you to do. You start with people first, and what they want. You can't ignore the others, I mean whether something is viable and the case of of government it's generally is it legal. Can you do it as within the law. Can you find budget for it is it feasible as the technology feasible which it often isn't in government. There's that sweet spot in the middle that little triangle in the, in the middle that is really about making innovation work.

[42:12](https://youtu.be/ggwy4Qcu6vs?t=2532) So, I've learned a couple lessons, I just told you two of them stay under the radar and let your customers speak for you instead of yourself. Another this comes from the D school at Stanford. A really nice document called a design scoping guide, which you can Google. Before you start using design thinking. Make sure you're using it kind of at the right scope. The, we don't want to solve. I don't want to solve technical problems, we can go get technical people for that I want to solve human problems like products or services. I want to make sure that I care about it, and that my boss cares about it or other people around me care about it. I want to make sure that I'm identifying my assumptions and not building the solution into the into the problem statement which we often do let's build an app for that. So, just some tips on setting your scope before you start to do the design thinking.

[43:15](https://youtu.be/ggwy4Qcu6vs?t=2595) The second, I think is really really important and in the classes that I teach, I'm spending more and more time on psychological safety. This is a psychological safety scorecard that was developed by a colleague of mine at the federal level Beth scuba. And if you're not familiar with the term psychological safety it's it's becoming more and more talked about. It was pioneered by Dr. Amy Edmondson at Harvard, who says, psychological safety doesn't imply, it's not that people are cozy and nice. It's the people are being are able to say I screwed that up, or I took a risk or I have this crazy idea what do you think about this. My friend Beth created the psychological safety scorecards that she used in her, she worked at the CIA so I don't know exactly what she did because she couldn't tell me. But she, she used these cards once a week with her staff and ask them to these questions you know if you make a mistake it's held against you, the people are able to bring up problems and tough issues, safe to take a risk and so on.

[44:28](https://youtu.be/ggwy4Qcu6vs?t=2668) And again you'll have this slide deck available and if you actually want a PDF of that scorecard I can send it to you via the innovate us people, but establishing psychological safety. According to many, many, many researchers is at the heart of teams that are effective and teams that are innovative. Just to, just to think about culture all the time and be intentional about it. These are some of the things that I've noticed work. I remember when I was at the Department of Labor, standing in front of a group of about 500 people, and it was a conference, and someone raised their hand and said, yeah, yeah, I know this design thinking thing, but what if the GAO or the, you know, OMB comes and has this, you know, concern about this or that? And I literally got out from behind the podium and stood in front of the room and said, I'm the regional administrator for the U.S. Department of Labor.

[45:31](https://youtu.be/ggwy4Qcu6vs?t=2731) You have my permission to experiment, to improve customer experience and customer outcomes. And people gave me a standing ovation. Like, people need some kind of permission. We've got permission now at the federal level. President Biden, a year ago, issued an executive order that talks about customer experience and involving end users in all the policy and program and service design that we do in the federal government. There's something similar here in California at the state level. Probably New Jersey has something, because they're awesome. So explicit permission is very important. And then building an infrastructure for ideas to be seen and implemented. Like, I talked to a guy who was the head of a, he was a cabinet secretary in a state. He'd just gotten the job. He said, Virginia, I've got like 2,000 people and I don't have any, no one has any ideas and they just, they're not innovative and they're all bureaucrats.

[46:34](https://youtu.be/ggwy4Qcu6vs?t=2794) I said, you know what, I can guarantee you that you have hundreds and hundreds and hundreds of public servants who really care about what they're doing and they really want to make it better and they just don't know how. So you've got to build some kind of infrastructure so that their ideas can be heard. And you have to train people in how to do innovation. And you have to give people agency over the work and the ways that they work. And then last is stay curious. So those are some, again, sort of quick tips and things to do when you're thinking about bringing innovation into your organization. And then just involve your people. I did this alone for a while when I was at the Department of Labor. And there's so many people who are ready to go, who are ready to come in, who are ready to experiment. And we just have to ask them.

[47:35](https://youtu.be/ggwy4Qcu6vs?t=2855) So I think with that, I am done with my presentation and super happy to just have a conversation now and answer any questions.

* * *

Original page: https://innovate-us.org/human-centered-design-february-21 · Licence: CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/), as stated on innovate-us.org
