[tempestn]

The point about paying extreme attention to a single user's needs reminded me very much of Stop Developing for the 90% Use Case: http://gist.io/5561992, which came up here a couple months back.

Basically it demonstrates the problem with aiming for the best ratio of user satisfaction to effort in each feature of your product. If each part of what you build covers 90% of users' needs, that sounds pretty good. But if your product has X main features, the percentage of users who will be entirely satisfied is 90%^X, which gets low very quickly.

You need to focus on servicing all of someone's needs, not most of everyone's, but consequently all of no one's.