Skip to main content

Donald Norman on Simplicity

Donald Norman recently wrote an odd column singing the praises of complexity. He challenges the conventional "do one thing and do it well" wisdom:

[P]eople want the features. [S]implicity is a myth whose time has past [sic], if it ever existed.
In a related article about Google, Norman wrote:

Why are Yahoo! and MSN such complex-looking places? Because their systems are easier to use [than Google's].
Yes, I did a double-take when I read that statement, too. Visiting the Yahoo home page to perform a web search takes longer than visiting the Google home page to perform a web search, if just because of the time it takes for a browser to load the Yahoo home page.

Yet Norman's claim is actually that Google is more complex for users who are trying to do something other than search. He has a point. If Jane goes to the Google home page to check her Gmail account, she probably has to go through more time and effort than Joe trying to get to his Yahoo Mail account from the Yahoo home page. The reason is that Google's home page is so sparse that it's not obvious how to get to Gmail from it. Yahoo, on the other hand, has a potpourri of links on its home page, including to its mail service.

But the obvious point that Norman seems to miss is that Google has a more popular, more profitable, and more beloved search engine than Yahoo. Simplicity is winning the search engine battle. Norman's example of Google and Yahoo undermines his own criticism of simplicity.

Nonetheless, underlying Norman's observations about Google are some important lessons about categories and some genuine challenges that Google faces. I will describe some of these lessons and challenges in my next entry.

Comments

Roger L. Cauvin said…
I'd like to see some hard facts demonstrating what's responsible for Google's success. Is it because people believe it returns more useful results? Or is it because the page is simpler and cleaner? Or some combination thereof?

One thing's for sure: Google places a lot of emphasis on simplicity, and they do a lot of user testing.

Regardless, I don't see how Norman can point to search in support of his contention that users prefer complexity.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem