A6.10
Misuse of memory-capacity numbers
Cards in this group · 7
- A6.10.1Classic memory-capacity numbers don't apply to counting visible options
- A6.10.2A long menu slows people down because scanning it costs time, not because it overloads memory
- A6.10.3Citing a capacity finding requires checking the original task type
- A6.10.4The classic capacity number came from an absolute-judgment task on a single dimension, structurally unlike most interface scenarios
- A6.10.5Popular science flattened the number into a universal design rule, detached from its original conditions
- A6.10.6Design limits on password length or color count that borrow this number lack empirical support
- A6.10.7Deciding whether a design limit should invoke memory capacity requires first confirming the user is really doing unprompted recall