Please enable JavaScript.
Coggle requires JavaScript to display documents.
CH 2: COGNITIVE PROCESS & PRINCIPLE, UNDERSTANDING USERS IN HMI,…
-
-
-
Use size, weight, and placement to signal importanace
-
-
-
Example: A user sees a red warning icon and immediately interprets it as an indication that something requires attention
-
Example: On a payment page, attention should flow naturally: Amount -> Payment method -> confirm payment
-
-
Temporarily holds information during active tasks; has a strictly limited capacity of 7+_2 items (5-9 items)
-
-
-
-
-
-
-
Ensure every action produces a clear, timely response reinforcing correct usage
-
Core Idea: A good interface should support human thinking, not make users think harder
-
-
-
-
-
Present clear, manageable choices to reduce decision fatigue
When you want to pay in a shopping app, the "Checkout" or "Pay Now" button is large
Imagine clicking Submit, the button instantly turns into loading spinner, followed by green checkmark saying Submission Successful!. That clear response tells your actions went through
- In a phone number field, letters are blocked so you can only type numbers
- The Submit button remains disables (greyed-out) until all required fields like email or address are properly filled out
-
-
- What functions should be included
- How information should be presented
- How users should interact with the system
-
System should be easy to learn and intuitive to use,
-
-
- Response - reacting quickly to input
- Reliable - behaving consistently over time
- Clear - communicating without ambiguity
- Consistent - following predictable patterns
-
Users expect to move through a system intuitively, without needing to read instruction
Buttons, labels, and behaviors should work the same way across all parts of the system