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.
4th benefit of prototyping – using it instead of traditional documentation to reduce misunderstandings and misinterpretations among teams.
All the questions and discussion about what prototyping tools is the best reminds me of a similar question among photographers. They focus so much on the right camera/lens that they forget about what’s really important. Don’t go crazy about the tools, tools are secondary, mindset and methodology – primary. Keep this in mind.
Prototyping for physical products is not that different from digital products. The cost may be a little higher due to the need of buying materials or even getting access to a 3D printer, but same process and mindset.