Enrol to start learning
Reading is open to everyone. Enrolling is free, and it is what unlocks the audio lessons, practice tests and progress tracking.
4.1. Organizing Quantitative Results
Interactive Audio Lesson
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free account
Today, we will discuss how to compile data from our user testing sessions into a clear format. What do you think is essential to include in our data summary?
We should add what tasks users completed and if they succeeded or not.
Absolutely! We'll also include the time taken for each task and any errors made, which will help us analyze performance. Can someone tell me why time taken might be important?
It shows us how easy or hard the tasks were. If they took too long, it might mean there's a problem.
Exactly! Easy tasks should have low completion time. Now, let’s create a sample data table together, what should the first column be?
Task performed!
Correct! This organization helps us later when we look for trends. Remember, organizing data is like making a clear picture of our findings.
To summarize, we need to include: Task, Success, Time, Errors, and Satisfaction scores in our table.
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free account
Now that we have our data compiled, what’s next? How do we find the patterns in this data?
We can look at the completion rates and see which tasks had the most failures.
Great point! We should focus on tasks with low completion rates or high error counts. Why do you think this is vital?
It tells us what’s most problematic and helps us know what to fix first.
Exactly! By prioritizing these issues, we can make our design better. It's all about listening to what the users are telling us through their performance.
Remember, we look for patterns like high error rates, slow completion times, and low satisfaction scores. Let's summarize this: focus on identifying critical trends in user performance.
Unlock the classroom podcast
The transcript is above and free to read. A free account plays the conversation back.
Create a free accountToday, we’ll categorize the issues we have identified from the data. Who can summarize how we classify these issues?
We categorize them into critical, major, and minor.
Correct! Critical issues completely prevent task completion, while minor ones are annoyances. Why is prioritizing these issues helpful?
It helps us tackle the biggest problems first, so users have a better experience quickly.
Right on target! So, after evaluating severity, we also need to look at the frequency of each issue. Why do these two factors matter together?
It shows us which issues affect the most users and should be fixed right away!
Excellent answer! To wrap it up, we classify issues by severity and frequency to prioritize our efforts effectively.
Overview
Short Summary
This section discusses how to compile and analyze quantitative data obtained from user testing, identifying patterns, and determining priorities for improvements.
Medium Summary
In this section, we focus on organizing quantitative results from user testing sessions, utilizing tables for effective data compilation. We highlight the importance of identifying trends based on task completion rates, error counts, and user satisfaction to prioritize improvements for prototypes.
Detailed Summary
Detailed Summary
Organizing quantitative results is crucial for translating raw feedback from user testing into actionable insights. Once you collect data from usability tests, it is essential to present that data systematically, often in the form of tables. A well-organized table allows you to compare results across different participants and tasks seamlessly. Users' success rates, time on task, error counts, and satisfaction scores can be analyzed to identify patterns and areas needing improvement.
Key Steps to Organize Quantitative Results:
- Compile Data: Create a table that includes information such as the task performed, participant success (yes/no), time taken in seconds, errors made, and satisfaction ratings.
- Look for Trends: Analyze the data for trends; identify tasks where completion rates are low or where users took excessive time or made numerous errors.
- Evaluate Severity: Categorize issues into critical, major, and minor. This helps in highlighting which issues need immediate attention.
- Determine Priorities: Use frequency and impact axes to prioritize the issues. The focus should be on resolving high-frequency, high-impact problems first.
- Root Cause Investigation: Delve deeper into why issues occurred and what cognitive models users were operating under.
- Brainstorm Solutions: Based on the findings, discuss potential design improvements and document all iterations.
These steps ensure that design improvements are based on actual user data rather than assumptions, leading to a design that better meets user needs.
Audio Book
Unlock the audio lesson
The script is above and free to read. A free account plays it back, in the voice you pick.
Create a free accountCompile data into a table:
Detailed Explanation
In this chunk, we learn how to neatly organize the results of user testing in a table format. The table includes various columns: 'Task' describes what the user was trying to do, 'Participant' shows who completed the task, 'Success' states whether the task was completed successfully, 'Time (s)' indicates how long it took, 'Errors' counts the mistakes made during the task, and 'Satisfaction' provides a score for how the participant felt about the experience. For example, in the table, Sam successfully found a chapter in 32 seconds with one error, while Maya had difficulties using the highlight tool, taking 75 seconds with three errors.
Examples & Analogies
Think about a sports game where you want to analyze player performance. Coaches keep track of how many goals each player scored, the time they were on the field, how many times they missed shots, and what their teammates thought of their performance. By organizing this information in a table, just like we do for user testing, the coach can easily see who performed well and who needs improvement.
Unlock the audio lesson
The script is above and free to read. A free account plays it back, in the voice you pick.
Create a free accountLook for trends:
● Tasks with low completion rates ● High average time or error counts ● Low satisfaction scores
Detailed Explanation
This chunk describes the importance of analyzing the compiled data for trends. When analyzing user testing results, we should identify patterns or trends that might highlight areas needing improvement. For instance, if a specific task has a low completion rate, it suggests users struggle with that task. Similarly, if the average time taken to complete a task is high or there are a lot of errors, it indicates that the task is not intuitive and might require redesign. Low satisfaction scores also alert designers to potential issues that affect the overall user experience.
Examples & Analogies
Imagine you're a teacher reviewing student test scores. If most students fail a certain question, this trend signals that perhaps the question was too difficult or not well understood. Just as the teacher would reconsider the teaching material or exam structure based on student performance, designers can refine their products by analyzing user testing trends to see where adjustments are needed.
--
Key Concepts
Core takeaways and short definitions to help you quickly recall the key ideas from this section.
Identifying Quantitative Results: Organizing data from usability tests helps identify key trends.
Trend Analysis: Looking for patterns such as low completion rates or high error counts.
Severity Categorization: Critical, major, and minor issues help prioritize user experience problems.
Prioritization of Issues: Determining issues to address based on frequency and impact.
Examples
Memory Aids
Interactive tools to help you remember key concepts
Stories
Memory Tools
Flash Cards
Glossary
Quantitative Data
Data that can be counted or measured, often used to determine patterns or trends.
Table
An organized arrangement of data in rows and columns for analysis.
Trends
The general direction in which something is developing or changing, identified through data analysis.
Severity
The degree of seriousness of an issue, categorized as critical, major, or minor.
Prioritization
The process of determining the order of importance or urgency of different issues.