The value of quick and dirty prototypes
In the world of user research and design, I often come across the belief that prototypes should always be as polished and functional as possible. The closer a prototype is to what a user of the finished product will experience, the better! Well, no, not always. These ‘high fidelity’ prototypes with slick appearance and interactive elements are great for fine-tuning and polishing designs, but we shouldn’t overlook the value of the quick and dirty prototype. Here are some of the significant advantages of putting something ugly with limited functionality in front of people:
Quick to produce: the most obvious advantage is how quickly and cheaply you can get ideas visualised. The earlier you start testing ideas, the less expensive it is to make changes. There is nothing worse than designers building beautiful prototypes only for them to be completely torn apart in the first round of user research.
Implicit permission to critique: which is a fancy way of saying people are more likely to suggest changes to a prototype that looks like it was made quickly. One of the most common problems with user researcher is that people hate being negative or criticizing other people’s hard work. So the more simple a prototype is, the more likely it is people will offer honest negative feedback.
Managing expectations: another great thing about quick and dirty prototypes is that everyone knows the final product isn’t going to look anything like the design they see. This can help to get buy-in from stakeholder when you need to make major changes after user research. If decision makers see a slick prototype they can get fixated on getting something that looks and feels like what they were shown, and then it can be hard to persuade to make changes if you need to rework your ideas during the design and development process.
Naturally, there are plenty of disadvantages too and I’m not suggesting you should always test with quick and dirty prototypes, but it’s always worth considering the ‘low fidelity prototype’ and how much it can add to an iterative design and development process.