From Post-its to Processes: Using Prototypes to Find Solutions

Before starting to prototype, you must take into account these circumstances and reach a consensus. Determine the objectives of your questions and projects.

Low-fidelity prototypes are rough and incomplete, with certain features of the target product, but in other respects is simple, usually rapid prototyping and testing of production broad concept. You can use paper, pencils, scissors to complete. Because of its simplicity can make all the stakeholders and to encourage trial and error process.

Just-good-enough fidelity means the quality is not too high nor too low, just right that users can grasp the concept or variable and give useful feedback.

High fidelity prototype is close enough to a final product to be able to examine usability questions in detail and make strong conclusions about how behavior will relate to use of the final product.

My contention is that Low-fidelity prototypes, which are just good enough to share with those whose opinions we value. This is all we need, because we prototype to learn rather than to test a theoretically finished product. This allows us to make mistakes faster, identifying areas that can be improved phase can identify and correct effectively.