Interpreting Usability Test Results

Part 1: From Raw Data to Structured Observations

After a usability test, you'll have a mix of quantitative and qualitative data.

• Quantitative data is numerical and tells you what happened (e.g., "3 out of 5 users failed to complete the task," or "The average time to complete was 95 seconds").
• Qualitative data is descriptive and tells you why it happened (e.g., "Users were confused by the term 'nesting options'," or a direct quote like, "I had no idea where to click next").

To perform a robust analysis, you need both. A key skill is learning to capture the subtle qualitative cues during a test.

Capturing these observations is the first step. The next is to organize them in a way that allows you to see the bigger picture.

Part 2: A Step-by-Step Framework for Analysis

A structured approach is essential to avoid getting lost in the details. We'll follow a four-step process to move from raw notes to actionable recommendations.

Let's dive deeper into each of these steps with some practical methods.

Step 1: Organize Your Data

Imagine you've just tested with five users. You'll have five separate sets of notes. To analyze them effectively, you first need to consolidate them. A spreadsheet is a fantastic tool for this, allowing you to map each participant's actions against specific tasks or expected behaviors.

Step 2: Identify Patterns with Affinity Mapping

Once your data is organized, you can start looking for patterns. Do multiple users get stuck in the same place? Do they use the same words to describe their confusion? Affinity mapping is a technique used to group these individual observations into meaningful themes.

You can do this physically with sticky notes or digitally using tools like Miro or FigJam. The goal is to create clusters of related findings.

After a test, you would group all the "red" notes together to see if they form themes, like "Confusion about shipping costs" or "Difficulty using the date picker."

Step 3: Quantify and Prioritize Issues

Not all issues are created equal. A typo is a minor problem; users being unable to complete a purchase is a critical one. You need to prioritize to ensure you're focusing your efforts where they'll have the most impact.

First, assign a severity rating to each issue. A common scale is:

• Critical: Prevents users from completing a key task.

• Serious: Causes significant frustration but doesn't completely block the user.
• Minor: A small inconvenience or cosmetic issue.

Next, you can quantify your findings using simple metrics. A UX Scorecard is a professional way to present this data, combining task-level metrics with overall experience scores. This format will feel familiar given your background in financial reporting and analysis.

A UX Scorecard visualizing task completion rates, time, and ease of use. This is a powerful way to summarize quantitative findings and pinpoint specific areas of user friction.

As you can see, this scorecard clearly highlights which tasks are causing the most trouble (e.g., low completion, high time, difficult rating), helping you and your client decide what to fix first.

Finally, always consider the effort-to-impact ratio. As a freelancer, your time is money. A low-effort, high-impact fix (like rewording a confusing button) is a quick win. A high-effort, low-impact fix might be postponed.

Step 4: Summarize Your Findings and Recommendations

The final step is to synthesize your analysis into a clear, concise summary. The goal isn't just to list problems, but to provide actionable recommendations. Your analysis should directly feed into a document that outlines the problem, explains why it's a problem (using user quotes or data), and suggests a solution.

The UX audit template from Curiosum, which you can see in the resource "Free UX audit template in Figma," provides a great structure for this. It breaks down a user journey step-by-step, showing screenshots, findings, and recommendations for each stage.

Activity: Analyze Mock Usability Test Findings

Now it's your turn to be the analyst. In the last lesson, you created a test plan for your multi-step custom gift ordering form. Imagine you've now conducted the test with three users. Below are your collated notes.

Scenario: Users were asked to order a custom wedding hoop for a friend, specifying the text, material, and a special request for gift wrapping.

Observations:

• User 1: Successfully completed the form in 2 minutes. Said, "The steps were really clear." On the final summary screen, they looked for an 'Edit' button to change the text they entered but couldn't find one.
• User 2: Got stuck on the second step ("Material & Add-ons"). They clicked on the "Premium Oak" option multiple times, but didn't realize they also had to click a separate "Add to Order" button. They said, "I thought just clicking on it would select it. It's confusing." They eventually figured it out after 30 seconds of hesitation. They also mentioned the final price seemed higher than expected.
• User 3: Abandoned the process on the final summary screen. They stated, "I couldn't see a breakdown of the costs. The total just jumped up and I don't know why. I want to see the cost for the 'Premium Oak' and the gift wrapping separately." They missed the small question mark icon that explained the cost breakdown.

Your Task:

Based on these findings, create a short analysis summary. Use a text editor to:

1. Identify and Theme the Issues: Group the observations into 2-3 distinct problem themes (e.g., "Lack of Cost Transparency," "Confusing Interaction Model").
2. Prioritize the Issues: For each theme, assign a severity rating (Critical, Serious, or Minor) and write a brief justification.
3. Write Actionable Recommendations: For your highest-priority issue, write a clear, specific design recommendation. For example: "Instead of hiding the cost breakdown behind an icon, display it as a line-item list on the summary screen."

This exercise will directly prepare you for our next lesson, where we'll take these recommendations and implement them in Figma.

Conclusion

Excellent work. You have now learned how to bridge the gap between user feedback and design decisions. By applying a systematic analysis framework, you can transform a sea of observations into a clear, prioritized action plan. This analytical rigor is a significant differentiator for a UX freelancer and aligns perfectly with the skills you've honed in your finance career.

Key Takeaways:

• Analysis requires structure: Use methods like spreadsheet note-taking and affinity mapping to organize raw data and identify patterns.
• Both 'what' and 'why' matter: Combine quantitative data (like task success rates) with qualitative insights (like user quotes) for a complete picture.
• Prioritization is key: Use severity ratings and consider the effort-to-impact ratio to focus on the most important fixes first.
• The output must be actionable: Your analysis should result in clear recommendations that guide the next design iteration.

Preview of the Next Lesson:

Now that you know how to identify and prioritize usability issues, it's time to act on them. In our next lesson, you will learn how to iterate on a prototype based on usability feedback and document the design changes made. You will take the recommendations from today's activity and apply them directly to your Figma prototype.