Prototyping is an important part of the M-Files design process because it helps us to identify and formulate the main direction of our design. With prototypes, we can visualize the whole software and interaction flows which shortens the time needed for actual development. In addition, prototypes allow us to test which features work and don’t work for the users and to spot possible usability problems in advance. Prototyping also enables rapid experimenting with new ideas.
Prototypes can be made with many different tools. In M-Files, we mostly use Sketch and Figma. These tools allow us to create high-fidelity prototypes quickly, evaluate designs, and share specifications with developers. For us in M-Files, prototypes are most useful in internal communication and design evaluation.
Prototyping as a tool for communication
One of the most important advantages of prototyping is that it enables better communication. With prototypes, designers can visualize their ideas to users, developers, customers, and other stakeholders. It is very crucial for designers to be able to explain their work clearly. One important part of this is to illustrate interactions and layouts to the developers to ensure that they are able to do the implementation correctly. But just handing out prototypes isn’t enough. Designers also need to explain prototype features and interactions to other stakeholders to avoid any misunderstandings.
Prototypes and evaluation
Evaluation is the second most important aspect of prototypes. It is important to test the prototype with end users because they are in the end going to use the ready product. The end users can either do different tasks or just free testing on the prototype. Usually tests are carried out with pre-assigned tasks which include testing different features of the prototype. Designers record and analyze usability problems and other feedback. The tests can also be iterative meaning that there are several test rounds of the prototype. After the usability tests, we often interview the end users to get even more insight. Finally, the M-Files design team analyzes the results, and found usability problems will be taken into account in the development process.
Prototypes are also evaluated with customers and other stakeholders. Prototypes allow customers to see the look and feel of the end product. Customers see what they are buying and can give feedback easily. This helps to prevent need for major changes later in the development.
Along with end users and customers, also designers and developers evaluate the design with prototypes. Members of the design team go through the prototype many times along with developers who do the actual implementation. In our agile environment, we get feedback from our design quickly and, then, do iterations to make the product even better with every round.
Prototyping in a nutshell
So why do we love prototypes?
Although prototyping is an important part of our design process, there are some limitations and challenges with them too. It is important to iterate prototypes and not to make them fully ready in the beginning because, otherwise, we are back in waterfall development. Iterating prototypes little by little makes it possible to design high-quality products in an agile way.
