The mock-up allows you to evaluate the order of information and the user's path before the project receives target colors and illustrations. It is a good time to check the structure and more difficult cases of content.
The mock-up answers the question “how does it work”
You do not need to solve all visual details at once to see if the recipient finds an offer and contact. Simple layout shows the relationship between headers, descriptions and actions. It allows you to focus attention on the importance of elements rather than on color preferences.
Prepare representative content. A model based solely on short labels can hide problems with a long name or extended description. It is worth showing at least one more demanding variant.
Move Several Tasks
Ask someone who does not know the project to find the service and indicate what he will do next. Do not immediately explain which block is responsible for the subject.
For example, the recipient may not distinguish “solutions” from “services” if both names lead to similar lists. In the model it is easier to change the division than after preparing all views, content and animations.
Include options that usually die
- Subpage with long title and short description.
- A card with no extra photo.
- A list containing only one result.
- Error message form.
- Mobile view with advanced navigation.
- Back to the list after seeing the details.
Not every variant requires a full board. Some rules can be described if the team understands behavior and can check them later.
Save decisions before next step
After the review, find out which problems have been solved and which remain open. The approved mockup should have a clear version. If the structure changes later, mark the impact on the other views and materials.
Appearance refinement can still reveal new needs, but should not reverse the previously agreed meaning of the site without a conversation. The mock-up is intended to limit random decisions rather than block legitimate amendments.
Read about further work in Submission of the project for implementation, about the hierarchy in the guidebook web page readability.
