UX Fundamentals and Project Brief PDF
Document Details
Uploaded by EffectualNashville
MTI University
Hussein Gaber
Tags
Summary
This document provides an overview of UX fundamentals, including the importance of understanding user needs and the iterative process in design. It also outlines a project brief, highlighting the necessary aspects for a successful project, like defining problems and collecting requirements. The information focuses on how to tackle design problems and outlines important considerations and steps to take in the design process.
Full Transcript
Practical UX Camp Today’s Topic UX Fundamentals and Project Brief Hussein Gaber Head of design 12 ايه هو ال User Experience هو كل حاجة محتاج اعرفها او افكر فيها او اعملها علشان اعمل منتج مناسب ألحتياجات الن...
Practical UX Camp Today’s Topic UX Fundamentals and Project Brief Hussein Gaber Head of design 12 ايه هو ال User Experience هو كل حاجة محتاج اعرفها او افكر فيها او اعملها علشان اعمل منتج مناسب ألحتياجات الناس اللي هتستخدمه Wearables UX matters because access to your competitor is only ever a tap or two away... Technical Great user experiences Theory, Concept يعني ايه تجربة مستخدم ممتازة Useful (Achieve goal) Desirable Usable (Easily perform tasks to goal) Desirable (Enjoy performing) Usable Useful 34 Technical Examples, 3 Products that deliver great Case studies Experiences 35 User's ROI A useful product that addresses their actual needs. A less frustrating experience that supports their natural approach to accomplishing their goals. Increased efficiency & effectiveness by optimizing the product for their specific technical, cognitive & physical abilities. Before we get started.. UX designer Characteristics بيعرف يسمع كويس جدا ً بيحاول يفهم املشكلة كويس جدا ً ويحلل اللي سمعه علشان يفهمه بيكون ملّاح لكل كلمة بتتقال بيجاوب السؤال قبل ما يتسأل بدور علي اكتر من حل ويوضح بيحط نفسه مكان العميل او الفرق بينهم املستخدم علشان يفهمه كويس بيحب يعرف ايه الغلط علشان يتعلم بيكتب التاسكات بشكل واضح مش علشان يدافع /يبرر 55 Understand The Problem Space Theory, Concept يفهم ايه املشكلة اللي بنحلها و ملني؟ 57 Let’s get started Definitions Product 📱🖥 Users 👥 Stakeholders 45 Problem Space 🔮 66 Define the problem Theory, Concept Shared understanding of the problem 5 👥 Users 😓Needs 4 Stakeholder Stakeholder 5 4 Stakeholder 4 Stakeholder 5 Stakeholder Stakeholder 72 Space/Domain Define the problem Theory, Concept Shared understanding of the problem 1. The problem space. Are you solving the right problem? For the right audience? 73 Examples, Case studies https://ifworlddesignguide.com/entry/163157-easy-open-cans Examples, Defining the real problem Case studies Problem Correction is taking action to correct a problem Corrective action is action taken to correct the cause of the problem and preventing it from happening again. https://strategies4enviro.com/2014/correction-vs-corrective-action/ Define the problem Theory, Concept Shared understanding of the problem 👥 😓 79 🤔 If the problem is industrywide, it’s crucial to understand why the market has failed to address it. Define the problem Theory, Concept Shared understanding of the problem 2. The product's stakeholders. What assumptions do they have around your product? What will your stakeholders consider success? 80 Theory, Concept ايه املشكلة اللي بنحلها و ملني؟ 81 Define the problem Theory, Concept Shared understanding of the problem 3. The product's users. What are their core needs in this space? What question they’re gonna be asking? What tasks they want to complete? What will your users consider success? 82 Define the problem Theory, Concept Shared understanding of the problem 1. The problem space. Are you solving the right problem? 🔮 For the right audience? 2. The product's stakeholders. What assumptions do they have around your product? 45 What will your stakeholders consider success? 3. The product's users. What are your users' core needs in this space? 👥 86 What will your users consider success? Best Practices Best Practices Common Pitfalls Don’t 🚫 Do ✅ Introducing implementation ideas at this Avoid the temptation to favor a particular early stage. Solution or approach. Finding creative possible solutions. Defining the problem. Trying to gather all research upfront. Answer what is needed when you need it. Failure to understand business requirements Asking the right questions. Failure to identify risky assumptions Know what’s known and unknown. 87 Don’t forget! Become better at asking the right questions to tackle the right problems. Know more of what’s known and what’s Unknown After all, you’re still defining the problem not trying to find solutions. Best Practices Links Useful Resources Defining The Problem Space Defining audiences and their goals Are You Solving the Right Problem? Thinking about users' relationship to your product with the Jobs-to-be-done framework 94 Intro to UX Fundamentals ليه المفاهيم مهمة ؟ كل حاجة ليها قواعد علشان تتعمل صح مش بتتحفظ ملجرد الحفظ.. Everything is controlled by rules. افهمها علشان تساعدك.. منا بعرف اعملها وخالص 96 Focus on the user Design for them, not you. Understand their needs, motivations and constraints. Put them at the center of your decision making. Reward their engagement and earn their trust. User Experience Fundamentals Solve real problem Solve real problems for real users. Be ambitious and innovative in your choice of product area and approach. Look around you and think about how the application of technology could change things for the better. Strive for simplicity Make sure your proposition and benefits are clear and understood by your users. Prioritize what is best for your users and work hard to remove roadblocks from their path. Reverse Engineering الهندسة العكسية A deconstruction process to reveal object’s designs, architecture or to extract knowledge from the object. 106 Do Research Understand the product space and what the competition strengths and weaknesses points. Test your assumptions with your users – if you’re resource-constrained even just friends and relatives is better than no one. Hypothesis فرضية — فتراض (noun) A tentative assumption made to draw out and test its logical or empirical consequences. 108 Adapt, Adapt, Adapt Your product is never “DONE.” —Based on research, user feedback and market changes Adapt your plans based on what you learn. The more frequently you course-correct, the better your product will be. Iterative Process Move from doubt to better- informed iteratively. 111 “It’s not iterative if you only do it once.” Stu Eccles Chief Product Officer, Percolate 112 Technical Iterative Process Discovery Design Testing Discovery Design Testing Understanding the problem, Visualize assumptions using The earliest we can test our targeted users and low to hi-fidelity covering all assumptions, the faster we competitions landscape. cases with accurate content. can iterate accordingly. 7 UX Fundamentals 1. Focus on the user 2. Solve real problem 3. Strive for simplicity 4. Do Research 5. Adapt, Adapt, Adapt Let’s recap together UX VS. UI 115 Let’s recap together Today you could answer some interview questions: 1. Tell us about yourself.. 2. What is UX design? 3. Your favorite examples of good UX? 4. What is the difference between UX and UI? 5. Walk me through your workflow.. 6. How do you respond to negative feedback? 117 Getting Project Brief Define the problem Theory, Concept Collecting Requirements 119 Let’s recap together Theory, Concept How to Start tomorrow Simple From Scratch Call New Know more about the project, Feature target users and client maturity. zoom.us Redesign Product input template.. 120 Let’s recap Before the meeting: ✦ ✅ Connect the charger. ✦ ( Don’t disturb mode. zoom.us ✦ ' Close un-related tabs/apps. ✦ + Set expectations. ✦ ) Summary before details. ✦MOM 121 ✦ * Ask before assume. Define the problem Questions in Client interviews 1. The scope of the project. —What? 2. Goals and objectives of this project –Why? 3. Targeted Users? —Who’s it for? 4. Timeframe and deadlines —When? 5. The Budget “If Possible” — How much? 6. What success can user experience deliver? www.tremoloo.com +20 127 465 2104 Let’s recap together How to Start tomorrow INTRODUCTORY MEETING Date: February 11, 2020 Project: Sea safari Attendees 1. Nasser Al qamlas - Sea-Safari Booking 2. Hussein Gaber - Tremoloo Call Questions 3. Ahmed Aboul Ela - Tremoloo Agenda—Closing comments. - Mutual introduction - Discussing the current user journey - Understanding the needs for the app - Discussing the next steps. Scope of the collaboration: Agenda The app should take into account the following user needs: MOM 1. Exploring service providers Summary 2. Scheduling 3. Forecast info 4. Booking 5. Payment Action items 1. Tremoloo will send 1. Portofolio (Presentation) 2. Financial proposal by 17th Monday Insha'Allah 123 1/1 Let’s recap together How to Estimation your time 1. Understand What's Required. Small Medium Large 2. Break the scope into modules and headlines 3. T-shirt size each headlines. 4. Break down larger tasks into detailed tasks. 5. Estimate the time needed to complete each one. 124 Please always Remember: Focus on the user You ≠ User Listen to learn & Adapt 125 What is ideation? ) راكفألا ةذه نم يا ىلع. the process of generating new ideas for a specific topic, with no attempt to judge or evaluate Ideation 06 Ideation In The Real World 00 Brainstorm in silence. 01 Brainstorm out loud 02 Document all Ideas 03 Focus on Quantity 04 Do not allow evalluation 04 Gather a diverse team 05 Evaluate the ideas Ideation 16 Evaluation Ideas 01 Technically possible to build 02 Best at solving the user problem 03 Financially beneficial for the business Ideation 16 PROBLEM Olivia is a parent who needs a way to ride her bike with her 2- year old Luca because he can’t ride his own bike. Ideation 06 Ideation 06 Why should we come up with a lot of ideas Because Ideas are narrowed based on constraints. Ideation 16 Ideation techniques Ideation Techniques HMW Ideation 18 How to generate a good HMWs? Don’t Be too generic Be specific “How might we have a better “How might we have more paying business” or “save the world” customers” Don’t Combine Make it Separated “How might we be faster and “How might we faster in product better?” developments” and “How might we have a higher quality standards” Ideation 20 How to generate a good HMWs? Avoid negative writing Be positive “HMW, make the return process less “HMW, make the return process difficult” quick & intuitive.” Avoid solving symptoms Focus on the root of of the problem the problem “HMW, stop users from “HMW, make users feel confident calling support.” they have all the information they need.” Ideation 20 Using AI? Why not? Chat GPT Ideation 34 After discovery; We know: The problem and the stakeholder needs. Assumptions about the users Now what do we need to do? What did Sarah do? 1. Observational study 2. User interviews 3. Competition analysis What is user research? - User research is a study focuses on understanding user behaviors, needs, and motivations through interviews, surveys, usability evaluations and other forms of feedback methodologies to create user- centered products. - Systematic process of understanding user interactions with a product or service. Why to use user research? - It helps design teams make informed decisions that resonate with the target audience. - Enhanced User Satisfaction. - It reduces Risks. - It removes biases from the process. - It helps evaluating solutions. Main types of research: 1. Primary research 2. Secondary research - Original data - Existing data. - Creating and implementing - Analyzes and data collection methods. interprets existing data. - Higher quality data. - Lower quality data. - More time-consuming and - Quicker and more expensive. cost-effective. Let’s start with primary research User Research When to use primary research? - Project discovery phase. - Project design phase. - After project launch. Primary research tools for discovery phase User interviews - User interviews are guided interviews where a researcher asks existing or potential users questions to gain an understanding of their preferences, thoughts and feelings. Focus group - Focus groups are a somewhat informal technique that can help you assess user needs and feelings both before interface design and long after implementation. In a focus group, you bring together 6–9 users to discuss issues and concerns about the features of a user interface. Surveys - A UX research survey is a set of questions, sent to a targeted group of users, that probes their attitudes and preferences. Field study - Field studies are research activities that take place in the user’s context rather than in your office or lab. - Field studies also vary a lot in terms of how the researcher interacts (or doesn’t) with participants. Some field studies are purely observational (the researcher is a “ y on the wall”), some are interviews in which the questions evolve as understanding increases. fl Diary study - A diary study is a research method used to collect qualitative data about user behaviors, activities, and experiences over time. - During the defined reporting period, study participants are asked to keep a diary and log specific information about activities being studied. Primary research tools for Design phase Card sorting - Card sorting is a UX research method in which study participants group individual labels written on notecards according to criteria that make sense to them. Usability testing - Usability testing is a popular UX research methodology. In a usability-testing session, a researcher (called a “facilitator” or a “moderator”) asks a participant to perform tasks, usually using one or more specific user interfaces. A/B testing - An A/B test – also called split testing – is a simple experiment where users are shown two variants of a design (e.g. background image on a webpage, font size or CTA copy on a homepage, etc.) at random to find out which one performs better. Tree testing - Tree testing is a UX research method that allows you to evaluate the hierarchy and ndability of topics in a website or app. It's an important step in your research plan. In a tree test, participants are presented with a text-only version of the site's hierarchy and asked to complete a series of tasks. fi Eye tracking - A costly quantitative user research method that requires special equipment to track users' eyes while they're scanning an interface. Its goal is to detect which elements of the page attract people's attention and which stay unnoticed. Primary research tools for post-launch & evaluation phase Analytics - A quantitative method that helps in discovering how users interact with the product. - Software applications or platforms designed to collect, analyze, and interpret data related to user interactions with digital products, such as websites, mobile apps, and software interfaces Surveys - A UX research survey is a set of questions, sent to a targeted group of users, that probes their attitudes and preferences. Any questions? What to use when? 4 Criteria 1 2 3 Also experience affects your choice - Usability testing is used for either - testing new design - Or figuring out reasons of issues - Moderated or unmoderated usability testing? - Moderated : - specific flows - Prototype - Unmoderated: - General testing - Real app 4 Finally, resources affects - Time - Money - People - Other: - Culture - Distance User Interviews Case study: Employee self service system What? Why/When? How we made our decision - Usability testing - Not enough data - What are the main components of the system? - How does the normal working day look? How does the system reflects the normal working day’s activities? - Who are the audience? - Field study ? Diary study? User interviews.. How? User interviews steps 1 - Before [preparation] - Plan - Recruitment 2 - During [the interview] 3 - After [Report] - Collecting - Analyzing 1. Before [Preparation] - Plan - Background - Goals - Main Questions - Script - Intro - Warm-up - Scenarios - Wrap-up - Recruitment [also part of the plan] - Who is responsible - Persona - Schedule/time Introduction about the product Why we decided to use user interviews? What are the hidden parts we want to know more about? [persona, preferences, real life, …] Who will be responsible about the recruitment process How should the participants look like? What should participants know before attending the interview When will the interviews be conducted? Intro Wrap -up Warm -up Scenarios Your turn 1 - Create a Plan [20 minutes]: - Background - Main Questions - Script - Intro - Warm-up - Scenarios - Wrap-up Questions [scenarios] examples - Pet Supplies: - How do you usually shop your pet’s supplies? - Cleaning Service: - May you tell me about your experience with any cleaning service you used before? Maybe a maid you knew from a friend. - Employee app: - Could you tell us about your role? What are your responsibilities? - Food subscription: - Have you ever tried to commit to eat healthy food? Tell me your experience Any questions? Let’s have a break 2. During [the interview] - Applying the script: - Intro - Warm up - Scenarios - Wrap up Your turn 2 - The Interview - Use the script part to ask the questions - You have 20 minutes to conduct your interview - Remember to write everything as possible - Listen carefully 3. After [Data analysis and reporting] - Collecting Data - Analyzing data User interviews steps 1 - Before [preparation] - Plan - Recruitment 2 - During [the interview] 3 - After [Report] - Collecting - Analyzing 3. After [Data analysis and reporting] - Collecting Data - Analyzing data Research report - The Report 3 - Create a list of at least 3 key findings based on the interview [15 minutes] - Select one of the team to present the key findings [5 minutes] Tips for effective user interviews - Plan your questions carefully before the study. - Prepare follow-up questions for different possible respondents. - Do a pilot study. - Avoid leading questions. - Record/Write down notes for each session. - Involve your team to the process to reduce bias. User interview possible outcomes User journey map 1. The actor: single persona. 2. Scenario + Expectations 3. Phases 4. Actions, Mindsets, and Emotions 5. Opportunities User personas A user persona is a fictional representation of your ideal customer. It should represent the key characteristics of the target audience. A tool to focus the project team efforts to serve a specific user needs and behaviour. Empathy maps UX Competitive Analysis Agenda: What is competitive analysis? - It is a process of comparing the performance of a digital product user interface to the performance of its competitor’s interface in order to identify its strengths and weaknesses. - A UX competitive analysis focuses primarily on design and interaction, but UX researchers also consider how business and other facets impact the overall user experience. Where can we see it? Why competitive analysis? For a business owner: - Knowing your market will help discovering your own strengths and weaknesses. - To determine your users’ needs better by focusing on the competitors’ reviews either gains or pains. - To help evaluating your product or idea to build a user-friendly product. - To help informing your value proposition which describes how you stand out in the market compared to your competitors. Why competitive analysis? For a designer: - Getting insights on the most used products can help us know the market best design practices and users mental models. - Knowing competitor’s pains can help ideating more to communicate the features better. - To making design decisions based on evidences. - To help designers understand their users better By looking at the competition through customers’ eyes. Competitive analysis phases - Discovery phase: Early quick research while you want to get familiar with a new industry. - Research phase Detailed analysis per feature with a number of real competitors. Types of competitors: Direct In-direct Competitors Competitors - Offers the same set of features - Offers different features. - Has the same users. - Or has the different users. - Solves the same problem. - Solves a similar problem. Direct competitors: VS In-direct competitors: VS So how can we make a detailed competitive analysis? Important considerations: - Don’t simply copy the designs you find in your research, just learn from them. - Always involve the users in your analysis. - Always include screenshots in your analysis. - Always document your findings. - Try also to write down some recommendations in design. 1- Know your product rst: - This step will be required in case of a project revamp. - Starting with this will enable you to study the product features, users, and its place in the market. - Knowing the product features will be helpful to create a competitive advantage over other similar products. - Start analyzing the existing product features. fi 2- Find the right competitors: - Ask the stakeholder first about the competitors from their point of view. - You should make your own research to discover more competitors with more solutions. - Start with 3-5 main competitors. Once you get the information you need for filling gaps, you should stop. How can I nd competitors: Mobile apps Websites App store Play store Capterra Google fi similarweb.com similarweb.com 3- Analyze the competitors: - Use the app/website like the user. - Take screenshots with the whole journey with your notes ( pros + cons). - Consider the users’ reviews about the product. - Analyse the competitor content and performance. Important factors Features set: The analysis of what they offer with thier pains and gains from the user experience. Tone and copy: The language they talk to their customers (formal - informal). Customer reviews: The users feedback and comments on the product or what they say about it. 4- Collect date & Make presentation: - You can collect all competitors with simple data in a matrix as a conclusion. - Write your recommendations to changes in the design. - Present it to your team and stakeholders to take decisions. UX mapping techniques Mapping methods: Task flows. Flowcharts. Wireflows. User Task Flows User Task Flows They represent the high-level steps for the user interacting with our product to achieve a specific goal. Task flows tend not to branch out with options or decision points, tend to be linear and sequential, and are generally meant to be simple, rather than complex. Making a pancake User Flows User Flows They represent the detailed steps the persona can take to achieve a specific goal. It tends to be more complex than task flows. Unlike task flows, user flows include decision points wherein the persona’s journey to the desired goal can differ, based on decisions the persona need to make in interacting with the design. Task ows focus on steps to achieve one goal, and user ows focus on one user’s interaction with your product fl fl User Flows Elements Indicates a choice for Marks the start/end Indicates the user Indicates a screen or the user of the flow actions details Making a pancake Making a coffee Making a coffee WireFlows Wire ows Wireflows are a combination of wireframes and flowcharts. We use it when we need to present user interactions using the wireframes. fl Thank You! Contact Person: Hussein Gaber Mobile: +20 127 465 2104 Research Plan Template Date of creation: September 08, 2023 Project: Type: Offline _ Moderated sessions Background - about the problem/project Research goals - why we decided to use this research tool Discover users’ real needs. Research Main Questions - What are the hidden parts we want to know more about? What are the available services they need? what additional services they might need? Recruitment Recruitment and Scheduling will be done by ____ Tremoloo will provide the instructions and tools. 1 Contact Person: Hussein Gaber Mobile: +20 127 465 2104 Personas - What should the participants look like? Incentives -What will users get after the session? Special gift. Recruitment plan - How many users do we need? 2-3 participants per persona. What participants should know about the interview The main goal: ○ To answer some questions to help us … ○ Also they should know about the session incentives that they’ll receive at the end of the session. The required task: ○ We’ll have a 1:1 offline meeting [45-60 minutes] with him/her to ask some questions about the process he had to go through while applying for any service under the targetted category. Timing - When will the interviews be conducted? Documents/Inputs needed Participants schedule [By Tremoloo] Final report and presentation [By Tremoloo] 2 Contact Person: Hussein Gaber Mobile: +20 127 465 2104 Tools Mobile for recording offline sessions. Zoom for conducting & recording online sessions. Script for user interviews: Introduction ○ My name is [NAME] from [Tremoloo]. We Want to Thank you very much for your interest in supporting new solutions that would make the current process easier and faster. ○ In this study we’re trying to explore the main process you went through while applying for any needed governmental services/support after being a single mother and the challenges you encountered to take it into consideration when we design our solution. ○ We need you to speak freely about your prior experience and what can be better and easier. ○ We’ll need to record this session as a reference while we work on the solution. Don’t worry we’ll only share it with the design team to be able to design based on your actual needs. ○ By the end of the meeting, you’ll receive your gift as a small sign of gratitude. Warm-up questions: ○ Welcome again, First we need you to tell us more about yourself (do you work? What's your job? What's your education? How many kids do you have?..) Ice breaker ○ What types of services did you need to apply for ( like: Divorce certificate, subside card,.. etc)? 3 Contact Person: Hussein Gaber Mobile: +20 127 465 2104 ○ Let’s talk about every service in more detail: Scenarios [Any “How” question should be accompanied by a “Why” question] ○ Service 01 ( ex: divorce certificate) These questions will be used as a pattern per service 1. Did you apply for that service yourself? if not who helped you? 2. How did you know the process before applying? Wrap-up ○ From all of the discussions we had, can you summarize the main challenges you face in the process? ○ Do you have any recommendations for an improved process? ○ Thank you so much for sharing your experience and insights, we believe that you are really powerful. Your answers will help our team build a better solution for all Egyptian single mothers. If you have any additional thoughts and comments, we would love to hear about them at any time. Please send any extra suggestions to the person who contacted you. Hope you have a wonderful day. The output from all of the above questions should be ○ List of most frequent services. ○ List of users’ real needs. ○. 4 05 Why usability Testing. 05 Why usability Testing. 1- You’re not the user 05 Why usability Testing. 1- You’re not the user 2- Convincing 05 Why usability Testing. 1- You’re not the user 2- Convincing 3- Cheap 05 Sometimes it’s called User Testing Usability testing is behavior driven NOT opinion driven ? Usability Testing When Do We Test ? We Test Early & Often. Design and development is expensive. Usability testing assures that time spent in design and development is not time wasted We usually learn new user insights through this testing that even stakeholders have not realized. Usability Testing Who Do We Test With ? TEST WITH 1- People who actually use your product (Target Audience) 2- Potential customers, people did not buy your product but they are interest with it. DON’T TEST WITH you don’t want any of your team members to know the participants, the researcher might help a user complete a task or the user might not want to criticize the product design. Usability Testing How Many Users You Should Test With ? 5-6 5 to 6 users are enough to identify 85% of your product problems. Usability Testing How Many Users You Should Test With ? Quote Testing one user early in the project is better than testing 50 near the end STEVE KURG The author of “Don’t make me think”. Facilitator / Moderator Facilitator What good facilitator do ? Make the user feel comfortable, Our job is make people feel relaxed not judged or shamed because the failed to make a task. Skilled moderators comes with different outcomes than non-skilled. Facilitator How to answer users Questions ? Common Mistakes Technics of answering Users Questions & Getting Clarifications 1- Echo. 2- Boomrange. 3- Columbo. Facilitator What is leading Questions ? Sally & Court Example You meet a research participant, Sally, and introduce yourself as a UX researcher. You say, “Thank you so much, Sally, for agreeing to participate in this research. I’m so excited to get feedback on this app. The team has worked very hard on it, and we know you’re going to love it.” Then, imagine you conclude your research session by asking Sally if there was anything she did not like about the app. She answers, “No, not really!” Facilitator What is leading Questions ? Which of these Questions are leading ? 1- Would Your rather use the old version or this improved version of the website? 2- What did you expect would happen when you pressed that button? 3- How would you normally perform this task, without this tool 4- Why did you have difficulty with the navigation ? 5-How easy was it to use the interface ? 6- What are some pros and cons of these designs ? Facilitator How to avoid leading Questions ? Practice, Practice, Practice … Avoid using Direct Questions (Yes/ No) Use Open Questions Facilitator Why Poker Face ? Hide your emotions from the users 1-Facilitator get defensive when their design gets criticized. 2-The Emotion Of Stupidity. Facilitator Observation vs Interpretation ? Write Down what you see & hear Not what you think. Here is the magic of asking questions Not go silently along with the study. Users Thinking Out ALOUD Thinking out aloud Importance. Remind him when he forget (rule) Forget Rule vs processing info. The Rule Required Practice. 1- show him video of people thinking out aloud. 2- give him a simple task to practice on. Tasks Create Task Scenarios. Why test scenarios 1- the test task lacks detail that will motivate the participant to complete the task authentically. 2- encourage him to interact with the system & motivate him to do the task Usability Testing Prioritizing Usability Problem Take your time to add any note you forgot to add it. Each sticky note add one observation & participant number. Usability Testing Prioritizing Usability Problem Group the observations into common problems. Usability Testing Prioritizing Usability Problem Select the top three Groups To Fix. Do Vote to select the highest priority. Usability Testing Measure Severity of a problem What is the Impact of the Problem ? How many users are effected by the problem ? Will User be bothered by the problem repeatedly ? Usability Testing Measure Severity of a problem