<story><title>Saying &apos;no&apos; to keep crap out of products</title><url>https://blog.orangecaffeine.com/the-art-of-saying-no-db012a22cd28#.sbmur7q01</url></story><parent_chain></parent_chain><comment><author>onion2k</author><text>Is it actually possible to know ahead of launching a feature that it&amp;#x27;ll be crap, or is it that most features get launched and the ones that are receievd well by the users are deemed &amp;quot;good&amp;quot; while the ones that aren&amp;#x27;t are considered &amp;quot;crap&amp;quot;?&lt;p&gt;We&amp;#x27;ve all written things that we thought would be awesome that turned out to be disregarded by users, and deployed things we thought were pointless nonsense that turned out to be fantastically engaging features that users rave about. Can you &lt;i&gt;really&lt;/i&gt; tell before you actually get proper feedback (eg the user seeing and using the feature, not just asking if they might like it because users say yes to everything)?</text></comment>
<story><title>Saying &apos;no&apos; to keep crap out of products</title><url>https://blog.orangecaffeine.com/the-art-of-saying-no-db012a22cd28#.sbmur7q01</url></story><parent_chain></parent_chain><comment><author>dan353hehe</author><text>This reminds me a bit about what was mentioned in the book &amp;quot;good to great&amp;quot;. A company, or in this case a product, can do everything at a level a little above garbage, or it can focus on its core competencies and be the best at something.&lt;p&gt;The more features you add to a product, (in my mind) the worse it becomes.</text></comment>