Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


 

Splitting your analysis by user group or other criteria (such as region) is a common need, especially for larger websites.

 

Analyzing by user group

If you have more than one user group visiting your site (and most of us do), analyzing a tree test is a lot easier if you analyze each user group separately.

If you run a separate tree test for each user group (as we discussed in Different tasks for different user groups in Chapter 7), then you’re going to have a separate set of results for each test, so that’s already taken care of.

If, however, you run a single tree test across all of your user groups, we recommend that you do a separate analysis for each group. That way, you can see the differences in their performance, instead of having their respective highs and lows mushed together into middling scores.

Suppose, for example, that we were looking at the results for a single tree test of the Shimano website. In Which part of the tree? in Chapter 6, we saw that Shimano has 3 major types of users – cyclists, anglers, and rowers. And suppose that the cyclists and anglers had no problem with tasks that covered the Corporate section of the site, but rowers failed miserably at those. If you looked at the results of all users together, the high scores of the cyclists and anglers would get mixed in with the low scores of the rowers, and you would just see a mediocre composite score, with no easy way to find out what caused it.

If, however, you could separate the groups and do the same analysis for each group, you could see that it was the rowers who had problems – the other two groups were just fine.

In Adding survey questions in Chapter 8, we suggested using survey questions to identify user groups, so we could easily pull them apart later for analysis. Now that we’re ready to analyze the data, we need to:

  1. Narrow the results to a single user group by filtering the data to only include participants who chose that user group in the “who are you” survey question.

  2. Regenerate the results (if this is not done automatically).

Here’s an example using Treejack:

  • TJ example of selecting participants based on user-group survey question, then regenerating results

 

Once you’ve generated the results for each group, analysis proceeds as we’ve described elsewhere in this chapter. But at each step of the analysis (success rates, backtracking, first clicks, etc.), we can compare how the groups performed and look for any major discrepancies between them.

 

Analyzing by other criteria

Just as we can split our analysis by user group, we can do the same for other factors such as:

  • Region

  • New vs. existing customers

  • Age or life stage

  • …and so on.

In all cases, we need to either:

  • Run separate tree tests for each cohort.
    For example, if we’re analyzing by region, we could run separate tests for region 1, region 2, and region 3.
    If we intend to use different tasks for the different groups, then we should definitely run separate tests – see Different tasks for different user groups in Chapter 7.

  • Run a single test, using a survey question to identify each factor.
    If we’re intending to use the same set of tasks for each cohort, we could add a “Which region do you live in?” survey question, then filter the results using the various values of this question (as described above for user groups).

 


Next: Discovering evil attractors

 

  • No labels