Minimum viable prototype
<p>I prefer to use <a class="wikilink" href="/mvp/">MVP</a> to refer to <a class="wikilink" href="/minimally_valuable_prototype/">Minimally Valuable Prototype</a> rather than "viable" or "product". </p>
<p>In [<a class="litnote tooltip" href="/literature/@cagan2018">@cagan2018<span class="tooltiptext">Inspired: how to create tech products customers love</span></a>], I found the idea of challenging the concept of MVP and moving it away from <em>product</em>, since this gives the sense of a final thing, something that has been validated by and with customers. Perhaps the seed of the confusion arose with The Lean Startup ([<a class="litnote tooltip" href="/literature/@ries2014">@ries2014<span class="tooltiptext">The lean startup: how today's entrepreneurs use continuous innovation to create radically successful businesses</span></a>]), in which the definition of an MVP is a bit ambiguous and people took it to heart. </p>
<p>Do you want to build something that people can <em>buy</em> or something that you can use to <em>test</em> assumptions, features, and benefits to your users? </p>
<p>Using the word "Prototype" leans towards the idea of learning, I am challenging the use of the word "viable" since it is also confusing. </p>
<p>Therefore, I would prefer to focus on things which are <em>valuable</em>: <a class="wikilink" href="/minimally_valuable_prototype/">Minimally Valuable Prototype</a></p>
Backlinks
These are the other notes that link to this one.
Comment
Share your thoughts on this note. Comments are not public, they are
messages sent directly to my inbox.