Establishing thresholds for idea validation

<p>When performing <a class="wikilink" href="/experiments_for_idea_validation/">experiments for idea validation</a>, the only way of preventing <a class="wikilink" href="/post_hoc_ergo_propter_hoc/">post hoc ergo propter hoc</a> fallacies is to set the threshold that defines success beforehand (not too different from OKRs: <a class="wikilink" href="/literature/202112050837_definition_of_okrs/">literature/202112050837 Definition of OKRs</a>.)</p> <p>However, it is hard to establish a clear value that is not overly arbitrary. For example, we can ask a pool of people whether they would use our product. Does it matter if 10% answer yes? What if it would be 73%? As long as it is more than 0% then it is an indication we would have customers. </p> <p>Of course, if the product relies on some network effect, below 50% may be too low. But for standard products, what is a common adoption rate? How many of us use Google Drive as opposed to Nextcloud (<a class="wikilink" href="/installing_and_running_nextcloud_on_raspberry_pi/">Installing and running Nextcloud on Raspberry Pi</a>)? However, a smaller adoption rate does not make it an unfeasible business case. </p> <p>Tags: <a href="/tags/idea-validation">#idea-validation</a> <a href="/tags/entrepreneurship-principles">#entrepreneurship-principles</a></p>