80/20 rule

80/20 principle and software programming

80 percent of users only touch 20 percent of their software features

Let’s talk about my job today. Yes, I code software for living, especially iPhone Applications (example one, example two) but I used to develop Web or desktop applications using different technologies. If you are not interested by programming don’t read any further and go on Youtube watch some funny videos.  I warned you this post is about techies. Otherwise keep reading. Even though you don’t care about coding I am pretty sure this principle could be applied to other area. Tell me.

Back to topic

One thing I observed and software designers all over the world would probably corroborate: Most users  use only a small bunch of features brought by software.

Think about it a couple of seconds. Even if you don’t have a computer-related job you probably use software like Word or a Web browser (at least to read my website). Do you use every capabilities offered? I don’t think so, especially for very comprehensive ones like Excel or Outlook for instance.

What’s the point?

If people use very few functionality, why do you waste your time creating minor features nobody but you will use?

Focus on the main feature of your application (at least first) and put all your effort into it. To figure out what is the main feature just answer the following question. What is the core purpose of my application? The answer is generally the short pitch you tell to introduce it. Example: a file-sharing application is made to share files, not to sort files depending their kind.

Be careful, I don’t mean additional features are not necessary, I just mean build first a small but perfect  application and then focus on secondary stuff. Would you use Firefox if it displays webpages incorrectly? Even though its add-ons system is great. No…

Pay attention to software and web application that are release nowadays. Most of them turn out as beta with very few features and developing team adds functionalities progressively with new revisions.

In this topic I recommend you the Getting Real ebook by 37signals. It’s focused on web-based application but worth reading. Excerpt:

Getting real is less. Less mass, less software, less features,  less paperwork, less of everything that’s not essential (and most of what you think is essential actually isn’t).

If you create programs (and even if you don’t) I would be curious to hear your point of view.

photo credit: mpalis

© 2009 Unbalanced man.