Skip to main content

Steve Jobs and Usability

Apple products are reputed primarily for two things:
  • ease of use
  • aesthetics
A Forbes article gives us a glimpse into how Apple has achieved ease of use in its products. Apparently, CEO Steve Jobs insisted that products be usable. Judging by the following quote from an Apple engineer, he did so by insisting on usability requirements without dictating design details:

Steve would be horribly offended [if] he couldn’t get to the song he wanted in less than three pushes of a button.

Design is important. But don't lose sight of the real usability requirements for your product. The real usability requirements are metrics, not functional specifications or UI layouts.


Unknown said…
I would like to point out that design is a process of iteration. It is based on user experience and psychology. Getting to three clicks is not where they started, it was where they worked towards getting to. It was the underlying software, the hardware, what was accessible at the time and what they learned as they iterated that has given them what they ended up with thus far.

Steve was more likely to be offended if the engineers, designers, etc, were not as passionate about the user's experience of the product as he was. The user is the first priority, and then they would figure out the money part.

Let's stop the myth that design is about making thing pretty. The best design is likely the most boring one because you didn't noticed it existed.
Roger L. Cauvin said…
Great points, Darren!

As you imply, usability requirements depend on feasibility. Usability metrics improve through iteration, and it's hard to predict up front what targets are feasible.

I also like what you wrote about the best designs being boring. I once asked Alan Cooper the best registration or login experience he'd ever seen. His answer: "I didn't."

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