User Strategies: Considerations for UX Analysis and Design
Published: October 17, 2011
A complicating factor in UX analysis and design is that people starting with the same goal can often pursue different strategies in achieving that goal. I once experienced this complication when conducting generative user research prior to designing a user interface. Once I had collected data from one group of participants, I decided to collect additional data from a second group to extend and validate the initial data. To my consternation, the data from the second group was strikingly different. Far from providing guidance for designing the user interface, this additional data left me feeling like a person with two clocks that tell different times. Further analysis revealed that, through some fluke, people in the first group tended to work in one type of situation, while those in the second group tended to work in another type of situation. This research led to the insight that our user population uses two different strategies depending on their work situation. This example represents just one of the many times when I’ve had to account for multiple user strategies in a UX project.
Over several years, I’ve sought guidance on how best to deal with user strategies in UX analysis and design. Questions I’ve tried to answer include the following:
- What are people referring to when they use the term user strategy?
- What has the UX discipline discovered about user strategies that I can leverage in my project?
- When I learn that users employ a variety of strategies, how should I address this in a product’s design?
These are the questions this article addresses. The answers represent my own views and describe practices I’ve formed by both learning from practical project situations and reading about the work of others. You can apply these ideas whether conducting formal user research or simply discussing or envisioning how users would use a user interface you’re designing.
User Strategy As a UX Concept
In my search for a useful way to incorporate user strategy in UX analysis, I’ve come across a couple of ineffective approaches. The first approach takes a simplistic view of user behavior that does not even recognize the existence of user strategies. This view, which I’ve depicted in Figure 1, describes user behavior in terms of one or more goals, each of which users can achieve by following a series of steps.
Figure 1—UX analysis that does not account for user strategies
Another ineffective approach places undue emphasis on talking about user strategies without an effective way of analyzing them or a clear vision of how the information should guide design.
I have come to think of user strategy as comprising three distinct parts—and the analysis of each provides useful guidance for UX design. These components, which I’ve illustrated in Figure 2, provide a sufficiently rich depiction of the user activity that I observe in user research—or even in everyday occurrences.
Figure 2—User task model representing the three components of user strategy
This user task model illustrates the following points:
- Starting with a goal, a user chooses one method among of a set of available methods and carries out the steps for that method. Each method consists of its own set of steps.
- Pursing a goal can result in a variety of outputs that all satisfy the user’s goal, but also differ from each other in important ways. The arrows pointing from the methods to the outputs show that, once someone chooses a method, that choice can sometimes constrain the possible outputs.
In this diagram, I’ve highlighted one path from a goal to an output in blue: a person with Goal A chooses Method 2 and produces Output B. This example calls our attention to another thing that an analysis of user strategy should explain: When would someone choose a particular method and output among the range of possibilities? The shaded area that I’ve labeled Selection Criteria represents the considerations that can explain a user’s choice of method and output in a given situation. I could represent this information in various ways such as flowchart or a simple list of choice criteria, depending on needs of the UX analysis.
So far, I’ve not used the term strategy in my description of this model. Strategy is simply the collective term for the methods, outputs, and selection criteria in this model. Often, I find it useful to analyze each of these elements of strategy separately. But sometimes these elements can be so intertwined that it’s useful to refer to them collectively as user strategy or user strategy analysis.
To illustrate this way of modeling user strategy, let’s examine a narrative description of a user strategy to identify each strategy element. (This example is based on a classic study from the 1970s, which Kim Vicente summarized in his book titled Cognitive Work Analysis. I’ve adapted his wording here.)
Research discerned the following strategies from observations of air traffic controllers:
- When there are up to three aircraft, air traffic controllers—especially those who are experienced—tend to provide an optimal path for each aircraft.
- Another approach is to assign uniform speeds and flight paths to all aircraft.
- Creating waiting buffers is a common approach when there more than six aircraft.
Table 1 shows how we can represent that narrative description in terms of the three elements of user strategy:
Table 1—An example representing the three elements of user strategy
Calculate the optimal path for each aircraft.
High-quality landing path
1–3 aircraft—that is, a low work volume; a highly skilled ATC
Assign a uniform speed and flight path to all aircraft.
Medium-quality landing path
4–6 aircraft—that is, a medium work volume
Create waiting buffers.
Minimally acceptable landing path
More than 6 aircraft—that is, a high work volume
The Nature of User Strategies
Success favors the prepared mind, as the saying goes. Being familiar with the diverse manifestations of user strategies can help you successfully analyze user strategies on a given project. The UX literature includes snippets of user strategy analysis from many domains. We can also practice user strategy analysis simply by reflecting on everyday user activities—anything from choosing a password to investing savings so we can spend our retirement traveling around the world.
One generalization about the nature of user strategy is that strategies occur at every scale. Depending on the project, you’ll need to look at the appropriate scale to discern different user strategies. At the largest scale, strategies differ among different groups of people. For example, engineers and field service technicians would take different approaches to troubleshooting equipment failures, each appropriate to their distinct job conditions. So, basing a design simply on user research with engineers would fail to support the preferred working style of field technicians.
At the next smaller scale, we sometimes see different strategies among different individuals in the same job or demographic category. For example, different people use different strategies for generating their computer passwords. To mention only two possible strategies: Some people prefer passwords that are easy to remember, while others prefer passwords that are easy to type. So, to understand the full range of users’ possible password-setting behavior, we’d need to study a broad sample of people and look for patterns or clusters among the password-setting behaviors we observed.
At the smallest scale, the same person might employ different strategies on different occasions. For example, depending on their opponent, good chess players choose the most appropriate strategy within their broad repertoire. Another example of the same person’s switching strategies is when people shift to a less effortful method as their volume of work increases, as we saw in the case of air traffic controllers.
I’ll briefly note a few other characteristics of user strategies that are useful to bear in mind when analyzing them:
- Sometimes users can easily describe the strategy they are using, while, in other cases, they are not even aware they are using a particular strategy.
- Sometimes users’ stated strategy is at odds with their observable behavior.
- Sometimes users’ behavior is opportunistic. That is, once a user starts to perform an activity, some condition arises that causes the user to divert from the original goal or method to pursue a new course of action.
- Generally, it is possible to explain the choice of method or target outcome using one or more of the following types of selection criteria:
- what is most important to a person
- the person’s competencies or resources
- the level of difficulty or uncertainty in the situation
- It is sometimes useful to describe strategies in terms of general styles such as defensive versus offensive; conservative or safe versus risky. In other cases, it’s more useful to describe user strategies in terms of a specific method—for example, in air traffic control, the method of assigning a uniform speed and flight path to all aircraft.
How to Address User Strategies in Design
The last question I’ll address in this article is this: Given a description of some user strategies, how should I address them in a design? Let’s look at all of the options, in no particular order. One option is to focus a design on supporting a single method—likely the most popular method. This seems like a common approach from what I have seen. One reason for this is that a design team might be familiar with only one method of achieving the goals a product addresses. Even when a design team has a good understanding of multiple methods in use across a user population, it often makes practical business sense to simply choose the most popular method and focus resources on supporting that approach.
The second option is provide separate user interface elements to support each method or user audience. From a textbook UX point of view, this option might seem like the only right answer. Such a design delights users who perceive that you’ve provided parts of the design just for them. However, this type of design can be risky to undertake because, among other things, it relies on a depth of user understanding that is not always feasible to acquire. So, pursuing this ambitious option entails the risk that one’s reach exceeds one’s grasp.
The final option is pursuing a generalized and flexible design that can accommodate the range of user preferences, without optimizing for any single method. On a recent project, I tried this approach, being at my wit’s end after exhausting many other design options. This project involved enhancements to a middleware product. Middleware refers to software such as application servers and database engines that a professional IT staff administers for large enterprises. The goal for this product was to make it easier to troubleshoot performance problems that occur. From time to time, performance slows down inexplicably, and the IT staff needs to resolve the problem.
For this project, I conducted extensive user research, which revealed a broad range of user strategies—in this case, mainly in terms of the methods they used. In fact, there seemed to be as many strategies as there were users. To further complicate matters, observational studies suggested that people’s actual behavior did not always match the method they articulated.
Things were looking grim until I realized their diverse methods included a handful of common diagnostic questions. For example, many people sought, at some point in their diagnosis, to identify which application transactions were using the most CPU resources. Once I realized that users’ diverse strategies comprised some common building blocks, I abandoned my initial design plan for a rigid, flowchart-like interaction. Instead, the design provided a modular toolbox, in which each tool answered a specific diagnostic question—such as Which application transactions are using the most CPU resources? The design gave users the freedom to pursue their own strategy, in terms of which diagnostic questions they wanted to answer and in what order.
In this article, I’ve shared some guidance on how best to deal with user strategies in UX analysis and design. This guidance is based on my own experience. The questions I’ve sought to address are:
- What is a useful way of including user strategy in UX analysis?
- What should one look for when observing and analyzing user strategies?
- How can information about user strategies guide design?
You can apply these ideas whether conducting formal user research or simply discussing or thinking about how you envision users will use a product user interface your team is designing.
If this article has whetted your appetite, I suggest you read Chapter 9, “Strategy Analysis,” in Cognitive Work Analysis by Kim Vincente. While he covers this topic from the perspective of his analysis framework for cognitive work, it’s still good reading for the general UX audience.
Unfortunately, there is nothing more I can recommend from the UX literature—though my familiarity with that literature is incomplete. I did peruse a handful of books about task analysis and found little on this topic. Often the term strategy did not even appear in the index. I have found most of what I’ve learned about this topic from reading serendipitously—usually, a useful nugget in an article whose focus was not strategy analysis.
When I’ve presented on this topic, people have asked me what cognitive psychology research has to offer on this topic. The literature on decision making from Daniel Kahnemen and his colleagues is certainly relevant and fascinating. However, this research looks at the topic from a different perspective, making it difficult to apply to the questions I’ve addressed here—specifically: How can UX analysis and design take into account the phenomenon that people start with the same goal, but take quite different courses of action, resulting in outputs and outcomes that vary widely, even if they all achieve the original goal?
Vicente, Kim J. Cognitive Work Analysis: Toward Safe, Productive, and Healthy Computer-Based Work. Mahwah, NJ: Lawrence Erlbaum Associates, Inc., 1999.