Efficient iteration

<p>The derivative task of <a class="wikilink" href="/prototype_development/">prototype development</a> and <a class="wikilink" href="/effective_feedback_gathering/">effective feedback gathering</a> is to create a loop of improvement. </p> <p>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 <a class="wikilink" href="/nanocet/">NanoCET</a>. I was happy with the increased resolution and thought it was a very nifty idea and that everyone should love it. </p> <p>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. </p> <p>A prototype has to be built to allow iteration. Be it a website, a microscope, or a consumer device. </p> <p>That's the <a class="wikilink" href="/importance_of_a_prototype/">Importance of a Prototype</a>, the capacity of iterating. </p> <p>In some contexts, a <a class="wikilink" href="/minimum_viable_product/">minimum viable product</a> 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 <a class="wikilink" href="/effective_feedback_gathering/">effective feedback gathering</a> is funneled back to the prototype design.</p>