Fourth step of the Rapid Prototyping methodology – Analyze. Decode the test results and understand why the users ask for something instead of blindly following their requests. Be careful with how you interpret results.
Third step of the Rapid Prototyping methodology – Test. You need to prepare the questions you want to ask, recruit participants, figure out logistics and equipment you need to use.
Second step of the Rapid Prototyping methodology I use – Prototyping itself. Depending on the phase of the project and details you have defined in Step 1, there are different stages I call: “Baby”, “Toddler”, and “Teen”.
Looking into the first step of the rapid prototyping methodology I use – Defining. You need to define the scope, the type, the fidelity, and logistics before starting creating the prototype itself.
High-level overview of the rapid prototyping methodology I use.
Saw an interesting debate on Quora about this subject, wanted to share my opinion.
Can you prototype any kind of product? Less user-oriented products (e.g. APIs) are harder to prototype, and you probably can’t test every aspect of it, but there must be something you can still test with a prototype.
There are 3 main types of fidelity in prototypes – visual, functional, and content. Visual – the looks, functional – the works, content – the text and other content.
Low and high-fidelity prototypes, when to use and why.