UX Design · Study deck
UX Evaluation: Evidence for Decisions
Is this setup flow ready for a field pilot?
UX Uma is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: The evaluator checks whether current, stale, offline, updating, and low-battery states have different labels, whether color is not the only signal, whether the latest timestamp is visible, and whether the next action is clear.
- Explain: Together,: Decision and errors, recovery, quotes frame the task-based usability testing claim: iot user testing record linking participant task, observed behavior, device state, support evidence, issue severity, and follow-up condition.
- Explain: The issue record should separate user hesitation from technical state: BLE timeout, wrong network, Thread border-router absence, expired invite, account-role mismatch, or cloud service delay.
Major section
Heuristic Review
Heuristic review is not proof that real users will succeed.
- Together,: Is it discoverable? And: Is it understandable? Frame the heuristic review claim: ux problem diagnosis decision tree for discoverability, understandability, and executability.
- For heuristic review,: Is it discoverable? Supplies visible evidence;: Is it understandable? Constrains the decision.
Major section
Task-Based Usability Testing
Together,: Decision and errors, recovery, quotes frame the task-based usability testing claim: iot user testing record linking participant task, observed behavior, device state, support evidence, issue severity, and follow-up condition.
- "You are leaving for a week.
Major section
Incremental Examples
A beginner evaluation can inspect a thermostat or room-sensor card before user testing.
- The evaluator checks whether current, stale, offline, updating, and low-battery states have different labels, whether color is not the only signal, whether the latest timestamp is visible, and whether the next action is clear.
- The test should include the physical device, mobile app, QR or setup code, Bluetooth discovery, Wi-Fi provisioning, Matter commissioning or vendor-cloud account binding, permission prompts, and a support path.
- The issue record should separate user hesitation from technical state: BLE timeout, wrong network, Thread border-router absence, expired invite, account-role mismatch, or cloud service delay.
Major section
Common Defects
Opinion testing: asking "what do you think?" instead of observing task completion.
- Heuristic overconfidence: treating expert review as proof that real users will succeed.
- Accessibility late review: checking accessibility after layout, controls, and device placement are already accepted.
- No support-path test: ignoring whether support can diagnose and explain failures.
Deck summary
Key takeaways
Heuristic review is not proof that real users will succeed.
- Together,: Decision and errors, recovery, quotes frame the task-based usability testing claim: iot user testing record linking participant task, observed behavior, device state, support evidence, issue severity, and follow-up condition.
- A beginner evaluation can inspect a thermostat or room-sensor card before user testing.
- Opinion testing: asking "what do you think?" instead of observing task completion.
Retrieval practice
Recall check
UX Uma says: answer from memory, then check your reasoning.
Q1A team asks five employees to explore a smart-home app and say what they think. Everyone says it looks clean. After launch, customers cannot complete setup when Wi-Fi pairing fails. What was the main evaluation problem?
Show answer
Answer: A Evaluation should be task-based, representative, and include realistic connected-system failure states.
Print reference
Answers
Answer key.
- A · Evaluation should be task-based, representative, and include realistic connected-system failure states.