You need to document the test, partly to remember what happened during the test but also to be able to share it with the team. In the team, you will then look through the documentation and arrive at insights and lessons about the idea and about the prototype.

How you document the test depends on your prototype.

1. Paper and pen

If you are testing a simple prototype, it may be enough to just write down what happens during the test.

Advantages of writing are that it is simple and that most testers feel comfortable with it. The disadvantage is that it can be difficult to have time to both record everything that is said and done during a test.

Here you will find a template that will help you organize your notes.

Test template

Download test template

Tip! Feel free to write down memorable quotes from the tester. You can use them later when you talk about your idea with others.


2. Record

If you are going to test a complex prototype, it can be good to record the test. Either you record the sound or film.

Record test with your mobile camera

The advantage of recording is that you can capture all the feedback that the tester gives (both speech and behavior, if you are filming). Disadvantages are that not all testers feel comfortable being recorded. It can also take a long time to go through all the recorded material.


No matter which method you choose (writing or recording), you should always ask permission from the tester. Always tell us how the material will be used, who will take part in it and if you will anonymise the result.

Tip! If you think you will use the documentation openly and show it to others, it may be a good idea to have permit forms with you. Testers can then give their permission and sign that you can use their answers openly.

If you are unsure how to use the documentation, you can request the tester's contact information so that you can contact them later.

If you follow one of those guides, go back for the next step.

10. Test the prototype

Open

5. Test the prototype

Open