Identify key takeaways faster with instant insight

Posted on October 13, 2021
4 min read

Share

When it comes to unmoderated studies, task-based questions are extremely popular for testing web-based experiences (desktop web, mobile web, and web-based prototypes). However, involved studies may include several task-based questions across multiple participants—making it difficult to evaluate all of the sessions in sum. 

Identifying patterns and anomalies within multiple responses can be time-consuming, yet, they’re often the most valuable pieces of analysis. Even worse, finding relationships across various participant sessions can be extremely difficult—causing missed observations that could lead to actionable insights. 

That’s why we’re excited to launch instant insight. 

Introducing instant insight

Instant insight is one of our newest features that helps you save time during post-test analysis and generate actionable findings by automatically surfacing interesting patterns, anomalies, and correlations for task-based questions.

Introducing instant insight

How does instant insight work?

Instant insight only works for web-based experiences and task-based questions. After a test is completed, the UserTesting platform automatically analyzes the results, identifies layers of data around intent, sentiment, and contributor flows, and generates insights on top of that data.

When analyzing the results, the algorithm explores two things:

  1. Aggregations to identify common patterns or anomalies across contributor sessions
  2. Correlations that detect interesting connections across various measures

Once these findings are identified, you’re able to view them summarized into easy-to-understand sentences as cards above the interactive path flows.

Examples of instant insight

In order to truly speed up your time to insight, the solution displays the insight cards prioritized based on the statistical strength of the findings.

When to use instant insight

Instant insight is a particularly useful feature when trying to fuel efficient analysis, guide which task data needs to be evaluated further, and quickly understand common themes and anomalies in the flow of a given task. 

Specifically, it’s particularly helpful when analyzing tests that have:

  • A high number of participants
  • Tasks that require many steps to complete
  • Tasks where there are many different ways to complete a task
  • A need to compare results from multiple task-type questions within one study
  • An expectation to have to analyze deeply to get patterns/anomalies

Moreover, you can easily share instant insights with colleagues and stakeholders as preliminary findings from research, as well as points of interest to drive product development or UX discussions.

In order to get the most from instant insights, you’ll want to pair this feature with success paths and custom insights through the use of tagging. By tagging via success screens and customer intents you’ll dynamically generate new instant insights.

Let us show you what we mean.

How to get the most from instant insight

When it comes to machine learning, the more information you provide, the more robust analysis you receive in return. In this case, by tagging via success screens and custom intents, the algorithm will begin to provide you with more meaningful system-generated analysis.

Instant insight + success paths 

By pairing using instant insight and success paths together, you’ll be able to tell which screens and intents (i.e., actions) are predictive of success or failure.

Here’s how it works:

  • When you put a task together, you may have a particular page or URL that you want contributors to eventually get to. We call this desired end result a success screen. 
  • In the search bar that sits above interactive path flows, you can look up a specific URL or page title. The search query will return a highlighted result in the path flow diagram below the search bar.
  • You’ll want to assign a success flag to that specific page or screen, and success-based instant insights will be generated dynamically.

Note: success screens are persistent and searchable. You can use this functionality to help understand how many contributors were successful, and which interactions or steps were predictors of that success.

Instant insight and success paths working together

Instant insight + custom intent 

Instant insight gets even more powerful when combined with custom intent, another new feature that sits atop interactive path flows.

Here’s how.

Let’s say the UserTesting algorithm doesn’t predict an intent that’s specific to your company, or labels it differently from what you’d like to see. By using custom intent relabeling, you can add or adjust the intent labels between the steps on an interactive path flow. Then, we’ll automatically tag all other relevant interactions with the same label. 

After you’ve completed your custom intent labeling, if the system detects new findings based on the labeling, corresponding instant insight cards will be generated automatically.Note: custom intents are persistent and searchable. Now that you’ve tagged it, your teammates can also see the same label and search for that intent when viewing the task.

Instant insight and custom intent working together

Post-test analysis for task-based questions just got easier

This feature is now available to accelerate your post-test analysis, and ultimately help you to build better user experiences, by leveraging the power of human insight.If you’d like to learn more about any of these features, contact your account team or reach out to us here.

In this Article

    Related Blog Posts

    • 20 questions project managers should ask their customers

      Product managers work across multiple teams, constantly meeting with engineers and designers—leaving less than...

    • 11 product discovery techniques to help your team succeed

      Product discovery is an essential phase in the product development cycle that allows you...

    • A/B test your mobile apps and websites for quick UX wins

      Every product designer or developer needs A/B testing in their toolkit, including those who...