Quickly Working Through UX Problems Visually | Jake Haugen | Skillshare

Quickly Working Through UX Problems Visually

Jake Haugen, Thinking design and design thinking

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
10 Lessons (32m)
    • 1. Introduction

      2:14
    • 2. Identify the Problem

      3:14
    • 3. Empathize

      4:52
    • 4. Choose a Scenario

      2:47
    • 5. Start the Map!

      3:47
    • 6. Where and What

      1:40
    • 7. Thinking and Feeling

      2:19
    • 8. Opportunities

      3:48
    • 9. Get Sketching!

      4:17
    • 10. Wrapping Up

      2:42

About This Class

An often overlooked skill for designers is the ability to step up to a whiteboard (or digital whiteboard) and collaboratively think through an idea on the fly. Being able to think on your feet and show your thought process is highly valued in today's collaborative work environments. This is why a “whiteboard” challenge is often part of the interview process at many respected companies like Google and InVision.

Stepping up to a whiteboard, especially in front of an audience, can be super intimidating. This course will give you an adaptable framework allowing you to confidently show your thought process, gain stakeholder alignment and explore new ideas in a user-centered way.

During the course, you’ll apply your learnings by working on a class project. By the end of the course, you’ll have visually worked through a problem and sketched key screens that are backed up with user-centered thinking.

The process you’ll learn is best used for a project kickoff when you're initially exploring a problem and documenting assumptions. It can also help you ace an interview whiteboard challenge.

No prior experience is needed for this course.

Transcripts

1. Introduction: Hey, what's up, everybody? My name is Jake. I am a senior user experience designer, and I am here to teach you how to think through UX ideas in a visual way very quickly, a bit about myself. I have about 10 years of experience in industry. I have worked on the agency side of things. I have also worked on the in house product design side of things. I have done everything from exploratory research, Teoh prototyping ideas and testing them in the real world outside of design. I am a father, I'm a husband. I also like to explore crazy ideas. Right now I'm trying to build a pinball machine from scratch and, yeah, I don't know. We'll see how that turns out. One skill that I think is super important for designers to have is the ability to confidently step up to a whiteboard or share your screen and think through a new idea and bring other people along for the ride. I'm talking about that scenario where you're sitting in a meeting and your CEO throws out an idea. Maybe your boss throws out an idea. Everybody turns and looks at you and they say, Well, you're the designer. What do you think you're put on the spot. And when you're in that situation, you're gonna wanna have a framework to go to and think through a problem. And that's what you're gonna learn. This course, a framework for thinking through problems very quickly in a user centric way. What this framework is is basically a condensed version of US process, and it's all assumption. So this is not a replacement for doing formally UX research. It's really just a starting place. It's a way to kick off a project, get everybody in alignment and identify what your assumptions are. I'm not the only one who thinks it's an important skill for designers to build a step up and think on their feet. If you interview at any sort of design central company, think Google or envision, chances are they're gonna have you perform a whiteboard challenge. What a whiteboard Challenges is. They're gonna throw an idea out. You are a problem. They're gonna ask you to work through that problem in a visual way so that they can see your thought process. By the end of this course, you'll be confident stepping up to a whiteboard or sharing your screen and thinking through an idea in front of a group of people and you're gonna be doing it in a collaborative way. You're gonna be kind of leading the show. So we're gonna go through an abbreviated UX process. We're gonna end up with actual sketches or wire frames that you can use to kind of kick off the next phase of a project, whether you're a new UX designer interviewing at places, looking for your first UX job or you already have a job. But you have to get put on the spot. There's probably something that you can learn from this class, so with that said, Let's get started. 2. Identify the Problem: I'm going to be doing this process digitally using my computer. You can use a whiteboard or pen and paper. Really, Whatever makes the most sense for you in the context. You think you're gonna be using this in. So if you're in a collaborative office and you know you often jump up in a whiteboard practice on a white board if you work remotely or you collaborate remotely practice doing any design program and sharing your screen. There is a class project that you can follow along with and do throughout the course. So after each video you can stop there and do that specific step for the class project. Or you can watch all the videos together, take notes and do it all in one. It's really up to you. All right, so we're gonna dive in. The first thing we're gonna be doing is defining the problem. It's really important to start with identifying the problem because you don't want to box yourself into a specific solution. Often, times a conversation about a new idea will start something like we need a calendar Web app for high school students. Now, this is in the worst statement I've ever heard. At least it includes a target audience, which is high school students in our case, but we're already focusing on a solution. Let's take a closer look at that statement. We need a calendar Web app for high school Students were already implying that we know the correct solution is a calendar web. So let's take a step back and actually define the problem. And if you're collaborating with others, you don't want to just write down the problems statement, you're gonna want to ask questions and kind of probe around and pull it out of people. Really, what you're doing is just facilitating. You're not actually coming up with the ideas yet. You're just trying to clarify and get everybody on the same page. So if you asking, you say, you know what is the problem we're trying to solve here? This sounds like a solution, and they say something like, parents have requested that that's not a problem statement. That's just a request. And in this case, parents aren't even the primary user there, just the parents of the students who actually using the app. So you're gonna wanna keep digging to get to the root of the problem that you're trying to solve. A popular waiter phrase problem statements is in the form of a how might be question. He's got popular with Google design sprints, and they're a really great way to frame a problem statement as a question. So it's open ended, and it's also more of a positive way to put it. So you're not saying something negative like, Oh, this problem is so terrible. But you're saying, How might we solve this? You know, challenging thing in a cool and unique way? An example of how might we question for our problem? Statement could be something like how my we help high school students better manage their time between school and social activities when we're talking about a problem statement, or how might we question We want to make sure that it's narrow enough so we know what we're talking about, but not so prescriptive that we jumped to a solution immediately. And once you're getting close to nailing down what the problem is or what your home might be, question will be, you're gonna want a document that in a public space. So in my case, I'm doing this digitally and I You know, in theory, I'd be sharing my screens. I'm gonna write it down on the screen here. How my we help high school students are user better manage their time between school and social activities. Now, this may seem really simple, but it's really important to, you know, put this in a public space so everybody can look at it and agree on it. And you're gonna want to turn to the audience at this point or the people you're working with and say, Is this really what we're solving for? Does this make sense? And if it's not, you're gonna want to keep asking questions until you nail this down. But if everybody agrees, then you can move on to the next. And that was it for the first step. I know it seems really simple, but you really want to get off on the right foot when you're starting with new ideas. So you wanna be talking about problems, not solutions. And I think we've done that so we can move on to the next step, which is gonna be diving in and empathizing with our users a little bit 3. Empathize: all right. Step number two is empathizing with our users. Now, if you have access to really use a research, you should be using that. In our case, I'm gonna pretend that we don't. Somebody just threw this idea out. So we really have to do our best on the spot to start trying to understand where users are . It's good to call out that this is all assumption based. You're gonna want to say that to the people that you're collaborating with because you want to set the stage for doing more user research in the future. So you can say that Well, we can talk about the users, but we have to all agree that were sort of making assumptions here. And then we may have to back this up with more research in the future. When we're talking about users is really two types. There's primary and secondary users. Primary users are gonna be those that use the system most frequently, and that's what we're gonna be focusing on for most of the activities in this process. Now it's still not a bad idea to call out who the secondary users are as they may impact the system. So we're gonna spend a little bit of time talking about who those secondary users are, but they may not play a big role as we go throughout the process. So let's now identify who our users are. Once again, you're gonna want to ask questions. You pull these answers out of other people, not just make it up yourself. We want everybody to agree, and that's why we're doing it in a public space for everybody. Concede it. I've already called out who are primary and secondary users. Are you concede? I just put it on the canvas here. It doesn't have to look pretty. We're really just kind of trying to show our thought process and bring everybody along for the ride. So for primary users, I have high school students, which we've already identified secondary users, parents, teachers and friends. So we're talking about school work so I could see this kind of cooking in and playing with are interacting with the school system. Or maybe teachers are potentially pushing information to the system parents. Of course, they're the ones probably requesting this in the first place, so they're gonna have a view into the system or impacted some way. And we're also talking about social activities here, which to me means friends. So maybe the high school students friends may also be able to be a secondary user. That sort of impacts their experience of the app that they're going to be using Now. The second part of this process is going to be creating what we call an empathy map. It's a really quick, easy way to kind of put yourself into a user shoes. Now I've already gone ahead and done the empathy map just to speed up the process of this video. But if you're doing this in a whiteboard, you're gonna want to draw out this grid and then label it with thinking, feeling, doing in goals, empathy. Maps are you know, there's not a pre defined way that you should be labeling things you can really kind of adjust. It would make sense for you, but these four things, I think, played really well into the next steps. I'd recommend starting there. So just to briefly kind of walk through, we're trying to do with an empathy map for thinking I'm putting myself into the high school students shoes and I'm saying I don't know. Well, I have time to go to the party. If I study, maybe I just want to play video games and my parents don't trust me to get my homework done . I think that's kind of what we're starting to uncover. What the root of this, you know, time management system is is maybe some, you know, the student isn't really mended in the time in the best way, and the parents are concerned. So that's kind of the story we're telling here for feeling. These are things that internally matter to the user, but they may not be vocalizing. So you know, they're worried about their grades. They're worried about looking cool, and they just want to play video games. Some of these can overlap a little bit, so you can see we have video games and thinking we also have been feeling that's OK for doing were really thinking about the actions that people are taking. So in this case, we're gonna be doing homework or studying. They're going to hang out with friends, possibly participating in after school activities and the goals a really kind of the you know, the end point that these users are trying to accomplish, so they want good grades. They want to get their parents off the back, of course, and they want to develop relationships and friendships. Now, I only have three things for each of these. You can really dig deeper if you want to you, but it's OK to just kind of do a rough past. We're just trying to get people to think in a user center way and kind of put themselves in their users shoes. So after doing this thean pithy map, it's possible that you might want to adjust your home. Might be statement. So going back to look at our home, I we statement, we said, How might we help high school students better manage their time between school and social activities? I think we've dug a little bit deeper, and maybe we can update this now, so I'm gonna change it around just a little bit. How might we help students get good grades? Because we've identified in the empathy map that grades is something that they're worried about and they're thinking about how might we helped them get better grades and still have time to play and developed relationships. So we're just trying to get a little bit more specific here. You know, we've identified that grades are important to our users. We've also identified that they want cool. They want to play video games or whatever it may be. So they won't have time to play. And they want also to develop relationships. So we're gonna translate that back into the how might we statement? And once again, we're gonna want to clarify this with everybody. Make sure everybody's on the same page, and that's it for the second step. So once again, pretty simple. We're just trying to cover a basis. So we have the problem identified. Now we're empathizing with our users a little bit. The next thing we're gonna do is jump in and start generating some ideas for what scenarios we could actually be exploring for the end result, which is going to be some rough sketches or wire frames of the apple will be making 4. Choose a Scenario: on a step number three. We are going to be defining a scenario in agreeing out with everybody. So what we're trying to do here is to limit the scope of what we're talking about. We've already talked about what the problem is and tried toe leave that pretty open ended. We've talked about the users, and now when we're talking about scenario, we want to bring things into a specific thing that we can really dive in and think through fully, We're gonna want to pick a key. Part of the experience of what that means is something that is going to be really important for the success of order for creating. So if it's an app, it's a really key Flo, or activity that user is going to be going through on a regular basis. And once again you want to be collaborative with this, you want to ask people for what they think. A good scenario to focus on would be let people throat ideas right those up on the white board or on your screen and, you know, let people kind of sift through and pick the one that bathing is most important. And once again, make sure you agree to because you're part of this collaboration. I have gone through here and just called out one scenario to speed things up. You can see I'm just kind of building out my art board as I go, leaving everything up so everybody can see kind of where we've been and where we're going. So for the scenario, I'll just briefly walking through what I came up with. For our example, it's Sunday night and autumn. Ah, high school student needs to plan for the upcoming week, so I'm just trying to get, you know, released, specific about When is this happening? Who is this person's? We can really put ourselves in that person's shoes, and the tasks are drinking down the individual steps that we need to be taken to complete this scenario. So once again, these are all assumption based on call that out. The things that I came up with, Adam's gonna need to identify how much time is needed to do homework. She's gonna need to identify any social activities that she wants to attend that week. She's a plan for free time. You know whether she must play video games or whatever autumns into these days, and she wants to make sure that her parents know that the task has been completed. It goes back to the empathy map when we're talking about you know, one of the goals is to get parents off their backs or tie everything back to what you've done before in the empathy map in the How might we question some other scenarios? I didn't think through these fully, but just kind of trying to simulate what some other ideas could be. Maybe signing up for the service in the first place of creating an account. You know, that initial arm boarding experience. Maybe it's sinking devices. So, you know, maybe this is a mobile app, and it's a just top app or something like that. So how did those things talk together? What is that experience? Or maybe it's something simple, like just creating an event. And I think creating event might be part of the scenario we're talking about here. But, you know, it's kind of a more narrow approach for our example. I'm going to say we all agreed on Scenario number one. It's Sunday night and autumn. A high school student needs to plan for the upcoming week. In the next few videos, we're gonna be doing a deep dive on the scenario and mapping everything out step by step. The end goal is to gain some more contacts done where these tasks and these activities are gonna be taken place so that it conformed the sketches and wire frames that we do at the ends. We're making sure that everything is, you know, user centered and based in reality, and we're taking the consideration, the environment, that our users going to be it. 5. Start the Map! : all right. On a step four, we're gonna dive in and explore that scenario a little bit further, weirding me doing this with a very simplified version of a journey map. Often journey mounts are very detailed there. Based on research. Ours is just gonna be assumption based. We're gonna be focusing on the happy path. What a happy path is, assuming everything goes correctly. So we're not going to be worrying about edge cases or weird things that may come up were really thinking, OK, best case scenario, How does somebody go through this process? So we're gonna be focusing on bite sized pieces of the scenario we laid out, which is going back to the document here. It's Sunday night and autumn. A high school student needs to plan for the upcoming week, and in this video, we're not actually gonna start doing the map. We're just gonna lay the foundation. So this is one of the more time intensive parts of the exercise. If you know you're doing this beforehand, you can just create this and then just copy and paste it into your art board like I'm doing here just to kind of go over what we're looking at. We have actions thinking, feeling environments and opportunities. These are all pretty standard things that included a journey map. But you can customize this like the empathy map to fit your specific scenarios. I want you to get more comfortable with these tools, feel free to add and kind of modify. You know, the specific things you're documenting now. We've already talked a little bit about actions which kind of relate to the tasks that we identified in this scenario. We did thinking and feeling a little bit with the empathy map. The environment is sort of a new one. That's where we're gonna be taking the consideration, like where they physically are kind of what's going on around them on the opportunities are really key. Those are the things they're going to really be the driving force for the sketches, wire frame, like things we're gonna be doing for the final step, which is kind of the the final output of this process. So I went ahead, and I'm just gonna paste in some of these actions here, and we'll just briefly walk through. So we're kind of trying to break down this process of planning for the week into bite sized chunks that we can really think through fully. So the first action might be. Maybe she remembers, she has to plan, and she sees what tasks she has to complete the next week. So we're sort of implying here that the information is coming to her now, tying this back to some of the users, parents, teachers, friends. Maybe they're a source. You could be in putting that information for autumn. We're just kind of, you know, spitballing here. We're just saying what is best case scenario if I open up the app So I want to manually at events? No, I kind of want that stuff to come to me. So we're just kind of thinking about what is the best experience we can provide them at this point. Once again, we're talking about this outside of the context of after that. Maybe she finishes her plan and she saves it after she saves it. She goes infuser, dashboard. You know, we have to think about the motivation of why somebody would be using this system. And when I think of a dashboard, I think of it is one of those kind of motivating factors. You go and you see your progress. Or maybe it's game a fight or something like that. This is where we're starting to get creative and kind of set the stage for what we think we might be sketching in the following steps. You want to be collaborative with this, ask people questions, kind of helping throw out ideas and then documented as you go. And for the last one, we're going to say, creates a new reward event, and we don't really know what a reward event is at this place. We're really just kind of making stuff up. Honestly, we're just taking a first pass and what we think a kind of cool experience would be. And we want to think back to what motivates them. And, you know, we had called out that, you know, they just want to play video games. They won't get their parents off their back. So having some sort of a reward for completing a task, I think is a good idea. All right now we have our framework for our assumption based journey map. We've also gone through and feel about the actions row, which is the top one kind of the most important one king. All the other rose to be filled out. And I did this very quickly because I had thought of this stuff a forehand just so I could make this video a bit more snappy. But in the real world, they're gonna be collaborating with others asking questions. So it might take you a little bit more time to fill out the action section of this. In the next few videos, we're gonna go through and fill out the remainder of our journey. 6. Where and What: okay, continuing on with our map. Now we're gonna focus on the wear and what and this relates to the environment so you can see I already filled this in. I'm drawing this from the scenario we came up with earlier, but just adding a little bit more contact. So I'm saying it's Sunday evening, our users at home watching a movie on her laptop. She's in her bedroom and she has access to her mobile device and a laptop. It's really important to call out what the environment is. In our case, it's relatively simple. It's one environment for the entire length of the scenario we're exploring. But in the real world, some of these things can sort of time hop. So, you know, maybe it starts in, you know, somebody's at home and then they're in their car or the writing bus, and you want to take the environment to consideration. You know, if somebody's gonna be outside at a park, you might need to think about screen glare or background noise. In our case, we're thinking about somebody who's multitasking. They are watching a movie on their laptop. They also have access to a mobile device and what will start to kind of inform what technology were using is this environment piece. So in our case, we know our user is already using their laptop for a different task. So maybe we can start to imply that she'll be using her mobile device to complete the tasks laid out. That's it for the environment. In our case, this was relatively simple. It was one contact the entire time for your case. It might be more complicated, you know, Maybe it starts at home and it transitions into a different environment. Maybe they started their laptop, then they only have access to their phone. Or, you know, they don't have access to WiFi or something like that. So you're gonna want to go through each step, really think through what environment you think the user would be in when they're completing that task. The next step will want to do is digging in a little bit more on thinking and feeling roads 7. Thinking and Feeling: genuine. With our journey map, we're going to fill out the thinking and feeling roads. Now, once again, it's really important here to call out that we're making assumptions. If this is not backed with user research, you don't want everybody in the room to think this is the end. All be all you want to make sure that everybody knows you're just taking your best guess right now for thinking and feeling. I've gone ahead and filled this out so you can see once again we're in the same canvas, keeping everything in a public space so everybody can see what we're working on. Often we want to be referencing back to the things we've done earlier so that everybody sees how the entire process ties together. Another good thing to point out is that this is a future state journey map. So sometimes journey maps can be passed state or current state. If you're redesigning a system, what we're doing is focusing on the future. So once again, these feelings are just our best guess going through each one of these the action. Our user remembers that she has to make a plan. She's thinking, Oh, crap, I better do that before I go to bed. No, for this feeling calm. You can fill this out however you want. I have to like to use Smiley faces just because it's really simple way of conveying emotion . Sometimes a little picture can mean a lot more than words. And once again looking at this, this does not have to be pretty. You know, this is something you'll be drawing on the white board or doing really quickly on the fly. It's okay if you know not everything is perfectly centered or things wrapped funny or you make typos. It's okay. You're going to make mistakes when you're put on the spot like this. The next action. She sees what her tasks are for the next week, and she thinks it's a lot of stuff, you know. It's just kind of got a media professors like Do I really want to do this? She completes and saves the plan. Good. I got that done. There's a positive feeling in our little smiley face as a smile. Then we transition into viewing the dashboard, and this is where things start to liven up a little bit more. Oh, cool evidence and points. Now at this point really don't know what points are. It's okay to come back and change things that are in the journey. Mapas you go. None of the stuff we're doing should be fixed. You can always come back and edit things as things unfold. And finally she creates a new keyboard events once again. We don't really know what a reward event is or what it looks like, but when they create that, I user's gonna think sweet, that's awesome And continue with the smiley face. So now we're getting a little bit more detailed into what our journey is going to look like . The last thing we're gonna want to do is call out the opportunities, which is a really key part of this activity. 8. Opportunities : okay, continuing on to the last step of our journey map, which is calling out the opportunities you can see once again, I filled out this row forest. But what I'll do is walking through my thought process of what I was thinking of when I was filling out The opportunities call just kind of another global thing to think about when you're feeling on a journey map. It's OK to do this step by step, so we're sort of doing it row by row. But in the real world, you should probably start with the action and then go through each column. The opportunities. Sometimes it makes sense to leave till the very end. Although you can write some notes down, just remember that you can add on to it over time. Once you get the full journey laid out, some of those opportunities start to become more obvious. There's no hard and fast rules and how you should fill out a journey map. It's really up to you. Just do what feels right for the specific scenario that yourself going over these opportunities a little bit. The first action she remembers, she has to plan. You know she's like crap. She's in that moment. I I can't believe I forgot to do this. So the opportunities first off, we can help them remember, so we can give them a push notification or something like that so that they remember in that moment they have to do their planning, thinking back to their feeling that they're being controlled by their parents. We could limit that feeling by only forcing to plan a couple days in advance. So, you know, maybe only planning the week days or planning one or two days at a time so they don't feel like they're being so controlled and going back and thinking about the motivations. We talked a lot about video games and sort of, you know, playing for these high school students somehow. Maybe weaken Gamma Phi this. How can we motivate them to get into the system and want to do the planning? The second action. They see info on what the tasks are for the next week, and we're sort of overwhelming. That's a lot of stuff. Once again, for the opportunities we can make it play full. We can, you know, have bright and happy visual design, fun interactions we should pre feel as much as possible for them. So this is an overwhelming task for our users who want to make sure that we're giving them everything they have. And, you know, maybe we could get to the point where they just have to hit. Okay, I accept, rather than having to go in and fill out all the details of their week here. We're talking about what technology we were using or he's going to use a mobile app. We're gonna use desktop. We know for our specific environment, we have access to both. So it's sort of open under at this point and going back to the pre filling process. Can we tap into a school schedule? Can we have an interface for teachers to add workloads? Estimated time they should be spending on task so that it will make their planning easier. Third action, they complete and save the plan. We can notify others who may be interested. I either parents, this also leads us to Maybe we need a parent view of this app, so going back to the secondary users, maybe they need a a way to interface with the system they view the dashboard now. And this is where we're introducing the concept of points or some sort of Gamification. We can allow some variation on how they spend their points, need to use it for free time, Internet time. Maybe they get physical prizes or Amazon credits just throwing out ideas here. We can allow for custom rewards, whatever that may be. And then we should also show them why they've earned the points to just reinforce good habits so that they want to come back and use the system again and again and the final step create a new reward event. This is that pay off for them doing their job Well, so we want to, you know, maybe suggest good times for when they should be scheduling that reward event. We already know their schedule. So we can say, you know, you have a couple of free hours on Thursday night. Maybe you should schedule the event for that time. Something like that. And of course, we should congratulate the user on a job well done. So zooming out and just looking at our entire journey map this is pretty good. This is, uh this gives us a lot of foundation to move into the next step. We're actually going to be sketching out some You I stuff up to this point. This should have been very collaborative. This whole journey map should have been a conversation with you and your stakeholders firming on ideas, talking once again. You're just really the facilitator writing this stuff out on the board so that everybody can agree to at this point, you're gonna want to look to the room and say, Okay. Are we all feeling good about this? Is it time to move on to the next step? If not, go back refined things? If so, move onto the next step, which is what we're gonna jump into in the next video. 9. Get Sketching!: okay on to the fun part where we actually get to start sketching out our ideas. As you can see, I've already gone through the whole sketching process and added it to the art board here that in theory I'd be sharing with everybody. So once again, everything lives in this common space. Now, the sketching your wire framing portion of this process can be a little bit time consuming . You don't have to do this in front of people you know, during this process. Once you get done with the journey map, you can say, Okay, that gives me everything I need to start exploring this idea in a more visual way. If you are comfortable standing up and working through these screens in front of everybody , you can do that too. I have quite a few screens here. 123456789 That's more than you really need for this process. These could be super super rough sketches, and you can involve other people with it to This is usually the part of the process for us . The designer will kind of step up and take it a little bit more control of the process, since you're gonna be actually drawing out the wire frames and you know that's our specialty. Is designers or one of our specialties is creating you. So I will walk you through the process of how I came up with these sketches and sort of the thought behind them. First off, you know, I'm always referencing our journey map over here. So the first step is remember, she asked a plan, so that was pretty simple. We called it out as an opportunity as well to give a push notification. So here it is. It's a notification moving into the planning step, also correlating back to our journey map earlier. I have, you know, some suggested events year, and there's a headline kind of explaining With this page is all about Here's your suggested schedule. Do you have any changes the user clicks accept? And that would send a push notification to the parent once again? All things we identified in the journey map. This also would bring them to the dashboard, and we talked a little bit about some of the opportunities here. They view a dashboard, you know, we can allow some variation in how they spend points. Custom rewards show why they've earned the points to reinforce good habits. So we're saying here you've earned two hours of free time, so we're not using the word points here. I just changed it two hours in the moment, cause that made more sense. And we say, You know, you plan for two weeks in a row, you reach your goal of three hours of homework time, and then you have this big action here that says, plan free time That brings you over into the create reward event. And I'm just throwing some, you know, things in here could be video games, hang out with friends, watch a movie other, and we're also going back to the opportunity is suggesting, you know, maybe a good time it would be to create this event so it doesn't conflict with other things . So that was pretty much the flow that we mapped out in our journey map here. I took some liberties and just kind of started to explore, you know, I don't know. What would the menu system look like? So I have, you know, a little hamburger menu up here? We have You know, maybe you can search globally. We have the dashboard view. Of course, we need a schedule of you. So that's what I kind of mocked up here. You know, what is the schedule look like? So not necessarily in planning. But what does it look like after you've planned? Didn't dig too deep into this. But, you know, you build a drill into one of these events, this one See, you don't even have to sketch the u Y all the time. Sometimes you can just add notes of what should be on the screen. And that's what I did for this one. You can view the date and time you repeats, etcetera. And then I also kind of thought of like the opposite end of the you know, if you're the high school student and you're looking at your schedule, but maybe you're not checking it all the time, so you have a general idea of what you have to do. It might be nice if we send them Reminder. Hey, it's time to do homework or something like that. And then I'm going in a new future idea here. Just a random idea. I don't know. Maybe there's a timer where they can record how long they're taking so that we can feed that information back into the system so that we can make it adapt over time. The sketching part of this process may take some time. Like I said, this took me some time to do it. You know, I wasn't doing it on camera. I made tons of mistakes as I was doing this. If you're doing it real time in front of people, you're going to make mistakes. You're gonna say something stupid. You're gonna have to raise something. It's okay. It's all part of the process. Just have confidence. You're the designer. Take control of it and just roll with it. So now we have a pretty complete looking art board we have. You know, we're talking about our problem or users. We have empathy, map, the scenario, the journey map, which then played directly into the screens. Now the last thing we're going to do is kind of wrap this up. We're gonna talk about what the next steps to do after you complete. All of these tests would be then also call outs in areas that we can probably do some more research toe validate the assumptions that we've been making throughout this process. 10. Wrapping Up: all right. Moving under the last step of this process is really just wrapping things up and getting everybody on the same page of what next steps are gonna be So you can see here I've added a few more things to our board. I have uses data to collect assumptions and questions. So these were just some kind of final wrap up stuff you can talk about with the group. If you had ended the process before the sketching parts that you went often did the sketching on your own, you could send those sketches along with some of this wrap up data that would make sense to or if you're doing a real time, go and just do it as a group for the uses data to collect. What I'm really talking about here is you know, if we actually built this thing, what are the things we could start to measure so that we could improve the system over time ? These are just some random thoughts, you know. We could track how time is spent overall. So how are people using the app to schedule homework versus free time versus whatever other activities and look at that data across all of our users to start to inform the system what free time is spent on. So what type of activities are most popular with high school students? And then also, when our users planning quote unquote, is it Sunday night? Is it Monday morning? Is it Saturday morning? I don't know. Just start to get some more information so we can make better design decisions in the future. This is all assuming if this actually shipped and it was a real product in the real world. So it was kind of thinking ahead here, setting the stage assumptions are really important. I've called out multiple times throughout the process. We want to say this is assumption based. This is an assumption. This is not based on research. So this is your time to kind of go back and write all those things on the board. You know, we assume that parents want to be involved with the process. We're giving them a push Notification. We're assuming that high school students are actually motivated by quote unquote free time . That was just a guess. We don't really know that We haven't really talked to high school students. Yes, etcetera. So there's a bunch of things here. We can go back and do more research on. And then we're also calling out questions thes air starting Teoh. Give some examples of If we do go out into the field and do real research the type of questions we could be asking, you know, how do high school students plan their schedules now? Do they do that at all? You know, if they do, plan doesn't actually help them. What would motivate them? Teoh, you know, plan in the first place, etcetera. And that's it for this wrap up step. It's really up to you to kind of customize it to fit your specific scenario. I think a good starting point is determining what things you could measure if this was a real product in the real world. That kind of set the stage for that, calling out your assumptions and calling with questions all the things to do. OK, that is it for the class. Thanks so much for spending your time with me. There is a class project. If you've been following along with the videos and doing the class project, go and post that up happen to give feedback. If you have any had started the class project, go ahead and take a crack at it posted up. I'll take a look at it. Thanks again. I really hope you learned something throughout this course in a lot of fun teaching it and I'll talk to you soon.