Module 1: Why Evaluate UX Experience? Flashcards
Utility
The extent to which a user perceives a technology to improve their ability to perform a task
Effectiveness
The precision, ease and level to which users achieve a specific goal. How users expect the technology to behave
Efficiency
The quickness with which users’ goals can be accomplished accurately and completely
Satisfaction
the absence of discomfort and frustration towards a product
Learnability
the extent to which a digital product/service allows users to quickly become familiar w/ them (intuitivity)
Accessibility
the extent to which X can be used by people in a population w/broad characteristics
ISO 9241-210 definition of user experience
“a person’s perceptions and responses resulting from the use and/or intended use of a product, system, or service”
Perception
is the conscious experience , subject to cognitive bias (able to explain and verbalize)
Retrospective bias
difficult to recall, the perception might be tainted from the 1st impression’s last moment
Response
automatic and unconcious
Expert evaluation/inspection based
based on previously determined guidelines (Jabok Neilson’s 10 general principles for interaction design)
Jakob Neilson’s 10 general principles for interaction design
- Visibility of system status
- Match between system status
- User control & freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimal
- Help users recognize, diagnose, & recover from errors
- Help and documentation
what are the 3 types of evaluation?
expert evaluation (heuristics), user-based and conformity assessments
difference between formative and summative evaluation?
formative: done during the development phase of the product
(aims for recommendations + improvement)
(100x less expensive)
summative: done when design is near completion
(aims to evaluate quality and met of requirements)
Type 1 Error
Concluding that “There are No errors!” when in fact, there were
Type 2 Error
“There are errors!” when in fact there were not
System
combination of interacting elements organized to achieve one or more stated purposes
User interfacee
all the components of an interactive system
Prototype
representation of all or part of an interactive system
User
person interacting w/ a system/product/service
Purpose
expected result
context of use
refers to users, tasks equipment, etc in which a product is used
Task
activity required to achieve a goal
Action
user behaviour that the system accepts as a request for a particular operation
Objects of the task
key units of info/data which users interact to perform their tasks
user interface elements
basic components of a user interface presented to the user by the interactive system
dialogue
interaction between user and system
need
prerequisite identified as a necessity for a user
requirement
condition/capability that must be met by the system
