<h2>Description</h2>
<ul>
<li>You have no idea why people like it, but it do be shiftin’</li>
</ul>
<h2>Disproof</h2>
<ul>
<li>Large-scale post-acquisition data on what the product <em>means</em> to the user and how they learned that meaning</li>
</ul>
<h2>Consequences</h2>
<ul>
<li>Success without understanding is luck, and luck runs out</li>
<li>Despite there being no immediate risks, this creates hubris/complacency</li>
<li>You won’t understand your customer better and miss opportunities to better serve them or solve other problems for them</li>
<li>You won’t develop the skills to position the next product, over-reach and die</li>
<li>The next shiny thing comes along and you lose your users</li>
</ul>
<h2>Causes</h2>
<ul>
<li>No culture of understanding what drove success</li>
<li>Satisficing biases - you think you know why people like it, read a few happy tweets from a fraction of your user base and don’t question it further</li>
<li>“Of course it’s awesome, we made it”</li>
<li>Time pressure to move on to the next one</li>
</ul>
<h2>Approaches</h2>
<ul>
<li>Frankly, it’s very hard to fight a rising market and it might be better conserving strength to act when things start to go wrong</li>
</ul>


Not asking why it resonates

Description

Disproof

Consequences

Causes

Approaches