Why prototyping?

Some people think that prototyping is a waste of time and resources and they are anxious to jump on board and develop right away. What they don’t realize is that prototyping can save time and money and above all, test the idea on the cheap without investing into a fully functional software.

You may have great big ideas but not a big wallet so you cannot afford to lose money on something which is not doable or viable at all. Or maybe you work in a team and each of the team members has a different idea of what the final product should be about. This is what prototyping can help you with. It brings different ideas and perspectives together into a final product which showcases all the functionalities that the stakeholders need.

Wireframes sketch a layout for the stakeholders to see how the information will be displayed, mockups give you the overall feel of the design, whereas prototypes bring life to the experience in “user experience”. See it now? Prototypes are the quickest way to detect any usability flaws that your product might have, and it stands to reason you don’t want to skip this step in your design making process.

You don’t go buy a car without having a test drive, do you? So why would you build your design without testing it previously? Sure you will save some time at first, and go straight to the development phase, but, trust me, what’s not done in the beginning will wait for you around the corner - ‘cause sooner or later everyone pays the piper.

Having a prototype made will give your client a greater understanding of the design while at the same time unearth any issues that might arise in the process. In a nutshell, I couldn’t agree more with the saying - “if a picture is worth 1000 words, a prototype is worth 1000 meetings” and it paints thousands of pictures.

Next up