Efficient iteration

First published:

Last Edited:

Number of edits:

The derivative task of prototype development and effective feedback gathering is to create a loop of improvement.

One of the challenges for many startups, is that they get stuck in the solution they have created, and they fail at seeing what customers are telling. I made that mistake with the NanoCET. I was happy with the increased resolution and thought it was a very nifty idea and that everyone should love it.

But customers were telling me things I didn't know how to process. Instead of iterating on the feedback, I kept pushing forward, made the device look nice, not work differently.

A prototype has to be built to allow iteration. Be it a website, a microscope, or a consumer device.

That's the Importance of a Prototype, the capacity of iterating.

In some contexts, a minimum viable product may not allow for iterations (for example, if production runs require a large minimum order). And that is why it's important to have a tight loop in which effective feedback gathering is funneled back to the prototype design.


These are the other notes that link to this one.


Share your thoughts on this note
Aquiles Carattino
Aquiles Carattino
This note you are reading is part of my digital garden. Follow the links to learn more, and remember that these notes evolve over time. After all, this website is not a blog.
© 2021 Aquiles Carattino
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
Privacy Policy