Change blindness

We are surprisingly blind to changes that happen during a flicker, reload or blink. Without an unbroken motion cue, even a big change can sit in plain sight until you go hunting for it.

The demo

We will alternate between two versions of a dashboard mockup with a single subtle difference. Can you spot it?

What this demo shows (text version)

An interactive spot-the-difference game designed to demonstrate change blindness. Two layout states of a status dashboard alternate repeatedly. In one state, the database sync service is listed as 'Pending' (amber badge); in the other, it is 'Success' (green badge).

When the blank disruption mask is enabled, a grey screen flash separates the states. Because the screen flashes, the user fails to notice the localised change: the motion-detection sensors in the eye are overwhelmed. When the mask is disabled, the status badge changes directly, and the motion transient makes the change immediately obvious.

With the mask on, the change hid in plain sight until you searched cell by cell. That is change blindness - and it is why a silent update needs a transition or a notice, or people simply won't see it happen.

The eye catches change by catching movement. Update something quietly - a total, a status, a count - with no transition, and you have removed the very signal people rely on to notice.

Any time the screen blanks or jumps between states, you have covered the change. Animate the thing that moved, or tell people it moved; don't assume they were watching the moment it happened.