UX Process Simplified - From User Research to Usability Testing | Muhammad Ahsan | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

UX Process Simplified - From User Research to Usability Testing

teacher avatar Muhammad Ahsan, UI UX Visual Designer 10+ Years

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

51 Lessons (4h 42m)
    • 1. Introduction to UX Process Class

    • 2. Aligning User's mind with the Product

    • 3. UX Process steps related to Business and Users

    • 4. UX Facts You Must Memorize

    • 5. User Life cycle Funnel

    • 6. Define Scope Of Your Project

    • 7. Project β†’ Write Product Scope Story

    • 8. UX Design at Macro and Micro Levels

    • 9. User Experience Process 4 Step Simple Version

    • 10. UX Process Simplified Diagram Explained

    • 11. Top to Bottom UX Design Process in detail

    • 12. Stakeholder Interviews

    • 13. User Interviews

    • 14. WAAD/Affinity Diagram

    • 15. Project β†’ Create Affinity Diagram

    • 16. Personas in User Experience Design

    • 17. Online tools to create Personas

    • 18. Project β†’ Create User Persona

    • 19. Empathy Maps

    • 20. Competitive Analysis

    • 21. Feature Matrix - Deciding which features for MVP

    • 22. Models and Diagram in UX Process

    • 23. System model Diagram

    • 24. Project β†’ System Model Diagram

    • 25. User Journey Maps

    • 26. Project β†’ Create User Journey Map

    • 27. User Scenarios

    • 28. Project β†’ Write User Scenarios

    • 29. User Stories

    • 30. Project β†’ User Story

    • 31. Use case diagram

    • 32. Hierarchical task inventory Model

    • 33. Project β†’ Create Hierarchical Task Inventory Diagram

    • 34. Task interaction models

    • 35. Information Architecture and Card Sorting

    • 36. Ideation and Sketching

    • 37. User Flows and Site Maps

    • 38. User Flow Diagrams in detail

    • 39. Project β†’ Create User Flow Diagram

    • 40. All about Wireframes

    • 41. Everything about Prototypes

    • 42. UX Design deliverable

    • 43. UX Designer + Development stage

    • 44. Four types of Usability tests

    • 45. 5-seconds to test First Impressions

    • 46. Project β†’ Conduct a 5-seconds test

    • 47. Essential Tasks Test- Usability Tests

    • 48. Project β†’ Conduct a Usability Test

    • 49. Exploration tests

    • 50. User Surveys and Questionnaire

    • 51. The end review and thanks

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

When a beginner start their User Experience Design process, they get confused about where to start the UX Design Process. There are hundreds of things involved in a UX Design process and each design firm uses their own version of this User Experience Process.

Project based course –

β†’ Creating and Improving User Experience of an Ecommerce Startup called Frokland

Should we start with User Interviews, Personas or Customer Journey Maps? Should we first define the scope of the product? Which UX process is related to Users or the Business?

In this class, you will learn how to start User Experience process in a simplified way for beginners and why do we need User personas, feature matrix, competitive analysis etc…

You will get tons of DOWNLOABLE RESOURCES in the format of

  • PDF Notes
  • UX Templates to get started

You will learn about

  1. User Lifecycle Funnel
  2. Defining the Scope of the Product
  3. Stakeholder Interviews
  4. User Interviews
  5. WAAD Affinity Diagram
  6. Personas
  7. Empathy Maps
  8. User Journey Maps
  9. Feature Matrix
  10. Competitive Analysis
  11. User Scenarios
  12. User Stories
  13. Hierarchical Task Inventory Model
  14. User Flows
  15. Site Maps
  16. Card Sorting for Information Architecture
  17. Task Interaction Models
  18. Wireframes
  19. Prototypes (in details with types of prototypes)
  20. Usability Tests
  21. First Impressions Test (5 seconds test)
  22. Essential Task Test
  23. Workaround Test
  24. Surveys & Questionnaire

I will also show you few online tools to create User Flows, Site maps, Card Sorting, Personas and User Journey maps so you can create them online with ease

If you have any question, you can always ask me

Now let’s dive into the course and start learning the UX process in detail


Meet Your Teacher

Teacher Profile Image

Muhammad Ahsan

UI UX Visual Designer 10+ Years


I started my Freelancing Career 10+ years ago and learned everything the hard way myself. I went from scratch to end up working for FORTUNE 500 companies like INTEL, PANASONIC and Coca-Cola.

In just 2 years of Serious UI Designing, I made my place on DRIBBBLE
Working with Art Directors from Coca-Cola and Project Managers from the UK, I learned a lot in short period of time.

Worked from App Icon Design to App UI Design, from wireframes, prototypes and Mockups Design. I have a hunger of perfecting User Interface from all aspects

What my students are saying about my Classes?



I am a multi-talented person who has won One Gold Medal, won a nationwide Poster Design competition from PANASONIC and won many Landing ... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Introduction to UX Process Class: welcome to my course about yours. Express design process. And in this course I'm going to simplify this process for you. Now I have seen Dunn's off different user experience design methods, user experience, design terminologies that are circulating online. And when a newbie like me or like you, when they start lending something, they get confused. That how I'm going to start my user experience design process. Now, I haven't I want to build an app or an e commerce store. Where should I start My user research. What is the information I'm going to get from it? How I'm going toe form that information into personas in tow, use the stories and into different affinity diagrams and all that that stuff. So in the scores, I'm going to go from step by step from step one, which is user investigation and research. And then we are going to go to step through design and we're going toe make sense off that user data we have collected and we're going to form in the end, on the end result will be our wire frames, which we will deliver to our designers and development. Now we are going to also make different business decisions that rich feature. We should build a rich feature we should not be. So these are all the things we are governed going toe cover in this course. If you are a big net. This is a project based course, so don't need to worry about it. We're going to build an e commerce store from user research to actually creating of I frames for this aecom a story. You are going to really love it. If you have any questions regarding the schools, you can always ask me. You can post your commands or suggestions, or if you want something more from me, you can always ask me. I can add into that course, so I hope you will learn a lot along with me in the scores. So let's start designing some awesome user experiences. 2. Aligning User's mind with the Product: Have you ever wondered why you are creating all these different user experience documents and artifacts like user personas, user flow diagrams and customer journey maps, different floor diagram, site maps, Dominion diagrams, all these different, kind off user experience, documents and all these things you are creating? Why and what is the reason behind them? I have seen a lot of designers. They have shown their you can say user experience process, and they have used different jar guns and different terms, which you know might not be. You know, you might not be, or even I might don't be able to understand. Now the reason is, whatever you do in your user experience process, you need to understand why you are doing it. And what is the reason you are building that user personas of your stories or whatever you are building. So in this video, I'm going to show you why. Actually, we do all this stuff and ah, why you should care about it. So the thing is, whenever we are producing user personas where we're taking user interviews in our user experience process or building any kind of diagram, what we are doing is we are aligning the understanding off our user and on the other side is the business. So we are aligning the user and the product developer or the start up CEO or the thinking off those developers closer to each other. They are going to match on a line. So we are going toe, get a shared but for both off these parties, users and business. So what we're going to do is we are going to get into the head off the user. We're going to interview uses. We're going to interview business and stakeholders, and we're going to see really the ghouls off. Both of them are going toe a line. So that is why we do use their persona. Mastic holder interviews different floor diagrams that what is the what is in the mind off our user how they want to, you know, go from one screen to another screen in our design and things like that. So you need to consider that we are bridging the gap between the understanding off the user off about your product and understanding off the business about their product. Maybe they're thinking that users want to order this stuff, but in fact uses might not like that feature off the product. They might try to use another one, or they might be using something else. So these are the things we are going to, you know, go through in this course. Second thing, I want you to, you know, focus on is don't try to create useless user experience, documents or personas or things like that. Artifacts. So if you are wasting your time creating tens and thousands off for hundreds off, different diagrams flow diagrams and you are not getting to the point or you are missing the big picture, then they are all useless. There must be a very solid reason behind every U X process document. You are preparing that it must be done, so there must be a solid reason behind it. Try to focus on bridging the gap between users and the business. What other users needs part of the business needs and what are their fears. What are their frustrations and try to eliminate that and create are useful product. So that is all door. Try to do you unnecessary user experience work. I hope you have enjoyed this lesson. If you have any questions to ask me, let's move on to the next lesson 3. UX Process steps related to Business and Users: fine ever. We are going through some user experience design process. There are three or four different kind off diagrams that you are building or documentations user experience documentations You are actually building, so I'm going toe, you know, categorize them into major categories. For example, there will be things that are littered to users and user behavior. For example, we have personas that are going to talk about what users frustrations are. What are his schools or hard goals? What are his daily life? Patrons and context were. Actually he uses our app or things like that. So these are all going toe based on users. So there is information that is a little too users okay. Similarly, we have empathy, maps where we actually investigate users and what is happening in their mind. What is their emotional state or things like that? So these are things which are related to users. Similarly, we have customer journey maps or things like that where we actually test the interaction off the users that along our whole part off their interaction with our organization with our website with our my our mobile Ikuma store were actually our user, got frustrated and we're actually he called our help line and we're actually Are we failing in all these different steps? So this is all about user behavior. So how our customers are behaving or interacting with our products? What actually are the frustration, What are their goals? What are their triggers to buy something, things like that. So this is these are all the study about user behavior and user psychology And what? How users that actually in directing with your product, then actually, on the other side, we are going toe generate different detailed diagrams that alleged toe how our business is actually going to work out. Our economist role is going to work. How are they? And what are the specifications that we are going to give to our developers, for example? And that will be later toe mostly business and how it actually works. So how our happy is going to, you know, help the user whether we are going toe, create a 24 hour help line or something like that. So what actually is going toe be present on the website or on the business side to solve this user problem that we found while investigating users So these are all the different types off diagrams, someone little toe business, some related to users, and some are also related to your competition. For example, I want to test my product. So how I'm going to able to see that I'm performing well, I can compare it with someone else. For example, someone else aecom store, a famous economist. Or if I want to test my log in or my sign up that how easy it is for my users to sign up and join my website or start ordering, I'm going toe. Compare it with a similar website on my competition. So some diagrams, some user experience, design, documentations and processes are related. Toe your competition. So your competition, your business and how actually it is going to work your website specifications. Your mobile app features all that thing. Then we have uses. So these are actually three or four different guy kinds off and user experience documentation we are going to see in this course on day. I hope to see you soon in the next lessons. If you have any questions to ask me, let's from one to the next system 4. UX Facts You Must Memorize: no. Before we jump into shoes expense design process or start getting information from a user's , there are few facts you need to understand. The 1st 1 is you are not your user. So whenever you are trying toe, create a new app or building AECOM a store or some product, you are not what your user is thinking. So your mindset and your juices mindset are totally different. Even if you are thinking that I know how to use this product, I know that he's going to click over here and he's going to do that. But when actually in reality, if you try to test any user, they are going toe miserably. Phil, when I waas doing user research for this course, I actually was building an economist role for girls dresses from age like three toe 12. So when I started, you know, investigating users about it, you can see that they were not even able toe sign up. They were not even able to create there account on that Ikuma store, so this is very alarming. If someone cannot even, you know, sign up for your website or cannot create an account on your website, how they are going toe order from your website. So there are a lot of things you are going to find that will be surprisingly, you can say surprisingly awesome. So try toe, understand that you are not your users. So always try to test 3 to 5 users that don't know anything about your website. And they have, like, you can say, um, different. Kind off. You can see expertise for ordering online. There might be uses that that are not very good with computers and ordering online. There might be users that are expert in ordering online, so you are goingto go from four port off them. Similarly, the second is that if you are going toe, make any user experience design decision you are going toe involve everybody in it. If you have a developers and if you have your business owners, you are going to get hurt them around and you are going toe. Select your priorities. Maybe the user may be the CEO off the company or the manager off the company. They might have more insight in tow, that feature or something like that, they might, which you might not know. So if you are just working alone or you have Ah, one team member with you are You are a freelance that like me. You need to involve other parties with you big before making any decision. Okay, so these are few things you need to keep in mind. One is that you are always going toe base your reserves on the user testing. You always need to test your prototypes, your products or whatever sketches you have designed toe at least three users. Then you are going toe. Go to the next step. Okay? So don't go into designing or into the next steps before testing it with a user's. This is going to be, you know, really awesome for you. You might, you know, get amazed by what users actually do with your website or video. They might not even be able to log in. So these are all the things you need to keep in mind. Before digging into he was experience, design process. I hope you have enjoyed this lesson. So you saw on in the next lesson 5. User Life cycle Funnel: in this video, we're going to talk about the business needs from user experience, design perspective and how we're going to quantify them into different stages and how we're going to plan our business, that how we are going to convert our customer or hope we're going toe on money using our business model, which is user lifecycle funnel. So this is actually ah, very good method off, accessing that your product is running something on order. We are losing business or North, so don't ignore that. I have seen a lot off newbies on New as you expense designers that they don't look at the business side off every product or each product because ultimately, our goal is that we need to earn more revenue or we need to convert more customers things like that. So this is actually user lifecycle phone and you can see on your left. Okay, so or maybe right, I don't know anyhow, So the first thing is, the first step is awareness. So you are making your customers affair off your product by advertising by using Facebook ads by using different channels, maybe newspapers or things like that. Second step is education, so you are, Uh, maybe you have some video on your ad or things like that. So users are going to play that and see and get educated about that part of what this product does for them. What is the benefit that they get from that product? So the second step, after 1/3 step after education, is once they learn something about it, then they are going to visit your website, so they are going to engage with your product. Maybe they are going to click on the get more info link and see what this product is all about, so they are going to engage with it. They might, you know, try to click on the Try it. No, for 3 14 days or things like that, they might click on that. So once they click on that, they have started engaging with your product. They have some interest in them. After this stage, we are going to convert them. Or maybe we want their email address on there trying on page. They have to give the information to get our download the better version or maybe free version off your product. So once they have download it that they have given you something and they have converted toe, you know, converted customers. So they have given you email and they have tried your product started trying your product. Now, after this stage, we are going toe convert these converted customers into our revenue. So we want them to, you know, shift to our $20 part month price model or things like that. So we want them to be our period customers other than free customers. So this is our revenue stage. Maybe we have genetic $10 or $20 part of customers or things like that. After revenue model, we have recurrence. The currents mean that maybe a customer he just tried your product for maybe one month. It's premium product. And he paid, like, $20 spot for the first time. And the next month he left. He left without saying anything. He left and he didn't come back. So this is the problem on your revenue stage, which means that after using your product for one month, there is something that your user didn't like. And they, you know, are not your recurrent customers that they are not willing to pay you again. and again. So problem can be on any stage. For example, if you're losing ah, lot off customers after your awareness stage. For example, whenever someone tried to click on the video and for example, I have used Facebook and I know that my ad has been reached toe 10,000 people, for example, just for instance. So when 10,000 people saw my ad, but none off them or maybe just 500 off them clicked on the video to play or they read about it. They go toe visit my website. So I am losing a lot off my customers just after the Awareness day. So I will. I will try to, you know, I saw that problem, that there is some problem on that stage. Similarly, if someone is trying out my product and I'm losing a lot off my customers when they try to convert or try my free product than this is again a problem that there might be something, or maybe something I'm asking in the submit form, which the user don't want to give. For example, I have ah phone number on my my website, and I have seen that a lot of my shoulders. They don't. They are not willing to give their private phone number two, you know, subscribe to my list. So this is a very big problem. I haven't taken care off that, but you can see this is a problem. So this is a problem on your yes conversion stage. So all these problems are at different stages. You need to find that where we are losing our customers, where the drop is too much and second thing we need to cover is cost. So there is costs related to producing a madness about your product. For example, I'm advertising on Facebook or Twitter or Instagram. I am using, like maybe $1 par customer. So one customer, when he converse or to my website or move to my website engaged with my website from there , that ad on Facebook, it costs me $1 par customer producer. So, for example, if I convey my message or my awareness campaign toe 1000 customers so my cost is $1000. So at all these stages, when the funnel goes to the last one, which is recurrent, I just get to customers which pay me for a lifetime like $20 per month or things like that . Okay, so I'm going to calculate my cost and my end benefit from this funnel. So if I'm losing like, $1000 in the later stage, whether I'm getting $2000 at my recurrent stage or at my revenue stage or not, so this is going toe. Show me the bigger picture off where I am losing my business, where I'm losing my customers, what is happening at these stages and why the customers are reluctant to pay or upgrade to the premium product or things like that. So these this is very important for businesses, for products, for APS, for websites because everyone wants their business spoken word Or maybe someone more subscriber list Toby increase or things like that. So this is a very important topic I want to cover in this video. I hope you have liked it and loved it. If you have any questions to ask me, let's move on to the next lesson. 6. Define Scope Of Your Project: Now, the first thing in your user experience design process is defining your scoop. So we are going toe justifying our scope that who we are designing for what we are actually building and what value it is going to give that do that user so that these other three things that are going to be your first small story about your product So I'm going to show you just a simple example. For example, we are building Uh huh. E and e coma store for busy moms. So this is our primary users. We are building on Egham, a store for busy moms that will help them easily filter their kids dresses based on colors , fabric type and things like that so they can easily purchase or make their but using decisions and by frocks or dresses for their little girls. So these are the three things actually I used in this whole story. First is what we are building. Second is the primary Jews. 1/3 is what is the value or the benefits. What are its unique features? So we are showing that we are different from others in thes unique features, So these are the main features like, um, filtering easy navigation and making buying decisions easy, easier for the users, these other things we're going to work on. So we are defining our overall goal for our whole user experience design process. So this is very important. Also, if you can make a deadline, for example, we want to develop it in three months. Are humans? So this is very good, because this will give you some off the timeline. That way, we want to be inside this time, and we want to limit ourselves. So we are going toe locate two days for user research or user interviews. One day for business are owner interview and three days for, you know, building of the first prototype or affinity diagrams or things like that. Two days to our testing usability testing so you can just build any product within a week. 10 days, 15 days. If you define your scoop and the time limit, you're going to do that during this time. So these other things I want to, you know, get before you even start any project to find the scope overall scope by showing the product features what they are going to solve the problem and for which users and what actually you are building. So these are two or three things you need to keeps. Aziz. Your you know, user experience design process in the first few steps and try toe show me and write your products. Ah, thuh this simple story off your scope scope story You can say there are no fixed terms in user experience design. Just you need to get the formula and try to use it in your projects. I hope you have enjoyed this lesson. If you have any questions to ask me, let's move on to the next lesson. 7. Project β†’ Write Product Scope Story: Now you have learned about your scope story or the first defining scope. Now is the time that you create a story or felines product summary off your product using your primary user and what value it will deliver to your primary users. So try to look at any website. For example, Air B and B are any other website, which you or service you use and try toe. Create a three line products summary off that three or four line products somebody off the product and its value it is going to deliver to the primary users. For example, if you have chosen Airbnb than the story will be for adventure travelers or maybe the travelers that want to save their cost, they are going toe. Uh, we are going to build, AH rental service, which will be used by Travelers Toe, book their toe economically, book different houses off people or rented out different properties. So this is going to be something similar to that. So try to write your story. O. R. You can say scoop story off your product and show it to me. Okay, so just three or four lines you can ride it about any product you have in your mind, for example, and in fitness, app or any weather AB or things like that. So these this is not, you know, constricted or a stick of one app or idea. So you can use any idea and just build a school and show it to me. OK, so I'm reading for your assignment. 8. UX Design at Macro and Micro Levels: user experience design process is evolving day by day. Every organization have different set off Jews experience, process and their documentation and all these things. They are different from other organizations. There is not a very fixed standard in all this process. So when I started user experience design, I was confused that there are different kinds of diagrams. There are users personas you, the interviews veer. Should I use which one and how much time should I give to that diagram or shoot or do this diagram really matters in my design process of user experience design. So all these questions I'm going to simplify this in this lesson. First thing you need to understand is that whenever you start building something, you are going toe, be less detailed, so you're your view will be from top to bottom. You are viewing something from very high above, like a birds eye view. Then, when you are going to move inside all in more details or in more depth into user experience process, you are going to get a bit more detail into your process. You are going to add more details, more specifications, more documentation. You are going to be specific because all these specifications are going Toby Toby handed over toe your designers and development team. So whenever you are solving a problem, you need to be very tough. You need to be very sketchy. You need to be very simple and you need tohave a broader view off the whole problem and the solution. So let me tell you a story off one of my clients what it is he had a great idea off an app . Hey, started bailing it and it was a neighborhood safety community. After neighbors inform others about the local area that this section is not safe or this street is not safe, I have seen some suspicious person over there and what he did wrong, Waas that he actually added, like 20 or 30 different more features into the same trap which will not needed. So you are going toe make different business decisions that should this feature be, you know, be added to this app right now or should we eliminate it? So you were going to build different priorities, business priorities that this is going to cost us that much. So these are all the things you are going to be doing in user experience process. You are going to first move from your baseline or base level diagrams, more detailed diagrams or more specific on diagrams or more specific tasks what your app is going to do. So that is all for this video. I'm going to show you all the different diagrams and names and hope Vale. Actually, they fall in the design process, so see you soon in the next video. 9. User Experience Process 4 Step Simple Version: user experience. Design is a problem solving skill and it is a process off solving a problem for your users and your business. So I'm going to elaborate just a basic four steps in any user expense design process. So let's sketch started now. The 1st 1 is analyzed like any other problem you are having in your real life situation, you are first going to analyze it. So the first thing is you are going to investigate. Why is this happening and with whom it is happening? Well, it was happening. So all these things are going to be go into analyzed it. Then we're going to move on to the Explorer and design. So whatever debt of we have gathered from over users and from other stakeholders, we are going toe, get their data and use it for quickly going through some off the solutions. For example, maybe for ah, one click card, for example, my customer needs ah, shopping cart that is just going toe be in just one click. So my user is going toe klik once, and everything is going toe done. They don't need to enter all these things. So for that, maybe I come up with three or four solutions. This is going to happen in ideation. Ideation Stage is going to where you are going to explore different designs. Solutions. Then we are going toe get those prototypes and we're going to test with our users and going to get feedback. So this is the explorer and design phase where we are going toe, create early prototypes and test them its users. Then we are moving toe implementation stage. So in the implementation stage, we are going to use the wire frames and detailed specifications we have developed are designed in our design and explore stated and give it to our developers team and they're going toe build some solution out off, dead. Then this implementation phase is going to end. And we are going to release our first product first version off our product and we're going toe conduct some usability test. We're going to get feedback from offer users. Did you like this game? Did you like this product? Did you like this website? What we can do to make it better? What is the problem you are having? So this is going to be a feedback from a juice it's so along this whole journey. There are two things that are very common, which is broader types and feedback. So, as early as possible, you should start building your prototype. So if you are in your analyzed age, you might have already some idea in your head that maybe if I have this kind of prototype, I can show it to my users and get some user interview and get some user data what is in their head so you can use the that prototyping analyzed it. Then in the design stage, you might have some more elite prototype that is almost closer to your are somewhat similar to your final product, and you contest that and explore more design ideas of once you have moved from designed to implementation. If you try to change something after, according it or once the product has been launched, the cost and time will be too much to bear, so it will be a loss of time and cost. So try toe, you know, get more into what the users and what is in the users had before you start implementing any solution. So try toe, invest more time into analyze and explore and design creates other than implementation phase. Now let me show you the overview off what we are going to do and how I'm going toe make you understand. Off the whole, you're the experience design process from a bird's eye view. 10. UX Process Simplified Diagram Explained: Now let's come to the actual user experience process. So in this diagram, I am going to show you how it can be simplified. What is a process and why we do it now On the top level, any product, any website, any Web, any mobile app. It is connected with two entities. One is users and the second is business. So one side, we have business on the right side. We have users, so the first step will be we need together why the users want this product and why the business wants this product. So we're going to conduct user interviews, persona journey, maps for users, for business. We're going toe conduct stakeholder interviews and things like that to get what is in the mind and what are the goals off over users and the business. So you get the idea, and we need to get into that goes the primary goals off users and primary goals of her business business. Schools might be profits market penetration. They want bite, want toe, you know, get into the market and penetrated. They want more sales. They might want more sign ups. So things like that these are business schools These are not features right now. So we're talking about overall goes. This is very a top U. For these, the requirements off our product now uses they might have different goals. Business have different goals. User might have scheduled a day easily get a doctor, a doctor's appointment easily book and online plane ticket easily or things like that. So this is the goal off the user. But every goal has some triggers, some behavior. Why do the users want this? So these are the triggers off the schools. We also want to look in those. Then we have the behavior. What is happening with the user? Why are they frustrated? Boy are the emotional Why are they in a hurry? Why they want to do it swiftly. So these are the things that this is actually the behavior off our users. So every goal has some triggers, and we also have user behaviors. We're going to cover all this in the school section. So this is all happening in the user. Interviews were going to get more information personas, Johnny maps, eso all this stuff. Then from our business side, we are also going to look for triggers Why do the business work? More sign ups? Why do ever CEO of wars, more market penetration or more profits or things like that? Now, after we have looked on, goes, We are going toe go a step further, and we are going to shape our goals in tow, actual features and set off tasks, our product specifications that we want these many features in our products so our users can do these tasks, do they can complete the stars. So on the user side, you can see we have set off tasks from over ghouls on these user scenarios, user stories and things like that. And we also have product specifications detail working off our the our product. So what actually is going to happen inside the check out task, for example, air to wish list What will be inside this task? So we want to clear any ambiguity any anything that our developer might have, you know, might mislead the developer to something as so we're going to clear our set off specifications, set off tasks users can do and things like that. So one more thing, which I really want you to show here, is boundary. If you are looking at any stage you need to set a boundary. So set off tasks are the things a user can do with your product is actually setting up the boundary. So we want these things to be part off the product. We don't want these features to be the part of the product, so you need to make sure that what you are going to develop or design and what you are not designing. So this is very important because a lot of projects they are going to fall apart when they try to build all the tasks are all the features they mourned. On the left side, you can see we have M V P, which is a minimal, viable product, and we need a few features like three or four features toe schedule our day easily or things like that. So we are going to decide that after getting thes schools, business schools, what are the features or what are the product features we need to build to achieve these goals? So we also are going toe, see what our competitors are doing so competitive and else is is we're going to see that my competition another e commerce website. What are they doing? How they are using the log in screen, how they are making their check out process easier. So what are the features they're doing, how they're marketing, how they're grabbing different market sectors. So these are the things we're going to look at in competitive announces. After that, the next step will be more details. So we are going from less detailed, a more detailed, and you can see what here we have tasked hierarchical mortal, which will be site maps and different tasks that users can do in each step. We have wire frames, we have prototypes. So why frames and prototypes? They're going to show that what information is present on the screen for the user and how the user is going toe interact. Interaction will be shown our fit, our prototypes. We are also going to use some and do some user flows to show that how the user is going to move from one page to another page of one screen to another screen things like that. So we are actually creating, getting more specific about what our product is going to do on the left side, which is business side. We have some limitations. So we're going to talk about the business model or the business decisions that rich feature is easier to develop and have more value for the user. So we're going to use feature magics where we are going to decide that the rich feature is essential for the user and we can easily develop it on the left side. We have cost off, eh? Maybe limitations of our product. Maybe there are some hardware limitations. Maybe there are some technological limitations. Maybe there are some time limitations. We might not be able to complete some feature within the time frame. Maybe we want toe develop our website are economists launch over e commerce app within two months so we don't have time to develop Ah, feature that requires, like, 10 months to develop. So once we are done with all this, we're going to give all these specifications toe over developers, our team of developers and we're going to develop our first minimal viable product. I have written, I think, most viable product or here. Anyhow, it is minimal viable product and few most important features will be present, which are really necessary to complete toe, you can say Satisfy our juice. Okay, so once our minimal viable product have been developed, we are not going to stop over here. We're going toe, test it with users. We're going to conduct usability test. We're going to keep on adding features. We're going to keep on removing pain points from this M V P. And we are also going toe do some prototyping. A prototype testing. Maybe if we want to add a new feature, but we're not going to build that feature to test it. We're going to build a prototype off that feature or that task or that specific portion off your app, and we're going to test it first, whether the users are really interested in them or not. So it will save a lot of time. We're going to make a lot of decisions. Business decisions. So we are going toe, keep improving and getting feedback from other users and improving other M V B and create a full fledge mature product from here. So this is actually the overview off how we are actually going to go from business and juices interviews toe. Actually the M V P or most rival product. So this is going to be this diagram, this chart or this diagram and the other one is included in the resource is make sure you download them, and if you have any questions to ask me, let's move on to the next lesson. 11. Top to Bottom UX Design Process in detail: in this lesson, I'm going to show you my process, which we're going to follow in this course from top to bottom, to less detail to more detail. And we're going to start with analyze and observed. So we are actually learning about our users and business or we're going toe do some user interviews, stakeholder interviews. We're going to build user personas, but personality, our personality and behaviour over users. Then we're going toe do affinity diagram to sort out what our data we have collected. Then we are also going to do some competitive analysis. So what our competition is doing, what we can improve upon that and what opportunities we have to be better than our competitors. So this is actually very important. So this is the first step. Then in the next step, we are going to move toe our different detailed documentation and diagrams. So on the left, we have high level system diagrams, So first we're going toe, see how our whole system is going to work from a very top. You may be from an airplane, or we can also call it Bird's eye view. So we are going toe build our bird's eye view of our system models, our design guidelines, that how we are going toe water, our design guidelines, our product is going to, you know, be in the minds and souls off of our users. Then we are also going to look at user or customer journey maps that how our users are going toe connect with our product on different touchpoints, whether they call our customer service first, or whether they use the contact US form on our website or how they actually interact with our products or other services. Then we are going to move on toe midlevel system diagrams in this mid level system diagrams . We are going toe, go to user stories, user scenarios where we're going toe, get the context off the user and how they actually use our product or any other product to solve their problem. So this is actually going to show that this is the user. It has this problem and hey uses this or she uses this to solve this problem or this problem is unsolved. So we're going to see a bit and more detail how, actually our user is actually solving his problem or heart problems so This is about what is the story behind the whole scenario, how the user wakes up in the morning. For example, if we have, um, any app, for example, a schedule and how actually they interact with die up on the holy or things like that. Then in the details system models, we are going toe build. Task based mortals task heretical mortals step by step. Use cases. How thes use case scenarios are use cases how actually the system are. The users are going to interact with each other than we are going to develop information, architecture, the wire frames and the floors off our our system. For example, how my user is going to go toe the check out if he is a new user. So for a new user and for on already signed up, user, both the Jackal process processes will be different. So this is going to be our detailed system models. So we're going toe go from high level system diagrams, toe made levels and then we're going toe extract information from mid level diagrams to create our specifications, detailed specifications and the boundary off our app that this app is going to do this and these tasks, and it is going to do that in this way. The steps included in that, um, do detailed specifications. Now, after this, we are going toe create a lot off early prototypes through of a prototypes. They are called because we're going to use them and throw away, and we're going to build upon them and create new I trade and create new prototypes. So I I always suggest you that create a leap, prototypes, even if you can create them in your design design stage, we are going to use that those prototypes and test them with our users. So those prototypes are going to be built upon the all the details. System specifications are wire frames and prototypes we have developed in the design stage , and we are also going to look at vire frames. So actually, fire frames are going to show that what is on the screen, what information is going to be present on the screen and prototypes are going to show the interaction. Then on the right side, we're going to have more detailed specifications off each feature. For example, we have we want to have a log in screen and what are the features of the log in screen? So should we ask the password twice? Or maybe we include a thumb impression o r. Sign up with you can see a tomboy identity or things like that. Then we're going to move on to our juice ability and testing and feedback. Once we have developed our prototypes and we have our you can say our early prototypes, Freddie and we have tested them with other users. We're going to develop it, and we're going to conduct some disability testing's. So even if you don't want to implement things, you can also go through. You can use an elite prototype and just goto the usability testing. You can skip the implementation fees because if you do a design springs oh, our age, I'll design, which is a fast I attrition off this user experience design process. What we do there, there is we actually use, Ah, our prototype, which is you can say I'm 50% or 60% similar to our actual product, and it is a dummy problem prototype, and we test it with and a ghoul or business school in mind with other juicers. So for example, if I have a business school like I want to have, like 1000 sign ups in for seven days. So I want to test my app that weather users are going to be interested in signing up instantly or whether it is going toe amaze them whether they will show in trust. Ah, a lot of interest when they see this and they say, Oh, wow, this is the thing I want. So once I hear this that they've or this and they wanted badly It means that my product, the whole product use express design process is a success. So this is actually Sprint design Sprint and actually used agile. We're not going to discuss it, but I'm telling you that you can vary your process off use expense designed based on each of the time you have. So if you have less time door, don't going to implementation. Just goto. Develop an early prototype that is almost working on the prototype them in prototype and test it with your juices. Get the first impressions, get how the users are, you know. Are they liking it or not? Or what? What is the problem they are seeing in it. So things like that. So in the usability testing and feedback, we also used user surveys, which is qualitative. Qualitative means we're going to mail the corn quality off the nature off, for example. Ah, when you submit our review on IOS App store or Google App store, they ask you that I love this. I like it. I dislike it. Or I really, um this I really hate this app. So this is actually quantitative survey. Then we have benchmarking tests were going to test our speed off loading off website with other Ikuma stores. Things like that were going toe do some benchmarking tests. We are also going to do some five second test or things like that to get the first impressions from our users. So these are actually the testing and feedback on. We're going to go a lot through this course, So stick with me and I hope you enjoyed this lesson. Let's move on. So the next lesson 12. Stakeholder Interviews: now the first step in Usually the expense design process should be stakeholders interviews . So why the CEO are the product manager or the product owner? Why, in the first place they created this product, what make them create this product? Why are they doing it? What makes them think that this product is going to solve this user problem? So a lot of times, the product owners of the product managers are the people like developers. Or maybe they are marketers or things like that, so that we need to understand why they are creating this product, this app, this e commerce website, or whatever they are building. Now, whenever you're going for a stakeholder interviews, there are two most essential things you are going to ask them. The first is what is the primary goal off your product. So ghouls are really important from stakeholders point of view or rather, to intervene users. The first thing you are going to ask is, what is your primary goal? So this is going to be a long term goal and short term goals, so long term goals might be that I want toe within five years. I want my users to have these many features or they can drive this car without any interaction from the outside world are this card is going to stop on any billboard that is , you know, connected with their app or things like that. So there are many things were going toe have on the long term list. So at least ask them t 25 short term goals and long term goals, then the other thing is emotional side what emotions they have about their product. So let them write a short story about their product to get the emotions in their soul or in the heart that my product is actually for busy photographers on the gold in the voil, and they are going to drop their camera. And this happened with me and my wife and we were, you know, in a lot of pain, and we don't know what to do. So things like that. So we need toe get the emotional part along with all the goals and what are their plans for their product. So this is going to help. These are the questions you are going to ask. I'm going toe, give you a resource. A list of questions you're going to ask. You can download them, so don't worry, don't you don't need to remember them. So you have already asked few questions, primary goals and emotional feelings and stories about that product. Now is the time that you want toe book into the fears and assumptions off your stakeholders . They might be thinking something that is not, you know, actually going to happen or what feels they have about their product, that if the user is not going to use my cloud features, then I'm going to lose my business. Will people actually be 100 bucks for this feature? Are you today? I'm going to get more subscriptions that are going to, you know, withstand the cost off my app or, ah, lot off. Different things take and these can come up with in their mind. So you are going to ask questions about the few years or assumptions. For example, a simple question would be, What do you think that what are the things that you fear more stature? Product is going to fill if something happens like this. So tell me three things are four things or five things that can make a product feel. So this is going toe, you know? Ah, very big thing, because we need to avoid it in every step. And also, if you are know about designs, prints and a J use that express design where we actually use a very swift user experience design process. We actually use these fears and assumptions, and we test one of them, which is most important. And if it proves wrong, then we're going to bring the product. So this is how we are going to ask about the fears and assumptions off for users on. The last thing we're going to ask our stakeholders is about their users. So for whom you are building this product, tell me who used this product where they would use this product. What do you want the users to feel about your product? What brand you are promoting? What are their brand values? What are your design principles? Things like that. These are actually you can say you can say s statics and actually, as tactical F aspects for example, brand guidelines or things like that. Also about the users, what they have in their mind, that their ideal user will be something a busy mom. Oh, are busy, Dad or things like that. So these are few questions you are going to ask before you get into any user expense design process. So I'm going toe share with you. Ah, whole document where I have asked a lot of different questions from other stakeholders. And in this whole course, we're actually building an e commerce store for a specific niche, which is princess dresses. So we are actually aiming the users, which are from our Angela, will be on the girls from three years toe 10 or 12 years. So why I took this example? Because it is easier to explain and comprehend. Don't go ahead and download the sample questions along with this lesson. I hope you have enjoyed this lesson. Let's move on to the next lesson. 13. User Interviews: now, once you have done with stakeholders and you quarter goes and what their aims are, why are they building this product? We're going to move to our users. This is our most important party because if you cannot, you know, build anything that is going to solve your uses problem your business is also going to fall apart. So you will lose a lot off business revenue, profits, anything you have. So we are going toe do a user interview because we want to get more information about our users, their behavior, how they interact with their products or our products or our company does products. So this is we are going to uncover in user interviews. So if you are planning for user interviews, the first thing we're going to do is we're going to create some sections for user interviews. For example, I have an e commerce website, so I cannot, you know, ask like 100 questions about everything about my users. That how you do this, how you do this, how you do this, we are going to have our sections divided into a few major categories. For example, I want to test new account set up, for example, sign up off my website that I want to see how our users log in or is there any problems in the log in section Then I also want to learn what makes my user to purchase anything on my website. So how What is the information? What is the key information the looks for when they want to buy something? What is involved in their purse chasing decision? What are their fears? Why are they afraid? Toe used my maps. I'd be use my payment gateway or things like that. I am also going toe test my Jekyll process. So I want to see how seamless is my jackal process. I can do this in a lot of ways. We're going to see them in the next few slides. So let's get ahead now. We have already divided different sections that we want toe death. These abortions are these tasks. Are these functions or features off any website or e commerce website? We are actually building, which is frog land and ah, you can see the missed major thing we skipped is motivations. What actually motivates my user to use my website? What are their goals. Why are they on this website? What are their fears? What have what is keeping them away or what is going toe? Frustrate them in the first place. So these are the few questions you can see I have listed over here. For what reason? You will purchase this princess. That's how quickly we want the different delivery. Toby, what should be written in the help line sections, things like that. So we sometimes don't want toe Ask these very direct questions. We might want to rephrase them Like what is the best help line you have seen in similar ICO mus websites? So if the user shows you another website and to show you that this is the help line, I really loved you. You ask them again that what you really loved about it, So they are going to you're going to explore and you're going to, like, book your users and ask booking questions What you loved about it. Why do you love it? And what's make you makes you think that this is the best solution or things like that. So we are going to get more information more and more information because we want to use this and improve our product, which is fraught plan, which is about princess, says dresses or little girl or little princesses dressed. So these other things you want ask in your user interview. Now this happens a lot when you are goingto do the user. You can say Use the interview for the first time when I did for the first time the first user, I actually you talked a lot. So this is the thing you need to, you know, Uh, stop. And you need to control yourself. Don't try toe talk a lot. Ask small, very directed questions on Don't give a lot off guidance to the user. Don't tell them that, um, do usually credit card to pay online. Instead, you can ask which method do you prefer to pay online so they might have something else in their mind They might not be using credit card, for example, In my side or in my country, credit cards are not used to pay online. Most off the 90% off the customers they actually use be at your doorstep. So the package arrives, you collect it and you pay the price toe. The delivery company So this is a total different mechanism in my country, and there are a few more services like Easy best are few more online payment systems that are not actually use being used by credit cards? No. Let's talk about some probing questions and how you're going to ask them. Probing questions are actually supportive questions for a main question. You have asked, for example, if I have asked my user that what problems you have faced with the item delivery or return off the item last time you ordered some clothes and wants the answer days and I'm going toe , ask another question to get more information. Maybe I don't ask. How would you like to return your product? Maybe something else, depending on their answer. So whatever the answer tried to poke into it, try to probe it. Try toe, See what else? What other information you can expect from your user. Okay, so a lot of time more stuff for the newbies that are going to use dough. Some user interviews, the first thing they're going to miss is user context. So whenever you are actually interviewing a user, you are goingto interview in their home or office or whatever device they use to order online or things like that. They might have very slow Internet connection. They might have very old iPhone, or they might have very old desktop PC that is very slow to Lord. So you need to see what are on their what is their environment. What are the hardware? Are the software there's using toe completely different tasks. So things like that, So you are also going to print your material. For example, you want to show your user that these are the questions are These are the products I want to explore with you. Show me the process or things like that. You can also record audio or video if you want. You can also take pictures off their context there, room on their hardware. Nor don't what the using on. At least try to interview Tito five users. So this is actually very important. At least three users and there is one more user interview technique that is called gorilla gorilla user interviews and what you do there as you actually go to any bar or cafe and get your friends or anyone, give them a coffee cup of coffee and show them that this is I want to ask you a few questions about this product, and I want to show you something and keep asking them questions like 10 or 12 questions. So this is guerrilla testing. It is very cheap, and it is very effective sometimes. But the users you are testing, they might not be the actual users that will use your app, but you can get some. You can see some impressions off your product about by going through this gorilla user testing. So I hope you have enjoyed this lesson off user interview. I'm going to share with you the document you can download for the user interview questions I have listed. I hope you enjoyed this lesson. Stay tuned and see soon in the next life. 14. WAAD/Affinity Diagram: in this lesson, we're going to talk about work activity, affinity diagram or simply call affinity diagram. Now you might have seen a lot of user experience. Designers basting different sticky Norse on their walls are there. They are filled with different sticking north. These is actually what they are doing. They are making an affinity diagram. So actually, why do we use this technique? Are wide we he was affinity diagram because when we interview our users and our stakeholders, we have different data collected that is in a raw form, it that doesn't make sense. So we are going to create different sticky notes. And we're going to write what we found out, for example, the fears user have or things like that, and we're going to sort them out into different sections. So we're going to make different connections between them common teams that these things are related to sign up or these things are related. Toe check out eso We are going to use sticky Norse and group them toe show what we can improve and then we're going toe map out our whole data into sections. Okay, Now the steps to create debut double 80 read or work Affinity diagram. Affinity diagram. So first thing you're going to do is write your findings on sticking north status obvious. So write them in. The short sentences are maybe three or four voyeurs or five words or six fours, and you're going to place them on a white board and you are going toe start creating groups . So, for example, I found that I have, like 10 Sticking or Start are going to belong toe log in screen or log in options. I'm going to place them over there. So don't worry if you find something else later on, you can move that sticking or to another section, So we are going to build some common teams between them. We're going to create groups and even subgroups that this is going to be logging, and this is going to be in tow Social log in So these social organ is actually a subgroup in the log in section. Similarly, we are at the end. We are going to give points and trading toe most important ideas. For example, ah user might say that I want toe have an ego mus website that can deliver me products within a one hour, so it is often almost impossible right now. So we're not going to, you know, give attention to these kind off user requests or user findings were going to give them zero points. So the most important once, which you really think that they are going to solve, uses problem. We're going to give them points. So these points are given by your whole team. There might be CEO in your team. There might be marketing managers. There might be developers. There might be a designer's off the people who have interviewed the users. So once you have gone into the user interview, try to bring your team members like your developers and your managers or CEOs off your product so they can also see what are the pain points off your juices. So in this giving points and rating, so most important ideas will be depending on the user interview team you got when you interviewed the users because the people who haven't seen the users actually in being they are not going to, you know, pay attention, toe the real pain points. So this is how you are going toe. Arrange your group, your ideas I'm going to show you my W 80 diagram. Now I'm going to show you my work off activity Affinity diagram from my for my for fraud Planned project So you can see these are different groups Top as actually yellow. You can use different colors. You can use sticky Norse but I have used something else. I'm using balsamic mockups toe cleared This eso you can see we have different sections we interviewed for logging Create new common security concerns Buying the CNES product information pricing ideas are dring and returns order check out returning items, menus and navigation. So this is actually this data is based on just to users. So you can see how much Ted how we can get If we interviewed 3 to 5 users, there will be tons off different sticky north Right now you can see I have Ah, like I think I have around like help line landing page such bar menus, air navigation. So I have liked 10 to 12 categories in then I have, like 5 to 6 sticky north Scinto each category so this is like 100 off sticky north for just two users. So you can see how much data you can collect. So from this data, you can see we have things like I like, for example, you can see if we have this log in What actually happened is my user actually had no email address are she doesn't remember email address for a lot off university students in our country. Most of them don't use email regularly. They have Facebook accounts. They have phone numbers, but they don't use e mails. So once they go to the log in screen, there was, you know, elect nto, you know, even log in or sign up with an email. So you can see Here are a few things I found during user interview User don't understand words sign up. So this is very, very specific to our area. So in Isha or in Pakistan or India, users might be ableto, you know, get more information or easier it is. It will be easier for them to create account if we have ridden, create new account, read it and sign up because signing sign up. They don't understand the difference most off them create. New countries should be used for sign up And this is a suggestion. Help video or help line would be visible because actually, my juicer one off. My users actually tried toe no contact with the help line toe. Help her create new workout. So this is, you know, these other things I noted down then we have security concerns. I asked a few questions about 30 security concerns and they wanted to have a password. I thought that in my assumptions, I thought that password is not necessary. They might log in just with their phone numbers, but they said that we want a password for security reasons. Then the trust issues were that they want to have something like 24 7 help line and things like return policy, Sean. So these other things that should be visible product information you can see product title available stock options to select color, size, fabric images and description and reviews. So these other things we need in our product Oh, are these other things that make them by this? So I also got some pricing ideas that what I showed some frog images, the different dresses off little girls and showed them that what could be the price off these frocks? So will you be able to pay how much you would would pay toe by this kind of fraud. So they were around $20 to $35. So it is like they are eager to pay. In my Pakistani currency. They were eager to pay, like, 3000 to β‚Ή5000. And when I asked him for the budget, they said I My budget is maximum to 3000. So you should also ask them What is the their budget? Okay, so off. For example, a college girl. They might not have a budget off, like $30. They might want toe purchase something you know, within their range. Then we have ah, order. Check out. This is we need to figure out we have toe, you know, fuck. Investigate more users for the checker process. Returning item. You can see she had a lot of bad experience. A clear with other websites. Here we can improve a rep Site menus, air navigation. I asked them toe, you know, show me different dresses. I brought these. Actually, I did a card sorting exercise. I write some off the terms like fancy dress princess stress, but before casual or court and frogs. So, um actually, Barbie folk waas ah found in the user's head. They were they were not recognizing princess dress actually developed using term Barbie frog toe such for Princess Tres. So that is why I have listed over here. User didn't and recognize hamburger menu. You can see this is very alarming for me because most of the designers like me, they think that user can easily, you know, recognize hamburger. Many user also keep on calling my navigation navigation bar options. So this is you know, it was very strange for me and ah, in the search bar, you try to use color keywords like Red Frog or white dress or things like that. They also search for both rocks. So these are the things we are going to use for in our product. For example, if I'm listing my products, I'm going toe use tags to enlist my products, and these tags will represent our It will make the users such easier. Like I never thought that that would be Barbie frocks or Barbie dresses. I just thought that there would be just princess dresses also on a landing page or our main page user always look for discounted or sale items. So they were looking for sale keyword on the whole page and they didn't find it. And, you know, they thought that they would first goto the sale page or discounted discount space rather than going toe explore other years so you can see this is actually really letter from my user interview, and you can see how much that we can collect. If we just interview 3 to 5 years, as I have just interviewed one or two users and you can see this is the data. So I hope you have enjoyed this lesson about how I created my work of activity, affinity diagram. And from this diagram, we're going to create more diagrams and more features and things. More specifications for our product. Let's move on to the next lesson, and you can download this affinity diagram from a resource is section from this lesson. I hope you enjoyed this lesson. Let's move on to the next lesson 15. Project β†’ Create Affinity Diagram: Now you have learned about user interviews, affinity diagrams, stakeholder interviews. Now your assignment is to create an affinity diagram based on a user interview. So take one user interview. It could be your grandma. I could be your father, your mother, your parents, your friends or anyone you have close by. Try toe, interview them for, like, at least 30 minutes or one hour and ask them at least 15 to 20 questions about how they use their product or any product you can take Airbnb or anything you have and try to extract what behavior they have. What are their fears? What are their frustrations? What are their problems? Try to group them in an affinity diagram, making different groups off different teams. For example, security problems are maybe cried. Card issues may be booking problems or booking behavior or things like that. So try to group that into an affinity diagram, and I would love to see the I definitely diagram. Try to use any online tools you have for that 20 diagram are you can use it by using panel people people, and you can also build it using balsamic, more cops or any graphic tool you have. So send me your of skin short or picture off your affinity diagram. And I'm looking forward to seeing your assignment, so start making it right now. 16. Personas in User Experience Design: now in this. Listen, we are going to talk about personas. You might have heard this name before. If you are, Are you a designer or you works designer. Now, a lot of people think that it is a real user, but instead it is actually a fictitious user. And we don't use the rial image off the user. For example, I went to an interview and I took photo off my user and then I based it in my personas. This is wrong. We're going to use just a fake image. And the name must also be fig. But about all the other information will be will not be fake. It will be really now it actually does. What are the behaviors? Water, the ghouls? Water? What are the triggers behind those goals off your users? Because these this is very necessary. You need to know and understand your users better. What are their behaviors? How they act with different technologies and all this stuff Now, normally, we get all the information from our personas and user interviews. So we you know, we all we extract all the information from there from the user interviews and put and create a persona based on that. Now I recommend that you should use at least three personas. 123 personas. Normally, it is very rare that you just hit only one type off persona. So actually, there is another topic that is coming to my mind, which is user archetype or user archetype, whatever you call it. So actually, persona is actually one type off user. For example. I have, For example, I have ah, website That gives me different. You can say different deals. Okay, so it is a deal website that give me all the discounted deals online. So there might be two different types off users for that. So there will be two different personas. One is a normal home user. For example, I won't few T shirts for me. And I saw ah bulk T shirt deal over there that five T shirts for $20 I'm going to buy it. Okay, so there is one type of person like this. There could be another persona. Another type off user that is going toe buy in bulk and he's going to sell on his shop. So he has a shop. He has a clothing shop or store. And he's going to buy all different stuff in bulk that he can get from that Deals website and in another season. Or maybe next season he's going to store it and he's going toe, you know, sell it on some other rates. So there could. So we can make one persona for the home user and we're going to name it home user. And the 2nd 1 will be selling. So So these are different types off personas you are looking for. Now. The second question is, why do we need personas? Why creating thes personas? Why should we have these? So the first thing is that we want our designing our development team toe have some empathy with other users. They need to know what are the pains off of us users? What are the ghouls and the personality off the user who is goingto use their product? So these personas, they are printed and there hanged in front of design teams and development teams so they can better align their user goals with their product. So this is going to, you know, give them shared part that our user is going to need these so we're building this for this type of fuser. So this is very important. You might have heard about personas, but you might not have heard about work rules. You are developing a product or an e commerce store for the users. Primary your buyers and you are making personas for them. But don't forget about the work rules. Verticals are actually different. Interesting parties that are linked to your product, for example, in this example and we are creating fraudulent store. So our buyers, which directly of those users we have created them three personas or coup personas, busy moms or things like that were going to come to that point. And we might also have adminstrator who is looking after all my products with adding products on my website who is removing products from my website. Okay, so this is the site administrator. Then we have call your company. So the Courier company delivery company that is attached to our website they are going to update our website, our users that the product or the delivery has been processed or things like that. Then we have the CEO now the sea off the company, which is me. I want different sales reports. I'm not an administrator. I adminstrator is different. So I want sales reports. So our website or our Web store, it might had some feature building that it can show me monthly sales and yearly sales or weekly sales things like that. Then we have a stock manager stock money that is a separate person who is managing all the stock. So these kind off pence, we have very low stock and he need to order more. So stop Manager is actually totally different Volk rule. So you need to understand. Don't try to forget about the vertical store. Just only focus on the users but all the different types of work rules that are going to be interested in your in using your system or product. So enough talk about personas. I'm going to show you my persona, which I created, And I'm going to also show you a website where you can create online tool ah, persona. They have very create templates, So let's move on to the next lesson. 17. Online tools to create Personas: in this video, I'm going to show you and tell you to different tools which have free version available. And you can sign up for free and use and create personas online. Okay, so foster is Accenture. You can see over here. I have already signed up. So if I goto my screen, you can see I have this template built in which you can use for your persona. So if I go back toe my main dashboard, you can see I have this all folios and I have this frog planning it. And then if I try to go like a date Folio, you can see it is going to show me this over here. Okay, so I can type the name off my personas. Maybe, Um, I mean three R's or something like that. OK, there you can use any photo off a female, then on the left. We have a condition that captures the person's personality so this condition will be related to your product or how their behaviour is online. Or maybe with e commerce websites. This is not their life, life's personality or their life's quotation that I want to live happily after my fifties or things like that. So you need to a wide that. Then we have some demographics. Like, what is the age work? Family, location, character type? Then we have this personality personality bars, introvert, extrovert, analytical, creative, conservative, liberal, active or passive. So this is actually telling us that how our users are going to be here, whether they, you know, going toe a lot off, people meet others. They are very creative or they're very analytical. What kind of thinking back when they have. So the main thing over here is thes goals, frustrations. These are very important. So these goals are actually alleged toe how they use your product or similar products. How they actually, you know, they have their goals in mind. What are the planning for? So when they open a website or open an economist roar, what are they thinking? What are their goals then? We have the frustrations of what other things they like to avoid. What are their fears? What are their pain points? So there are different words for this frustration, whether Spain point or sometimes referred as a few years or things like that. So these are the things we're going to list Over here. This is a short Biograph biography off describing yours user what they do, what they live for and how they spend their whole day. So this is also very important. On the top. We have traits which are, like, busy, punctual. These are actually defining the personality what kind of personality they have. Maybe they are very busy. Businesswoman may be punctual, are regular or things like that on the right. We have motivations of what motivates them toe, pursue their goals or you can say, pursue their daily goals or things like that. So whether it's incentive, if they have given some incentive or whether it's fear that is motivating them, that I don't want to lose the trust off my kids or things like that, so they might have feared to purchase the frog. So are their kids. Just they might. I feel some achievement that I would be a great mom if I purchase these frocks for my these great looking dresses from for my kids. Then they might have some growth possibilities, like I want to, you know, be better at my job on what to grow, because I don't want to waste time I wanted to be, you know, do it quickly and easily, so I don't, you know, feel frustrated when I goto jobs my daily job on then it might be power than it might be. Social behavior I want Oh, my. I want my kids to look better than there are scared. There aren't these kids or things like that. She might be comparing Harkins with other kids. So this is actually motivation on social behavior. Then we have brands. So what kind of different branch they love? This is going to tell us what their tastes are, how they like different brands when why do they love them? So this is a few images over here for different brands they love. Then the preferred generals. What are the preferred generals they normally use? Because we are actually going toe ultimately advertise and market our product first. So we need to know what are the ads they are looking for? Whether they read traditional airs. Newspapers are the use. Online services are social media. Whether they use instagram spend their time on Instagram Facebook or what are the groups? They are regularly checking. So these other things we are going to look for then whether they get some reference from their friends or what are different, you know? So these are different preferred generals. So the whole layout or the things are actually similar. If I goto extension you are you express here. This is another tool. This is actually the one I created and it is called busy moms. You can see this is their Archie type of our men. Type off the user Busy moms. This is the name market size that this user is almost 30% off my personas than on the left . I have demographics. Female 35. This is a location. Married. What? What they do. What is the income? Parliament. If you want to add more fields, you can add over here. Then I also really need toe see the skills they have because they are going toe or order online using my e coma store. So they have some computer skills. So I'm going toe go with these kids that home, how many times they have ordered online, but that they have ordered online before or not. So the this is actually comfortable Ikuma store orders using mobile phones. I want to check that, but that they have already are used their mobile phones to order online or not. Then we have technologies they use. So this is actually an right there using android than they're using windows. In my country, Max and apples are very rear, so very few people use them. Then we we need to know what browses the as using. They're using Internet Explorer. They're using this chrome browser of which brother type because we need to adjust our websites for those brothers. Then we have this channels. This is the same brands and influences many. So Zara, Joe J and Mario. So these are actually branch they are motivated with. So this is an actual you can say this is extracted from my research, which I did with two users. So one is this busy mom, and one is a college girl. So this one is actually making the scenes for my kids and buying clothes only for them before the start off season. So this is their goal. So every season, maybe summer or spring, our winter, they are going toe, you know, make their purchases. Before that, I don't want to burden myself with extra Lord and frustrations. So as my life is already very hectic, so this is their goals. They have the these fears and frustrations that I don't want extra Lord, I don't want extra, um, work. And I want to be free myself. So always looking for things to go smoothly. So this is their court that they don't want any, you know, setbacks when their purchasing online's or things like that. Then we have some background. You Can you write a whole story? Your hair married three Children. Teacher Computer science in school doesn't like to spend him hard time, so I have You don't know here his This is going to be hard. Hard time on shopping preface to buy everything online has several credit cards. They should buy different banks. Mostly look for local clothing store ads on instagram, so you can also write a whole background story that she wakes up early in the morning. She is very busy. She goes to school before going to school. She make sure that, um, three Children already and the and then she hurry up and things like that. So this is going to be a background off Thatcher's it. So this is how we are going toe. Create a persona. You can add more personas. I really like this. You express your template to there is no standards. But make sure you have goals. You have condition, you have more division and frustrations. You have brand influences. You have Ah, all you got for technology and how comfortable they are with this technology and some off the demographic background. So this images, dummy, this is not said Robin does. It is someone else. So that is all about using personas and creating one persona online. Your next assignment will be to create a persona like this one, so let's move on to the next lesson. 18. Project β†’ Create User Persona: Now you have learned a lot about creating personas. And what are different things? School triggers and motivations and all that stuff about persona now is your turn to create a persona so you can use a paper or pencil or pen. Take that screen, shot off the persona on and ascended to me or uploaded on you. D me or skin share were ever the plate formulas using Show Me in your assignment or project , and your task is that you are going to create persona for Amazon, or maybe for any train booking app or anything you have. So give me the title off that project that trained booking or maybe some other AB. Whatever app you're creating, you're going to create a user persona. Take any user may be your friend or anyone interview them a little bit, maybe ask five or 10 questions and get into their head. What motivates them to use this product bought all their cools when they use this app or things like that. So what is the thing that frustrates them? What are the products they like or what are the brands they like? So all that detail about your friend your mother or anyone taking any product consideration , for example, and we really real booking or maybe flight booking app and see what are the problems they get. So this these are the things you are going to present me in the persona. I am hoping to see your persona soon. Let's move on. So the next assignment? 19. Empathy Maps: in this video, we're going to talk about empathy maps. Now A lot of my students, they have asked me that Please include these empathy maps and tell us about what are these empathy, maps and hard we use them now. Empathy map is actually, ah, collaborative tool, which we are going to use toe, get more into the head and heart off our users or other customers were going toe. See, what are they saying? What are the thinking? What are their feelings and what actually are they doing? So what our users do is north, sometimes the same as their feeding or thinking and saying So this is the map. We actually draw four different sections on the page where we will point out what our user was saying and at the same time what he was thinking or she was thinking, what were their feelings, what whether they afraid, whether they were confused, things like that and what they were actually doing, whether they were clicking the by no button again and again and they were feeling dumb, and they were thinking, What is happening? Why it is not giving me any feedback that my card has been My order has been confirmed or not. And they might be saying that, uh, I'm not sure. Maybe I'm doing something wrong so you can see there are contradiction and difference differences between what they're thinking, seeing, saying, feeling and doing. Now, let's talk about why we actually do empathy, maps and what aren't the benefits we we can get from them now. The first thing is that we are actually uncovering user needs. And most of the times users are not avail off what they actually want. So we want to see what they are actually thinking. What are the emotional knees? How we can make them comfortable using our app or how we can improve our trust and things like that. So we are going toe also get into user behavior. So most of the things we are doing over here is actually seeing what? How they are going to behave. What are the triggers that are going toe? Um, what is triggering these user behaviors? So this is going toe get, um, so we are actually digging deeper into our users feelings. And what are the problems they have? What are the fears they have? What are they thinking? What are what is the emotional state? So these are all the things that were going toe, uh, use and map out in our empathy maps. Let me show you one example. And then we have we will move on to the next lesson. Now, here is an example. Off empathy map. This is from an in group, nor Nielsen. Norman, I think normal. Nilsson, I don't remember any. How you can see for Sting is you're going to notice. Is at the top overhead buying a TV. So you need to show the process they are. The user is actually going through. So maybe some task, maybe check out process or things like that. So this is actually Jimmy, which is actually yours. User persona might be a user persona, and you are going toe attach a user and a process to your empathy map. These are cool things. Then we are going to have a section or here where we're going to post whatever they're thinking, whatever they're feeling, what actually the user is doing and what he actually says. So he might be saying time something and doing something else, and he might be thinking something you have tow. Ask your user. Please think aloud. What are you thinking? What are you feeling? Why are you afraid off doing this? What is happening over here? Tell me how you are feeling right now. So you are going toe. Ask these questions while user is performing this task which is buying a TV in this example . So this is how actually you create on empathy map. So that is all. If you have any questions to ask me, let's move on to the next lesson. 20. Competitive Analysis: in this video, we're going to talk about competitive analysis and whatever you're building, whether it's a website or app or a new product that is revolutionary, there will always be some sort off competition. So by competition, I means there must be some products that are similar to your product or they are close to your product. So don't think that there is no competition. There will always be some competition or some computer to your product. So why we do this? We are going toe check and benchmark our app, our website or our product with other similar products. So we are going to see where we stand in this race. So this is very important. It is going toe, give you a lot off in depth analysis off what the competition is doing and what we should do. No, the question is what are different factors you should test with your competitors now The first thing is, in my case, which is fraught Clan website. I'm going to check navigation information architecture er how they are moving their customers from the log in page to the check out bitch Then the 2nd 1 will be product information and details for our different frogs or dresses informations our pieces off informations that are present on other websites. What are their standards? Similarly, we are also going to see just incredibility. So how much and ah, why our customers? They have more trust on other brand or maybe other Ikuma store or maybe the app why they use it on. Why do you think that it is more credible then? I also have asked few things about on boarding log in and sign ups. You are also going to see what are different call to actions. What are the labels they have been using? How effective their call to actions are, for example, by no button or add to card you have seen on amazon dot com. It is totally different from the whole bids and it is orange and yellow and they really attract the customer. Similarly, we want to see the check out process because H website each e commerce platform, the different jobs different jack or process. So if you are building any app or anything, these things will be different for those. So if you are in my case, I was testing ICO Mus website So I have listed these fuel things, which I'm going to test with My competitors know how we are going to conduct competitive analysis. The thing is that you need toe. Ask your users during their interview toe, order something or to use your competitors website. I actually did it and it is the best way to learn what they have in their products and what they lack in their products. What are the trends? What are their weaknesses? Because we need to see what are different. Usability problems are the when my customers they go to another e commerce website or a similar app I'm building. What are the problems they face how and which areas or sections off app we can improve or we have opportunity to improve that. So in this whole competitive analysis, we are going to look at different sections which we think are essential to our app. We are also going toe benchmark, our system or our app. If we already have a nap, we're going to benchmark. It said that right now we stand at 60% or we give our our self like 50% on Logan so I would log in this 50% easier with respect to the standards which are others are falling, so we need to improve that. So whenever you are doing user experience, process of your experience, research or user interviews, there will be two scenarios whether you already have the product build or you have to build a product from scratch. So these are two points from very You will always start your user experience design process . So in the both processes you are going toe check your website, your app, your, um, your mobile app or whatever. You are building your product with your competition. So even if it's not a digital product, you are still going toe. Check it with similar products already build. Now let me show you the document I prepared and what I did in my competitive analysis. And you can download this competitive analysis document from this lesson in the resource is so don't worry that you will not get it. There are different formers. I'm going to show you it is very easy. Don't worry at all. That's see this example Now Here is my competitive analysis for fraud plan and you can see I have written over here tested for log and sign up credibility, searching, filtering and check out process. So you can see here I have tested the my competitors. Main competitors were Daraz PK, which is one of the biggest online store in my country. Then I have sharp high, which is very old and very credible online store than we have e export leftovers yellow, which have different kind of category off clothes to sell. So I needed to see what are different online competitors and what are their strengths and weaknesses. Now, if we talk about sharp high, they are very credible. But they are not related. Toe my niche, which is clothing. So shop high waas, lady toe You can say technology products, so they are selling computers, things like that. But I included it just to see how their jacquard process is and how they're logging is and how their sign up is. So you can see here are different strengths like like draws is the biggest. Your Friday of protection slack from already established, well known card and wish list are powerful. There are very powerful features. You can easily move your item to visual ist and from visuals to card surgeon. Many filter options because it is a very big platform and now coming to the weaknesses. Slow delivery. So I have seen I have ordered myself and heard about about its ordering problems that this delivery is very slow. Sometimes it takes seven days, sometimes five, sometimes 10 days. Sometimes you even don't get your product even for a month. Too many suppliers Quality is insurance is not good, so there are too many shops that are supplying on draws, so it is a very messi with supplies when we go to check out. There was no clear payment method selection selection section, so it was difficult for the user to see which method should I select. It is. Is it selected or not? No auction for to filter by February type, which is our I mean you can say Ah ha moment for filtering. We're going to add this fabric dye filtering to our website, which is fraught clan economist. Or then we have sharp. I've There are different stents and weaknesses similarly from yellow. So the main layout off this whole competitive analysis will be competitors and some off the description. If you can use the only neural that is okay, then we have some of the strengths. Then we have some of the weaknesses. So this is actually the men template for your competitive analysis. Let's let me show you one more template Extension pole. I have already shown you this app and you can see over here here is again. We have competitive analysis, and here we have you can say our top down layout for the same thing. We did image off the computer or logo over here. Then we have completed name, location size off the company that How big is it for example, like draws dot com or trust or pick? In my case, it was the biggest, very big online store on then. Some of the description, if you can you use the jewels on the Web. You can use that product photo if you want to list over here and then again the main area or section, which is strength and weaknesses. So weaknesses are the things where we are going to learn, and we're goingto grow from this. We are going to learn from the weaknesses off others. This is how we're going to improve our user experience. Okay, so here is another section which, which is called market Breakdown. It is showing us the kind off competitive we're dealing with. So whether it's a very premium budget, you can say that it is very costly to bring something like that, whether it's business to business or business to consumer, kind off competition or website or e commerce. But there's ego Hama's jail, local or global services or products. What are the selling? So things like that it is just to get the estimate off, how much costly the computer is. If you want to build something similar, it will be very costly or things like that. So this is me in template if you want. Oh, say it is going to be on extension of upside competitive competitive analysis, and that is going to sum up my this lesson, which I think is really important. You need to compare your products with other similar products to see where we can improve where we can have some standard function, which others are expecting. Other uses are expecting that check out should have these many steps are these many options , which is industry standards we're going to find these two things industry strainers and weaknesses were we can improve. So that is all about competitive analysis. I think we should move on to the next ness and now. 21. Feature Matrix - Deciding which features for MVP: Whenever we are doing our user experience design process, there are tons off features that your user might want. So they might want to, you know, back there laundry or maybe victim up with a smile or things like that. They can ask for anything. They can even ask for magic. So what you are going to do is we cannot develop or design all those features. Everything is not possible. It might be due to some limitations off cost. It might be limitation off time. It might be limitation off development process. Maybe it's difficult to develop, so we are actually going toe trade off and select The features is using the feature metrics , and we're going to see what feature is valuable. And also we can easily build it, so it is cost effective, valuable and less time consuming. Similarly, when we are improving or redesigning, are improving our design. Maybe we release our first version and we got some feedback from the users. Now we are going toe at least our second version and we want to improve it. We are game going to build feature metrics that these features can be or these problems can be adjusted easily, They have more value, so we're going to do them first. So this is actually to prioritize, which features you want to develop first and which we are going to develop later. So let me show you one example. Now you can see this is how you develop feature metrics and you can see on the left side we have value to user. How much value our product has are this feature has for the user, So from low to high, then we have on the bottom we have from the left right, we have difficulty or cost off implementation. It might be cost in monetary terms, like dollars. Or it might be time. So you can see or resource is from the left right. We have low and too high. So you can see the features that are going to fall in this quadrant, which are expensive and high value, like automatic stock alerts to supplies. So it is not very necessary. We are not going to build them right now. Similarly, package tracking In my country there is no package tracking online, or you can see you can visually see your package going through different routes this is not possible. So we're going to leave those. Then on the left, you can see easy wins. They have high value and they have very low cost. So on the left you can see Facebook. Logging is easier to develop. Then we have taking all in order by phone. It is not very difficult. We just need a phone number. It is also going to improve the trust and credibility off our website e commerce website filtering based on color, size and fabric. This can be done easily. We just need to have a few filters applied. So when you are making this decision or this magics, we are going to have our developers. We're going to have our Martic marketing managers. We're going to have our CEO and we're going to have our design team. All of them should be present. And they're going to give some points that these are easier toe develop. Our These are easy wins or things like that, because user experience design team, they know water the Pain points development team. They don't border the development costs. Marketing teams they know what actually user wants to see toe are a feature that we can market easily, for example, sorting by fabric type. So things like that. So on the left side, you can see we have low cost, low value. So logging option with just phone number that can be implemented tow It has medium to low value and it has very low cost. So anything that is going to fall in this section in this area, we're going to implement it are try to create it in our first version or every P minimum minimal, viable product. Ah, and everything that is expensive and low value, we are going toe neglect it almost totally so things like that. So this is actually very important in the sea and making because we don't want toe our product to be a feature creep. I have. Ah, I had a client. I'm going to tell you a little story. I had a client and he had a brilliant idea and a product which was an Web app and what it does it It was a community ab. So if you are in a town, for example, my town or my area is called D C. Clooney or deceive Road or things like that, so if I am living in a loony like Disick Allouni and on that app you can join that community and everyone is going to inform you about what actually is happening around them . Maybe they heard some teeth last night. They heard some gun short last night. So they're going to inform you about the safety and other things and what is happening in the community. Maybe some advertisement that I am selling. I'm opening a new shop for this thing and things like that. So it was a brilliant idea, but the problem waas that he actually suffocated the app with, like, tons off features. There were 20 different features that will not needed by the his users. So So he was my client from U. S. A. And the idea was great. I left that project because itwas getting getting bigger and bigger with a lot of features . I was our designers, your expense designer. For that, that was a social app category. And I had very bad experience off because off this feature creep. So this is very important. I think it is going to make or break your ab because you cannot deliver everything at a time, so you have to select few parties. You have to paradise, which features are more essential or they are the bread and butter off my APP. Users are going to attract to my app with this feature, so try to develop those which have high value, and you can easily make them in a within six months or three months. Technology is very fast paced. If you are going to make our improve feature and you are going to introduce it with the next five years, then you are going to lose the business. Because world is changing a lot. There might be tense off APs that are going toe deliver that feature and maybe before you. So it's a race. So try to focus on what is high value and you can easily develop it. Easy wins. So that is all about this feature metrics and the story I have told you. I hope you have learned some lessons. Let's move on to the next lesson 22. Models and Diagram in UX Process: Whenever we're designing something or planning something, even we are building a new house. We actually draw some diagrams and models off that house and explain and how all the rooms will be planned. And once the room has been planned, we go into details what we will be playing. We will be placing in each room. We will be placing so far over here. The tap we'll be over here on the TV station will be over here, things like that. So in user experience design. Similarly, we have two types of model simple models where we're going to view from a bird's eye view where you and they're not very detailed than we have detailed models. So in this is and we're going to see some of the diagrams or models we're going to look at during over process. So that school head now there are simple models and use expense design. If you are like system orders whole, your whole system is going to work, then use a journey. Maps. What are different, Touchpoints, where our users are actually connecting with our product s user stories. There will be long stories, a visual story off your user using your whole product, or there will be short, single line stories about the usage off Europe. Now then we're going to move into more detailed models like user scenarios where we have very long scenarios. Are users using your app in his room or things like that? Then we have, ah, task indirection models. So there will be tasks. Our users will be performing talks tasks, and we're going to show all the interactions during that dusk so there could be, like 10 different task or maybe 20 different pasts. A user can do so. We have to make each task model forage task. So it is in more detail than we have use case dry grams how our users are actually going to interact with the system and how the system is going to reply back and things like that. No, along this whole journey off, creating user experience, diagram and models, there are two things you need to keep in mind. One thing is feature road map. We already decided that we are not going to develop these features or we might develop these features in the next six months, so you need to create a roadmap diagram off your product. So in the 1st 3 months we are going to launch these three essential features than in the next one. We're going to launch these four features and similarly move onto the next. It will be based on what we did in feature metrics, which features are necessary and essential for your users. So, um, design principles and guidelines is a different story. It is actually the boundary off your design and the direction off your design. You want your app, Toby conservative or you want your app to be used by just professionals. Oh, you wanted to be invited by other designers on Dwight. Only app. Things like that. There must be some principles that are going to guide your design that we wanted to be intuitive on. We wanted Toby inviting and things like that. They are not related to what features that you were going to develop. But they are actually the guides that in which direction their design will go. Now let's start with our first moral, which is system moral. In the next lesson, let's move on to the next lesson 23. System model Diagram: No. The first diagram you're going to build in user experience. Design process is actually system moral or some may call it proposed system Oral that this is how our website or our app is going to work. These are the work rules or the major interesting parties that are going to use your system . Okay, so that is going to be Ah bird's eye view. We're going toe. Look at the overall build off over system, how it is going to work and what is its major boundaries. So here we go and let me show you what are actually work rules. We have already learned about work rules and personas. But here, actually why I am talking about thes vocals is that they are more latitude. Are your system diagram? Because each work rule have different jobs and different tasks. So from those work rules, you are going to extract different tasks, and those talks is going to be built into your requirements off your app. So, for example, in my frog clan e commerce website ah, shopper is actually a user his Virk role than we have an admin delivery guy company, our delivery company supplier, even the SMS or the mobile network company. These are all linked. They are linked into my system. Somehow they are my work rules. So this is the thing you are going to, you know? Look for when you are going to create your sister models. So let's see some example the real example which I created. This is not rocket science. It is very easy. Don't you know? Try to think that Oh, my God, I How I'm going to do that. This is very simple. If you can and draw some circles, you can draw this system diagram on a paper. Okay, so let's see some examples. So you can see here is a system model I created using balsamic markups. You can use any software, any tool when you can use paper and pencil. So the dotted line you can see it is actually the boundary off my system that these other tasks are functions that can perform the outside people that are CEO and main, customer or shopper, third party vendor, dressmaker or delivery company. They are actually my vocals and they're interacting with this system. The system, this is my boundary. And here we have admin that is managing product details, images, prices and creating deals. Then we have CEO. Sales reports have any generated in monthly sales. Then we have customers, article frogs and dresses and keep updated about the new products filtering on DA with these few cried areas. Then we have order straighter updated wire tracking number and SMS receiving SMS giving sending a semester. The customer, not this SMS and order. Trick tracking is also linked with delivery company because they are going toe send this SMS. Then we have order dispatch with printed labels for delivery company. We are going toe dispatch that or delivery company. Maybe there might be someone else who is dispatching this past manager or something like that, but I'm not showing it or him. Then we have stock level alerts or maybe someone men really calling The third party renders that we have this shortage off this dress. Please send us 10 more pieces or 50 more pieces. So stock level alerts we also need dresses were not going to make them. But we're going to buy them from third party. So this is actually the system mortal simple system, moral or system Diagram off. How my e commerce store for Frog land is going to work. I hope you have enjoyed this lesson. If you have any questions to ask me, I'm going to share all these documents. And the resource is so don't forget to download them and see them up close. See soon in the next lesson. 24. Project β†’ System Model Diagram: you have learned about the system model and the mean diagram off how your system works for your website or APP is going to work. So it is a system model diagram, which is a base diagram off the whole picture, that this is how the whole thing is going to work. So, for example, I'm wearing this smartwatch. You can use any smartwatch, Fitchburg, Apple Watch or Samson watch and try to build a system modeled off there AP, and they've watched working together. So how, actually the whole thing is going to work together and how the user is going to be involved in all that. So all the system users, or you can say, system users, which are going to use that system and how they are going to be, you know, integrated with each other. For example, the app on the product, physical product and the Jews. So build a system diagram, and I'm looking forward. Toa see your assignment soon 25. User Journey Maps: Now let's talk about user journey map and I have been asked from a lot of students what these are. And they are actually a simple map and diagram off things your customer is going through while they are engaging with your company, your services, your products, your web app, your mobile app and also we are going toe pinpoint different improvement areas because it is just like you went to a doctor and the doctor asks you there, Do you have the pain right now? Tell me this area. So you are going toe point to your abdomen that I have been over here and you don't know whether there is stomach in there or you have intestinal pain or whatever you have that is going to be decided by the doctor. So they're going to ask more questions that how are you feeling right now? What is the level off the pain and things like that? So they are going toe in this user journey map. Actually, we are pinpointing our major pain areas. It is just like a doctor investigating a patient and seeing well, actually the pain resides. So we want to see in which section off our Inter our hold user journey map wherever customer is actually ordering something or from the point he sees our ad online. So from the time he actually become aware off our product, you if you remember the awareness, the model we discussed user life cycle model and we are going to see that how actually the user took those steps and we're actually they started feeling pain. Now, what are actually different benefits off user journey maps. They're very obvious, and I have already talked about them higher customer satisfaction or user satisfaction. If we remove the pain off any person or if a doctor gives a medicine to any person, they will always be thankful they will be more satisfied with the doctor. Same. Our customers, our users there will be more satisfies. A satisfied lower customer turnout or journey Generate is actually customers leaving after using your APP for for four or five days. So we will have less turnover. We want toe see that there is the point where we are losing our customers. It is also similar somewhat similar to our user lifecycle funnel, and we will have more sales if we have more customers satisfied satisfaction. We will have motions. Similarly, we will be pinpointing customer pain ideas. This is actually a very void diagram, customer or usage in the map. They can be applied to service industry where you are giving services to your customers. They can be. They can be applied toe restaurants. They can be applied toe hotels, any schools, anything. This is a very great you can say user experience, tool and designed tool you can use to pinpoint where are the pains and how we're going to eliminate them. Now, if we look at the example off my usage enemy for my frog land and e commerce stores, you can see the first interaction will be how my customer actually found my store. What they what they were clicking on a Facebook ad are they found it from a friend then how she interacted with my have upset. What was her first interaction? How happy she was when she interacted for the first time. Why did she do she decide to choose the clothes? How whether she called her friend in the process or she called the help line in the process or how actually she I ordered those clothes whether she was using mobile AP or she was using my Web app or website whether there were some delays in the delivery. So you can see if you are creating a digital product, there will always be some other touchpoints like calling the help line which is no digital . It is ah, calling people, calling other people. So we need to check how satisfaction satisfied? Are our customers at different touchpoints? How actually they actually they selected any other website Why they left our website. What waas their frustrations. What were their feelings? Were they happy? Were they left alone in the end, things like that. So this is all our user Jenning map Every user journey map have some essential parts and these are actually actions. What actually uses are doing it is similar to somewhere what we have covered in empathy maps. But at that point, we were more interested in what uses emotions are and what they're thinking and doing. So this is this is a bit different hair. We are actually checking there. The problem resides in our whole process with an interaction with a customer. So we have motivation. What is the reason behind that action. What was why they were motivated to click by now and things like that? Then what are the frustrations? What are the issues that are happening at that touch point, for example, a check out They might not be able to check out using their email because they don't have any email barriers. So why they are not purchasing that dress? Maybe the price is too high. Or maybe the button is disabled. They don't know whether the stock is low or whatever the reason. They don't know how toe, you know, get past that, then the opportunities so opportunities are the things we can improve. These are the areas are improvements we can make in each touch point or each section off our users journey. Now here is a customer journey map, and this is my, uh, customer journey me for Franklin, and you can see here we have one user persona that is attached to it. So on the top of yours usage on the map, you have to show that this persona is attached to this journey map. And along with that, we also want toe show what actually, their goals and motivations are. What is the scope off this journey map? Whether we're testing the whole lab, we're testing the sign up. We're testing the check out. Oh, are we are testing some fun, adding things to their card and doing their card guard things like that. So you can see here we have the first is first impressions. You can also start it from maybe from the awareness of the product where they got fast, it clicked the Facebook image or things like that. You can start from there. You can show your customer. Oh, are your user that we have this ad and ah, you are going to start from here. So let them start from here and give them to task what they're going to do so you can also interview. You're already You know, old customers are old users which are already using your app. You can ask them what their what their feelings are. Frustrations are during this whole process. So, touchpoints our first impressions searching for dresses, selection process adding to cart and check out. So this is I I'm actually checking first impressions to the check out. So this is actually the whole journey off ordering customer new customer orders. So actually, this whole process is later to new customers. Order. You can see over here. I have written in our hair new customer order in my scoop. So, um, thes are different touchpoints. I'm showing what the user is doing. These are the actions users start taking. You can see over here. And these are all the actions at the top. Then these are the feelings. What? How they are feeling really? Smiley face. First impressions were created, then the next. When they were searching, they were not feeling very well. Selection process will not was okay, okay. And this is very bad because they stuck over here and they were not able to, you know, check out easily. So here we have the opportunities here. We have the frustrations on that. What were the problems that happened? Are what was the barriers that they faced during this whole process than what are the opportunities we can, you know, count on. We can improve these things toe, make it more user friendly and make it user centered, and we will have more satisfied customer. So this is a very simple map. I am sharing all these templates and all these files with you so you can download them and use them in your own user expense design process. I hope you have enjoyed this lesson. If you have any questions, do ask me. Let's move on to the next lesson. 26. Project β†’ Create User Journey Map: Now you have already created persona. And you know, you have taken user interview from any user. Maybe your mother, your father, your sister, your friend or maybe someone in the cafe. Now is the time that you are going to build a customer or user. Jenny map. So in that map, I want you to, For example, I want toe by our domain, for example. I want Oh, they create a new website. So I'm just a newbie. I don't know how toe, you know, use that. So I went toe, for example, godaddy dot com. Okay, So take your father or any other person, show them this website and tell them that what you were going to do over here, how you are going to, you know, just to that product or things like that. Or if someone have some already have some experience with, you know, this whole process, ask them questions. So the last time you put your online ticket, what was your whole experience? How did you do it? So he will. Or she will tell you the story that first I went to the website. I click this and there was no information about this thing and this make me frustrated. So step out all the different touchpoints. What were the feelings? What were the feelings for? For the frustrations. What the happy at the end over they confused at the end toe. So create a whole user Jenny map for any product or the persona you have already created. So take that. For example. You can take any e commerce website. You can take any app, so I'm not. You can see bonding you toe one concept or idea you can use anything, Anything you like. Your own product, your own start up or anything. Okay. So I may well be looking forward to your user journey map. So some medic soon. 27. User Scenarios: we as human beings. We love stories from past when we were used to live in gives and, you know we used we were hunter hunter gatherers. We used to love stories, So use a store. A scenario is basically a short you the story in which we will describe hole. The user is going to use your product when and in which circumstances which conditions which problems they were using your product and what they were facing and things like that . So it is just a short story built on the context and behavior off your user while using your product or a similar product like yours. So we are going to, you know, get more information about the usage and the context and the user behavior from these short user scenarios. Now there are few don't and doze off users scenarios. So when you're building or writing a user scenario, you are not going toe tell each step performed by user that she clicked. Now add to cart button and then she clicked. Check out. Then she clicked something as than other than an ever happened and the she tried to remove it and things like that. You are not going toe tell each and every step taken. Okay, so it is a short story. We are going to write it in a story. Form it. We are not going to elaborate each and every step taken by the user. Now the things we are looking for in a user scenario, is goals off our users. Motivations triggers. Why? Actually they are going to purchase this frog. What are their expectations? What are their actions? They are taking what I have, what is happening with them but that they're frustrated or things like that. So we are also going to look at the context. For example, she was sitting in her home. Was she using our e commerce mobile app Boissieu trying to use it on Internet Explorer using her PC WASI on the left up. So things like that. So this is actually the context. Let's see the parts off user scenario now. Here are some building blocks off a user's nephew. First thing is that we are going to use on a tat ah, persona toe. Use a scenario story. Short story. We are not writing like Jeanne was using things like that. We are actually using the whole persona, our group off users and their behavior and we're attaching it to your product. Similarly, we are going to go for motivation and triggers. Why? Actually they started this behavior. Why, actually they were purchasing what happened? Why they were looking for ah, shirts at to him at night, things like that. Then we are also going to see the problems they face during the usage or users scenario how they actually used it, Whether they were they were facing some problems in the middle, mid or at the end, they were satisfied or nor things like that. Also, What is the problem they are trying to solve? Is there any particulate problem in their mind that I want to solve this? I want to do this or this is my problem. Maybe their purchasing this frog for some other reason. Maybe they want to order it for some party or things like that. So you need to find that problem. What is the problem they are trying to solve? Here is one example off user scenario using my product, which is actually frog planned, an e coma store for little girls. So here is our users scenario. I'm going to show you another example off the same user scenario with some other ending. So there could be a lot of user scenarios which are related to different tasks and different personas. So right now I am using a persona off a busy mom. So here it goes. It's late night Zanna. A busy mom, which is a persona, needs to go to her office early in the morning so you can see this is their need. This is actually their behaviour. Why, actually they want to buy the dress because they they want to get off and you can see the burden off. There's just they want to buy it so they can easily relax and work in office without any destruction. But before that, she needs to order a blueprints, a stress for her daughter. So you can see Blue Princess means we are highlighting blue blue is actually a color. So most off the EECOM stores, they don't have filtration based on colors. So we are going to highlight that because this is I use a need and this is really it can be a really great feature in our frog and e commerce store because it was her daughter's first day at school, she took her cell phone. You can see this is the contact. So how, actually they are going to use our product and search for Barbie frogs So rather than you can see this is user behavior, they are not going to any website or you are directly. They are Googling it. They're searching for Barbie frocks, and we're also going to look at and use this term because when I was doing research user research, when I interviewed to users, Barbie frogs was a term used for princess dresses rather than, you know, Princess. Just so they tried toe type RB frogs. She clicked frog land from Google. This is scenario results and saw princess stress sections she ordered. While what September as it feels easier and quick. So most of the people in my country they don't, you know, get very you can say familiar with other payment options. They feel that it's easier for them to use WhatsApp number as it is direct, and if they want to ask some questions, they can ask it to a real person. So this is the need she hopes to get the item delivered by tomorrow. So she is right now and she's and the and she's waiting for her products. She wanted to get delivered soon. So this is another thing we need to look for. Now. Here we have the same scenario. Everything is almost the same. But you can see at the end this is another behavior they are showing. She, uh she found Princess Ter section and she didn't find the material off the dress, so they were looking. This is actually about their selection. So when they are, they have found the product and they are selecting the product. So this scenario use a scenario is later two more about the selection off the product. So there are different user scenarios for different things, like log in might be something else for check check out. Might be some something some other user scenario. There have been different problems using that feature jack out than for sign ups. There might be some other users scenario sore. So for each user, we are going to have different scenarios. So how we actually gathered or make made these scenarios, we actually let our users do this task in the user interviews. So when you are preparing a user interview, actually I am showed and opened a few. You can say a few screens and let my user do the task. So I gave them that as that. You need to order this address for your sister. How would you do that? Okay, so go ahead and use my PC and our How would you do it at your house? Use your mobile phone. So this is how actually they did it. And they actually try to do things like that. So you can see they didn't find the material off the dress at the end. And she wants to make sure that it's cotton and emailing the support at this time off the night waas. You know waas not going to help our because it was through him, So her problem is not solved. So in the end, she her problem is not solved. See, she is frustrated and things like that. So this is actually we are going toe build in a user scenario persona than their motivation . Why? Actually what is the trigger? Why they are actually behaving like this than how actually they used the product. They ordered the use Google and things like that. They clicked over here. The search for these terms then, of what were the problem they were facing? She didn't find the material off the just. This is a problem. The fist And then in the end, what waas their feelings at the end. What? What? They frustrated or things like that? So this is a user scenario. I hope you have undistorted and I hope you have will have no problem is using it on making it. And there are things you can get from here. You can see there are a lot off requirements and you you can save features off your product , which you can extract from users scenario like we have dress color filters and then we have material filters. This is actually what our idea off uniqueness is based on about this frog planned project. So that is all. If you have any questions to ask me, let's move on to the next lesson. 28. Project β†’ Write User Scenarios: Now you have already learned about use a scenario. Now it is Jordan to create one use of scenario. So show me that what you have learned so far now the user scenario is very easy. Just keep in mind that it is a short story off your user, using your product in a context. So they will have goals. They will have motivations. They will have some expectations. They will perform some action. There will be They will have some reactions. So you need to keep all these into the story. He right as short user scenario in a story for made and show it to me that how it went so you can use any product Airbnb or an e commerce website or anything your father, your mother or friend used in the previous few months off previous few days. So try to create a user story and submit your assignment and show it to me so I can see what you have learned so far. I'm looking forward to seeing your assignments start making it right now. 29. User Stories: in this lesson, we are going to learn about user stories and in the previous lessons we have learned about user scenarios. So choose a scenario czar. The short story sometimes a bit long, But they're mostly in a story for Mitt, which shows all the soundings like a story. What is happening? What was happening outside things like that. But user stories, even the name is you. The story. They are very short one line sentence and they are going to show the user requirements. OK, so they are coming from. They will be written in a form it which is from users perspective that this is the need off the user and this is how they're going to interact with the system. And this is the benefit they will get from this interaction. So do the stories are attached to personas? Are your users of work rules so it is Actually you can say requirement, scattering for all your work roles and personas. Now let's see how we are going to write a user story so they use a story format. It is very simple, very straightforward as ah user and at the place of the user, you can use a work rule. Like in my case, it could be adminstrator off my side. It could be CEO who is going to see the reports sales reports and then they need. I want tohave this or I have want to have this feature I want will be able to do this so that I can get this benefits of why I actually do they need this feature. So we also want toe have both the need and its benefit. What actually is they are going to get from it so you can see in my frog land example you can see it's ah ah, busy Mom Busy data college Dean. They are actually the users or personas, and benefit is a value. They're going to get out off using my system or my product, like saving time like maybe ordering before the summer o r automate my workflow, automate my things, things like that. Now here are few user stories from my frog land. Start up and you can see we're here. As an administrator, I want to create a date and delete products easily so I can save time and manage my products So we can also separate them in each sentence. Like create products at it products, deep products or we can mix them all into one. Use a story on that is up to you. Then we have a busy mom, so you can see the need of a busy moments. I want order using WhatsApp number Onley so I can feel safe and order without email. So actually there What is the benefit they want? They actually, their problem is they want to feel safe and order without an email, so it could not be always of WhatsApp number. This is up to us to decide in the design process on implementation process that how we can make our website secure and we can let our users order without email. Maybe they can long and using ah, phone number or mobile number. So this is open. Okay, then we have the third, which is another college girl or teen girl which was another hour rt type in our personas as a college girl or teenage girl. I want to get my package within two days, so the package arrives before my sister's birthday. So this is actually a user need that they want to track their package. They want to see one. It is goingto be delivered. Will it be in the morning, or will they receiving it in the noon afternoon or whatever? So this is actually another user need and their benefit. They're going to get from them attached toe a user persona. So this is all about you? The stories, They are very simple, very easy. Now, why do we write you the stories? So actually, we write them so we can get what will be the cost. So actually, in from these whole Jesus stories, we are going to get the requirements. So these are the features we want to build in our product, to compensate or to fulfill these user needs and these users satisfactions. So we have the list. Now we have all the list off all the features or functions users and have a vocal wants and why actually devoted so we can easily estimate no costs and development times. What are what are the features we actually want to build? What are the features we can't build because of the course limitations or development time limitation? We can also discussed with other stakeholders different stakeholders see you and other people that these are the things we cannot fulfill or these other user stories we cannot sort out right now. Maybe in the natural ease, we can fulfill them. So this is all about you. The stories I'm going to give you templates and exercise toe create some user stories. So let's move on to the next lesson. 30. Project β†’ User Story: Now you have already learned about you. The stories. Now it is your turn to create. If you use a story so I can see what you have learned so far. So very simple. Form it off you the story. As a user, I want this feature so I can have this benefit. So this is actually a simple template. You can also download it from my resource is downloadable. Resource is and try to create at least three user stories using different work rules and personas. For example, As a shopper, I want to do this so I can do that. Um, second is as an admin. I can do that. I want to do this. So try to use three different users and try to create three different user stories short of the stories and submit your assignment and show them to me. So I'm looking forward to seeing your assignment start creating it right now. 31. Use case diagram: no. In the previous few lessons we were talking about users and ideas. User stories. What are the user needs? What the what is the context they have used? And they are wildly. There was using our product or our Ikuma store or anything and mobile app. Now is the time we are going into the interaction, how the interaction between the user and the system is going to happen. What will be the actions? What will be the even start are going to trigger them. What will be the system behavior? So this is actually basically ah, software requirement gathering tool use guest diagram. And, ah, when I was in college, I usedto love creating them, and at that time it was later toe databases and things like that. But right now we use them in a simpler way in user experience design. Now, in any use, guests and diagram, there are two things in case off my frog land. You can see we have actors that are going toe, you know, be action performers because it is about action and reaction off the system. Action off the user and reaction off the system. So action is going to be related to actor, so actors could be other customer or other shopper than our delivery department, website, administration, Help line girl or help line guy. Whoever they are, they are stock. But she is manager. It could be 1/3 party managers, stock management party or things like that. Then we have the even so our actions. So this is actually the whole use case diagram. Elation. So if we are showing a use case diagram off logging than it will only cover the log in interaction between the actor and the system. If we are looking at check out process for a new user than it would be just the Jackal process, the whole process and how the act of what are the different ah, things are user can do. What are the different functions? Are user can perform on your system and what will be the system doing after the click or perform that action? Then it could be also calling the help line. So I'm going to show you and share with you my example off use case diagram. I build for one process or action, or even so, let's see that now you can see This is a simple use case diagram for busy moms ordering using WhatsApp so you can see we want to be very specific what is actually the action or the process which is happening and the whole use case diagram is about so this is very, very important. So you can see on the left side we have users on the right side, we have another actor on the left. We have busy. Mom, this is an actor. Zoom in a little bit. Okay, so we have busy mom actor on the left then and the process or the functions they can perform within the system, you can see distorted line all around is a system Boehner, you can see here I have written system boundary and this is actually what she can. She is going to view deals or browse products. Then she will add to the card. So they are in a sequence from top to bottom. You can see. Then we have check out with what SEB calls or send messages. Why are works up so she's actually messaging. And this message will be received by this help line guy. You can see how he's also a you can see interacting with the same process. So she after she messages he's going to ask for dress product ideas. What are the product ideas? Lady to your dresses in your card. Okay, so next this guy is actually going to create an order recorder updates, talk with whatever she has chosen because she is not ah using their system to order. She has just a frill card and she's not checking out. So all the stocks will be the same. They will not effect. So he has to create some dummy account or things like that to create a record off that that order engineered an order. I d. Okay, so you can see here is his process is now. This is only later toe this actor so it has nothing to do with our busy mom. So then you can see at the end send order number, amount, estimated delivery time. These three things He's going to send the order confirmation SMS on mobile after he will generate that order. Ah sms will be ultimately region Richard and hair where you can see she receives SMS on the mobile. This is going back to busy Mom. So This is our system boundary. This is very simple use case diagram. It actually shows what is the interaction off the system and how the user is actually going to interact with the system. What functions they can use, how in the rich sequence they are going to use it. What will be the unfortunate outputs like? You can see what will be the US and what she will be sending into the system. What? Hey will be asking for the system or the user toe send. Ah, these things. Okay, so, uh, these are this is very simple, very simple use case diagram. You can find a lot off different examples online, but this is actually what we will be using simply in our user experience diagram the you use case diagram, which we use in a software development with databases and things like that. That is a bit different, but this one is what you can use. Okay, So I'm giving you all these into a pdf former Don't forget downloaded and ah, see and try to build upon it. I hope you have enjoyed this lesson. Let's move on to the next lesson. 32. Hierarchical task inventory Model: now here is another thing we will be doing in our user experience design process, which is hierarchical task in one tree. Okay, Now, don't get confused with this term. And don't think that this is very difficult or this is very simple and why we do it. We are actually building all the different tasks ah user can perform or a work rule. For example, an animal shelter can perform in our system in our app, in our Ikuma store or whatever we're building. Okay, so we are actually building. Ah, hierarchical structure, hierarchical structure off. All the different tasks are use again. Our persona can do within our system. So this is actually our boundary diagram. We are defining the boundary off our system that these are the task the user can only do. He cannot do other tasks or anything as for example, in our case, a shopper or a busy mom or our personas that are going to be other customers can browse products. Such products, fertile products add to cart active wish list, etcetera. So actually, we are defining the boundary that this user can do these many things. So if we are going to decide later on that which features we're going to build or not at the wish lists and things like that. So So these are the things he or she can do, log in, sign up on the tasking gentry items. So we are actually defining the whole boundary off over system. This is very important. So our developers are our development team. They go, they don't go into wrong directions and try to build something else, which we are not, including in the task and country. Now, this task invent tree is actually providing all the different task User is needs and needs to perform toe achieve their goals. So this is actually what we have listed in our user stories, and we're going to build all different task from there. And ah, we can also break up these tasks into sub task. So there could be do tasks under one task. So we can do that now. Here is ah, task hierarchical, mortal for of a shopper which is a server cruel. And you can say we have different personas within that. But this these are actually all the task taken to a shopper Can such look, address view product. It is at two card log in. Enter order details like address, phone numbers and things like that. Then we have check out. Then we have You can see sub tasks for check out on the right. We have 1.8 point one, which is check out wire email and check out via phone number. So there are $2 subbed us within this check out. Then we have created a counter order which is sign up creating a new account and two favors or visual ist than we have post comments or reviews. So these are all the things they are going to define our system boundary that these are the tasks are user. Ah, shopper can perform similarly, We can be the same model for our administrator off the side for our c o r. The person who is goingto see the reports sales reports there will be different set off us for them. So we This is actually called hierarchical task in a country and this is this is going to tell us what is the boundary off our system? These other tasks we are going to build, So that is all. If you have any questions to ask me about this task and reentry diagram. I hope you have enjoyed this lesson. Let's move on to the next lesson. 33. Project β†’ Create Hierarchical Task Inventory Diagram: Now you have learned about task hierarchical, mortal. Now is the time that you create a task hierarchical model for on your app or anything. Any idea you have. For example, let's take any flight booking app. So what are the things that are going to be in the tasks? Uh, for example, adventure. Ah ah, frequent flyer. We'll have to look at so a frequent flyer, the tasks related to that frequent flyer flyer. You can give me all the major task that really necessary in any booking app, and you can show me few sub tasks. Okay, so this is the model I want you to build. You can use any thing you can use pen or papers you can use online. Any tool to build that sketch. You can use adobe exterior before the shop or sketch or any tool you have. So build that model because it is very necessary. It is little specifications that what users can do, and it is going to map out the whole boundary off your system that these are the things juicer can perform. These are the tasks user can go on your system, your upside, your app. So I'm looking forward to your task. High radical. I'm not sure this pronunciation instance good or right or wrong task. Heretical model or diagram. So do submit it now. I'm looking forward to it. 34. Task interaction models: Okay. Now, in this lesson, we are going to see what its task interaction mortars now task interaction models as the name suggests that they are going toe be revolving around a task and the interaction between the user and the system. So a task contraction model is required to show all the interactions between your system and the user. You can define all the requirements and all the different stuff. Let it to your user needs and things like that. But how? The development team or developers are going to know how the user is going to interact and what will be the system response. For example, we want toe show. So show some any mission or some you can say swipe effect for the users to, you know, get the idea of what is happening. Maybe we want to show some other message. Eso This is actually going to show all the required steps and user actions to complete a task. Now, this is actually very you can say formal interaction model. You can also do what you can also do. In recent years, we have seen a lot off great prototyping APS like proto. By then we have principle than we have Adobe, Actually, you can also build different task interaction. Mortals using Adobe X'd. Okay, so you need to show how user is going to interact with the system. What will they use? Your system response. You don't need to write a long stories and long documentations, which which will be difficult for the developer toe. You know, understand. You can just show them by using prototypes so you can build different prototypes for different task interactions between the user and your system. And there is all but right now we need to see what is actually starts contraction, morals just to expand your you can see on knowledge, frame frame off knowledge that this is actually why we're doing it now. The parts off past contraction mortars are the task. Name the ghoul off your task. What is a trigger? What was the trigger? Why the user started this task. What are the needs during the stocks, for example, logging task needs Ah, log in name or email address and then the pass for and also the barriers faced by users during the task. So what will be the barriers or what will be the problems user actually face during the task. So this is actually, you can say, a D deal task interaction model, which shows that how and why user started this task and what happened during this task and how the system responded with the with messages or things like that. So let's see one example which I build for specifically for this project Frog Land. Let me show you that. Now you can see this is a task contraction model for ordering arson rail address. So this is the task I gave to the user. And this is how actually things are going to happen on the left side is the user on the right side of the system customer search for Cinderella in the search box and click such burden. You can see this is very deal treated. It is showing each and every step taken by the user. This is actually very necessary. Now the next step is customer clicked on The first item on such is their spirit is also showing. But is the behavior how they actually select things? System returned the detail page for the trust customer selected customers like it pink color from the two available color options systems, which the preview image to a pink dress. So this is actually we are showing that this is actually how our system is going to work. Customer selected 4 to 5 years from the sizes list system highlighted the selected size and updates the in stock status. So right now it is installed. Customers is a bit confused about the sizing options, so this is actually the Battier custom faced customer actually faced. Ah, and then we have customer clicked on size charts to see whether she has selected the correct side system. Shows the size jars on as an overlay image customer clicked on size chart to see whether she has selected. So this is actually user and system interacting with each other. These are the imports. What the user is doing border the outputs originated by the system. What are the barriers doing that which Jews actually faced? So this can also be in your a task analysis you did in your user research. Oh, it can be done on a prototype you have already developed. So you had a prototype assured to use user the used it they perform the task and this is what happened. So this is all about task contraction model. You can skip that. You can skip that and just try to build a few prototypes because it is easier and they're more visual and the show's rather than tell that is what we need. Okay, so I hope you have enjoyed this task. Interaction. Moral. If you have any questions to ask me, don't forget toe. Ask me a lot of questions because I love them and sometimes a lot off my students that they give to star of Wonder Star three star reviews. The daughter happened to ask any questions to me. So this is very you can see very sad for me when they don't ask questions and they just leave Onorato Star reviews I hope you have enjoyed this lesson. Let's move on to the next lesson. 35. Information Architecture and Card Sorting: Now we're going to talk about information architect er and how I actually did research and you can say and hasta information architecture for my frog land. I'm going to show you some clips off my users. How, actually I, you know, interviewed them and used different techniques. Toe locate good information about our information, architecture and how, actually, ever users consume and search on a frog land or any economist wrote. Now the information architecture is all about the information in the form of radios in the form of tax in the form of headings in the form of images are in the form off products listed listings, different listings on in the form off, different context you see on your mobile. And we're going to present that information in the most understandable way, which our users can easily understand. So the things questions like how users will find this information, how users with reach them this information, which but they are going toe selector, reached it, this information and how they are going to understand this information structure. So, for example, if you look at any products phase where we have details off any product or any a sweeter or clothes or shirt. You can see there are chunks off different informations like color. We have, ah, material. What it is made off. Different sizes available different reviews from our customers. So these are all part off the information blocks about that product. Also, we are going to look at navigation, for example, our main navigation off our website. Different categories off our clothes. Breadcrumbs. You can see bread comes are actually the part, your product pages showing that this product is in this category and this category resides . But in this category, things like that, then we have product tags. So what is the product act tag? So there are different tags you might have used hashtags on Twitter or Facebook's that are also part off information architecture and how you actually find information of what is included in information architecture. Everything that you are going to label or you were going to sort a search or find are organized information in a way that it is easier for the user to consume is actually all inside the border off information architecture. Now, in my frog land e commerce website, you can see we have some features like sorting with price low to high alphabetical date or based on the tags categories like Maybe we are going toe sort our information using fabric type like cotton, linen and things like that, then we also can sort based on colors. It's if I just click on blue or ride or things like that. It is going to list all the different items based on these so product view. You can also use the same thing with product tags. For example, read Cinderella. So it is also going to help find that dress. And it is also going to help build our database off information about that particle thing that user actually needs. Now we're going to talk about a technique that we can use to build information architecture or get some more information about the architecture off your website. Major categories. So it is called guard sorting, and car sorting is a simple technique where you were going toe, categorize the information in by asking your users to sort out the different categories. So in my frog land example, I let my users toe, you know, decide the categories off my top navigation bar and what they are looking in that top navigation. But in the end of the lesson, I'm going to share with you the screen shorts or the images I have taken while my user while you know, filling out different cars, sorting things and different information architecture questions. Before that, we need toe. Learn more about card sorting Now there are different types of card sorting. There is open guard sword. They disclosed card sore technique than we have hybrid guards would. The open car sword is that you're you let your users to, you know, make sense off the dead. Also, if you show them few frogs that these are different kind of frocks, what will you call this category off? Rocks. So if the right like fancy dress or maybe Barbie dress, you make that category. So this is your users are deciding everything. They are sorting their cards into categories and labeling them, so you give them the opportunity to label them. Then we have closed card sorting. You are going to give and write all the labels on the cars and your participants, all your users, they're going to just soared them into the order. The thing that this should be falling in this category. This should be falling in this category. So this is you know, the user has less control over it. Then we have hybrid guard sword sort, which I actually used. I will get I gave participant few cards and I also let them write different categories off their own choice. Maybe they have something else in their mind. Now, here are a few images when I waas doing some information architecture, research using my user It is not a very you can see unique study that is very simple. I just gave them such bar and assured them few for images off rocks. And I tell them that what you are going to write in this such Barto such for this kind of dress. So I wanted to learn What is the category of what is a term they are going to use to find this information which is ready essential in information, architecture, how they reach the information? This is a question I showed you in the start. Here you can see I gave them a few closed card sorting. I have already given them few for four or five options and I let them choose which one makes motions to them. So instead of party justice, they're selected fancy frocks and you can see they're taking this, That this makes sense. I'm going to look for fancy frocks. Party just doesn't make much sense to them. Casual dress and Princess tres waas also create, but actually instead off searching for princess dresses, you can see on the left they used Barbie dresses in the search bar. So these are actually you can see the categories our user actually started. You can also see in at the end I have written over here summer collections. Okay, so this is actually they were looking for. They were looking for winter collection and summer collections based on the season, which I never thought that it would be, you know, possible. I I have never seen any e commerce website that has a seasonal collections or have some collection at the top that season, for example, summer collection or winter collection or autumn collection, things like that. So this is this was a new idea to me. You can see here and the category, she wrote. She's writing right now Bobo type dresses, which will here you can see here. Fancy dresses. There were actually fancy justice, but they had some balls on the top off on the neck near the neck. And actually, and this can be our you can say hashtag because user tried to search for bored, bored I presses or bull dresses or dresses with booze so we can give them suggestions while they were trying to type. Wants that ibu. We can give them suggestions in a pop up, and they can easily search for that so we can use a suggestion based feature for such ing, which makes it easier for the users. And we can use tags, toe dags, different elements off our, um, our dresses. So this is actually how we are going to do car sorting and get some information architecture we can. I also actually give them some images and, uh, you know, for getting the product details. Which was another thing. So information on a product detail page I collected on another side, which I think I don't have an image right now, but that is all about cars sorting and information architecture. You can collect information like that and don't keep try to keep the record of that. You must have something like this so you can refer back to that and a build your information architecture upon that. So I hope you have enjoyed this lesson. If you have any questions to ask me, let's move on to the next lesson. 36. Ideation and Sketching: now the quickest way to build any idea or generate any idea is sketching. You always need a pen and a pencil, are a pencil with the paper, and that is the most easiest and most cost effective and time. Ah, less time taking procedure off generating ideas. So once we have decided that these are the things our customers are our users or our personas need, we already have identified what are their needs and things like that. We already have defined the categories off their information architecture. We are going to quickly sketch out the layout off the information. So what will be present at that off? What will be present in the middle of the page? What will be at the bottom off the page and we're going toe prioritize information hierarchy on the page. So sketching is actually going to be an exercise. You can include your developers. You can include your stakeholders, your CEOs, whatever you can all credit them around and give them papers to sketch. Now, here are the things you are going to keep in mind. Valuer doing this ideation exercise. It is a collaborative effort you are going to include toward three or four people around you from your team toe, do the ideation. So try toe. Give them a limit that we have 30 minutes to do six sketches. Whatever comes up to your mind just tried using whatever information we're going to present . So they all have the idea off the personas and, ah, the things. They must have gone through all the things so they can generate different ideas. So the sketches should be enough. You are not going to, you know, make them pixel perfect or draw them using our ruler or ah, pencil. So just at least create 2 to 3 ideas minimum. So give everyone a task that you should create 2 to 3 ideas. You can also do this exercise in a user interview, our stake holder interview. So you get the idea off the user what is in their head or to get the idea off. The stakeholders works in their head. You can also use this at the design stage where you are going to start your design, so this is just technique. You can use it anywhere in your design and user experience design process. Here are a few examples sketches your stakeholders might have sketch something like this. Like you can see over here, which only you can understand when they are drying there might explain it to you. You can tell them what is this? Explain it to me to get more ideas. You can also highlight different sections and label them that this is going to do this. This is going to do this, but it should be readable at least and understandable by anyone who is looking at them. So try to create a sketch which is easily recognizable easily. Ah, tell the story what it is, what is happening in the sketch. And here are a few more you can see. This is a bit more detailed. It shows, videos, music and things like that. Then we have this one. So these are different examples. I hope you have enjoyed this lesson. Let's move on to the next lesson. 37. User Flows and Site Maps: in this video, we are going to talk about user flows and site maps, and I am also going to share with you an online tool that can easily help you generate user floors and site maps visually and very easily. You just need to drag and drop, and that's it. And it has a free version toe, so we are not worried about paying anything. So let's get started. First, we're going to see what our user flows and why they are important. Now. Flow off your website and your APP is actually the part off information architecture. How the user is going to move from one page to another, or from one screen to another rich part they are going to take and how actually user reaches a certain portion off. For example, a check out page ho. This person is going to reach that. Similarly, we have ah, very common flows like we have check out floors, we have log and sign up flows. Oh, are we have on boarding use a flow when the user is actually starting or installing our app or website for the first time. So this is actually on boarding, so we are on boarding them. That how they What is this website or app is about and how they are going toe get value from it. So this is these are common user flows. You can design user flows for your whole website for each process and it is very simple. It is actually just deciding how the user will reach the information. Similarly, we have site maps that are mostly lettered tau websites and why? Actually we create a map off website and all XP ages because of the users and searching just they can find the information or what they're looking for easily. So we actually may about create a map of all the pages and sub pages off your website, and we put it in a one of one page of sometimes of one diagram to show that this is how our whole website structure is going to lay out. So this will be our page structure. This is how we are actually have different structures or you can say, like if we talk about architecture, we have ah house and we have different rooms and then within those rooms we have different smaller loan rooms like washrooms bathrooms or toilets. Dressing rooms, eso in the kitchen. We have dining room. So this is similar to how actually you are going to map out a house or your home. So we are actually have big rooms like parent pages. Then we have child pages that are sub rooms or sub smaller rooms of smaller portions inside that same category, and it is actually how our whole website is actually going to have our structure. So search engines, mostly Google. They have crawlers that are basically software's that actually go to your website and they crawl different pages and get information from them. So site map and planning out how you are going to structure. Your website has a great impact on your marketing and your search engine optimization. How your website is going to appear in such engines. So this is very important part if you are designing or developing for our website. So let's see a tool that I recommend you can use for creating site maps and user flows. So this is an AB core flow map, and this is just for site maps and use. It flows, and it has a free version and free sign up. So here I have. I created this site map and you can see this is a site mare for fraud plan. Let me go to this view. It is very simple. What you have to do is just you have tow click over here, and there will be different pages. You can add from that. For example, if I want to add more pages, for example, Alexey, we have frog land men paid. Let's zoom in a bit. Okay, so we are now zoomed in. Let's drag it up. Frog land, Main page. Then we have some pretty is deal. Deal speed on browse products with category. So whatever category they're going to select over here, it will be a category page with filters you can see on the left. We have small filters. Then we have contact us page log and sign up page. I am just, you know, making sure that you understand. What is this concept then, from these two pages, we have product details, product item, and this is the same product page product details page from deals page or products with this or this bro's product page. So user will go from here to this page. This is a common page. Then we can add to cart. And here we have our card. Then we have check out process than we had been. Have to select payment options than we have orders. Success based. So these are all the different pages we have listed overhears. You can also list different category pages over here. For example, in my case off frog land, I can add a few more pages by clicking this one over here. And I have few more categories. Like, let me add a catalogue over here and bitch here. We have a new page. Let's name it. Mm. Princess dresses. OK, so we have this one more page or hair. Let's move it. If it's let me see, I'm not sure why it is, you know, structuring like this. Anyhow, it is choosing it automatically. Then we can add one more category Page. Let's add one more category and we are going to add another one. This will be casual dresses. Okay, So you got the idea. This is how you are going to create Ah, site map and you can export it over here. You can see here we have export options. We have svg PNG. I'm going to use PNG and generate preview. Let's see how the preview looks like. This is not actually smart so far, AB. But actually I cannot create a new project as I am on a free version. So let's export as BND so you can have this PNG and you can use it and show it in your board folios and just generate site map like this one. And we look great. Similarly, let me move again to that same spot and let's go back where we can go back here. Well, we can go back. That's signing again. Not sure how you have to go back over there anyhow, so off now we're moving to user flow, so user flow here we have the user flow and you can see there are different wrecked angers . And then we have this, um, kind off triangle type shape, and it has it is actually a decision. So this is a process, so I'm actually not using most off the you can. Same next to move this and most of the things we're here. I think your user flow must be very simple. So just think that this is a screen. Right now I'm showing you use a flow for an app I designed. This is a user fruit welcome screen. Then we have have you. Do you have an account? If you do have an account, you are going to log and you can see or hear than this is actually. If you don't have an account, you are going to create a new account. Then again, you're going to Logan. So once you have been logged in, you can connect your smart so far. Why are Bluetooth OK? So if your Bluetooth is already turned on, you are going to go toe the introduction to so far controls and this will be the end. And if you are not connected with blue two so far, this is actually the other part. You are going to connect your Bluetooth if not connected eso the message will appear and you will again be connected toe the Bluetooth and again goto this same screen. So this is actually on boarding user flow for a smart sofa app when the user for starts it . But she is is the smart so far and they try toe open the APP for the first time. This is going toe. What happened with them? So there are actually two decisions or two things they are actually making over here. One is Do you have an account? And second is whether you are connected with the so far, Bluetooth or not. So there are two parts with that. So whenever you have some selection or you have something to decide with, you're going to use this kind of symbol over here. I'm not sure why. Actually, it has. Bean. There was something over here. Let me show. Okay, So once I click over here. So if I click over here, I can change it. Toe this decision symbol. Where's okay? So we have something like that or here. Okay. So once you have made made this so it is very easy. All the controls are at the bottom. If you want to change something, just click on it and you can have another. You can say color over here. For example, I want to show green for the connected again. I want to show green or here for the connected. And it is going to show green or here. Okay, So that is all it is Very easy. Weird. There are a lot of different more examples off very simple user flows. I'm going to show you which others have created. You don't need this app if you want to create it in sketch at obey, actually, for a shop, whatever tool you have or even paper or pencil, you can do that. So here is another example of user flu. I found it on a B B house. I'm not sure who designed it, so I'm not taking the credit so you can see kids dashboard car customization. So this is actually two things. It is showing that non appearance dashboard. We have flows like we can go toe kids profile kids task or confirmation. So these are two things where you can do also destroying that log out will show the confirmation your kid, you are going to select the kid and then the goods profile. So this these this is another kind of user flow. This is another kind, which is very simple. I really love it. It is what actually shows a user flow on boarding an authorization sign up. Sign in for God password. So this is actually a good example. So it is actually reversing again and again. If you forgot the passport, you have to sign in again from the email you get anyhow, sign up, create been upload photo documents at withdrawal method. Choose Texas Service Home page. So this is actually a user flow off. Ah, whole app, nor just one process. So from on boarding to choosing a taxi home going toe, home page news, they did profile. There are a lot of things going on over here. I don't recommend that you create two big user flows. I think it is better if you keep your focus on one or two processes rather than a very big desert floor. So create, like, three or four years of floors, different user flows and divide your whole big gap into four different shows that flows. That would be great. Hes a user flu I created using Adobe X'd, which is Ah, designed to you a design tool. And this is a busy mom user flu. And you can see I used that user flow for a checker process a busy mom would have. So it is actually attached your persona. Main page deals page product details. This is how this user is going to reach the information so they are more inclined to go to deal speech other than browsing products. Product details view card check out. Check out with mobile number. Check out with Logan face Facebook. Then we have both these pages going toe Receive order confirmation SMS for E and email. So this is a very simple process. Very simple. Lay our saying What? Actually the user flow must do. This is how your user flows must look like and work like it is very easy. I just created it using ah, wire frames free viral via framing kit. I'm going to share the length with you. So do try to download that. And if you have adobe extra features a Frito, I have a full course on that. If you I don't know. It is really easy to use and is becoming most popular with within user experience, design, community and your design community. You can download that and use that to create something similar like this one. Or you can use any app you want. And I hope you of the best and ah, we will see you soon. In the next lesson 38. User Flow Diagrams in detail: in this video, I'm going to show you and introduce you toe float user flows and how actually you can create this flow diagram And what? Actually, all these symbols mean what this war Does this rectangle mean? Where does this or will mean Where does this diamond actually means? And also this parallelogram. So we're going to cover just these four basic A shapes. There are a lot of other shapes, but I think we don't need most off them right now. I'm using flow map, which is an awesome online after creators of flows I'm on right now are free plan so you can go ahead, sign up and use that and create start creating user flows and side maps anyhow, so right now we're going to start with this user flow. No, this user flow is actually about ah user downloading the envision app, which is a prototyping app and actually commending on the prototype. So all the steps involved from start to finish till the time he commence, we're going to show them in a flow that it uses going to flow from here to here. Tito new screen to new process to new action. So you can see the first step is actually a rectangle rectangle means ah, process or activity. So download and region happen abstract. So there's a process I'm doing. I'm doing an activity that I'm going to launch it. This is another activity. Now you can see Sign is in is actually in an oval. Now why it isn't in an oil because over means that it is going to be the starting point off that process. So you can see these are actually pretty me three luminary actions we had to download invasion app to, you know, do that. I had to comment on the prototype. So this is actually the starting part. Sign in and you can see if we I'm pressing actually space bar and dragging it up. And here we have already have an account. So this is a decision. So it has two parts. If you have the account, you're going to go toe one part. If you don't have the account, you're going to go toe another part. So these are two parts. So once we have a decision to make, we're going to use this diamond so already have an account question mark. So If yes, we're going toe enter log in and password. So this is an input we are in putting into the system. Our log in and password fields were in putting data. So this parallelogram is actually mean means that we are giving some imports off. Whenever you try toe, give some input to your system. In any format filling a form or feeling sign of form or things like that you are going to enter. You're going to use this parallelogram. If you don't have an account, you have to go through the sign up process. It is a process. So that is why it is actually showing into a rectangle. Let's go down. Okay, So after logging and sign up, we're going to go to the home screen. And then we are moving to the next application navigation than we want to see and comment on the prototype than we have. Open prototype. Perhaps So these are all the processes and user is doing, so he's right. Now open the part photo type tab. Then we have an active prototype, opens up or try Proactiv products like the layout opens the layout hordes, tab tap so you can see, these are all different processes. There is no decision. It is a straight forward. One step next step and next step. Then we have you can see your hair wants to leave a comment. So whether he wants to press cancel. So there are two parts whether he can leave a comment or he can, um hey, can press, cancel and go back toe this layout so you can see your here. Here we have two parts. One is this cancel and it goes back toe opens allowed. And if we press yes and click on the comment board it is going to go to the command more so this is actually going to another process line over here and you can see click comment more select comment area writes our command. So whenever you are typing something you are in putting so again we're using a parallelogram and press to publish. So this is actually the end. Whenever a process or every anything completes or ends, you are going to use a circle. Okay, press to publish. You can see it is a green circle. Now, here it ends. So that is all about creating user flow diagram in this flow map, you can use any other graphic tool to, but I think using this online is very easy. They have all the ships and everything already built in. So, um, if I go to my account, let me go to my account. I have projects. This one is frog land. And if I go over here, you can see Here is the, um, site map I have created Head is the user flow diagram. Okay, Now, if we want to add something over here, I'm going to click in over here in this empty area, and I am going to use ah, circle over here because it has ended. So I'm going to say something like, um ah, successful on boarding. Let's make it a little bigger, like this. Like this. Okay, we're going to connect it with, like, this one, and let's turn this to green. Okay, so we have our successful on boarding, so you can see over here. You can also, um, do something over here, like, ah, this and I'm going toe press over here. Um, start. So before that, if we want to have a few more screens over here, I can link it over here like this. If I want to have something like, um, a process which is download app, download app from APP store, and ah. Then we are going to have another one, which is, uh, over here, Launch cap. So far, AB or something like that. Okay, so we're going to connect them like this, like this, So you can see it is pretty easy. You we have these two processes. Then we have the start. Once it has been lost, it is going toe. Show us a welcome screen. Have an account? No. Then we're going to have this create account or sign up a sign up. And if we have this, then we are going toe Go to log in. You can also use an input over here. But for simplicity, I I am. I have skipped that. And if you want to use it, you can use it. Thats dragging a bit at the bottom. I'm going toe expand it a bit because it is not showing. Okay, so now it is showing. Let's move this subject over here. Make your hair like this. Okay, so here we have our on boarding user flow diagram. And if you want to export it, you can go to this ad over here you can share it with from over here and you can export it from here. So if you click on exports, you can see we have few options that export as SPD format export as a PNG format Transparent background. If I wanted transparent background, I can have a transparent background project title document creation date. You can hide it if you want to show it, then we have original size and ah, I think we can also have custom size. But it is actually maybe for the PNG because SP jeez, scalable vector graphics. We don't need a size for PNG. We might want toe use some custom size over here. For example 3000 by 101,012 and I'm going to export. It has a PNG and if you want exported as spg, that's another thing you can also export. Is it as undocked? Document X, which is Ah ah, new feature. I think they have just started. You can also export it as a PdF So these are all different exporting options. You can click on germinate preview and it is going toe Lord, the preview project Name eso that is, This is it's side map. Okay, so that is all. If you have any questions or any commence or anything, you want to learn about this APP flow map are about user floors or site maps. Let me know if you have any questions to ask me. Let's move on to the next lesson and the next video. 39. Project β†’ Create User Flow Diagram: now, your next task is to create a user flow diagram. You can use the app I have showed you flow map or you can use any other graphic design tool . It'll be actually for a shop sketch to create a user flow diagram off an on boarding process. So on boarding means that user is going to download the APP, start the app, and then Logan are signed up to the APP and then start using it. So this is the whole process. We don't want to create ah, flow diagram off the whole app using everything, just focusing on one process. So I want you to create that user floor diagram and show it to me. I want to see what you have accomplished and how you have understood on the concepts off floored Agam. Okay, so if you have any questions to ask me, I'm looking forward to seeing your assignments. Start making flow diagram. User flow diagram now 40. All about Wireframes: Now we have all the requirements off of a user. What actually is user needs on a page what information they are going to use to make ah, buying the CN. And then we have all the user flows and how user is going toe move from one patient, another one. We have information architecture built on the user research where we found that user is going to use such a box or sometimes looking for main categories of summer collection and things like that. And they are looking for deals, speech on the main page and things like that. So we have collected all the essential information Togo to and create a wire frame off our concept. So this is actually our design phase, and we are actually using all the information we have gathered in the previous last lessons we have covered. And it is going to be a blueprint off what? Actually, the content must be present on a page, so we are going to add more structure and details. But the colors we're not going to use colors and typefaces because it is more off subjective issue. We are more concerned about what the information must be present on a page for a user to make the decisions. And ah, secondly, we're going to test it with the user that this information is essential Or is it a deck Wait for the user. And also, we will show it to our stakeholders over CEO, which is in case in me to see whether this is appropriate are not so. This is actually these. This is far from stage and wire frames is Let me tell you one most important thing that wire frames are the bread and butter, or you can say the last final stage off a user experience designer. If you want to use experience, researcher or whatever you are, these are the things that will be the final deliverables to your design and development team. So this is very important. You can create them with any tool you have. You can create them on panel paper. You can create them digitally. You can create them using balsamic mockups. Oh, are you can use adobe X T photo shop or sketch software or whatever tool you have. No, let's talk about the level of details when you are designing something. So most of the times when you read any requirements for a job or things like that, there is. There are terms like lo fi, medium fire, high fire lo fi. These I have seen a lot of times low Fidelity means Lord details. They are like, close to sketched things. So the vile frames are almost at this stage. Medium Fidelity might have some colors. It is a tough you can say interface built Porter prototype. Maybe enough prototype might have a medium fidelity. And the high fidelity is actually our more cough, which we are going to create and sketch or so before the shopper Robbie Extreme, which will be the final user interface for our website. So this is actually the difference. You should know this difference because sometimes it is inside a job application and you should be able to understand it. Now, let's see the wire frame I created for the main page, and I'm going to show you why I actually made all these decisions. So let's see and go and see that now. This is balsamic moke up software, which I used to create quick, more cups. You can use adobe X T for the shopper, anyone Anything you have are a piece of paper if you want. Okay, So, um, here's a wire frame. I really recommend that you create a wire frame using additional because it is more precise , and you can print it and show it to others. So you can see here we have the logo. This is our logo, Frog land. This is just the meeting were not more in. And we're not focusing on the visuals or visual design. We're focusing on the message and what must be present or for the user to make the buying the CNN and to make the users. Apache is easy and user friendly and improve the user experience off this EECOM a store. So let's let's zoom in a bit. Let's see if we have a full page view. There might be something over here to show it. Control F. Okay, so this is good. Okay, so now you can see here we have on the left frog plan and authentic place to buy imported girls dresses just to show that in our country, the mindset is that we love imported things. If it is from Germany, China USA or any other country people are going to have more value to them, attaching more value to them. So this is actually the tagline ensuring the message. Okay, then we have on the right. You can see Logan and create new account rather than sign up. Because when we were starting for the first time user interview with my users, most of the users they didn't understand sign up things. So they think that it is also Logan. So I changed it to create new account rather than signing. Then we have log in, which is ready common. Then we have these two things called help line or seven days return, which is actually assuring, because I have seen that in the user interview we had users thinking that this site is not trustable because they are nurturing in his return policy. So we make sure that we have some return policy over here. Then we have over here the card which is showing clearly eight items, and we have a big search bar which user is going to expect on the right side? I have seen a lot of websites that they use on the such bars on the left, which is not a very common place for that such bars. We will have some drop down with such suggestions. Anyhow, here we have the main page items I have added home over here because most off the users in my country they don't know if they click on this logo, they will go back to home. So I have added a home categories because most of the users, if they're lost, they're going to go back to home. Then we have deal speeds, which busy moms, our persona, which was looking for on the deal space. And we have party dresses, which was a selected category when we had a card sorting exercise and most of the users the selected party dresses other than fancy dresses. Then we have casual dresses. Then we have Barbie princess frocks. So I have used both terms, princess and also Barbie. So this is it, then. We have main top two sections here. We have summer collections. You, if you remember that I showed you an image off a girl when she I interviewed her. She was looking for summer collection because it was summer right now on the left, we have top deals again. We are focusing on a deal. Spades, maybe user is going to get more focused on this one than clicking over here. Bottom at the bottom. We have different dresses which are right, No popular. So let's move down popular dresses and ah, which are mostly bought right now. So user might be inclined to buy dresses which others are looking at right now or maybe trying to buy right now. So these are different dresses. We can add more cut, agrees. But this is actually our mean. You can say focus toe cover the first ah section, which is mostly above the fold or in the full area where the user is going toe mostly browse. So users if you don't know what is fold for exactly the top seven or 800 pixels, which mostly uses browse on a PC. It is not the same on your mobile. Mobile phones will have like 4 to 5 hundreds, and we might have just this section over here. Maybe this one. So we're going to show these two in the top section. Okay, so that is all again. We have off fraudulent address and phone number at the bottom to make sure that users have something over here. Then we have again repeating the same at the food. Our users are not going to be very much interested in the photo right now. Um, also over here, we can add something like ordered by a bar. Accepts. Let's add that right now because we found out that users actually love ordering via what's app. So we are going to replicate this by clicking art. This software is very easy to use. I have a free video on my YouTube channel. If you want watch how to use balsamic markups, you can go to my YouTube, general land. You exciting. And you can search for wire frames and you will have a detailed 15 minutes video on how to use the stool. Eso we are going to have order Lourdes and part of Okay, so they exchange the icon over here if we have Ah, um message. Are things something like this? Something like this. Okay, so we have something like that over here. So this is going to, you know, let's move it to this one, like, over here, because use is going to look on the light right side and the corner, we'll hear more. So that is it. I think this is our wire frame and I have shown you all the decisions we have made via actually, we are using the's categories over here because we found out in our card sorting that users are using these terms to define our different categories off loads. Then we have summer collection which uses were looking for When it comes winter, we're going to show the winter or we can show, like, three columns over here. And we can also show winter because sometimes users might want toe look for winter collection before they even though before the winter is going to come. Okay, so again we have Ah, all these. If you have any questions regarding why and how I created this hold wire frame and water that the scenes we had you can see in the D deals I have 90% off, which is a very good call to action that please buy this. Then we have this just arrived, which is showing that these are latest designs. So it is also showing the fabric over here you can see made with imported chef own February S O this is the title of the Frog and then we're going to show the fabric off what it is made off because most women, they are mostly interested in the fabric. So that is all. If you have any questions to ask me, this is how we went through the whole user experience design process and created this y from off the main page. We can also create Ah, wire frame off the products page. And ah, right now I don't have time to create all of our frames was the reason is just to teach you how the use, expense process, how this information architecture user flows. Everything is going to help you decide and make a better user experience for this focal and e commerce website. Let's move on to the next lesson and see what we have. I had see you soon in another video 41. Everything about Prototypes: No, we have already created wire frames. Anwar frames are going to tell a lot about what the information is there present in your pages, websites or mobile app screens. But the interactivity. How, actually those static pages are going to work or interact When what happens when a user clicks on? Add to guard what happens when a user clicks on. Shorty deals how the whole product is going Toe Works of Working model, which shows mostly the interaction feedback off your system and border the transitions between screens. And what will happen one. Some user gets error messages of things like that. They are going to be present in your prototype. These prototypes are bread and butter off Usu's expense design process, and they are the biggest cost savers. Why? Because you can have and develop a prototype or paper prototype with no costs and no time. You can create them in just 30 minutes and you can test your idea, and you can Truitt of it. These Air corps. True of re prototypes, you are not going to, you know, get yourself emotionally involved with the prototypes. They are just for testing purpose. They are for making your product better and better. You're going toe. I treat your design and again and again based on the feedback you get from the users when you test your prototypes. So try toe. Create prototypes as early as possible in your user experience design process. Even you can use them in user interviews and ah, let's see some off the different types off prototypes, which I have already covered in my adobe X'd course design product. I've been collaborated, but I'm going toe cover it over here again because it is more later toe this scores than Adobe X'd. There are three major types off prototypes, one our paper prototypes, which are most easier to produce. You can use just the papers, you some markers and things and create paper prototypes. Then we have digital prototypes are interactive prototypes, which users can easily tap on and click on, and you can move from screen to screen with some transition. Some effects. There are many tools. Pro Tobi, Principal Flynn, toe Adobe, X T. These are all the tools you can use to clear digital prototypes. Then we have developed prototypes like you can see, we mostly used them in Ah age and UX, where we just at lease or leave the better version or health a version of a product and just to test it, the how will be the response of the users. What will happen? So if you remember that InVision studio they started with Andrea studio is a your design app, if you don't know, they started with an invite off testing their bitter product and consecrate the invite to send you a link protested, and you give them feedback that how what you think about their product. So this is a good way, but it is a bit costly, so if you are trying to develop a prototype using some chords, it will have some cost now. Horizontal prototype, as the name suggests, that it has horizontal features means that it has all the features, but you are not testing each feature in depth, for example, the mean screens or main pages off any website. They are mostly going to fall into this category. Horace, under pressurised because they are a lot of options to choose from. User can click on deals. If you have seen remember the wire frames off my website. Users can click on anything, but they are not going to go toe check out page each time via each part. So you are actually testing a lot of different things, but you are not going into depth. So this is actually like you are not going toe show all the process. Are all the prototype behind ordering off rock? You might have just need to test. For example, if I have placed summer collection on the first page, whether the users are going toe first, click that or not. So this is actually horizontal. Prototype is actually going toe Jack, you're you can say empty doors. So you just placed few empty doors in your app or in your browser. Like if you have recently used YouTube, there was, Ah, empty button, which does nothing. And when you click on it, it shows you that this feature is coming soon and you say What what the heck, what is happening? And they placed it just to test the user. That user is actually interested in this feature or not, So this is actually horizontal prototype you placed, if a lot of features just to see which one attracts more to the user and you are not going toe injected. Ah, check the functionality in depth off each feature. Then we have vertical prototypes. They are going to go deep into any feature you are testing. For example. I go from main page and then I'm going to go toe the whole check out process. So if we have a perfect type that shows the whole check out process, this is a vertical prototype for check out. So these are not different things. You can see if I try to create ah, ordering process ordering 40 vertical prototype. Then I'm going to show how the user is goingto go from browsing address, toe ordering address and adding it to cart and things like that. And, for example, if we have, ah, like logging or sign up vertical prototype than we're going to go into details off. If user get some error, message of user is already logged on or Jews are already have an account or one. What if he or she forgets the account? So the vertical product, I will have all the details off. Ah, single feature or function. Then Deep prototype is actually combining both horizontal and vertical prototypes. So it has. It is going to cover a broad functions, but it is going to test just one or two off them introduction. So I'm going to show you at the end of this lesson mighty prototype, which I have used tojust desk A. My searching function. And I used Adobe X'd to create that prototype, and you will really love it So you can just test two or three things out off your whole app , which are most important for your user, and you think that are going to make or break your app or website. Okay, now, in the last, we have local prototypes. Local prototypes means that they are going to reside on a single screen single webpage, and they are more focused on detailed on ah, single aspect off that page, for example, you might have seen a B testing where we test that the burden the label off the burden should be add to cart or at the shopping bag or by no, and we will see the results on by dusting on different sects. Sections are you can say different portions off users and see which is going to win. So a B testing if you have heard that we actually created two versions off the same page or two versions off the same screen and show half off the users one version and half off the users. One version and see which one is going to win and which one is going toe. Get us more sales. So it is about how we are going to have more converted users. More, more money. So it is a bit a little bit of a different kind of testing. So I hope you have enjoyed this lesson. Now let's see the prototype I created using Adobe X'd. If you are interested in joining Adobe Extra, you can take my course over Toby X'd. Um, you can see I really love toward wear ties about my courses. Anyhow, let's move toward a backstage and see what I have created. No, we are in an O b E X t, and you can see here is my prototype here we have like then different screens. 56789 10. Ok, so they are actually 10 anyhow, so these are different screens and ah, prototype is going toe. This prototype resembles almost ah final product. So I'm going to show you. Now I'm going to play this and let's see how it looks like and how it plays out anyhow. So we have this main page we have search. We have this menu bar which is not working. So does deep prototype. We have just a few functionalities working over here. Not everything else. Okay, so we can A user can go to deals by no press over here. Okay, so we have this speech, we can select the size we can click on by now. A message appears and disappears. Keep shopping, or you want to go to check out. So we're going to go to check out because it is more about check or process. So we would all our card. So this is my card. I viewed all my card. If I won't remove, remove is not working. So there are few functionalities we're testing over here. Then we're going to slack. Our payment method from these three payment methods which are very common in my country, is a pesa ubl omni and be at your doorstep, which is the most common. I placed it at the bottom so user can tap it with his heart fingers easily it is reachable . It is accessible. If you want to learn more about usability, accessibility, user behavior and how psychology effects that you experience, there is a separate course from me, which is on user experience. Principal models and behaviors use their behaviors anyhow, so we're going to go to confirm mortars, tanks and confirm order Text. You will receive SMS on your number, this one. And now we're going to go back to home and we have another functionality. So this is a T prototype, Okay, so we have to function. It is over here in depth. We have searched now, and you can see we have such over here we have different popular searches, which are suggestions, and we're going toe bake one off them, which is Barbie dress. And there are different results showing about this case of we didn't go in depth with the result filters because this is another page. This is another topic. Or you can say I didn't have time for that one. So this is a such functionality. We can lured more reserves we have add to cart. We have different color options available over here. We have price entitled. So this is all about how you can create prototype and test it with users. So might be user might be looking for fabric type over here. So once they go to this filter results we have placed over here, we can add, like Corton fabric or something like that. Or maybe we can add over here that it is she foon, or this is the material off the cloth or things like that. You can vary it in summers or maybe things like that. So filters will be separate, which I didn't have time to create. Anyhow, this is a prototype I created. I hope you love this lecture off prototyping and how I actually created this prototype. You can build it using principle on. There's another airport, Opie. I'm planning to create another course on just this separate fighting. And I hope to see you soon in that one too. Anyhow, so this is all about prototyping and user experience design. If you have any questions to ask me, let's move one to the next lesson. 42. UX Design deliverable: no. In the last, I'm going to talk about the detailed specs and what are detailed specifications off or your system, your app, your website or web. Now detailed specifications are sometimes necessary, venue or whatever you are designing. For example, if you are designing on airline software, which is going to be installed on airplanes and you can see that airplane are aviation technology, which is very you can say detail, and you have to get each and every step and details because it is about the safety. It is a critical app because your app can make a plane crash and hundreds of people are going to lose their lives. So you're dis user experience. Design process will be very elaborate. You are going toe, have very detailed specifications. You are going to generate tasks and functionality off each airport, the whole interaction, everything in detail. Your Jews expense design process might take a whole year, a 12 months or maybe more than that, to develop that design specifications and develop that actual AB. Now here we are going to work with your developer and development team to create all these specs because sometimes there is miscommunication between designers as you experience designers and developers, so try to communicate with them. Normally in all other designs, mostly which are not, you can say very critical apse where we have, ah, life saving or life threatening APS. Things like that. We have mostly specks, which are going to have high fidelity more cups, which are original designs. We will have wire frames. We will have interactive prototypes to show that we will have task and Wendy diagram, site maps and user flows. So these are actually the major diagrams of things. Maybe your system model, the whole the whole system model horse. It is a ho. It is going to work things like that. Maybe you use cases, but I normally don't use use guesses in most of the time, and on the business side, you might have visibility or reports or your limitations or cost or things like that. Maybe a strategy or plan off having different features at different times. Things like that. These are different things you are going to generate in your expense design process at the end. Now let's see why. Actually we are going toe deliver these detailed specs and in what are the aspects we are going to cover in our specs Now, this is actually very important. You have toe, you know, create an image off this one into your minds into your tiny, teeny or large brains. Anyhow, so we have functionality and features. So functionality and features is actually what is this system capable off? So what is this system can do? So these are actually the features. For example, we are just launching 10 features or five features in our first leads off our app. Then next we have flew off F. We have navigational part. We have information architecture that is going to cover this section. We have guards sorting. We have ah user floors. We have site maps that are going to cover. Then we have interactivity. We I have already showed you Ah, prototype, which was steeper that I've We're going to show our developers rather than telling them in a long, detailed document that this is how it should work. This is how user is going to get. Our message is this is how users going toe logging. So these are interactive prototypes were going toe have. Then we are going to develop site map, which is also going to show the boundary over app or website that this is the the broad spectrum image off your whole pages and sub pages. These are actually the pages that are going to be produced by a Web developer. Then we have detailed via frame. So we also want to make sure the content and how that content has been organized on each page. How the product page is showing the details off your product or justice. What is present over there? The colors the size is the size guide. Oh, are we have fabric type? These things are easily viewable or easily, you can say readable for years. Users does that those makes sense that does the user really need this content detail? We're going to check all that messaging and details of your content in vire frames. So that is all about the tail specs and what should be in your detailed specs and what we should be in your deliverables when you are ending as user experience design process and you are delivering your documents and whatever research or things you have created to your design and development team, mostly you are going to work together with them. You are not going to just deliver them the documents and go home and sleep and just a work they're going to do. You are going to collaborate them on a daily basis. You are going to go to them and see the progress on each step. Show me what you have done right now. No, this is not the user won't see this and document over there. The user interview we did for the first user. This is the requirement record you are making. You're not making the right sense or right use off that. So this is actually going to happen because before implementation or according you are going, you have more time and you can easily save cost if you try to, you know, interfere in that. So try toe, collaborate with your developers. Your design team. You are a user experience designer. You might have some design experience, so you will be working closely with developers. So that is all. You are also going to include your CEO because they also have ah a lot on marketing team because they have a lot of more insight into customers and their purchasing behavior. Eso that is all. If you have any questions to ask me, let's move on to the next lesson. 43. UX Designer + Development stage: now. In the last session, we were designing wire frames for our frog land Ikuma store. And now is the time that we are moving to the development fees. Now, in the design, we had prototypes. We had wire frames which were the bread and butter and end result off our hold User experience, design research and holders Expense design documentations. Now, in this session, we are actually moving to development phase and there are few things I want. O, make sure that you understand that on your development side there will be a lot off decisions based on speed off response off some system or spot starter time off any website or servers Or maybe some limitations are different frameworks. So you are going to as a you a designer ux designer. You are going to work closely with the development department or the developers. So in my case off Rocklin, we I had two options like going with the vert press, which is ah, along with e commerce or vou commerce, which is a plug in. And we can also go with Shopify, which is another solution for e commerce stores. So Shopify is good for you can say novice users or beginners. So I might, you know, went towards that. It is also a big, fast than vou Commerz who promises a plug in. So it might be a little bit and option off performance anyhow, before going into full production and, you know, building a whole website. We are going to build a dummy website Dominions that we will have everything like we had in our fire frames. But we will have, like, 15 or 20 or just 30 Dominion products data. It is very easy these days. A lot off these frameworks thes online solutions, e commerce solutions. They let you export or import data and lorded the dummy data into your store, so just repressed it out. So on my BC, I have some development background, a bit off development background. So I installed a local serval and I am using a fill it with some sample data, and I'm using WordPress withdrew commers. This is a plug in WordPress plus rue. Commerce is a plug in solution for e commerce websites. So this is actually ah will save you a lot of times of why I actually don't did this. And your developers might also do that because before you know, going into more details and ah, you know, configuring the whole website or uploading like 1000 on may be 500 off different actual images of products you need to test it. You need to test run it with few users. You need to do some juice ability tests. So that is why we are going to work with our developers to come up with a solution that is , you can say, a Demi solution, having some dummy data with just few products just to see how actually we have reached toe our level off user satisfaction. So that is all I wanted to show you. I'm going to show, you know, the example. We're actually I am right now testing. So let's see that now you can see this looks very empty, but we have most off our bits and pieces together, like you can see here we have a logo and the tagline, Then we have the location than we have. What's app number than we have email than we have. Few search of social links we don't have right now is a big such bottle. Hair, maybe, of we want our developers to, you know, change it, Albert, you can see every time you use. This is a free WordPress team I'm using. This is a free team, so these are actually the functionalities. We have very good card than we have sharp dresses. These are dumb, different categories we discussed and we are also going toe make them into, ah, two different menus or here this will be down and one will be above then we have sales and deals stuff. I've haven't configured everything. Then we have featured categories like singles or clothings or whatever. 50% off. Still, some off the data is missing, but this is actually going to work for us to we testing have with our users, you can see there are few featured products. Then we have something from our blogger and news than we have the footage. We have free shipping and done. We also need to post this at the top in the header section. Free shipping and return. Also moneybag Randy and 27 47 support something like that. We already have our full number, everything up there. This is our address and things like that. So this will be our starting point for our development. We are not going to go into full fledged and developed website or developed app. I have worked previously with a software firm in Ah UK United Kingdom and there was a guy I used to work with. He was a project manager and they choose to develop few mobile games, mobile app, games and ah, what they had. Actually, whenever I designed a new wire frame or you can say user experience solution for them, they had, ah, game engine ready for prototyping. So actually, what they did, they had, like just in this case, I had vocal Mazar e commerce and I just use the dummy that are similarly They had a whole set off dummy game built already built behind the scenes and just they use that engine and attach it to the You can say the interface. That is also it was very quick development. They were using age I ux in there software house or software firm or agency, whatever you call them. I think I still remember that guy. He was a great project manager and ah, I'm just telling you the story that most of the software houses, most off the intelligent and voice developers or quarters. They have their major engines or major models already built, and J just put together just through in the interferes Jane bits and pieces over there, and it starts working. This is actually a new era off using models based you can say a jail UX or a jail mattered off developing something that you use different blocks and juice combined them and create a full product. So in this case, you are going to work closely with your development team and you are going to tell them that we need these two, ah, things separated and we want to show these show these categories. We don't want them to hide in the drop down because it will not be visible to the users. So we really want toe want our users toe, actually see them see these categories and slack them rather than, you know, having a drop down. Also, we can move this my account and blawg and context contact us at the top Now, Right now, in this course, I cannot develop full fledged website right now. We will use this Thomas I to perform few user testing usability tests in the next few lessons. And I'm going to share the results with one or two users because I don't have, like five or 10 users right now. So I will do with one or two users. You can do it with at least 3 to 5 users. So I hope you have understood my idea that you need to work closely and how you will rapidly develop your app or website. If you have any questions and to ask me, let's move on to the next lesson. 44. Four types of Usability tests: usability tests are essential in any stage off your development or your design, or even is in a user investigation or user interviews. So once you have prototypes built for your product or you have a completed version of your product, you are ready to test it with your actual users. That is actually the usability tests we're going to see. What are the pain points? What are the frustrations that still are residing in our product and we're going toe ICT it and remove it. Most of the things we have done so far are already aligned with the users, and it's his knees or hard needs. So right now we are actually testing whether we have met those needs. We are going to validate our assumptions that we have made a usable of user friendly product or not. So there are many things. There are many terms. There are many details in usability tests. I'm not going to go into too much stepped, but I'm going to stick with just four types off test that are essential for improving the usability off any product, and you can do them at home. So don't worry that you need to you know, go to some lab to do these disability tests. Now, the first test you are goingto do with your product with your app with your website is first impression test. The first impression test is actually also called five second test and it is very popular. This is going to be your first test. You need to see what your users first impressions and parts about your product. What do they think about it? Do the trusted Do they want to buy it? Do they want to use it? What is your message? Whether they are understanding your websites message or your abs message accurately or not eso these kind of things we are going to, you know, such in these first impression test. So you are going to show your users your website for 1st 5 seconds and then hide it and ask them questions like, What is this website about? What are you going to do things like that? So you need to get the initial ideas off your users about your product or your website. Now walk around or exploration test is. Actually you are going to let your users browse your app. Try toe see what are their impressions when they try to struggle with something when they try to browse different products. In my frog land website, for example, when they try to apply some filters when they try to do is to different filters and different product details, I want to see their impressions. What are the thinking about it? What are the impressions? So don't let you know. Explore them for, like one hour. Just give them five or 10 minutes toe, get familiar with the product or app and see their expression. Record them if you can. That is the best thing. So these are really nice. You might catch few problems on during these exploration dusts. Now this is the most essential step or test in your usability desk, which is essential tasks. Thus, you are going to plan for different tasks that are essential to your each user persona. For example, each user is going to create a new account. Then we have logging than we have jackal process than we have filtering products than we have removing products from your card and adding them back shopping card check out. So we are going to test these five or six essential tasks with like 3 to 5 years is to see what we have achieved. And we're going to compare our results with benchmarking them with other websites with other popular solutions and other popular E comma stores. Now, in the end, after you have conducted your usability tests, in the end, you're going to give your users some question here and surveys that How did you feel using this product? What would you expectations and, ah, how well do you think you are going to read from 1 to 10 about this product? And we're actually asking them You can say qualitative data, which is, ah, usability technique, qualitative and quantitative. Quantitative is we are maturing different, like clicks or times and things like that and quantitative. Sorry, Qualitative is that we are actually checking the satisfaction and emotional Lewis boss off always uses. What is the product quality, how satisfied our users are, How are the feeling after using their our product? So we're going to get the overall emotional satisfaction and user satisfaction. Why are these? Question is so. I hope you have understood this lesson. We're going to see these in detail in the next lessons and I'm also going to give you downloadable resource is don't forget it and download them, so let's move on to the next lesson. 45. 5-seconds to test First Impressions: in this video, we're going to cover what is actually five second test and how we're going to conduct it. And what are the questions we're going to ask our users during after this test? So via actually we do it. We have to test What is the initial impact off our website on our app on users? What are their perceptions about our product? How, actually they are going to perceive it, whether it's just for the or valuable or not human mind, actually, take ST five seconds toe, make up their mind about a product, whether it's bad, are cool or is it cheap or valuable things like that? So we are going to take 3 to 5 users and we're going to show them our product or our website or app for five seconds, and then we have been go hide it, and then we're going to ask a few questions about our product. So this is how actually we conduct five second test. Let's talk about the questions you are going toe. Ask them after you showed them your website or product for the 1st 5 seconds. What is this product or website about? So this is the first question. What do you think this is? Second is what do you think you can do with it? Why are you here? And third is what are your emotional feelings about it? Was it fun, Mother? Serious? Was it professional and things like that? Then we have trust, trust, ability, test how trustworthy this website or this app looks to you. This is very important. Second, as we are going to see how much they remember about our product, whether they saw it for the 1st 5 second, whether it is memorable or not. So we're going to ask them. Can you tell me the name off you off the product you see on a few more questions like how would you describe this to your friend or your user about this problem? If you want to tell that you have seen this website or product, what would you say? How would you explain it with us? And a few more things you can ask is that What are the first steps you are going to take of what is the first step you're going to take on this website? So these are all the questions you can ask. I'm going to give you a download. Downloadable resource. So don't let all these questions seven or eight questions and you can start from there. Now, why do we do our five second test and what are different facts about it? Now, here is the thing. If you are if yours user is using your website and for the first few seconds they are unable to tell what is the message off your website of what it actually does? You are going to lose your business. They are going to go to a computer. So this is actually very you can see essential for you to test most start ups and Kickstarter projects. And I have seen a lot of APS and things like that websites landing pages that suffer from this. They have a very attractive message like solve your pain and that is all, and then the product. So I don't I have a lot of pains which being actually it is solving, whether it's my muscle pain or any, you can say psychological pain or whatever, actually, so this is very confusing. You have to be clear about your message. Let me show you a few examples. One for the bed, one which is Ah, five second just feel. And one is a great website that shows their message clearly. So here is an example. Off a field five second test and you can see over here. This is submitted by my student Daschle. Coffee from my course trucks designed for big nose. Too expensive bills, concept and models. Now you can see over here we have ah, farm over here on this page. We cared one hour off our recruitment ambassador recorder to you shortly. And the user confused about why and what is happening on this page. And why should I give my personal email and name and phone number toe over here? So this is what, actually my student road that I don't don't don't know. Why should I submit my personal data? There is no tag line. There is no clear message that why should I use this product? Why should I give my subscriber give my email address over here? So this is an example of a Field five second test? We do not know what the product is. We don't know what is their message? What? Actually, I can do over here. Now here is an example Off a great message or five second test, which is going to be this crafted website. You can see we're here within few for three seconds. I can guess that this is a digital marketing agency and this is a professional complaint. We have all blew over here, and ah, in the 1st 5 seconds, you can always ask me what actually you saw. I would say the product name was crafted or from name was captured. And they are additional marketing agency. So this is a create example Off successful five second desk. This website is going to pass it with great colors. I will give it five stars. So this is how actually you do it. You have to have a clear message. Ah, clear tagline. A clear a memorable product, name or service you are offering. So that is all about five. Second test. If you have any questions to ask me, let's move on to the next lesson. 46. Project β†’ Conduct a 5-seconds test: Now you have learned about five second test a first impression test. This is very important, and I want to give you a task or assignment or a project to complete this five second test . What you were going to do is take one user, your grandma, your mother or brother. Anyone, show them a service or website or an app and show them for five seconds and then ask them the questions I have shown you in the template. You can download that template from my resource is off the schools and ask them those questions and show being your findings. What is the most surprising thing you have found while doing this First impressions or five second? Just so that is all. I'm looking forward to seeing your five second test reserves start doing it right now. 47. Essential Tasks Test- Usability Tests: Now let's talk about essential tasks. Test now. This is actually the cream off your disability test because it is actually the main based off usability tests. This is the main test you're going to do with your app, your website. And as the name suggests, you are goingto list out all the different essential tasks your users are going to perform on your website or your app on daily basis or again and again. In my case, which is fraught Landy Coma Store. My users are going to mostly do Logan sign up, check out browsing products, finishing products, finding products, adding them to the cart, removing them from the card, moving them to the fresh fish list and moving them back from the vicious toe. The card. Things like that. So I'm going to list out all essential tasks, and I'm going to plan out different tasks scenarios and build them toe followers users to perform. And we are going to test all these tasks based on some metric we're going to see in the next slide. So let's see what that is now. In any usability test, there are two ways to do it. One is that for example, I have already a product already of upside which I want to improve. And I have found few problems that I think that this is my problem statement that I believe that users are not taking an action on the spit. This is in case off my frog and website because the major categories are hidden. Now I'm going to show the screen after this, so this will make more sense to you. Users will navigate easily if we make sub categories toe categories. So we are going to move sub categories and show them visibly on our main categories in our navigation bar. This is my hypothesis that this is how it will solve this problem. Now, metrics are what are actually the bank marking things were going to use to test these, for example, number of clicks or time to look it item. These are the things that are going to decide that I was right or it actually has improved . Now. This is my frog plan. If you remember in the previous lesson, we had one main category shop over here and all these categories party dresses schedule. They were inside that shop and now My hypothesis is that if I move them outside, like, over here and made the major categories rather than sub categories, it will help user to locate them. And it will increase our you can say revenue or clicks. So we are going toe just it with our metric, which is time to look it. This is very essential. And I will write some task scenario that, um, you want something for your summer vacations? What would you Where would you go to find that dress? So if the user goes toe or hair summer and summer collection that is going toe, tell me if it takes, like, five seconds to them, I'm going to make sure that this is create we are improving. But in the previous design, actually, we're going to test two versions off this design. One is the previous one, which is called a B testing. So we're going toe test two versions, different versions off the same men page and see which one performs better, and we will decide that this is actually helping them. They are able to get to that within two seconds. This is great. Now we're going to write our task details in a scenario for made a short story, we're not going to say them that try to click on this, go to check out and things like that. We are not going to give them any hints and labels. Any navigational items, names. I am amusing. For example, in case off my website, let me show you. For example, we have someone winter collection, party dresses, casual Princess Barbie and things like that. So I I'm not going to use a check out or things like that. I might use that. What would you do once you have added your items to your card? How would you go forward from? There are things like that. I'm not going to give them a hint off like try to check out using my website. This is not your visibility test. This is a direction. You are giving them the whole thing. You are not going to give them any hints. Here is an example off writing a tasks and four years usability desk. In case off my front line here, I'm going to give you something like this. You clicked on a Facebook ad for a kid's clothing website and reached this page to buy. Ah, dress for your daughter. What is the first thing you would do? I would like to see whether they're going to create a new count or they are going to start adding dresses to their car, things like that. Now, there is another technique that you lied your user from one task to another. So I start with one toss, which was previous fund. I am going to give them a new task Now the next asked. No. You want to get a perfect dress for your little girl for her birthday party by tomorrow. What steps would you take now? Can you show us things like that? Then after that, once she has added a few dresses to other card I'm going toe. Say, what would you do next to get those dresses at your doorstep? I am not using keyword. Check out. So if you see my website right hair, you can see I have used check out over here. So I am not using this keyboard. I'm not going giving them hints that try to check out from here. So I would like to see how they actually approach it, whether they click this A guard were here first or better the click on this Check out things like that. There are few things you need to do while you are conducting your usability test. The first thing is that keep quite. Don't give yours, user. You can say hints and don't grind them. Just keep quiet. This is the most difficult thing I find. I found out that this is most difficult for me because I talk a lot. Eso You have to keep quiet. You have toe, not answer their cook Yuri's. You just keep them asking. What do you expect it to do? What do you think it does? You are going to answer their questions with another question. One more tip is there. Try to rehearse with your friend or team member before conducting any issues. Ability test Because in the first few minutes you are also going toe. Tell them that this is the product introduced them to that. Tell them a little bit about it and tell them that you were were going to give you some tasks and we're not testing you. But we're testing this product, how good it is and how bad it is. So do whatever you do freely. Don't try toe. Think that would be We are testing. You were just testing this product. So just to build up some confidence with your user and get familiar with them one take me Courting allowed technique as you are going to ask your users toe keep thinking with their mouth. So they are going toe Say all the worst they're thinking in their head And you're going to record that video and audio and also write down some north if you find something and this is actually going to help you Ah, lot, let me show you what? Actually, this thing allowed technique is now you can see that I'm user and I have given a task toe. Go and find some summer collection. Our summer clothes are clothes for your heart whether I am also excluding somewhere over here anyhow, so I would say something like that. Okay, so I need ah dress for ah, hot weather. I would go and summer summer collection. Okay, so I have found it. I'm going to click over here, and these are few dresses, Aiken. See? So this is actually think aloud technique. Yours user is going to say whatever they have in. They have been thinking all along while performing these tasks. If you use a stop somewhere you have tow. Tell them that I want you to think aloud. Tell me, what are you thinking? So asked them like that. Now what we will get from thes usability tests, we are going to know down all the pain points or all the major frustrations of problems over users actually faced. And we're going to list them out. We're going to give them suggestions over developers and designers that this is how this problem can be tackled. This is how this problem can be solved. And we're also going to list that What is the time taken? What were the number of errors? Whether the user completed successfully or not. So things like that I'm going to show you template off a form user announced this form you can use while doing these usability tests. Make sure you download it now. This is a very simple form. We have name off of a user. We have prototype number. Whichever prototype whether it waas Ah, check out prototype or whatever we had than the screen name. What? Which screen they were on, whether they were on log in screen, sign up screen, last detail. What does they were performing us to complete? I had addressed to their card or whatever. What is the time Taken? Eight minutes, whether they complete it or not, yes or no completed possible pain points No or yes. And we are going to write some north. So here that this is the pain point they had. You can also write. Add another column and give them suggestions that this is how it can be solved. So this is actually the listing off all your pain points and using different pass on different users. So I suggest that do it with at least 3 to 5 users. This is a sweet sport, and I hope you have enjoyed this lesson and understood what is actually usability tests and how we perform them. So let's move on to the next lesson and see what we have ahead 48. Project β†’ Conduct a Usability Test: Now you have learned about essential task test and hard to conduct as usability test for your major tasks that are going to be performed by every user daily on daily basis or a lot . Now it is. You're done toe. Create a usability deaths like this one just right. One description off one dusk for the user. I want to see how you're going to write that description. Guide the user, set up some environment that this is You are a busy mom. You are in a hurry. And you want this stuff or something like that. Don't give them any hints, Okay? So create that user task description for their death test. And do that. Do that test on values that can your friends or family, Your father, mother, grandma, anyone. And show me your findings along with the task you have given them. So I want to see that task you have written in text form it. And also, if you have any findings, are amazing findings about them. You can show that to me as well. So I'm looking forward to seeing your essential task or usability task test. Ah, start doing it right now. 49. Exploration tests: Now, the second test we're going to do is exploration test. Now, this is very simple. We are going to leave our user on the front page of the first screen off our app and let them explore the app, the website, and were wild did do that. We're going to record their screen their emotions and see actually what actually they are doing on our screen or the website. Now I'm going to give you a very useful tape here if you use user asks you what this but Button does never answer this question. Instead, answer this question with another question, which is What do you think it should do? So this is going to help you become a better usability tester or visibility analysis sky. So this is actually very important of why I actually we're doing exploration tests. We are actually testing the menus. Is mental model. We're going to see which parts are off our product are most attracted to our users. What are the first steps they're going to take, whether they're going to click on subscription or whether they they are going to go with the downloading A PdF or they're going to contact us or things like that. What are the first things they are going to look at? Whether they're looking for some return policy or things like that. So this is actually first time usage exploration test. We're going toe test our users that what are the things that they are testing or checking on our websites? Second, most important thing is their emotional response, whether they were showing in trust in our product, but that they were they. If you feel that they were ease at ease during exploration, they were not frustrated. So that is all about exploration tests. If you have any questions to ask me, let's move on to the next lesson. 50. User Surveys and Questionnaire: no. Once you have completed a usability test videos users, you are goingto get their emotional feeling about your product. You are going to get what, actually, their overall tarts after using their product. So we are going to use juices surveys and we're going toe. Give them to others users after they have completed usability tests, and it will have, like 2 to 5 questions, or maybe six or seven no more than 10. I suggest that it will be easier for the users to give feedback on after using your website or your app. Now there are many only tools you can use, like surveymonkey or tie form toe. Create these surveys all you can give them a print out in their hands and take on that. So if you are using some online tools, you can give them some incentive, like we're going to give you 50% discount, 10% discount on your next purchase of things like they're just a little incentive or incentive. Our reward for filling out that survey form now you might have build a lot off different surveys. I'm going to give you a few surveys data lady toe visibility test on digital products. One of them is used. Question here. Now this use questionnaire. It is going to test four different things useful, less easy fuse is off learning and overall satisfaction off your user. So I'm also going to show you one example that you can go ahead and see what are the questions you can add from that section. Toe your app according to your needs. How much easier for your users to learn it? How much easier for the user to use it, How useful it is, whether it meets the need off your users or not. How much satisfied watches user? Maybe from 1 to 10? Maybe he was. She was satisfied. 50% or things like that here is used questionnaire from Gary, gary pullman dot com, And you can see over here here we have different questions that are related toe usefulness . It helps me to be more fact. It helps me to boom be more prepared, protective, productive. It is useful. It gives me more control over the activities in my life. These questions will be different based on a little bit different based on your product, so you can see we have strongly disagree strongly agree and no answer. Then we have ease off use. It is easy to use. It is simple to use. You can picked, been picked one off them, for example. I would say it is user friendly. So maybe Ah, it is simple to use this. This makes more sense to me. So my users might say, like, four or things like that. Then we have ease off learning. I learned to use it quickly. It is easy to learn to use it. I quickly become skillful with their things like that. Satisfaction. It is fun to use. I'm satisfied with it and things like that. So you can see this is actually a question and I'm going to give you the link. You can use that and you can have few more things like Ned Negative expects a positive aspects off. Whatever you have yours, users have found in your app. So that is all about use question here. I hope you will use it in your usability test after that. So let's see what we have more. Now let's talk about another kind of question here that is going to test the emotional impact off your product on the on your user so it might have questions like whether the product was delightful or not. Was a product unique or ordinary? Was interesting or boring? Was visually attractive? Was the product we are confusing? Was it trustworthy or shady? Was that simple or complex? So these are different questions we're going to ask in a attractive questionnaire or survey . You might have seen it in a lot off Alia's, where whenever you talk to any customer satisfaction or so customer support a guy after completing your customer support call, you have ah, survey to fill. And that is mostly about the emotional impact that was you. What you satisfied with the user or whether you were happy about your interaction with him . Things like that was a problem solver North. So that is a bish, basically the overall satisfaction or see warriors, frustrated or not, anything you want to say about it. Now you can see on the right. We have a form from customer thermometer on, and you can see over here we have one star smiley face, Ah, frowny face and a sad face, a serious face and a sad, sad face. So this is actually checking the emotional impact from customer support or things like that that you that actually liked it. He was happy. He was frustrated. So this is actually, you can say emotional testing off your user. One more thing is whatever question or surveil you use, always give your user our space to write freely. You can also give them scales like one pretend rating or things like that. You are also going to give them a text area where they can use that and, um, right freely over there. This will help you. If they have something or some suggestion in there, might they might write it over there. So I'm going to show you a few off the forms are surveys I actually used to improve my courses. Let me show you which tool I use and how I do it here. You can see this is type form and I have 12345678 different surveys and these are 95 responses for this one. So let's open this one, and I'm going to show you how you can make one for free and post it to your users. So you can see you were here. Here is my title image for Do you want to learn next two minute quiz. Always mention how much long it is because users are going to get boring or maybe they leave it. And then this is the next question type You're on so ahead and I have some things to select from here. Then I have another question. Then I have the last one, which is what are your comments or ideas? So this is Ah, text field I'm talking about. So once they have completed it, you will get some results over here. Uh, let me show you. But you can see here are all the reserves. And here we have this question which goes courses you want me to teach you next. And here are different responses and this is how actually makes 20.9%. And you can use this kind of thing to get this, create a question here and get the satisfaction or reserves from your product or whatever you have. So this these are different commands. You can see you were here, so this is a great tool type form. You can also use surveymonkey And you can also use heart chart If you have ah, current website. I have used this heart heart jar and it is going toe give pop up over here does a lot of things, but it actually give feedback over here like you can see what here happy and things like that. So this is actually it is going to test the emotional impact and also give the user our tax field to fill. Okay, so this is Ah, great tool if you want to use it properly. And I would always go for type form. I haven't used this surveymonkey, which is another popular tool. I know. And I have seen a lot off cos they use it. So these are different tools toe create surveys and get some feedback from your users. I hope you have enjoyed this lesson. Let's move on to the next lesson 51. The end review and thanks: thanks a lot for staying with me during this whole learning process. And congratulations are completing this user experience design process. Simply fight course. That was not very simple, but I think it is the basics. Eso you have learned something valuable. You have like the score. So if you have loved the scores, try to write some commence or ah, nice review about them because I normally live on reviews. Okay, so I am waiting to see your commence about the schools. If you have any suggestions are you want some improvements in the schools? You can always ask me. You can write me privately. You can go to my website learned you excited or calm and you can contact me from there. So I'm looking forward to seeing you soon. In an other course, don't forget to write a review and thank you all. And congratulations on completing their schools till then. Ticket And by