When users act differently than expected
05. Jun 2026
Everything actually looked good. The user flows seemed logical, the most important functions were visibly positioned and the entire process made sense from a product perspective. Nevertheless, questions remained unanswered. Why were certain functions hardly used? Why did users drop out at certain points? Or how would they deal with a new feature that wasn't even live yet?
Reading time: 3 minutes
What we see again and again in user studies - and why the real insights lie between the data
Suddenly it became clear how differently people perceive digital products. Navigation elements that were supposed to provide orientation hardly played a role for them. Instead of the intended user path, completely different paths through the application emerged. They revealed where uncertainties arose and expectations were not met.
We experience such situations in user studies more often than many would expect. Not because users use applications "incorrectly", but because they use digital products with their own expectations and experiences. This is exactly where the most exciting findings arise.
Why the look before the click is crucial
Many teams today are data-driven. Analytics, KPIs and A/B tests provide valuable answers to important questions:
- Where do users drop out?
- Which functions are used?
- Which variant performs better?
What we observe in projects, however: The really interesting questions start exactly where traditional data ends.
A dashboard does show that users drop out at a certain point. However, it rarely shows why they do this.
It often becomes crucial even before the actual click: A quick glance at an element, a hesitation, a moment of uncertainty or a search for orientation. It is precisely these seemingly small situations that determine whether a process works intuitively - or not.
People see things - and still don't use them
We encounter one situation time and again in tests: users perceive elements, but evaluate them differently than originally assumed.
Buttons, navigations or content are perceived, but do not always lead to the expected action.
We regularly observe this seemingly contradictory behavior in user studies.
Perception does not automatically lead to interaction.
An element can be visible without users classifying it as relevant. Navigations are perceived, but not always used as an orientation aid. And it is precisely at this point that we are no longer talking about visibility or placement, but about expectations and mental models.
Eye tracking does not simply show eye movements - but thought processes
That's why we use eye tracking. It helps to make visible where perception and behavior diverge. This raises questions that were previously missing:
- Why was something perceived but ignored?
- Why does uncertainty arise at precisely this point?
- Why does a user path not work as it was originally intended?
The actual insights are not gained through gaze data alone, but through the combination of observed behavior and qualitative queries.
Because users don't always say everything. At the same time, they find it difficult to explain their own behavior.
Conclusion: Good user experience rarely comes from assumptions
This is exactly where user research comes in. It helps to make causes visible, understand correlations and view products from the perspective of the people who actually use them.
Eye tracking can provide additional insights and reveal areas where users have difficulties. The method is particularly valuable in combination with qualitative methods, as it allows us to better understand why people act in a certain way.
