Skip to main content

Familiarity and Ease of Use

Familiarity has powerful effects on the ease of using a product. For example, consider a pointing device for a computer, whether it be a mouse, a touch pad, or a trackball. Someone who has exclusively used a mouse and never used a touch pad will almost certainly encounter difficulty and frustration when they try to use a touch pad. But after a sufficient time using the touch pad, she may actually grow to prefer it to a mouse. This concept applies to just about any product, including computer operating systems, e-mail software, toothbrushes, and even food.

Ease of use, therefore, depends not just on the person but on how familiar they have grown with the product. A product may intrinsically be easier to use than a competing product, but temporarily be more difficult for some users. As a consumer, whenever I have encountered this situation, I have generally felt a strong inclination to learn the unfamiliar product. I face short-term frustration, but the long-term benefits often are well worth the effort. But other people are much more reluctant to invest the time and effort to realize the long-term benefits. In fact, some people don't even seem to understand the distinction between intrinsic and temporary ease of use.

A product manager faces some interesting questions with such products. To what extent should the product features enhance intrinsic ease of use versus catering to those in the market who want a familiar user interface? Perhaps the product manager should segment the market as follows:

"Adventurous Learner" - excited to learn a new user interface for its own sake
"Pragmatic Learner" - willing to learn a new user interface for long-term benefit
"Reluctant Learner" - requires prodding to learn new user interface
"Resistant Learner" - will actively resist learning new user interface

This market segmentation helps the product manager to formulate ease of use requirements that ensure the product's user interface will appeal to a sufficiently large market. The company can bring in product testers that represent each of the target segments.

I realize that these observations resemble those in Geoffrey Moore's Crossing the Chasm. A difference is the emphasis on user interface rather than on disruptive technology.

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