---
layout: handbook-page-toc
title: "Defining goals, objectives, and hypotheses"
---

## On this page
{:.no_toc .hidden-md .hidden-lg}

- TOC
{:toc .hidden-md .hidden-lg}

### How to define goals, objectives, and hypotheses

Conducting user research takes a significant amount of preparation before you even begin asking users anything. However, the time you spend creating alignment and developing a research plan pays off *tremendously* because it keeps you on track as you carry out your research.

Starting with a good question *and* the right question will ensure you end up with a useful answer. A good research question is specific, actionable, and practical. That means:
* It’s possible to answer the question using the techniques and methods available to you.
* It’s possible but not guaranteed that you can arrive at an answer with a sufficient degree of confidence to base decisions on what you’ve learned.

Only after you have identified your research question(s), can you select the best way to answer the question (i.e. [which research method to use](/handbook/engineering/ux/ux-research-training/choosing-a-research-methodology/)).

As the figure below shows, there are 5 main steps to creating research hypothesis, goals, and objectives. 

![5 Main Steps to Creating Research Hypothesis, Goals, and Objectives](/images/uxresearch/Steps_to_create_hypothesis_goals_objectives.jpg)

#### Step 1 - Start thinking of a problem
* Ask yourself:
    * What current beliefs do you have about the user?
    * What organizational or other barriers do you need to be mindful of?
    * What are the business objectives for the project?
    * What questions does the research need to answer?
    * What are we trying to learn?
    * What *must* the research achieve?
    * Does any prior research exist? (previous research can be found in [UXR_Insights repository](https://gitlab.com/gitlab-org/uxr_insights/))
        * What did prior research tell us?

| **Start thinking of a problem** | **Questions we need answers to** | **Hypothesis** | **Goal** | **Objectives**
| ------ | ------ | ------ | ------ | ------ | 
| Let’s imagine that a hotel chain has noticed they have had a lower number of bookings in the last few quarters, but they are unsure why. |
 
#### Step 2 - Start populating ‘Questions we need answers to’
- This is meant to be a brain dump of all the answers you came up with from step 1. 
- These aren't the questions you'll directly ask users - you'll get to that step later as you fill out your discussion guide. 

| **Start thinking of a problem** | **Questions we need answers to** | **Hypothesis** | **Goal** | **Objectives**
| ------ | ------ | ------ | ------ | ------ | 
| Let’s imagine that a hotel chain has noticed they have had a lower number of bookings in the last few quarters, but they are unsure why. | Are people not booking because they don’t like the hotels we have? Do we have issues with the website or app? Are our prices too high? Are we missing hotel amenities that customers are looking for?  |

#### Step 3 - Fill out the hypothesis
- The research hypothesis is simply the assumption you have about the product/feature/experience. 

- Read more about [how to write a strong hypothesis](#how-to-write-a-strong-hypothesis) further down this page.

- Use the questions you listed in step 2 to guide you.

| **Start thinking of a problem** | **Questions we need answers to** | **Hypothesis** | **Goal** | **Objectives**
| ------ | ------ | ------ | ------ | ------ | 
| Let’s imagine that a hotel chain has noticed they have had a lower number of bookings in the last few quarters, but they are unsure why. | Are people not booking because they don’t like the hotels we have? Do we have issues with the website or app? Are our prices too high? Are we missing hotel amenities that customers are looking for?  | We believe `that by improving the experience of selecting and deciding which of our hotels to stay at` for `users of our website` will result `in an increased number of hotel bookings`.

#### Step 4 - State the goal(s) for the research
- Goals need to be specific enough so you’ll know when you’ve reached an answer, practical in that you could answer them within the scope of a study, and actionable in that you could act on your findings once you’ve completed your research study.
- The goal is the central question that has to be answered by the research findings.
- Always start goals using a verb such as identify, understand, learn, gauge, etc.
- Limit the number of goals you define per project. Try to learn one or two things very well. This will help you connect your research to a design outcome and emerge with a clear understanding of one aspect of user behavior.

| **Start thinking of a problem** | **Questions we need answers to** | **Hypothesis** | **Goal** | **Objectives**
| ------ | ------ | ------ | ------ | ------ | 
| Let’s imagine that a hotel chain has noticed they have had a lower number of bookings in the last few quarters, but they are unsure why. | Are people not booking because they don’t like the hotels we have? Do we have issues with the website or app? Are our prices too high? Are we missing hotel amenities that customers are looking for?  | We believe `that by improving the experience of selecting and deciding which of our hotels to stay at` for `users of our website` will result `in an increased number of hotel bookings`. | Understand how people make their travel plans.

#### Step 5 - Create research objectives
* A well written list of research objectives: 
    * Delineate and align with the goal of the project.
    * Define the overall high-level approach and the questions you might ask.
    * Dictate the most suitable methods and tools at your disposal.
    * Determine the outcomes you will get from the study.
    * Need to be high level, but specific enough that research can provide a concise answer for each.
- Create no more than 4 objectives per research effort. If you try to achieve more than 4 objectives in one study, you are doing too much, as each objective will represent up to a dozen questions/tasks in your discussion guide.
- Review the list of the ‘Questions we need answers to’ and identify the themes you see there. Reference the 'Hypothesis' and the 'Goal(s)' you have previously written. 

| **Start thinking of a problem** | **Questions we need answers to** | **Hypothesis** | **Goal** | **Objectives**
| ------ | ------ | ------ | ------ | ------ | 
| Let’s imagine that a hotel chain has noticed they have had a lower number of bookings in the last few quarters, but they are unsure why. | Are people not booking because they don’t like the hotels we have? Do we have issues with the website or app? Are our prices too high? Are we missing hotel amenities that customers are looking for?  | We believe `that by improving the experience of selecting and deciding which of our hotels to stay at` for `users of our website` will result `in an increased number of hotel bookings`.  | Understand how people make their travel plans. | Identify ways people start planning their travel and the tools they use. Understand what elements make it easy for people to plan travel and what elements make it difficult. |

The chart below shows the relationship between your research goal and the tasks and questions you will ask your participants in usability tests. 

![The relationship between your research goal and your tasks and questions](/images/uxresearch/Research_Goal_Obj_Questions.jpg)

This chart shows the relationship between your research goal and the interview questions you will ask your participants in user interviews. 

![The relationship between your research goal and your interview questions](/images/uxresearch/Research_Goal_Obj_questions_interviews.jpg)

As you can see, the more objectives you start out with, the more questions you will need to ask and the longer your research session will be. It's a good rule of thumb to not have the user session last longer than 1 hour. Our typical research sessions at GitLab last 30-45 minutes. 

### How to write a strong hypothesis

<!-- blank line -->
<figure class="video_container">
  <iframe src="https://www.youtube.com/embed/i-LIu-zDOOM" frameborder="0" allowfullscreen="true"> </iframe>
</figure>
<!-- blank line -->

#### Video transcript

When you hear a customer problem, it can be tempting to just dive right in and devise a solution. However, it’s important to remember there is never just one good solution to a problem. A problem can be solved in many different ways, depending on what we need to focus on. 

Users can also be unpredictable, what we think might solve their pain points, may not actually even begin to address the problems they are facing. Therefore, it’s advisable to test your ideas before you start building a solution. A way in which you can do this is to write and test hypotheses. 

A hypothesis is basically an assumption. It’s a statement about what you believe to be true today which can be proven or disproven using research.

A strong hypothesis is usually driven by existing evidence. Ask yourself: Why you believe your assumption to be true? Perhaps your hunch was sparked by a passing conversation with a customer, something you read in a support ticket or issue, or even something you spotted in GitLab’s usage data.

There are lots of different structure for hypotheses, but I recommend using this simple statement:

> We believe [doing this] for [these people] will achieve [this outcome].

The statement is comprised of three elements.

The first part: `We believe [doing this]` should detail your proposed solution to users’ problems.

The second part: `For [these people]` should identify who you are targeting.

The third and final part: `will achieve [this outcome]` is where you should document your measure of success. What is your expected result?

For example:

We believe `storing information about how an incident was resolved, how long it took to resolve and what the outcome was in a historical record` for `engineers responsible for incident management` will achieve `a 20% faster resolution time for incidents`. This is because referring to past incident information helps to inform potential solutions for remediation.

When writing your hypothesis, focus on simple solutions first and keep the scope small. If you’re struggling to articulate your assumptions about users, it’s probably better to start with developing a better understanding of users first, rather than forming weak hypotheses and running aimless research studies.

A strong hypothesis is easy to test. It shouldn’t take you much time to design a research study to validate or invalidate your hypothesis. 

If your hypothesis is invalidated by users, don’t feel disheartened. You’ve stopped precious Engineering time being spent on building a solution that simply doesn’t solve users’ problems. A good measure of being iterative is throwing something away because user research proved that it wasn’t going to work. You’re not always going to get things right the first time. We learn more about user needs as a result of testing multiple hypotheses and, in turn, we generate new ideas for future rounds of testing.