Miller’s research highlighted limits in immediate memory, but the familiar seven-plus-or-minus-two phrase is not a limit for menu items or cards. Working-memory performance depends on the material, the task, prior knowledge and how information is grouped. A useful design response is to reduce avoidable remembering while someone is doing another task.
Reading a visible list is different from recalling a list that has disappeared. Navigation does not need to stop at seven items simply because Miller studied immediate recall. Later research often finds smaller central-memory limits under specific experimental conditions, which is another reason to avoid turning one number into a universal layout rule. In practice, look for the places where people carry details across screens: a verification code, an order number or the steps remaining in a procedure. Keep those details available, support copying or safe autofill, and test mistakes in the real workflow.
02 / RECOGNISE
See it in real products.
Examples of how the principle can appear in an interface.
1Password can store one-time passwords and fill them during sign-in; its support example also shows a code that can be copied. The interface can remove the need to remember a changing sequence while switching applications. Successful authentication still depends on clear account matching and appropriate security controls.
Google Keep’s single-note widget makes a note or list available on the Android home screen and allows checklist items to be toggled there. The list acts as an external memory aid: the person can check the next item without holding the whole list in mind.