1/9
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Visibility of System Status
The system should always keep users informed about what's happening through timely and appropriate feedback.
Match Between the System and the Real World
The design should speak the users' language, following real-world conventions so information appears in a natural and logical order.
User Control and Freedom
Users need clearly marked ways to exit or undo actions so they don't feel trapped or frustrated.
Consistency and Standards
The interface should use consistent words, situations, and actions, adhering to both internal and industry conventions so users don't have to question what means what.
Error Prevention
The best designs stop errors from occurring by eliminating error-prone conditions or offering confirmation options instead of relying solely on error messages.
Recognition Rather than Recall
It minimizes memory load by making options and information visible or easily retrievable, so users don't need to recall information.
Flexibility and Efficiency of Use
The design should cater to both novices and experts—e.g., by providing shortcuts or customization so users can tailor frequent actions.
Aesthetic and Minimalist Design
Interfaces should exclude irrelevant information—every added element competes for attention; focus on content and design that supports primary goals.
Help Users Recognize, Diagnose, and Recover from Errors
Error messages should use plain language, clearly explain the problem, and offer constructive solutions, with visuals to help users notice them.
Help and Documentation
While ideally unnecessary, when help is needed it should be easy to search, task-focused, concise, and contextually provided with clear steps.