Visualizzazione post con etichetta product design. Mostra tutti i post
Visualizzazione post con etichetta product design. Mostra tutti i post

domenica 11 agosto 2019

Why Is Bad User Experience Design Still A Thing?

Why Is Bad User Experience Design Still A Thing?



The other day I decided to set up two relatively common household products: (1) a wireless router and (2) a portable steamer. The instruction manuals and the resulting experiences of each setup couldn’t have been more different. Can you guess which required more energy, brain power and patience?



Ding ding ding ding ding! It was the steamer!

Why did setting up an appliance with mechanical engineering akin to a kitchen kettle feel like preparing a space shuttle launch…while a device manufactured by a cable company took five minutes with zero aggravation or ambiguity? The answer: User Experience design.

Good UX: The Router Setup


Setting up routers used to involve sitting on the phone with the cable company and wishing it was somebody else’s job. Now it’s as simple as flipping open a glossy, single-page pamphlet and following clear, colorful diagrams placed alongside highly legible text.



There was even some witty Easter Egg copy as if a real human being wrote it and not just a systems engineer:



Relax? No problem! In fact, when the blinking lights stopped flashing after just two minutes, I felt like a technical genius.

Bad UX: The Steamer


The steamer was another story. A list of 14 steps with essentially no visual hierarchy made it nearly impossible to skim for the most important information: how to avoid burning yourself. In fact, this nugget is all the way at the bottom of list item 13, below a mountainous, monotonous section of text. “The water in the reservoir can severely burn skin.”
Seriously?!

The visual aid stresses the importance of moving the steamer up and down. This doesn’t seem like the most important and/or complicated piece of information for a user to grasp.


___________ 

Here’s how I would have written this information: 

Before You Begin:
1. DO NOT fill with water past the max line.
2. DO NOT tilt the steamer back and forth or water will drip out.
Use an up-down motion, not too long in the same spot. 
3. When you’re done OR need a refill, unplug.
Wait 5 minutes after unplugging for unit to cool before handling.

STEP 1: Fill steamer with water.
- Twist reservoir cap clockwise to open.
- Add tap water up to the maximum line. Do not overfill.
- Replace reservoir cap and twist counter-clockwise to close.

STEP 2: Turn on device.
- Plug device into power outlet and press ON.
- When on, the switch will light up.
- Wait 2-3 minutes for unit to heat up.

STEP 3: Steam clothing.
- Always keep unit in an upright position.
- Point steam holes at wrinkled fabric. Move steamer in an up-down direction.
- For best results, pull fabric firmly in place while steaming.

STEP 4: Unplug and allow to cool before handling.
- Even after turned off, any water inside the unit will remain boiling hot.
- Wait 5 minutes before handling.
- Once cool, empty excess water and replace cap.
- Store in a cool, dry place.

_____________ 

People who buy portable steamers value convenience. It should be easier to assemble. My revision lists key safety concerns at the top followed by a logical order of steps, told in fewer words.

source: emsok

lunedì 28 maggio 2018

10 Usability Heuristics with Examples

10 Usability Heuristics with Examples

by SaiChandan Duggirala
Imaginary design by Icons8 to improve the User Experience of a Boarding pass.
User Experience is a qualitative metric subject to many factors. It’s an evolving discipline and it’s evident when the forerunner of great user experiences, Apple, humbly tags their iOS Human Interface Guidelines as Beta. Google termed their material design guidelines as a living document which will be updated regularly. One of the pioneers who tried to objectively evaluate the user experience on digital platforms is Jakob Nielsen with his heuristic evaluation. Though they date back to the 90’s, these general rules of thumb are still valid and are used today.
In this article, I attempt to explain these 10 rules in common language with examples:

1. Visibility of System Status
2. Match between system and the real world
3. User Control and Freedom
4. Consistency and Standards
5. Error Prevention
6. Recognition rather than recall
7. Flexibility and Efficiency of use
8. Aesthetic and minimalist design
9. Help users recognize, diagnose, and recover from errors
10. Help and Documentation

GoDaddy’s Help page

Conclusion:
These guidelines are general rules of thumb and will mostly be applicable to any web & mobile application with some exceptions. Always use your judgment to implement these principles or any other UX practices by keeping yourself in end user’s shoes.
_____ 

Heuristic Evaluations and Expert Reviews

Advantages and Disadvantages of Heuristics

A heuristic evaluation should not replace usability testing. Although the heuristics relate to criteria that affect your site’s usability, the issues identified in a heuristic evaluation are different than those found in a usability test.


         Advantages

  • It can provide some quick and relatively inexpensive feedback to designers.
  • You can obtain feedback early in the design process.
  • Assigning the correct heuristic can help suggest the best corrective measures to designers.
  • You can use it together with other usability testing methodologies.
  • You can conduct usability testing to further examine potential issues.

         Disadvantages

  • It requires knowledge and experience to apply the heuristics effectively.
  • Trained usability experts are sometimes hard to find and can be expensive.
  • You should use multiple experts and aggregate their results.
  • The evaluation may identify more minor issues and fewer major issues.

____

Though many groups have developed heuristics, one of the best-known sources is the set developed by Nielsen’s in 1994.  Nielsen refined the list originally developed in 1990 by himself and Rolf Molich.  Nielsen’s Heuristics include:

  • Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  • Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
  • User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
  • Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
  • Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
  • Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
  • Flexibility and efficiency of use: Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
  • Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
  • Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
  • Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Expert Reviews

In an expert review, the reviewers already know and understand the heuristics. Because of this, reviewers do not use a specific set of heuristics. As a result, the expert review tends to be less formal, and they are not required to assign a specific heuristic to each potential problem.