Vous voulez un aperçu concret de notre outil ? **Testez-le gratuitement !** Et n'hésitez pas à nous contacter pour en savoir plus. 

Essayez gratuitement

Démarrez gratuitement

Se connecter

Emmenez-moi à l'accueil !

Oups, vous êtes perdu !

Tests utilisateur optimisés par l'apprentissage automatique

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-5RZTTPW"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

Vous avez une **Question?**

OPEN-GRAPH-FR.png

Odaptos | FAQ

Centre de ressources

Odaptos | Ressource Center

Bienvenue chez Odaptos

Retour au centre de ressources

Le **Blog** Odaptos

Odaptos | Blog

Bienvenue à

Retour au blog

Payez seulement pour ce dont vous avez besoin.

Tarifs

Titre Conditions d'utilisation

Conditions d'utilisation

Contact

Menu Utilisateur

**Presse** d'Odaptos

Bienvenue à la page de

Revenir à l'accueil

Cas d'**usage** 

Découvrez nos

Revenir aux cas d'usage

S'inscrire

Nous avons hâte de vous montrer comment Odaptos peut vous faire changer la manière de comprendre les émotions de vos utilisateurs. 

Inscrivez-vous à la newsletter

medium_imt_mines_ales.png

small_imt_mines_ales.png

thumbnail_imt_mines_ales.png

imt_mines_ales.png

thumbnail_axlr-satt-montpellier-logo_bleudeprusse.png

axlr-satt-montpellier-logo_bleudeprusse.png

medium_BPI-france.png

small_BPI-france.png

thumbnail_BPI-france.png

BPI-france.png

thumbnail_logo-Occitanie-rect-1.png

logo-Occitanie-rect-1.png

medium_crealia-logo.png

small_crealia-logo.png

thumbnail_crealia-logo.png

crealia-logo.png

Do you want a concrete overview of our tool? **Test it for free!** And don't hesitate to contact us to find out more.

Try for free

Try it Free

Log In

Take me Home! 

Oops, you're lost!

Got a **Question?**

OpenGraph@2x.png

Resource Center

Odaptos | Resource Center

Welcome to Odaptos

Back to Resource Center

The Odaptos **Blog**

Welcome to

Back to Blog

Title Terms of service

Terms of service

Back To Legal

User Menu

The Odaptos **Press Page**

Back to the Home Page

Use **Cases**

Discover our

Back to Use Cases

Register now

We can't wait to show you how Odaptos can change the way you understand your users' emotions.

Subscribe to the newsletter

# What is usability?

It is always difficult to admit that a finished product does not fulfil the user's true need, or that it is too complex to handle. It is also important to note that the more involved a team is in the conception, development or marketing of a product, the more difficult it is to recognize the tasks the users will want to accomplish differently or the difficulties they will encounter.

If you are currently at this stage of development, or if you would rather avoid it altogether, it is probably time to make some room for improvement and for the iteration of your process.

There are several methods of research on the user's experience, but usability tests are deemed the most relevant when it comes to thoroughly understanding your users, their  feelings towards your product and the use they will make of it. 

## Usability testing 

The goal of usability tests it to make your final product easier to use. Each of the tests you conduct informs your objectives in relation to the adjustments, modifications and improvements that need to be made in the future.

Usability tests are not 'debugging' sessions. They allow you to analyze the users' journey and emotions as they experience your product, as well as the ease – or on the contrary, the difficulty – with which they handle its functionalities. It is consequently essential to resort to those tests during the development phase.  

Your actual users are the participants of these tests. During the tests, they use your product to perform the tasks they would perform in a real-life scenario. With the observation and recordings of what they do, say and feel during the tests, you can significantly reduce the  bias-effect that most development teams suffer from when it comes to using the product.

The tool that we have designed is here to assist you as you carry out usability tests and to help you understand the participants' gestures, comments and emotions in depth. 
Because it is backed by Artificial Intelligence, our tool produces full and thorough reports which allow for hassle-free development. 

## The goal of user tests

### Inform and understand the product experience

The main objective of these usability tests is to allow you to enhance your product's overall usability, through the collection and subsequent synthesis of the data on the participants' experience during the product handling phase. 

This **synthesis/compiling** will show you if your product:

- targets the right audience
- is easily handled
- helps the users reach their objective
- provides a satisfactory – or, in a best-case scenario, delightful – user experience 


### Flush out problems and frustration

As you eliminate friction points in the user journey, you not only foster a positive customer relationship, but you also make sure your products and their user experience are perceived as being high-quality in a durable way and across all of your products.

In order to achieve this, there are 4 key principles you need to follow:

- Give the user control
- Be coherent
- Optimize User-Computer interactions by offering adequate responses (mouse-click animation, confirmation message, error message, ...)
- Find the balance between the cognitive load necessary during product usage and the user's attention span


### Enhance profitability

If following these principles is part of your objectives, reaching those goals will allow you to minimize the risks of your product/new functionalities being badly received upon release. Their impact will benefit your brand image and will by extension allow you to boost your sales.
  
The recordings and results history which comes with our tool will allow you to maintain and even enhance your quality standards for your product's future iterations.                 

Finally, by creating products focused on the user and the use they make of it, you reduce the workload of the product's support service.


**Here are the nine rules that you need to follow in order to enhance a product's usability:**

1. Use an understandable language
2. Adapt to the user's vernacular
3. Facilitate the user's task
4. Be coherent
5. Facilitate the dialogue with your users
6. Offer a clear and suitable browsing
7. Offer shortcuts
8. Offer failure feedbacks giving insight on what corrections need to be made 
9. Minimize the risks of failure




## What is the right time to plan Usability Tests?

**An agile methodology : Design / Testing / Development**

“Agile” software development refers to a set of methodologies based on an iterative system in which demands and solutions evolve thanks to the collaboration between inter-functional, self-organized teams. 

User-focused development is fundamental when it comes to the conception of products. It Is particularly important during the first steps of conception, as with the iterative methodologies. Consequently, it is crucial to adapt the concept to fit the agile methodologies in order to generate the user feedback which will lead to increased usability and, as a result, increased user satisfaction.

Data-driven design is at the basis of the researching phases which happen prior to a product's development. Even though it is massively employed, this approach's fragility is rooted in it being impersonal and limited to the data collected before development. It does not include, from the product's development to its launch, human data provided by actual users.

Putting into place a methodology that allows a development team to collect images, comments and feelings generated by the handling of your product really brings added value to the development process. 

Development teams are so familiar with the product they are working with that they lack distance and perspective, which can lead them to regularly miss important or critical issues which the users will then face. These problems unfortunately often persist up to the finished product. 

With the platform we offer, the users' emotions and comments are seamlessly implemented in the agile process, thus reducing the often too great amount of time, energy and money alloted to code or functionalities refactoring. 

## Useful resources:

[234 Tips and Tricks for Recruiting the Right Users as Participants in Usability Studies ](https://media.nngroup.com/media/reports/free/How_To_Recruit_Participants_for_Usability_Studies.pdf)
**- NN Group**

[How to Conduct Usability Studies](https://www.nngroup.com/reports/how-to-conduct-usability-studies/) - **NNGroup**

--

**How to Plan, Design, and Conduct Effective Tests** - Jeff Rubin, Dana Chisnell

**A Practical Guide to Usability Testing** - Joseph Dumas, Janice Redish

-- 

**The Design of Everyday Things** - Don Norman

**Flow: The Psychology of Optimal Experience** - Mihaly Csikszentmihaly

large_Group 41.png

medium_Group 41.png

small_Group 41.png

thumbnail_Group 41.png

Group 41.png

Your product will be chosen if it rises up to the users' expectations, demands, and if it helps them reach their goals. In a world where we are constantly switching from one task to the other, your goal is to make their journey easier by ensuring the use of your product is intuitive. But ultimately, it is the persons who will use it who will be the judges of its usability.

Introduction to UX Design

# How to plan a usability test

To plan a usability test, you need to define the following elements: 

- The test's objectives
- Researching approach
- The test moderator
- Types of participants – [How to select your participants ](https://www.nngroup.com/reports/how-to-recruit-participants-usability-studies/)
- List of tasks – (Available template in Odaptos App)

These elements will allow for a structured study and ensure that the resulting data is trustworthy.


## Who to choose as the test moderator?

The moderator is crucial when it comes to carrying out a usability test. If your organization does not include a team or a person dedicated to the user experience, we will present you with a list of options as to who in your team is best qualified to endorse this role.

Please note that it is not advised for the product creator to conduct the usability tests. It is inherently difficult to remain impartial about your own product and to avoid guiding the participants, even unconsciously. Of course in practice, if the creator is the only person available to carry out the test, it remains a possible option. 

> In the words of the Nielsen Norman Group (NN/g) **Testing is always better than no testing.**

Among the usual work-positions existing in a structure, we have identified the following as the ones best suited to become the test moderator:

### Social, Behavioral specialist, UX Designer

Because of their ability to analyze humans, they are the candidates of choice to perform these tests and to bring out concrete leads on what needs improvement.

### Marketing Specialist

Qualified marketing specialist would also be good moderators. They are user-oriented and know your product offer, so they would be able to ask the participants the right questions.

### Technical Writer

This profile can be a fit as well. Technical writers could carry out usability tests because they possess a global vision of your project, your industry and they know how to present a product to the end user. 

If none of these profiles is available to you, you can also ask a colleague who does not work directly on the project but who is in the same marketing sector to carry out the test. Once the test is prepared and its tasks planned, you can hand it over to them. This way, the test has no risk of suffering from bias. You can then return the favor by carrying out their product's usability test.


## Required characteristics and skills

- Good learning ability
- Listening skills
- Good human relation skills
- Flexibility
- Empathy
- Good communicator
- Effective organizer and coordinator

## Finding the rights participants

Selecting your participants is an essential part of the usability testing process because your test results entirely depend on it. To successfully complete this stage, you need to have identified your product's target.  This target corresponds to your “personaes”, which have usually been established at the beginning of a project. 


## Finding pools of participants

Now that you have identified your target, you can start soliciting your future participants. Here is a list of potential sources:

To begin, you can start **working with your co-workers**. You can start figuring out what your exploration zone is and make the first adjustments. The collected data will be interesting to use, though it will undoubtedly be very different from the one you get from your end users. Mainly because of their affiliation to corporate culture/the company's culture/the organization's culture, and because of what they know of the product, the data will inevitably be biased. But in spite of this these participants serve as a viable additional source of material. 

**Your family and friends** can also be a good pool of participants if they share characteristics with your target. In that case, it is advised that one of your co-workers or partners carry out the test so as not to let your personal relationship affect the results.

**Your existing clients** are experienced testers who are familiar with your products and who will provide you with clear leads on what needs improvement. It is however still necessary to find targets who have no experience using your products in order to acquire contrasted views. When prospecting for clients, do not forget to mention that your prospecting is not part of a marketing strategy, but rather part of the improvement process of your future product and of the overall user experience. 

**Associations.** If you or your partners are part of associations, you will probably be able to find people who fit your target. These groups might also manage blogs or forums on which you can do your prospecting. 

**Your professional network, your partners and the participants who have already been tested.** You can ask your network and your partners if they know people in their own circles who fit your target and are willing to participate in a test for your product. Finally, do not hesitate to ask your participants if they know other people in their circle who might accept to be part of the study. 


## How many tests do I need to run?

[According to the NN Group studies](https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/), you can start by carrying out a quality study by having 5 persons participate in the usability test. These tests should allow you to understand up to 80% of your product's issues. 

Once these issues are solved, so start collecting quantitative information, you can involve up to 20 additional participants to understand in more detail what the user journey is like or how functionalities are handled.
[Study from the NNGroup](https://www.nngroup.com/articles/quantitative-studies-how-many-users/)

Thanks to our tool you can run these quantitative tests in a simple, efficient and cost-effective way. 
The more you increase the number of participants, the more issues you will be able to identify and fix.


## Create a Scenario


It is common practice to put a scenario in place for your test in order to introduce the participants to the context you have pre-defined. This scenario, which should be a few lines long, will allow them to immerse themselves in the use of your Product's/Service's, in a range of usage that is neither too large nor too narrow. 

*“You wish to use the new version of your company's messaging program. To accomplish this, you will create a user account and use the messaging program's main functionalities in order to familiarize yourself with them.”*

The goal of this test is to identify usage issues. You have to focus your attention on creating **essential tasks** for your product, because the more defined these tasks are, the more efficiently and quickly you can troubleshoot your product's usage issues. Such tasks are: 


- exploring potential problems linked to usability
- based on your interests and experience
- the ones that the participants will accomplish with your product
- derived from other criteria

Based on this list, you can elaborate a guiding thread which will lead participants through their user journey. 

Here are some examples of the tasks that need to be carried out in order to test a messaging service: 

- Create an account on the platform
- Log onto the inbox
- Create a new message
- Save a draft
- Modify a draft
- Attach a file to the message 
- Send a message
- Forward a message
- Delete a message
- Find a deleted message 
- Create labels to sort messages
- Move messages to different folders
- Sort messages in a folder
- Select all messages in a folder
- Set up an automated filter for incoming messages
- Tag messages as 'Read'
- Log out

It is crucial to organize these tasks following the order in which the participant is likely to carry them out. This will make them easier for your user to understand.

It is also preferable to ask the questions that matter to you the most at the beginning of the test, so that they can benefit from the participant's maximal attention and are sure to be answered in the test's allotted time. 

> **“A good task is a task that allows you to detect usability issues.”** - “A Practical Guide to Usability Testing” by Joseph S. Dumas

In order to efficiently frame your test, it is best to create “sub-scenarios” for **each of the tasks** you have listed. These scenarios will contextualize the steps of the test and guide your participants. 

These scenarios must be short (no more than two lines) and phrased in the participant's everyday language (and not in the technical jargon used by developing teams). 

A good scenario gives enough information for the user to be able to understand and carry out the task you have planned for them. 

Make sure, however, that you are not giving away too much information when you describe the task, as it could influence the test results. 



## Useful resources

[234 Tips and Tricks for Recruiting the Right Users as Participants in Usability Studies ](https://media.nngroup.com/media/reports/free/How_To_Recruit_Participants_for_Usability_Studies.pdf)
**- NN Group**

[How to Conduct Usability Studies](https://www.nngroup.com/reports/how-to-conduct-usability-studies/) - **NNGroup**

--

**How to Plan, Design, and Conduct Effective Tests** - Jeff Rubin, Dana Chisnell

**A Practical Guide to Usability Testing** - Joseph Dumas, Janice Redish

-- 

**The Design of Everyday Things** - Don Norman

**Flow: The Psychology of Optimal Experience** - Mihaly Csikszentmihaly

large_Group 42.png

medium_Group 42.png

small_Group 42.png

thumbnail_Group 42.png

Group 42.png

Usually, this part of the process is carried out through a collaboration between the different teams involved in the product's conception, development and marketing. Together, the teams formulate the issues they wish to solve and create a common document to list them all.


Planning a usability test

# Key principles on usability test methodology

The key principles of the methodology of usability tests are based on the conventional scientific lab-testing approaches. You formulate an hypothesis regarding an issue that needs fixing, and then you analyze the causes and effects as well as their relation with each other in order to draw conclusions.


## The attitude to adopt during a usability test

Before running a usability test and benefitting from its results, it is first necessary to understand creator does not equal the user.  To ensure this, NN Group has crafted a list of recommendations, in the collection “230 Tips and Tricks for Better Usability Testing”, whose goals are to help craft and run the most efficient usability tests possible. Here are the nine recommendations that we consider essential: 

1. Stay humble.
This sums up in two words what your state of mind needs to be throughout the whole test. 

2. Make sure your product's functionalities and their ease of use are optimal. Do not hesitate to involve your teams in this consideration process. 

3. Regularly check the standard of your working process. 

4. Find ways to maintain or enhance your skills.

5. Keep track of the existing publications in your area of expertise.

6. Avoid what has to do with personal opinion and, as much as possible, base your approach on hard data. 

7. Avoid making developing decisions based only on the users' opinions. “Don't tell me, show me!” should be the formula for any usability test.  

8. Do not test your own creation. No one is impartial enough to efficiently appraise criticism on what they have created. It is however preferable to test your own creation than to not test at all, if it is indeed the only option available to you.

9. It is entirely possible to have a previous participant test the product again once modifications have been made. This can even be particularly beneficial since the user already knows the product, and will thus be able to provide more in depth remarks. The results might however be biased, seeing as this will not in fact be the first time that the participant handles the product, and might want to prove his or her previous remarks were accurate. 



## Interaction with the participant:

If the creator has no choice but to endorse the role of moderator during the test, it is essential that he or she has as little interaction with the participants in order to fully benefit from the user / platform interaction. These interactions must be tailored in a way that reveals the product's issues and their origins. 

In the same way, the creator-moderator has to be as impartial as possible during the product's presentation, in order not to influence the participants. Any attempt at justification, resolution or explanation offered to the user – about a functionality still being in development, for example – are to be strictly avoided.  What has to be kept in mind throughout the test is that its goal is to highlight problems. The steps of understanding what these problems imply and how to solve them have to come after the test.  

Finally, it is necessary for the participant to feel confident during the test in order to guarantee conclusive results. This implies formulating to them that it is normal to make mistakes and that there is no right or wrong answer. We are assessing the product's performance, not the participant's. If participants encounter difficulties during their journey, it will surely be coming from the product and not the user. 

Generally speaking, the moderator will ask as few direct questions as possible. This will leave room for the participants to express themselves. The recommended questions are those which do not await a right or wrong answer. For example: 

- What are you thinking about right now?
- You seem surprised / confused / frustrated. What's happening?
- Is there anything here that is different from what you expected? 
- Do you believe that this piece of information should be provided?
- Is this close to what you were expecting?

It is important to treat each participant as individuals and to interact with them without taking previous exchanges into account. 

In order to bring out as much information as possible from the participants, several techniques can be used:

## Thinking aloud 

**Description**

This method's objective is to bring out the issues that participants face through their commentary. This verbal protocol allows them to think out loud and to better understand their feelings during the test. 

It is also important that the participants verbally convey their emotions for the purpose of later reviewing the test's video recordings. 

**Pros:**

This technique allows you to record the participants' emotions and their journey without having to ask them questions.

Throughout the test, the participant provides clues as to what the sources of the issues are and what can be done to troubleshoot those issues.

The participants are usually more focused when describing their actions and experience out loud. 

**Cons**

Certain participants might struggle to follow this method.

On the one hand, the “Thinking Aloud” process can slow down the test and add further strain on the participant's cognitive load. But on the other hand it greatly improves the quality of the obtained results. 

**How to improve this experience:**

By experiencing it yourself: the creator/designer takes the time to think out loud when testing his or her own product. 

The moderator can ensure that the participant feels heard by nodding or expressing approval at the user's remarks. This is a very effective way to encourage the participant.

By paying attention to and respecting the participant's pauses and silences: they generally signal that the user is focusing on overcoming an obstacle. This allows you to identify a friction point and to observe how this obstacle can be overcome.


## The five “Why”

**Description**

Thanks to this easy-to-use method, it is possible to go all the way up to the source of each of the issues that the participant encountered. It allows you to identify the cause not through supposition but by having the user describe the issue he or she is facing. It is applied by asking the participant a set of questions, each reprising the problem raised in the previous question. By doing this, you can get to the heart of the problem and find its source:

Why can't you log on?
*I can't find the login button.*

Why can't you find this button?
*I'm looking for it at the top of the page but there isn't any interaction available.*

Why are you looking at the top of the page?
*This is where I usually find the login button or the access to my account.*

By using a few quick questions you have been able to grasp what the issue was and find a suitable solution which could fit your product.

**Pros**

- It is easy to put in place.
- It allows you to go to the heart of the problem;
- It allows you to find solutions quickly;

**Cons**

- The participants can answer the same question in many different ways.
- It is necessary to take some time to condition the participant before asking the set of questions.
- It cannot be used too often as it could become frustrating for the participant. 

Finally, it is essential to remember that the moderator should only help the participant as a last resort. This aspect is detrimental to the identification of usability issues on a platform. This is a tricky exercise because providing help to someone who is struggling is instinctive. The appropriate alternative is to encourage the participants to voice their impressions.

The times when the user faces difficulties will be the foundation which will allow you to formulate future improvement hypotheses.  There is nothing more convincing to a sceptical designer or lead product manager than seeing a video recording of a user who is not able to carry out a task on their platform. 

## The Results of Usability Tests

Once all of the tests are run, we will present you with a detailed analysis. Using the data collected during the test sessions, we will create a general report which will highlight which participants had difficulty using your platform and which tasks the participants struggled with the most.  
“See section – Comparative analysis”

You also have access to a detailed analysis for each of the tests that was carried out, so as to thoroughly understand where the participants succeeded and where they failed.
“[See section – Individual analysis](https://odaptos.com/fr/centre-de-ressources/#Analyse%20de%20l’émotion)”

## Prioritizing Problems

After the major issues faced by the participants have been identified, you need to classify those issues and to find the balance between how much effort needs to be put into fixing them and how much you will benefit from it. 
It is also advised that you create a comparative list of the friction and satisfaction points that were identified during the tests.

[According to NNGroup, you can prioritize your list using 5 degrees of importance for the issues that require your attention.](https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/)


0 = False positive, the problem raised does not require any fixing.

1 = A graphic design problem, to solve if there is enough time to do so.

2 = Minor usage issue: to put in the 'necessary but non-urgent' resolution category. Those are issues that have to do with spelling, typography or spacing for example. 

3 = Major usage issue: high-priority, important to solve. This can foster frustration during the use of your service or product. 

4 = Usability disaster: it is imperative that this issue be fixed before the product's release. Top-priority. For example, the payment system is not working, or the user cannot log onto the platform, etc.



## Making changes on the product/the procedure – an Agile methodology

It is time to take the necessary measures to improve the product. Ignoring or delaying this step will lead to usability issues. If the product is launched with these issues, there is a high chance that it will not be successful on the market. 

### Discuss the results with your team

The objective that is central to usability tests is to create or improve a product/service that your clients will use and appreciate. 

It is important to include the different parties that were involved in the development of the product in the analysis of the results from the usability tests. Each member will have the opportunity to better grasp the issues encountered and to actively participate in fixing them.

### Set goals for yourself and your team

Depending on the degree of importance assigned to the identified issues, it can be very useful to make projections of the impact that solving them can have for your product. 
The ROI methods will be useful for you prior to the UX research stage, but also when implementing your product's functionalities. 

### Additional testing for improved results

Once the necessary modifications and improvements have been made after having been identified with the usability test, it is particularly useful to repeat the research process, even with limited range, as it would allow you to check and confirm each iteration.  

As of today, user experience methodologies do not allow for multiple tests on the same product. Because they are carried out manually, these methods are time-consuming, can become costly and do not fit the rapid production model that the market dictates.  

Because it can be implemented instantaneously and is cost-effective, the solution we offer will integrate seamlessly in your Agile development and your swift user experience research process. If you are not already familiar with it, this [introduction to UX research](https://odaptos.com/guides/what-is-usability#what-is-the-right-time-to-plan-usability-tests%3F) will allow you to better understand the aforementioned Agile methodology. 

Lastly, if you do not know where to begin when it comes to using our software, please refer yourself to this part of the [Odaptos user guide.](https://odaptos.com/resource-center/)

large_Group.png

medium_Group.png

small_Group.png

thumbnail_Group.png

Group.png

Remember you are here to facilitate not to guide or influence.

UX interview guide

Our Guides

# About the app

We created this document to guide you on the usage of Odaptos services.
No matter what your level of experience, you should be able to find an answer to all of your questions in this document. We cover everything from the navigation in the interface to the optimal use of the various functionalities.

## How to create a Project
### Create a project - A Test

In the Odaptos app, you will find a button to add a project to your workspace.

Create a Project.mp4

You can also add a test to an already existing project.

### Configure your project & test

In this space you can fill in the fields detailing your project, then your test. The addition of a keyword will allow us to advise you of the contents of help according to your sector.

FIll the project.mp4

### Choose your plan

We offer the possibility of choosing between three different types of plans.

- **Freemium** allows you to perform 1 test of 10 minutes with 3 tasks.

- **Basic** allows you to carry out 30-minute tests with 10 tasks costing 1 credit of € 50 per interview.

- **Advanced** allows you to carry out tests of 60 minutes with an unlimited number of tasks costing 2 credits or 100 € per interview.

You have the possibility to choose the number of interviews that you wish to carry out in your research and then to go to the purchase summary.

Choose your plan.mp4

We also offer corporate subscription plans based on a yearly contract

Subsequently, when placing the order, we invite you to enter your bank details in order to make your payment. We use the Stripe payment platform to secure your transaction data.


## Configure your test

### Add Tasks to Your Test

In this section, you must enter the tasks to be performed by your user.
They will allow us to architect the results at the end of your interview.

To add a task, you can either create your first task by clicking on the button **create a task.**

Add a Task.mp4

You can also use one of our **interview models** that will allow you to select a curated list of common tasks to structure your interview.

Add a template.mp4

We have also created a guide to help you with the creation and architecture of your interview. [Plan your usability test.](https://odaptos.com/guides/planning-a-usability-test)

**Warning:** When you have done your first interview you will no longer be able to change the tasks asked of your tester at the risk of compromising the results of your research.

### Add a scenario & an URL

You can complete the scenario in the field to the left of the tasks.

In the same way as the scenario, you can add a starting URL for your user which will be provided to him in the chat at the start of the interview.

Add scénario and URL.mp4

Adding a scenario will allow your user to put himself in a state of mind allowing you to better perform the requested tasks.

This scenario will be displayed in the chat at the start of the interview.

### Adding notes

You can add notes to your interview in the space below the task. These notes are personal and your user will not see them. You will have access to it during the interview in order to help you guide the interview.

Add Notes.mp4

### Invite a Tester

When you have planned the tasks that will guide your users during the interview, you will have the possibility of inviting your users to take your test.

Name and Adress.mp4

We have created a section relating to the invitation of your testers in our guide 
[Find the right participants](https://odaptos.com/guides/planning-a-usability-test#finding-pools-of-participants)

### Configure your interview date & language

You have the possibility to test in 4 main languages ​​(French, English, Spanish, German) and their varieties .

Date and language.mp4

### Add interviews slots

Here you can add new interview slots to your test to increase the accuracy of your usability research.



Add Interviewee.mp4

The interview slots that were already added to the test correspond to the number of users you selected during the test creation.

### Viewing Test Details

You can view the details of your test in the Details section to view the information you entered when creating the test.
In the payment section, you will be able to see your purchases and download your invoices.

Details of the test.mp4

### Access your Dashboard

Now that you have configured your test and invited your testers, you can see your next scheduled interviews displayed in your Dashboard.

Launch Interview.mp4

## Operation of the interview room
### Interface of your videoconference

You are now in your interview room, your user has joined the video conference and you see it displayed on the right of your screen.

- The main screen shows you your user's screen sharing in real-time.
- The toolbar at the bottom of the screen allows you on the one hand to start recording the interview and send the first task to the user.
- You have a summary of your progress in the interview with the various tasks that you configured before the test.

Interview.mp4

**Tip** : Do not hesitate to consult our [UX interview guide](https://odaptos.com/guides/ux-interview-guide)

### The Chat

Below you will find the chat in which you can communicate in writing with your user, he will find the scenario and the URL if you have filled them.

### The timeline bar

The timeline allows you to see the time remaining on your interview as well as the markups already placed.

**to know:** The interview will start recording 2 minutes after all the participants have joined. Likewise, in the end, we will grant you 5 minutes to wrap up the interview with your tester. (the 5 minutes will not be considered part of the interview on the results).


### Markups

You have the possibility to mark the video with several mark-ups allowing you to quickly return to your key points of the interview during the results view.

### The tasks and the start of the recording.

To start the interview, you can either start the first task or use the record button at the top right of the screen.

## The results of your Research:
### Consult your overall results / Meta-analysis of your interviews

Your dashboard also allows you to consult the tests carried out, to see there displayed a first overall result of the feelings of the users tested on your platform, the percentage of positive tasks as well as the most difficult task.

Dashboard.mp4

### Understanding how Meta-Analysis works

In this meta-analysis part of your interviews, you can see the user's individual tasks and their predominant feeling about the task performed.

User sentiment.mp4

**Tip:** The more you test, the more accurate your results will be. A study by Don Norman's NN Group explains that for research, 5 tests make it possible to understand the major problems encountered and that to obtain more details on your results, 20 tests allow you to make a complete analysis as much qualitative as quantitative.
[How many tests do I have to do?](https://www.odaptos.com/guides/planning-a-usability-test#how-many-tests-do-i-need-to-run%3F)


You can access your interview through your dashboard or through your results page.

### The different features of your recording

We have created a recording for you that will allow you to save time while viewing it.
You can navigate your interview in 3 different ways.

#### Emotion analysis

The Interview analysis by Artificial Intelligence allows us to give you access to the person's feeling throughout your interview and gives you the opportunity to '' quickly access the most important pain points of your test, but also you can access the most positive and neutral points.

Navigation Sentiment.mp4

**Tip:** The lowest bar of the data-visualization allows you to navigate through the tasks posed to your users. 

#### Markups

The markups you placed during your interview allow you to go back to the moments that you deemed most important in the interview.

#### Chat

Thanks to the audio transcript of your interview, you can go directly to your user's sentences and watch their interactions on your platform.


**Tip:** In our interview guide, you will find a section on [analyzing the results of a usability test](https://www.odaptos.com/guides/ux-interview-guide#the-results-of-a-usability-tests), do not hesitate to consult it!






We are constantly updating our guides and documentation, here you should find everything related to user experience and usability testing, we have listed some of our most essential guides below.