Miller’s Law

Keep essential information available instead of asking people to remember it.

01 / UNDERSTAND

The idea

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.

1PasswordEXAMPLE 01

Carry the verification code into the sign-in step

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.

1Password · Interface exampleProduct reference
GoogleEXAMPLE 02

Put a checklist where the task happens

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.

Google · Interface exampleProduct reference

03 / CONNECT

Why it matters.

Measure transcription errors, repeated lookups and recovery effort in tasks that require people to carry information between steps.

Possible influences to investigate, rather than guaranteed outcomes for every product.

04 / APPLY

Put it into practice.

  1. 01

    Keep task-critical details visible while they are needed

  2. 02

    Support copy, paste and safe autofill

  3. 03

    Test recall demands rather than counting menu items

05 / EXPLORE WITH UPSLIDE

Apply it with Upslide.

Use a practical guide, read a deeper explanation, or examine a related Upslide project.

Examine how organizational settings and related context remain available during administrative tasks.

Explore HR Software UX

Keep exploring

70 PRINCIPLES TO EXPLORE

The UX glossary

Current principle: 40 of 70 · Alphabetical order

THE UX GLOSSARY

Find your next idea.

PASS THE IDEA ALONG

Share this page

LinkedIn WhatsApp Email

UPSLIDE DESIGN STUDIO

Watch the explainer

Playback unavailable? Watch on YouTube ↗

SHARE WHAT YOU NOTICED

Contribute an example.

Share a screenshot and a few words. We’ll review it before publishing.

Add links or contact details (optional)

Reviewed by the Upslide team.