At BAM, our role is to make sure that your product appeals to users. For that, there is no magic recipe, you have to test and iterate. The longer you wait to test, the higher the modification costs will be. You must therefore regularly test your hypotheses at each stage, from the paper draft to the final phase of the project, and even after production.

However, carrying out tests can require a lot of organization and time. So how do you choose and pass your tests and validate your product experience?

Here are the first steps that should not be overlooked:

‍

1. Recruiting your users

The target should be as accurate as possible. Who is your product for? Make a list of the characteristics of your typical users:

• Demographic profile
• Age
• Digital experience
• Mobile/tablet/desktop use
• Center of interests etc.

‍

Use the tools already at your disposal

• A database retrieved following an online questionnaire that you sent during your user research phase
• A database of your customers
• Your own coworkers/family/friends if they are in the target

‍

Recruiting via Twitter, Facebook, Linkedin?

When you send an email or post an announcement to recruit your users, specify who you are, the purpose of your tests, the users you are looking for, the dates and slots of the sessions, and the rewards.

Tips: Add an image to your post to make your message even more engaging and understandable at a glance. For that, you don't need to be a designer, you can use Canva.

Example:

Hello.

We are looking for testers for our e-commerce project.

WHO

People living in Île de France and Paris (between 25 and 50 years old) who:

• Are used to ordering their groceries online
• Tried to do their online shopping and gave up,
• Would like to order their groceries online but have never tried.

PROJECT

A mobile e-commerce platform for a G20 store chain, U Express on Ile de France.

WHEN AND FOR HOW LONG?

Wednesday 07/11 and Thursday 08/11.
Allow about 1 hour.

WHERE?

At BAM or by videoconference.

‍

How many users do you need to recruit?

For the sake of time and cost, 5 users is a minimum because it makes it possible to find 80% of usability problems according to NN Group.

Reward your users who travel for tests. This will give them additional motivation to test your product. You can offer them a voucher, goodies, a promotion on your product when it comes out etc.

‍

2. Choosing an appropriate methodology

There are several methods to carry out your tests; Guerilla or Quick and Dirty in the early phase of your project; A/B testing to test 2 alternatives, face to face with a user in a “laboratory” etc.

NB: For more details on the various tests, consult the first white paper dedicated to Af83 testing : unavoidable.

To do your tests you do not need a large amount of equipment. For a classic “laboratory” test. Your computer equipped with a webcam may be more than enough. For example, use Quicktime to record the screen (don't forget to check “show mouse clicks”).

For mobile testing you can use Lookback.

For remote testing, you can use Skype, Zoom, Hangout for example.

‍

3. Prepare

Upstream of your tests, You will have to write the test scenarios (upcoming article: How to write an effective scenario for your user tests?).

Your users will be much more comfortable using computers or phones that they are used to using.

If you have test mobiles or computers, ask them what they prefer to use and before your test make sure that the site or app works properly.

‍

4. Plan

At BAM, we plan 4 to 5 1-hour slots spread over the week. Remember to leave some extra time at the end to debrief. Approximately 10-15 minutes to share the learning with your partner.

The tests can be carried out by the agile coach, the client, a designer or a developer.

During the tests, you must:

One person to guide the user and ask the questions, and a person To take notes and ensure that all stages of the scenario have been tested by the user. Both people are completely free to call and ask questions.

If you are guiding the test, be careful to what your user does. If the same person asks the questions, looks at the journey, and takes notes, you may miss out on important elements of their journey, and you won't be able to go deeper by asking questions like “Why is this bothering you? What would you have imagined you could do? ...”.

‍

Conclusion

1. Define with your team the type of tests you want to do (tests on the production site, on models, quantitative or qualitative tests...)
2. 1 to 2 weeks before your tests, anticipate the recruitment of users and schedule all your slots.
3. If it is very difficult to recruit users (specific target), motivate and thank your users by offering them something.
4. Prepare your test scenarios so you don't forget anything.
5. Make sure you always have 2 people to carry out the tests and form your partner before the tests.