The importance of UX Research and how to conduct It

In today's competitive app market, user experience (UX) research is essential for building a successful app. It's the process of understanding your users – their needs, behaviours, and pain points – so you can create an app that solves their problems and meets their expectations.

Why UX Research Matters:

UX research helps you answer two fundamental questions:

  1. What do users say? This involves gathering user feedback on their opinions, attitudes, and feelings about your app (or app concept). This is attitudinal research.
  2. What do users do? This involves observing how users actually interact with your app. This is behavioural research.

To better understand the landscape of UX research, it's helpful to consider a framework that categorises methods based on two key dimensions:

  • Attitudinal vs. Behavioural: As mentioned above, does the research focus on what users 'say' or what they 'do'?
  • Qualitative vs. Quantitative: Does the research aim to gather rich, descriptive insights (qualitative) or numerical data (quantitative)?

This framework, visualised in the image below, provides a helpful overview of the diverse approaches available.

The 2x2 Matrix of UX Research Methods
👍 Pro Tip: Qualitative research also typically involves a smaller sample size than quantitative research. Nielsen Norman Group recommends 40 participants—see our full rundown of how many user testers you need for different research methods.

Common UX Research Methods

Before we begin any research, you should customise your approach to suit the objectives of the research. Below is a list of 11 popular research techniques for you to leverage:

User Interviews:

What: One-on-one conversations with target users.

Why: Deep insights into user needs, motivations, and pain points.

When: Early stages of development, exploring ideas, defining your target audience, or gathering feedback on prototypes or existing products.

How-to Articles:

Field Studies:

What: Observing users in their natural environment – where they would typically use your app.

Why: Contextual understanding of how your app will be used in the real world.

When: This can be used at all stages of development

How-to Articles:

Focus Groups:

What: Moderated group discussions with a small group of target users.

Why: Diverse perspectives and initial reactions to concepts.

When: start or end of project, to gather diverse perspectives and get initial reactions to your concepts or

How-to Articles:

Surveys:

What: Questionnaires distributed to a larger group of users.

Why: Quantitative data on user satisfaction, preferences, and demographics.

When: Throughout the development process, to gather data on user satisfaction, preferences, and demographics.

How-to Articles:

Usability Testing:

What: Observing users as they interact with your app (or a prototype) to identify any usability issues.

Why: Insights into how users interact with your app and where they encounter problems.

When: Throughout the design and development process, and critically, before you launch your app.

How-to Articles:

👍 Pro Tip: Design realistic user testing scenarios to encourage authentic behaviour. For example, "You just received a push notification...what do you do next?" (leading into the task) allows for organic exploration. Avoid overly structured tasks that trigger a "completionist" mindset.

A/B Testing:

What: Comparing two versions of a design or feature to see which performs better.

Why: Data-driven insights to optimise your app for conversions and engagement.

When: Throughout the design and development process or on large scale after launch, for continuous improvement and optimisation based on real user data.

How-to Articles:

Concept Testing:

What: Gather feedback on a new product or feature before you invest in development.

Why: Validation of your product or feature ideas and their potential appeal to users.

When: Early stages of development, to test the feasibility and appeal of your concepts.

How-to Articles:

Card Sorting:

What: Users organise topics or information into categories that make sense to them.

Why: Insights into how users think about the information architecture of your app.

When: Early stages of design, when you're defining the structure and organisation of your app's content.

How-to Articles:

Tree Testing:

What: Users try to find specific items within a text-based version of your app's navigation.

Why: it's great: Evaluation of the findability and organisation of information within your app.

When: During the design process, to refine your app's information architecture.

How-to Articles:

👍 Pro Tip: While Tree Testing is excellent for measuring findability (how easily users can locate a specific item), it's less directly suited for measuring discoverability (how easily users can stumble upon new or unexpected content). Discoverability is often better assessed through methods like card sorting (to understand users' mental models) or unmoderated usability testing where you observe user behaviour without giving specific tasks.  Consider combining Tree Testing with other methods to get a complete picture of your information architecture.

Five-Second Testing:

What it is: Users are shown a design for just five seconds and then asked about their impressions.Why it's great: First impressions and understanding of your design's clarity and effectiveness.When to use it: Early stages of design, to ensure your design is clear and effective at a glance.

How-to Articles:

Diary Studies:

What: Users keep a diary to track their interactions and experiences with your app over a period of time.

Why: Deep insights into user behaviour and how your app fits into their daily lives.

When: Early stages of development, to gain deep insights into user behaviour in real-world contexts.

How-to Articles:

To help you get started:

To help get your started on your next research project. Here is a list of 50 templates that ODette Jansen put together for the community 50 notion Research templates