Ever wonder how bland, feature barren, largely useless lowest common denominator shit that nobody really seems to like, or identify with can come to dominate de

Ever wonder how bland, feature barren, largely useless lowest common denominator shit that nobody really seems to like, or identify with can come to dominate design of software products? My theory is that the assumption there is some kind of meaningful "Average user" which a product is then built for ultimately destroys utility in software. If you have 50 features that on average 1% of people use, you can easily reach the false conclusion nobody cares about these features, when on aggregate 90% might use at least one of those features. Thus in aiming for the average, you haven't designed for anyone at all. http://en.wikipedia.org/wiki/Ecological_fallacy http://en.wikipedia.org/wiki/Ecological_fallacy