There is no single method that allows us to answer all the questions on a project.
The researcher has to know which technique should apply in each case, depending on the questions he needs to answer.
A general classification of methods includes:
-
Quantitative techniques answer questions as “how much” or “when”. The data they provide is useful for comparing values over time or statistically confirm the findings of qualitative methods.
-
Qualitative techniques provide answers to the “how’s” and “why’s”. They are based on observing what users do and say to gather insights about how they are, what they need, problems they face, etc.
Although there are many, some techniques stand out for their results. Among others, these are the ones we use the most:
-
Surveys. A widely used quantitative technique. Surveys help us with things like monitoring user satisfaction over time or defining our roadmap, prioritizing the features most demanded by users.
-
User behavior analysis. Through different tools, we can obtain user feedback and statistical usage data from different sections of the product. Analyzing this data is a great way of finding issues with the product or areas of improvement.
-
In-depth interviews. We talk (but mostly listen) to users so we can get to understand in depth the problems they face, discover unsatisfied needs, etc. Only by understanding these aspects, we’re able to propose solutions that truly respond to your needs.
-
Usability test. This is one we use often. Before releasing any new features, we need to make sure that our proposal is easy to understand by users. To do so, we let them play with our design proposals through a series of missions to complete. This technique is really effective (and fun), and often reveals unexpected issues with the proposal.
Carrying out this type of testing is time-consuming, but totally worth it, as they are the best way to keep us aligned with your needs as a user.
