Welcome back. In this lecture we'll talked about task and walk-through scenarios. Now you remember in the previous lecture we talked about used cases or usage stories. Which were rich representations that included some information that were often link to a persona. And included information about goals a person was trying to achieve and often details about how they might achieve them. Now, if we think about tasks in particular and we review a bit, remember a task is a specific description that a complete job that users want to accomplish It is the what, not, how. This is it's not, it has nothing to do with the specific interface or way of doing things. It is important to provide details, typical details about how somebody would do the job and it isn't just a list of features from assist them. And instead is the complete job recovers transitions between sub-task. And it's also important to note that once we go to the travel of sort of factoring a task, we're probably committed to saying this is something we actually want to design to try to achieve. Hasn't perhaps been achieved yet with the system but we probably want to do it. So that's a task. It is the what not the how. Now, a walk-through scenario or scenario we typically say it's a specific instance of system use for a particular task, in a particular interface. It's how a user would do this task in this interface. So, again this is all review. So, some examples that Joe gave in an earlier lecture. Somebody might be told a scenario might be telling people click on a calendar icon in this system, hit the next year button to get to May 2017, click on this next link and so on. Or open fitness tract or software on your desktop computer, select share under options menu and so on. Now a key thing is a target user can follow the steps of the scenario without understand the task. And that I think is important when we say target user, because no known as what sort of embodied. And these two very simple examples I gave, somebody can click on the calendar icon, they can hit the next year button. But what has to be true for that? They have to understand that this icon is a calendar icon. That it represents a calendar. They have to be able to Use a pointing device, like a mouse, they have to be able to see the screen. So these are assumptions that we often don't even realize we're making. But later on, in future courses, we'll touch on, well what happens for people that may have motor disabilities, who may be vision impaired, who may be low literacy, who may not understand English. All those things are very important. And you need to take those into account when you understand who is your target user group. >> And for those of you who are taking this course out of order, we did the full introduction to tasks and scenarios in the first course in this specialization. Those of you who went through that probably remember, the exercise where you first evaluated the set of flood in different ways, task and scenario descriptions and then, write your own in the P reviewed. Some of the others for learners who are taking that first course. If you haven't been through that and you don't feel this was enough to feel comfortable with the material. You may want to pause and go back into the task and scenario material and the introduction user interfaces course. >> So let's take an example and this builds on what we have just done in the previous lecture on usage stories. So This is a task description. Anna often finds herself at the mall looking for way to kill a few hours while her family shops. One thing she likes to do is take in a movie, so she'll head over to the mall theaters. But she's got a problem often she's only heard of one or two of the movies, she's not sure which one she'll enjoy the most. And so often she lend up seeing a movie she doesn't like that much. Anna's task is to find the movie playing at the theater that she will like. Now, if you want to go back to the usage story it might be interesting to contrast that with a task in the usage story that we presented for Anna. We heard a little bit more about Anna, we linked it to the persona and we also saw more about how she might do it with Movie Lines Mobile, which does not exist yet. But that's okay because the usage story was aspirational, here in the task description, we're simply factoring out. What she's trying to accomplish, namely, get a recommendation for a movie playing at the theatre, that she would like. >> And I think sanity check you can always use for task description is, could you give this to somebody, who's one of your target users, and say go do this. And could they do it on different interfaces and at the same time would they understand what it means to do it? And with something like this you might operationalize it for them. You might tell them the name of the mall differently depending on where you were running your tests. Pick a local mall wherever you happen to be. But the idea of find a movie playing at the theatre that you'll like, is a task somebody can figure out how to do. >> Mm-hm. Okay, so let's, I'm going to walk you through a couple of scenarios for this task. And remember, a scenario is a particular way to do a task in a particular interface. Now on this slide you have a set of step by step instructions for doing it using the Google Chrome web browser. Let's go over to Google Chrome, and I'll actually just sort of lock through this myself and illustrate how you might do this. Okay so the first step would be and we've already taken the first step. Which is to type into the address bar on Google Chrome the name of the theater you were at. Again this is one way to do this task in a particular interface, here Google Chrome. So I've done that and I get Showtimes at AMC Southdale 16. And I can start to look and see what's showing I see Suicide Squad is showing, Sausage Party, Pete's Dragon. If I wanted I could here at the bottom I see it says more show times, there's a down arrow here and if I wanted I could click on that. And if I do that, oops I get a list of all the movies that are playing, including Ben-Hur. And if I look over on the right side here, I see lists of aggregate information from different rating sites, so IMDB rates it 4.7 out of 10. Rotten tomatoes gives it a 30% and metacritic, I think, gives it a 41%. If I scroll down a little bit more, I can see cast information, I can see people also search for, and so on. I can go back if I want. And look at information for other movies as well. So if I click on suicide squad for example. And then look over on the right side again. I can get this aggregate information. And if I scroll down I should be able to get information for critic reviews. Now notice this isn't personalized for me. It does not tell whether I would like it, how much I would like it. But what I can do is I can click on any of these pieces of information like one of these reviews. I can get the full review. I can click up on Rotten Tomatoes here. And I can go to Rotten Tomatoes page. And I can see a bunch of information about that movie. I could read through it and make my own determination as to which movies at this theatre I might like. So now if we go back to this scenario for Google Chrome. What I would say about this is this is a way that I might be able to satisfy the task, but it's not tailored to it. It leaves me doing a bunch more work. And that sort of takes me to the next point. Which is since this scenario does not fully support the task I had to specify the theater I was interested in and then even worse. I had to look through all this information about all these movies playing to see for myself rather I might like them or not. It's not a great way to support the task. And so, let's preview a little bit a technique will be talking about a lot in the next course. I could prototype interface that supports this test much better. And then we'll see how I would walk through that interface with a scenario to do the task, and I hope that scenario will be much easier. Okay, so what I just did was I sketched out on paper a prototype as design idea for a mobile application that would support this test very well. Now the basic idea here is I created a paper prototype. This is a quick way to capture design ideas and as we'll tell you if you go on to the next course. This is a surprisingly useful way for testing interface ideas at getting fundamental feedback on whether the design idea makes sense or not. And so, I sketch something out I call it movie lands on the go. And I have a couple of things that you can tap or touch to move on. One says, let's see what does that say. It says recommend near me and below it is movie lens classic. And I look at those and I think, well I'm actually interested in Getting recommendations near me. So I will touch that. And so, the first step in this scenario is to tap or touch the length that says recommend near me. And when I do, movie lens on the go tells me you are near the AMC Southdale 16 theaters. And the options it gives me then are recommendations for movie showing. Here, more theaters, and again, movie land's classic. The next step in the scenario is to tap on recommendations for movie showing here, and what I see here is a, let's see, yeah, I see in this prototype. Thank you Joe. >> Yeah, there goes the cursor. I see the idea being communicated here is I have a little graphic for each of the movies. I have the movie title. I have movie lands predicted rating for me, which I gave as a number. And I have upcoming show times. And so I can immediately, at a glance see what are the movies playing, how much I would like them, when they're available. And if I want I can then touch the title of any displayed movie to get more information about the movie. And I can I can repeat this step as necessary to give me a little more information to support myself in this decision that I need to make. And so just to recap what we did, we presented a quick sketch of an interface that makes a lot of sense. Movie lines on the go that lets me get information for movies. As I'm out, s I'm about it uses my location and it makes it easy for me to see my predicted liking for the movies that are playing. Now that doesn't exist yet but it is a design idea that I have captured with this paper prototype. And it is sufficiently detailed that it let's me specify what's a scenario would look like for Anna's task. >> So just we don't lose the context of this in documenting user research, what's critical here is that we've looked at capturing tasks These are not necessarily all aspirational tasks. Most of the tasks we will capture are what people are trying to do now. >> Mm-hm. >> It just may be that there are certain tasks that are not very well supported. And so we will use scenarios as we did for Chrome to show how do people do this now? And by capturing what they do, and how they do it or what they want to do and how they failed to be able to do it. We can identify the opportunities for design that allow us to create this type of prototype and say there's an opportunity to make life better. We could do the same thing in mundane areas like payroll or signing up to for garbage collection or anything else. We look at what are the steps, what they are trying to do, what are the steps today, and when we find out that the steps today feel inadequate. What might we start thinking about as we move toward prototyping of how we could make it better? >> Absolutely. And that's it for this lecture. What we did is we took a deeper dive into tasks and walked through scenarios. And as Joe just said we gave you a quick preview of moving into the design world of doing paper prototyping. Which is a useful technique for capturing ideas, ways that we can better support tasks that are not so well supported today. We'll cover that in detail in a future course, and we'll look forward to seeing you next time.
