1. Discussion
Nedas Matulionis 09/07/2018

2. Usability Testing Quantitative Qualitative
Formal interaction with the user
Statistically significant
Data analysis is important
Huge user participant number
More informal and personal feedback
Statistical analysis is not needed, yay!
Identical to actual user experience
Fewer participant number

3. Why does it work? Why it is not popular?
All sites have problems, even Amazon
Most of the serious problems are easy to find
It makes you a better designer
Why it is not popular?
Usability testing requires time
Reluctance to show work before it is done

5. The 4 step process:
Welcome
Questioning
Tour
Tasks

7. What problems did you guys notice?

9. “The Big Honkin’ Test vs. Do-It-Yourself Testing
Time spent for testing
When the tests are done
Number of tests
Number of participants
Who are the participants
Where are the tests done
Who is watching
Reporting
Who identifies the problems
Purpose
Recording a video
Costs
“The Big Honkin’ Test vs. Do-It-Yourself Testing

10. “We don’t have enough done yet.”
Common Excuses
“It’s too rough.”
“Why waste people’s time looking at something we know we’re going to change?”
“We don’t have enough done yet.”

11. Testing your existing site Testing other people’s test
Testing wireframes
Testing page designs
Testing the sketch on the napkin

13. Make tasks to scenarios
List of tasks
Make tasks to scenarios
Don’t allow to use search or other sites
Pilot test

14. Norman, “Knowledge in the Head and in the World”

15. Imprecise knowledge can come from:
Knowledge is both in the head and in the world
Great precision is not required
Natural constraints exist in the world
Knowledge of cultural constraints and conventions exists in the head

16. Declarative knowledge
Procedural knowledge

17. Constraints Simplify Memory
“The constraints by themselves are often not sufficient to determine the proper reassembly of the device – mistakes do get made – constraints reduce the amount that must be learned to a reasonable quantity.”

18. Knowledge in the Head
Required difficulty of remembering specific information creates a new layer of vulnerability.

19. The Structure of Memory
Short-term memory
Long-term memory
“It is the memory of just present. Information is retained automatically and retrieved without effort; but the amount is severely limited.”
“It is the memory of past. It takes time for information to get to LTM and effort to get it out. Sleep plays an important role.”

20. Knowledge Retrieval Types
Memory for arbitrary things: there is no meaning and no relationship.
Memory for meaningful things: meaningful relationships are formed.
“Design implications are clear: provide meaningful structures: constraints, mapping and feedback. The most effective way of helping people remember is to make it unnecessary.”
For designers: the easier it is to enter information to relevant equipment, the less chance of memory error.

21. Tradeoffs Knowledge in the World Knowledge in the Head
Information is available whenever perceivable
Interpretation is learning, depends on skill
Slowed by the need to find knowledge
Ease of use at first is high
Can be unpleasant because a lot of memory is required
Search is required if material is not in the head
Requires learning, easy if good conceptual model
Efficient if learnt that it is automatic
Ease of use at first is low
No need for visibility: more pleasant

22. Discussion Questions
Can you think of personal experiences where you lacked knowledge precision? Why do you think it happened?
Education systems nowadays tend to be very scientific. Is it a good thing?
Can anybody think of a solution to the password problem?