Developing a Prototype

Prototyping is the first step to actually feel an idea.

The goal is to develop quick prototypes in order to create a first user experience of how the idea might feel, look like and work like (remember Steve Jobs!).

The key purpose of a prototype is validation with users.

There are may approaches to build a prototype. At the end it has to be any materialization of the solution, which can be validated with users.

Link to the Ted Talk:

https://www.ted.com/talks/tom_wujec_build_a_tower_build_a_team

The figure illustrates the main components of low-fidelity prototypes.

The figure illustrates the some traps in low-fidelity prototyping.

There are various techniques for prototyping.

Use a role play to show the impact of your solution, for example, in the "day in the life of" your persona.

Don't try to be too perfect. "Feeling the idea is key, not perfect make up".

Compose low fidelity mockups by using traditional material.

Don't try to be too perfect. "Key functionality is key, rather than polished metal."

Another prototyping approach is the creation of a storyboard.

Use a story board to represent the ideas in different perspectives or context.

Don't try to be too perfect. "Simplicity and a good story is key, rather than a high glossy comic strip."

This is a good template, when it comes to planning of a roadmap or action plan for your prototype.

The figure illustrates the typical evolution of application prototypes. Starting with a vision, over low-fidelity prototypes and Wireframes to the high-fidelity prototype.

There are various types of prototypes commonly used, which can be used to evolve initial prototypes further:

• Critical Function Prototype
• Dark Horse Prototype
• Funky Prototype
• Functional Prototype
• Role Play

Link to Design Thinking at University of St. Gallen: http://dthsg.com/