CoCreAid Toolbox - Click here to view
Funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the National Agency. Neither the European Union nor National Agency can be held responsible for them.
Home » Methods » Usability Test

Usability Test

Differences in the methodological approach
1 project managers & min. 5 citizens
1 hour per participant & preperation and wrap-up time
  • Adobe XD or Figma (or any other platforms that the digital prototype was created on)
  • Video conferencing: Zoom, Microsoft Teams etc.
  • MS Teams to take notes
Best Practices

Explanation of the method

  1. Preparation phase: Create a concept describing what you intend to do, what it is about, what your goal is, what you want to find out and what your test object is, e.g., website, app, product.
  2. If the prototype is a physical product, you need to think in advance about how to make it available to the test persons. Also, define the different roles needed, e.g., test leader, observer, etc.
  3. Recruit the test subjects. In order to detect at least 85% of the defects of a prototype, at least 5 test persons should be recruited. They should be similar to the user.
  4. Define exact test scenarios. Which tasks should the test persons perform on the prototype? As many different use cases as possible should be tested.
  5. Make sure that you have all the necessary materials for the application test. It is best to conduct a pilot test with another project manager.
  6. Implementation phase: In this phase you start with the welcome of the test person. Explain the process and the tasks of the test scenarios to the test person. Then carry out the tests. While the probands are performing the test, have them share their thoughts. This method is called the think-aloud method. In parallel, the observers should accurately document the performance.
  7. Follow-up phase: Evaluate the documentation and findings (video, audio and notes) and present the results to the team. Use these results to optimize the user-friendliness of the website, product, or app.


  • Usability testing can be helpful for identifying ambiguities in order to develop the most user-friendly product possible.
  • Testing on a prototype can validate a concept first and help to make plans for future features before investing a lot of money to create a final product.
  • Usability testing is a great way to develop empathy for the people who will later use the product.


  • Creating a well thought-out concept requires a lot of time for preparation and a certain level of experience or training.

Advice from practice

  • Do not invest too much time in the details of the prototype, as these may have to be changed again after the usability test.
  • Rather, conduct usability tests early and more often. Before the test, make sure that the test scenarios are clearly defined and you know how you want to measure your findings.
  • Let the test subjects think out loud, i.e., they should tell you as much as possible what is going through their minds while performing the tasks.
Please note that the tools and methods were created as of August 2024 and all Miro Boards are editable.
© 2024 CoCreAid. All rights reserved.