Clicking the prototype allows you to evaluate the transition from offer to contact confirmation. It is worth checking the whole sequence, not just the appearance of individual screens.
Select a task from the client perspective
Instead of showing more views without context, specify the situation: the recipient wants to check the service and send a query. Then prepare a passage through the necessary screens. This allows you to notice a lack of information or an unclear button before the entire page is encoded.
For a company from Warsaw, the scenario may also include the choice of place of execution or way of conversation, if relevant in its offer. Do not add such fields automatically to each form.
Include decisions along the way
The user may want to return to the scope of the service, compare variants or check the company's data before sending the message. The prototype should allow these roads to pass without losing context. It is not enough to make one perfect sequence of clicks always leading to success.
- Check the transition from article to related offer.
- Show back from the service information form.
- Prepare the message after the correct completion.
- Select places to explain before contacting.
Separate the simulation from the running function
The prototype may show the reaction, but does not confirm the operation of the shipment or integration. Participants should know which elements are the simulation. Functional reception will occur later on the implemented page and will include actual data processing.
Save observations before corrections
Ask the test person to perform the task without hinting at the next click. Note the place of hesitation and the reasons for the choice. Not every suggestion requires a new button; sometimes a better text or order of information is enough. The rules of organizing the content describes Information architectureThe prototype is a tool for talking about the website's operation, which helps order decisions before their change becomes more laborious.
