80/20 rule of Web functionality 12/2004

I frequently come across systems, or I am asked to redesign sites, that try to satisfy 100% of all possible user scenarios. In an attempt to satisfy all functional possibilities, no matter how infrequent, sites become overly complex and cluttered. In the process these sites risk alienating and confusing the majority of users.

Web teams should concentrate on satisfying or meeting 80% of user needs. And seek to meet the requirements that some (20% or less) users are interested in, only if it doesn't decrease the usability for the majority of users. It's important to stay grounded and focused on user needs. Try to avoid adding functionality or content because "you can" or "it might be cool" or "some people might like it." Everything on a Web site should have a useful purpose and reason for being there.

Some sites have been successfully in the "all things to all people" approach (e.g. Amazon and Yahoo.) But many more have failed. Understand your target audiences and their core needs. It's better to do a few things well, than a lot of things poorly.