9/14/20

Outline
UX-driven
Heuristics for
Every Designer
Why should UX-driven
Why
Hestiasari Rante UX vs UI I care about Heuristics
‘heuristic’?
UX? by Nielsen
Webinar Series #9
Magister Terapan PENS
3 September 2020

UX vs UI

Source: www.crc-inc.com, 2016

1
 9/14/20

Why ‘heuristic’?

Source: axisbits, 2020

Heuristics can be thought of as rules of thumb.

A heuristic evaluation in UX design is a way to test

whether a prototype functions well as it desired.
Why should I care about UX?
Unlike the user-testing, where the prototype is
evaluated by users, in a heuristic evaluation the
prototype is evaluated by usability experts.

2
 9/14/20

Norman door = Bad UX design

The Norman door is basically any door that is confusing or

difficult to use. It was named after (and not by) design guru
Don Norman to define this all-too-common design foible.
(Morgan, 2018)

3
 9/14/20

DON’T
MAKE ME
THINK

4
 9/14/20

1: Visibility of system status

The system should always keep users informed about what is going on, through appropriate
feedback within reasonable time.

UX-driven Heuristics by Nielsen

2: Match between system and the real world 3: User control and freedom
The system should speak the users' language, with words, phrases and concepts familiar to the user, Users often choose system functions by mistake and will need a clearly marked "emergency exit" to
rather than system-oriented terms. Follow real-world conventions (mental models), making leave the unwanted state without having to go through an extended dialogue. Support undo and
information appear in a natural and logical order. redo.

5
 9/14/20

4: Consistency and standards 5: Error prevention

Even better than good error messages is a careful design which prevents a problem from occurring
Users should not have to wonder whether different words, situations, or actions mean the in the first place. Either eliminate error-prone conditions or check for them and present users with a
same thing. Follow platform conventions. confirmation option before they commit to the action.

Radio buttons are meant to be used when there is only one

option allowed. Checkboxes on the other hand should be used
only when the user is allowed more than one option.

6: Recognition rather than recall 7: Flexibility and efficiency of use

Accelerators — unseen by the novice user — may often speed up the interaction for the expert user
Minimize the user's memory load by making objects, actions, and options visible. The user should
such that the system can cater to both inexperienced and experienced users. Allow users to tailor
not have to remember information from one part of the dialogue to another. Instructions for use of
frequent actions.
the system should be visible or easily retrievable whenever appropriate.

Recognition refers to our ability to “recognize” an event or piece of

information as being familiar, while recall designates the retrieval of
related details from memory.

6
 9/14/20

8: Aesthetic and minimalist design 9: Help users recognize, diagnose, and recover
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
from errors
Error messages should be expressed in plain language (no codes), precisely indicate the problem,
relative visibility.
and constructively suggest a solution.

10: 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.

THANK YOU