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.

Comments

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.

Tue Jul 22, 05:18:00 PM 2014

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."

Tue Jul 22, 05:41:00 PM 2014

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

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

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

Cauvin

Search This Blog