Building prototypes

When you start to design your solution, you want to make sure it meets the needs of your customers.

However, you don’t want to spend too much time building a solution, especially if you aren’t sure it’s actually what your customers want.

If you really want to create a product or service that meets your customer needs, you need to build prototypes. Unfinished and ugly prototypes.

A prototype is not your actual product, it shouldn’t look like a final product, and it shouldn’t be your Minimum Viable Product (MVP).

Build rough prototypes that are not perfect and do not look nice so your customers can give you feedback on how the solution meets their needs.

Why?

If you make your prototype look perfect, when you ask your customers for feedback they will inadvertently give criticism about the design and aesthetics which is what you don’t want.

  • Create a wireframe for websites – a black and white prototype of the layout of your website.
  • Use placeholders where logos and branding will appear – your solution should focus on the functionality, not the design

Hey, smarty!

Login or signup to get started

What's your name?

What's your password? Lost Password
We sent a link to reset your password to your email.
Create a new password
Upload file