Skip to main content

Getting Feedback on Usability

It's common for people at all levels of a company, and in all company departments, to comment on the usability of the product or company web site and give suggestions on how to improve it.

Why? Here's a clue. I wrote in late 2005 that:
Most people, including executives, consider much of marketing to be common sense. We're all consumers, so we all know how we respond to products, names, logos, advertisements, and PR, right? So we're all experts on what works in marketing, no?
Wrong. See the original blog entry to learn why marketing is not common sense.

The same principle applies to usability. In playing the role of consumer in many aspects of our lives, we use products and web sites, and we know which ones are usable - and perhaps even what makes them usable - right?

Wrong. Just as marketing isn't common sense, usability isn't common sense, and for the same reasons.

Nonetheless, debates over usability and strategies for redesign can get quite contentious and time consuming. Even if a company is smart enough to have skilled interaction designers and user interface designers, the designers are often caught in the middle, but their expertise ignored.

There is a way of resolving these questions: a product manager frames the usability metrics and conducts tests on representative users to measure the usability of the current and proposed designs.

Unfortunately, many team members still have a bit of "overconfidence" in their ability to conduct this testing themselves. For example, a favorite idea of executives is to form a focus group, ask members of the group questions about the designs, and possibly ask them for design suggestions. Good product managers and usability experts know this approach is flawed.

Usability guru Jakob Nielsen tells us why usability testing is not as straightforward as the average company employee or executive may think:
The way to get user data boils down to the basic rules of usability:
  • Watch what people actually do.
  • Do not believe what people say they do.
  • Definitely don't believe what people predict they may do in the future.
Good product managers know how to elicit, gather, and interpret usability feedback, because by definition they know how to facilitate market input and draw appropriate conclusions from it.


Jeff SKI Kinsey said…
>> Watch what people actually do. <<

M1EK said…
One of my earliest real-developer experiences was as a summer intern at IBM where I wrote some of the control-panel-like objects in the Workplace Shell interface in OS/2 2.0. Really cool setup they had going there in a lab converted from an old hardware testing facility - a ring of rooms with 1-way mirrors where others (including us) could WATCH the users they brought in from temp agencies try to use last weeks' build...
Jeremy Gorr said…
I think you hit the nail on the head when you talk about "overconfidence" and "ignoring expertise".

As is the case with most product management problems: let the experts in the discipline guide you, rather than having the executives think they know better because they get a bigger paycheck.

Respecting the roles of everyone in the process, and not trying to control the outcome from above, is the key to getting usability right.

Jeremy Gorr
I believ this is something that is essential to any app like the one I am working on, SOOK. An app can solve a problem but if it is not designed properly it is not going to matter. How useful is an app if it is not easy and seamless for the user.

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

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

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