Prototypes
Decide when to test a prototype and prepare it for a remote study.
Prototypes
What to check in a prototype before testing
To test an interface, you will need material: a prototype, static screens, or images. In product teams, prototypes are usually provided by designers, but sometimes researchers create them themselves if they have the experience and the right tools.
To quickly prepare materials and adapt them for testing, a technical brief will be useful. It is usually created by the researcher, who already has an approximate research design in mind. The technical brief should think through and describe:
- The required screens and the connections between them. If the materials are static, which exact screens or images are needed? If we show a prototype, from which screen will the flow start and where will it end? Which transitions are needed from one step to another, will they be linear, or will we allow users to go back?
- Functionality. Do we need an interactive prototype or a static screen? Which elements need to be active? Which actions does the respondent need to perform?
- Target action. What main action are we checking, for example placing an order? Which actions will be considered indicators that the task was completed correctly?
- Element states. Many interfaces have elements that change status, such as color, enabled state, or activity. To help respondents correctly understand what is happening on screens during testing, you need to think through the state of key elements, for example toggles on or off, buttons active or inactive.
- Data on screens. If you are testing an interface with personal data, products, or other objects, think through what they will display so they are suitable for different respondents while creating a relatively relevant situation for each of them, for example account balance, dish options, locations.
If you already have a prototype or know that the test material will be a prototype, check its readiness using our checklist. And if you still need to decide what to show respondents and at which stage of the project to start testing, let’s figure it out together.
When and what to test
To get feedback on an interface concept, you can start researching it at the earliest stage of idea formation. Moreover, the earlier you start, the more confidently you can move forward in designing the user experience.
Testing material can include:
- Static screens
- Interactive prototypes, from low to high fidelity
- Test environments and beta versions of the product
- A live product version, production
Different levels of prototype and material detail correspond to different stages of concept development.
The scale on which the desired level of detail grows can be illustrated like this:

This means that at the idea stage, you can test very rough prototypes or static screens that show the concept to understand whether you are moving in the right direction. However, the closer you are to releasing new functionality, the more important it is to be confident that everything works as expected throughout the whole flow and that corner cases are considered.
Pathway lets you use static images, detailed prototypes, a link to an already working website, and even record a respondent’s actions in the browser as test material. This makes our service an ideal tool for testing at every stage of your project development.

Specifics of prototypes for unmoderated testing
The unmoderated testing format determines how prototypes should be prepared. Here is what this means:
- Start point and flow length. In moderated testing, we can afford to start far away, for example directly from the product home page, even if we are testing functionality hidden in the profile, so we can also check how intuitive the path to the target action is for the respondent. In unmoderated testing, however, the participant usually spends less time with the prototype, and unnecessary flow length increases the risk that they never reach the target area. If it is not critical for the research design, you can start 1–2 screens closer to the target area, for example directly in the profile.
- Number of degrees of freedom. In moderated testing, the researcher can gently guide the respondent if they go the wrong way and bring them back to the target flow. When a person works with the prototype alone, you need to minimize the chance of getting lost or stuck: think through clear transitions without dead ends and limit prototype interactivity to only the necessary actions.
- Stability level. For unmoderated testing, the prototype needs to be carefully checked for possible errors. Without a moderator, the user will not be able to report that the prototype broke, and you will not be able to fix it quickly.
Checklist: how to prepare a prototype and what to do after the test
Before the study
Additional checklist for international products
After the study is complete