20 ms·
From the article: "I don’t have an clear actionable answer to these issues and this piece is more of a rant than anything" Not too helpful, then. There are use
by Animats 3y ago
From the article: "I don’t have an clear actionable answer to these issues and this piece is more of a rant than anything" Not too helpful, then.
There are useful and testable ways to think about usability. A good metric is, can you achieve the goal without backtracking? This is tested by making videos of people attempting the task and observing when they have to back up. Such user testing was common in the era of desktop applications which cost money to buy and had to keep customers happy. It is seldom seen in the era of webcrap.
Not having to backtrack is close to what mathematicians call "obvious". Differentation is obvious but integration is not.[1]
The avionics people work hard on this.[2] That's a rather long document which collects info from other sources. A few excerpts:
• The primary test for designation of color is:
- Red - Immediate action required
- Amber - Pilot action (other than immediate) required
- Green - Safe operation indicated.
- Other advisory lights - any color distinct from the above.
This has been a standard for industrial equipment and aircraft for a century.
• If the flightcrew’s only way to determine non-normal values is by monitoring display values
presented on the display, the equipment should offer qualitative display formats. Qualitative display
formats convey rate and trend information better than quantitative (e.g. digital) presentations.
• Controls whose functions are not obvious (they mean yoke, throttles, etc.) should be marked or identified so that a flightcrew
member with little or no familiarity with the airplane is able to rapidly, accurately, and consistently
identify their functions. All the abbreviations seen on cockpit controls are standardized. There's a list, and it's not that long.
• To avoid visual clutter, graphic elements should be included only if they add useful information
content, reduce flightcrew access or interpretation time, or decrease the probability of
interpretation error.
The section on "Menus", on page 156, is definitely worth reading. And following.
This stuff isn't a mysterious unknown. It's well-known and well documented in aerospace.
[1] https://xkcd.com/2117/ https://xkcd.com/2117/
[2] https://www.volpe.dot.gov/sites/volpe.dot.gov/files/docs/Human_Factors_Considerations_in_the_Design_and_Evaluation_of_Flight_Deck_Displays_and_Controls_V2.pdf https://www.volpe.dot.gov/sites/volpe.dot.gov/files/docs/Hum...
- pdonis 3y ago> what mathematicians call "obvious" My favorite joke about this: a math professor starts the class by writing an equation on the board. Then he tells the class: "from this, it is obvious that--" and writes a second equation below the first. Then the professor stops, wrinkles his forehead, and mutters, "Wait a minute, I may be wrong...". He thinks a few moments more, and then starts writing more equations. More and more equations. Equations covering the whole board. He does this for the rest of the class, and then just before the bell rings, he says "Aha! I was right after all! It is obvious that the second equation follows from the first."