Skip to main content

Thoughts on "Simple is Better"

Simple user interfaces are catching on. Sparse user interfaces generally make for products that are easier to use. The main Google search page is a model of simplicity, and it is one of the most visited pages on the web. It is almost difficult to do anything but search when you visit the page. But the simplicity of Google's search page is likely something that has been under constant attack.

Usability trades off against features. Forces within Google are no doubt constantly pushing to add features to the search page. The temptation is great for two reasons:
  • Since the page is so popular, you can guarantee traffic for whatever link or feature you add to it. When Google releases a new product, think of how tempting it must be to add a blurb to the main search page urging visitors to check out the new product.
  • Google could implement more flexible and customizable searches if it included some options on the main search page.
Resisting this temptation is hard. Whoever is resisting it faces "death by increment" arguments: "I know simplicity is important, but don't be unreasonable! What could be the harm of adding just one new feature to the page?"

For this reason, it's helpful to define usability metrics up front. The metric might limit the amount of time it takes for a typical user to accomplish the most common and important tasks. Or it might measure the likelihood that a novice user will perform these tasks successfully when visiting the page. Each new feature Google adds to the page will tend to increase the amount of time and decrease the likelihood that a visitor will perform the most common and important searches successfully.

Comments

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio