Scope creep: When “more” is actually less
We all have had it at some time or another - the typical client that dreams of having an application deliverable that should be a rough equivalent of a Swiss army knife (and for the very same budget, of course - but that’s a different topic). That it should do this, that, that other thing too and -yes- if it can also do X, Y and Z, all the better. After all, isn’t our job about incorporing as much “usability” as possible into whatever we work on?
Turns out, the amount of features has little to do with usability in itself, because it’s not about if something does X or Y, but how you, as an user, can be able to do/make/achieve X or Y through a device without even thinking about it - because the moment you have to think about a way to do something, that becomes a stumbling block in your train of thought (a cognitive strain), ruining what should otherwise be a seamless experience. And the more bells and whistles you have to deal with, the cognitive flow suffers and the potential for confusion (and consequent user frustration and anger) increases. Not the best case scenario for anyone.
Steve Krug analyzed greatly this fact in one of the best UX books ever written, in my opinion: Don’t Make Me Think. Take that VCR you bought in the mid-90s, for example. You probably bought it because you were told it did everything between A and Z - and then some. Now ask yourself: How many times did you use it to the 100% of its feature capability? If you are like 99% of the population, you probably learned to use the basic controls, change channels, use the TV/VCR switch - and that was it. And what about the other myriad functions? They were there all right, but you probably had to skim through a thick manual and operate some cryptic key commands on your remote control to access them. And -as thousands of appliances with clocks flashing permanently at “12:00” can attest- who has time and patience to do that?
This hasn’t stopped people from thinking the more bells and whistles something has, they’re getting “more” for their money, though. One of the most interesting “less is more” cases might well be Apple’s iPod - When it debuted, there were many, many things the competition did and it didn’t do, like video, and others that still doesn’t do out of the box, like radio. However, the iPod has become the best-selling personal music player in history. Why, you may think? Apple didn’t really invent anything that wasn’t there before the iPod. However, by rethinking the way people accessed and used the few, expected features of a personal music player in a way everyone could access and use them, it won the hearts -and wallets- of people everywhere. There are few better examples of “doing one thing right instead of a hundred things wrong”.
It’s up to you to fight scope creep. More isn’t “more” all the time. Underpromising and overdelivering is much better than the opposite.