Suckage to Usage Ratio

The team over at 37signals writes a pretty awesome blog. It is mostly tech-focused since they make web-based software, but I find that a lot of their topics have broader applications as well. Take today’s genius post about the suckage to usage ratio, for example. The basic idea is that when creating a product, it’s okay for some features of the product to suck if they are not the most important or frequently-used features. So often the pursuit of perfection, in software, in projects, in life, can get in the way of progress. As a recovering perfectionist, this concept really resonates with me. Focus on what really matters and don’t worry so much about the rest.

There is an eternal contest in my mind between the following aphorisms:
If it’s worth doing, it’s worth doing right.
The perfect is the enemy of the good.
If it’s worth doing, it’s worth doing half-assed.

Mostly I try to side with the last two in that list, lest I drive myself and everyone around me insane. I predict that the suckage to usage ratio will become another tool for me to use to combat the inertia that comes along with the pursuit of perfection. Focus on what really matters and don’t worry so much about the rest. Focus on what really matters and don’t worry so much about the rest. Focus on what really matters and don’t worry so much about the rest. Practice makes perfect, right?

Add Your Comment

Make sure you share your opinion with us. Fields marked * are required. Any other information is optional and for your own pleasure. Your email address will be hidden and never published or used in any way.


Optional Details

If you like you can tell us your website URL and Twitter Username. We'll link your name to your web address and we'll add a twitter link to your comment. This is completely optional.