The Simple Guide To Product Testing
post-template-default,single,single-post,postid-3842,single-format-standard,bridge-core-2.8.5,qode-page-transition-enabled,ajax_fade,page_not_loaded,,qode-child-theme-ver-1.0.0,qode-theme-ver-26.9,qode-theme-bridge,disabled_footer_bottom,qode_header_in_grid,wpb-js-composer js-comp-ver-,vc_responsive

The Simple Guide To Product Testing

The Simple Guide To Product Testing

When we’re in the very beginning of a new project and validating a product idea through testing, we’re miles away from proper usability testing (which we do later in the project). This is just one of the reasons we don’t refer to these sessions as usability testing or user testing—we instead call it product testing.

“You shouldn’t do product design without product testing.” These guidelines aren’t just for teams already building products. They’re also for anyone who’s just starting to think about new product ideas and ways to validate them.

While there are multiple things to keep in mind when planning and conducting a product testing, here’s a simple list that can help you focus:

  1. Start testing the very first week of the project
  2. Do more than ‘just’ usability testing
  3. 5 users per target group
  4. Do it more than once
  5. Take care of the details

1. Start testing the very first week of the project


As an agency, we start new projects with a short discovery/research phase followed by a design sprint. Sprints are great when kicking off new initiatives, testing new product ideas and features, etc. We end the workshop by creating a medium-fidelity prototype that we then test with users. We want to validate the direction we’re heading right at the start.

Can you imagine how rewarding that is? There was almost nothing a couple a days ago—now there’s a concept, a business case, and actual feedback from real customers.

What a great way to start a project.

No Comments

Sorry, the comment form is closed at this time.