We have understood the user and got together some ideas. Now let's turn those ideas into reality.
The main thing is that you produce something quickly and present it. You would want to give them limited background knowledge whilst using your prototype and just let them explore as well as collect feedback from them. But we will talk about this more in the testing stage.
Whilst building the prototype you want to make it as fast and cheap as possible. It can be messy and easily made with simple materials like drawing on sticky notes to show various pages in an app. Users should be able to get a basic idea and feedback. You may want to use things such as scenes, props and roles whilst creating a prototype.
It should be made with only one focus in mind, answering a single question or implementing a single idea rather than hosting multiple features. Once you do this multiple times, through the testing stage you can figure out which ideas work and then pull them all together in a singular prototype but that is for later.
Make sure to keep the user's pov in mind and the research that you did in the first stage. The prototype, in the end, should be based around the user.
When you make your pitch, know who the right audience is, keep it short and draw on emotions rather than the logistics.
Storyboarding
You can deliver your prototype in the form of a storyboard or use it to build your prototype.
By storyboarding you can display key phases/interactions that the user will go through during the project and it can be used to show to a client/executive committee.
Remember to communicate an emotion, idea or step and to not make it too detailed. There is no need for minor details just yet.
An idea to keep in mind is MVP or Minimum Viable Product.
The cycle this uses is produce -> measure -> learn
Only introduce limited features to the market to see how it works and then repeat multiple times. Make sure that you do not spend months or years making something that the market doesn't need or want.
Next step - test
Top comments (0)