6

Usability is too important to be left to usability professionals

 3 years ago
source link: https://uxdesign.cc/we-are-all-designers-25505d144e8f
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Usability is too important to be left to usability professionals

Flashing clock on VCR
Flashing clock on VCR
The classic usability problem. Credit: Gfycat

Raise your hand if you had to go through the Hunger Games labyrinth to score a COVID-19 vaccine earlier this year — figuring out which phone number(s)/website(s) to try, navigating it, answering all the questions, searching for available appointments within reasonable distances, and, usually, having to try all over again. Or, raise your hand if you’ve had trouble figuring out how to use an Electronic Health Record (EHR) or an associated Patient Portal.

Maybe you thought it was you. Maybe you thought you weren’t tech-savvy enough. But, a trio of usability experts reassure us, it’s not: it’s just bad design. And we should speak up.

“Everyone everywhere: A distributed and embedded paradigm for usability,” by Professors Michael B. Twidale, David M. Nichols, and Christopher P. Lueg, was published in Journal of the Association for Information Science and Technology (JASIST) in March, but I didn’t see it until the University of Illinois School of Information Sciences (where Dr. Twidale is on faculty) put out a press release a few days ago.

“If you think good design is expensive, you should look at the cost of bad design.”
“If you think good design is expensive, you should look at the cost of bad design.”

The authors believe that bad design has costs — to users and to society — yet: “The total costs of bad usability over the life of a product are rarely computed. It is almost like we as a society do not want to know how much money has been wasted and how much irritation and misery caused.”

Whatever the numbers are, they’re too high.

As Dr. Twidale said:

“Making a computer system easier to use is a tiny fraction of the cost of making the computer system work at all. So why aren’t things fixed? Because people put up with bad interfaces and blame themselves. We want to say, ‘No, it’s not your fault! It is bad design.’”

He specifically referenced the vaccine example: “When hard to use software means a vulnerable elderly person cannot book a vaccination, that’s a social justice issue. If you can’t get things to work, it can further exclude you from the benefits that technology is bringing to everyone else.”

They’re serious about the social justice aspect, calling for “Distributed Usability Activism:” promoting “distributed usability through mass awareness leading to usability activism across society.” They cite how user activism (e.g. Ralph Nadar) led to changes in vehicle safety several decades ago.

Moral of the story: encourage more complaining.

Many designers or developers would blanche at that prospect, and many of us users might shrug at the notion that our complaint would make any difference. However, “usability is too important to be left to usability professionals.” The authors urge that users be given both concrete examples about how complaints can lead to positive changes, and better venues (including social media) in which to air them.

The end result, they suggest, might be a “Usability Kaizen,” likening it to the Japanese factory practice where everyone is encouraged to identify flaws and to voice suggestions. I.e., “everyone should be involved in usability discussions, including end-users.”

There are, they admit, a lot of smart people, in numerous professions. involved in the various products and processes that we use, but “a wider usability movement would remind members of any profession that regardless of their domain and efforts in making the world a better place, bad usability makes everything worse.” They remind us that: “Their complaints are valuable data if only we would listen, and if only people believe that their complaints will be listened to — and acted on.”

The authors believe that what we often view as “user errors” or “human errors” are, in fact, usability problems, asserting: “Hard‐to‐use software should be as unsuccessful as hard‐to‐drive automobiles.” Indeed, they view the need for training as a tip-off there are design issues:

“it is particularly egregious to first blame the end user for errors, and then to adopt a training regime for these users to conform themselves to a badly designed product….

…the default should be to regard the provision of substantial training as indicative of potential interface design failure.”

For example, iPhones are an engineering marvel, with a huge range of functions, but did you ever need training to use your iPhone? That’s the point.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK