Testing static screens vs. interactive prototype – Which is the most effective method via UserTesting.com?



I am in the process of revamping a form page which the users were finding it difficult to attempt. Consequently, I have developed a prototype with some click-through interactions which is consist of about 3 screens - a form page followed by the pages for review and confirmation. The main objective is to test it with the users and see whether they will be able to answer all the questions in the form easily and move forward towards the confirmation page or not.

I have once used usertesting.com in past and what I have learnt there was when we have a set of screens (mockups) to test, we should include a description along with instructions to narrate every screen/step in the flow. However, in case of using an interactive-prototype we may not be able to guide them (or interrupt them) at the screen-level but to have only some introduction-text in the beginning. Considering these conditions, will it be effective to launch the test with a set of static-screens? Or the interactive-prototype? – Please suggest.


Mostly, it depents on your resources.
Of course, it is better to make an interactive prototype, because respondents will be less constrained in interaction this way. There wont be descriptions and narrative in the real form, and also, you make the situation more hypothetical for respondents.

Most of the main problems for forms are the confusing instructions, and the unnoticed error messages. The best way to test it - give respondents interactive form.

On the other hand, if you don’t have much time to make interactive prototype, and only want to see, if people understand what to write in what field, and if they can find the confirmative button, you can easily do it with static screens and first-click test.


Thanks, Sergery Rozum.