<story><title>Dangling by a Trivial Feature</title><url>http://prog21.dadgum.com/160.html</url></story><parent_chain></parent_chain><comment><author>fatbird</author><text>Any implementation must accept that you will lose users this way.  You can&apos;t implement every &apos;trivial&apos; feature possible in order to avoid shedding users; implementing one way precludes a different way that also sheds users.  Overall, you try to maximize the number of users that you don&apos;t shed, but that&apos;s it.  And in fact, you&apos;re frequently better off shedding users willy-nilly, iteratively finding what the core features are that build a userbase, and forgetting about all the rest.&lt;p&gt;This post is a prescription for paralytic featur-itis.</text></comment>
<story><title>Dangling by a Trivial Feature</title><url>http://prog21.dadgum.com/160.html</url></story><parent_chain></parent_chain><comment><author>jthurman</author><text>As someone who sells software online, the most horrifying thing about this scenario is that the user is very unlikely to ever tell me why they moved on, and so I&apos;m terrifyingly unlikely to ever know that this trivial feature is missing.&lt;p&gt;This literally keeps me awake at night.&lt;p&gt;Statistic: it takes roughly 200 non-converting free trial downloads of my software to get one data point of feedback telling me why they decided not to buy.</text></comment>