Simplicity Sells: Customers Do Not Want More Features

10 percent.

That is the percentage of mobile phone product features that manufacturers estimate the average customer uses.

The number who actually read the product user manual? You can guess.

There is a profound disconnect between strategy and market in much of tech design. People are using smart phones and tablets to make their lives easier. Convenience is the strategic imperative. That is why they willingly surrender the last vestiges of their personal privacy and pay more for a device than for their monthly rent. And that is also why they want their devices to be easy to use and understand.

Most of them hated high school math. The majority are not engineers. They would probably not long survive the Google, Facebook or Microsoft hiring process. But they are the market.

New features that are not aligned with the convenience imperative conflict with it. The purchase impulse relies to a great degree on word of mouth. Perceptions matter. If a device is confusing or difficult to master, its reputation will proceed it. But not for long, because it won't last in this environment where 'new' is redefined daily and 'forever' is a concept as alien as life on Mars.

Apple has led the way in proving that design can make a difference. But less may truly be more. JL

Donald Reinertson and Stefan Thomke report in Harvard Business Review:

There is a common myth about product development: the more features we put into a product, the more customers will like it.

Product-development teams seem to believe that adding features creates value for customers and subtracting them destroys it. This attitude explains why products are so complicated: Remote controls seem impossible to use, computers take hours to set up, cars have so many switches and knobs that they resemble airplane cockpits, and even the humble toaster now comes with a manual and LCD displays.
Companies that challenge the belief that more is better create products that are elegant in their simplicity. Bang & Olufsen, the Danish manufacturer of audio products, televisions, and telephones, understands that customers don't necessarily want to fiddle with the equalizer, balance, and other controls to find the optimum combination of settings for listening to music. Its high-end speakers automatically make the adjustments needed to reproduce a song with as much fidelity to the original as possible. All that's left for users to select is the volume.

Getting companies to buy into and implement the principle that less can be more is hard because it requires extra effort in two areas of product development:

1. Defining the problem. Articulating the problem that developers will try to solve is the most underrated part of the innovation process. Too many companies devote far too little time to it. But this phase is important because it's where teams develop a clear understanding of what their goals are and generate hypotheses that can be tested and refined through experiments. The quality of a problem statement makes all the difference in a team's ability to focus on the few features that really matter.

When Walt Disney was planning Disneyland, he didn't rush to add more features (rides, kinds of food, amount of parking) than other amusement parks had. Rather, he began by asking a much larger question: How could Disneyland provide visitors with a magical customer experience? Surely, the answer didn't come overnight; it required painstakingly detailed research, constant experimentation, and deep insights into what "magical" meant to Disney and its customers. IDEO and other companies have dedicated phases in which they completely immerse themselves in the context in which the envisioned product or service will be used. Their developers read everything of interest about the markets, observe and interview future users, research offerings that will compete with the new product, and synthesize everything that they have learned into pictures, models, and diagrams. The result is deep insights into customers that are tested, improved, or abandoned throughout the iterative development process.

2. Determining what to hide or omit. Teams are often tempted to show off by producing brilliant technical solutions that amaze their peers and management. But often customers would prefer a product that just works effortlessly. From a customer's point of view, the best solutions solve a problem in the simplest way and hide the work that developers are so proud of.

One company that has understood this is Apple. It is known for many things—innovative products, stylish designs, and savvy marketing—but perhaps its greatest strength is its ability to get to the heart of a problem. (See "The Real Leadership Lessons of Steve Jobs," by Walter Isaacson, in our April issue.) As the late Steve Jobs once explained, "When you start looking at a problem and it seems really simple, you don't really understand the complexity of the problem. And your solutions are way too oversimplified. Then you get into the problem, and you see it's really complicated. And you come up with all these convoluted solutions....That's where most people stop." Not Apple. It keeps on plugging away. "The really great person will keep on going," said Jobs, "and find...the key underlying principle of the problem and come up with a beautiful, elegant solution that works."

Determining which features to omit is just as important as—and perhaps more important than—figuring out which ones to include. Unfortunately, many companies, in an effort to be innovative, throw in every possible bell and whistle without fully considering important factors such as the value to customers and ease of use. When such companies do omit some planned functionality, it's typically because they need to cut costs or have fallen behind schedule or because the team has failed in some other way.

Instead, managers should focus on figuring out whether the deletion of any proposed feature might improve a particular product and allow the team to concentrate on things that truly heighten the overall customer experience. This can be determined by treating each alleged requirement as a hypothesis and testing it in small, quick experiments with prospective customers.

Development teams often assume that their products are done when no more features can be added. Perhaps their logic should be the reverse: Products get closer to perfection when no more features can be eliminated. As Leonardo da Vinci once said, "Simplicity is the ultimate sophistication."