Simplicity is Complex
Everybody’s talking about simplicity. Even me.
Joel Spolsky, software developer and blogger, certainly got a lot of mileage out of agreeing with Don Norman: (as of today, Spolsky has the #1 rated post on Norman’s original article on Technorati)
If you’re using the term “simplicity” to refer to a product in which the user model corresponds closely to the program model, so the product is easy to use, fine, more power to ya. If you’re using the term “simplicity” to refer to a product with a spare, clean visual appearance, so the term is nothing more than an aesthetic description much in the same way you might describe Ralph Lauren clothes as “Southampton WASP,” fine, more power to ya. Minimalist aesthetics are quite hip these days. But if you think simplicity means “not very many features” or “does one thing and does it well,” then I applaud your integrity but you can’t go that far with a product that deliberately leaves features out. [My italics added]
But, back in November, Joel wrote on the horror that is the Microsoft Vista shutdown menu and offered this commentary after describing how to cut the different ways Vista allows you to shutdown Windows from nine (!) down to just two:
Inevitably, you are going to think of a long list of intelligent, defensible reasons why each of these options is absolutely, positively essential. Don’t bother. I know. Each additional choice makes complete sense until you find yourself explaining to your uncle that he has to choose between 15 different ways to turn off a laptop.
This highlights a style of software design shared by Microsoft and the open source movement, in both cases driven by a desire for consensus and for “Making Everybody Happy,” but it’s based on the misconceived notion that lots of choices make people happy, which we really need to rethink.
But wait, I thought that Simplicity was Overrated. Indeed, simplicity can be overrated, especially if you define features as, well, just about anything that comes together to make up the experience of using a product:
evangelism, clean and spare design, emotional appeal, aesthetics, fast response time, direct and instant user feedback, program models which correspond to the user model resulting in high usability, and putting the user in control, all of which are features of one sort, in the sense that they are benefits that customers like and pay
Simplicity is overrated? No.
Though perhaps catchy phrases to described complex ideas should be.
One comment on “Simplicity is Complex”
Leave a Reply
Blog at WordPress.com. Theme: Duotone by Automattic.
[...] Don Norman, respected usability guru, wrote an article on the demise of simplicity as a selling point, and it’s caused reverberations all around the world. In fact, his article has been so controversial that he’s found it necessary to write a clarifying addendum for the essay (added to the bottom of the article), fearing that many of his readers interpreted his article as concluding that simplicity should no longer be a design goal. Norman’s point is that a product with a greater number of features is more appealing than a similar product with fewer features. The “more complicated” product is therefore more likely to sell. In other words, feature creep is driven by the knowledge that consumers will be suckered in to paying for a product that looks more complicated, even though, in many cases, they might complain about the difficulty of using the product when they get home. [...]