Literature/202303251644 metrics used to measure success by customers

<ul> <li>Source: [<a class="litnote tooltip" href="/literature/@ulwick">@ulwick<span class="tooltiptext">Jobs to be Done: Theory to Practice</span></a>]</li> <li>Tags: <a href="/tags/product-market-fit">#product-market-fit</a> <a href="/tags/jobs-to-be-done">#jobs-to-be-done</a> </li> </ul> <p>In the <a class="wikilink" href="/literature/202303251644_jobs_to_be_done_framework/">literature/202303251644 Jobs to be done framework</a>, one of the core principles is that the jobs customers are trying to accomplished are studied as processes. Knowing <em>what the problem is</em> does not say much about what the customer was trying to achieve and why it was not successful. </p> <p><img alt="images/Pasted image 20230325160817.png" class="wikiimage" src="/images/pasted image 20230325160817.png" /> According to [<a class="litnote tooltip" href="/literature/@ulwicka">@ulwicka<span class="tooltiptext">The Jobs-to-be-Done Needs Framework</span></a>], there are anywhere from 50 to 150 outcomes that customers use to judge the success of a core functional job, and around 10 to 30 per consumption chain job.</p>