Change blindness

Websites and apps are constantly changing—new features, redesigned menus, updated content. Companies invest heavily in these improvements and expect users to notice and adopt them. Yet studies reveal a paradox: even large, obvious changes go unnoticed. Users complain about missing features that have existed for years. The question is: Why do even conspicuous changes remain invisible? What factors determine whether users perceive them—and what does the evidence tell us?

Studies

The Flicker Paradigm

In 1997, Ronald Rensink, Kevin O'Regan, and James Clark conducted groundbreaking experiments at Cambridge University. They showed participants photographs of everyday scenes—such as an airplane in front of buildings. After 240 milliseconds, a blank screen appeared briefly, followed by the same photo with one alteration: the airplane's engine had disappeared. This alternation repeated every second. The astonishing finding: participants took an average of 10 seconds and more than 10 repetitions to detect the change—even though they were actively searching for it. Some overlooked even substantial changes for over a minute. Without the brief interruption, the change would have been immediately noticeable.

The Invisible Person

Daniel Simons and Daniel Levin demonstrated change blindness in a real-world, everyday situation in 1998. An experimenter approached passersby on campus to ask for directions. During the conversation, two people carried a door between them—creating a brief but complete interruption. At that moment, the experimenter switched places with another person who had been concealed behind the door. The two individuals differed markedly: different clothing, different voice, different build. The astonishing result: only 50% of participants noticed the switch. They continued the conversation with the new person without any apparent awareness of the change. The effect was even more pronounced among older participants: only 33% detected the substitution.

Principle

Which principle for Customer Experience Design can be derived from this? The change blindness phenomenon demonstrates that even significant changes in digital products can go completely unnoticed if they are not actively brought into users' attentional focus. For customer experience design, this means that new features, improved functions, or important updates must be deliberately communicated and visually highlighted to achieve their intended effect. This becomes particularly critical with incremental improvements or subtle interface changes that objectively enhance user experience but remain subjectively unperceived. The principle operates most powerfully in familiar environments where users function on autopilot, but becomes less relevant when users are already actively seeking changes. The following guidelines show how to implement this principle in practice.

Guidelines

Explicitly announce changes

Don't rely on users to discover new features or redesigned areas on their own. Use targeted tooltips, modal overlays, or highlight animations to draw attention to changes. Announcements should appear in the relevant usage context—not just on a separate "What's New" page. For example, if a button has moved to a new position, show an arrow with a brief explanation on the user's first visit.

Maintain continuity during updates

Avoid abrupt layout changes during use. When elements need to shift position, use smooth animations that make the transition visible. The brain tracks changes more effectively when they occur fluidly rather than suddenly. For example, when a filter menu moves from left to right, animate the movement over 300-500ms instead of having it appear instantly in the new location. This reduces cognitive load and helps users update their mental model of the interface.

Place change logs contextually

Instead of collecting all changes in a central location, display notifications exactly where users need them. When a feature has been revised, a 'New' badge appears directly on the affected element. This approach is more effective than a general newsletter or change overview that users must actively seek out. Combine this with version numbers or 'Last updated' timestamps so returning users can quickly identify whether something has changed since their last visit.

Progressive Disclosure in Redesigns

For major interface changes, offer an optional tour that explains new elements step by step. Don't force it, but make it prominently available with a clear value proposition: "Discover 3 new features in 30 seconds." Users who opt in experience a brief sequence with spotlight effects highlighting the most important changes. This approach is more effective than lengthy videos or text tutorials that users rarely engage with.