Have you ever wondered why you delete a new app in frustration after five minutes? You tap a button and expect one thing to happen. Instead, an unexpected menu opens or your entry simply disappears. You lose time, feel foolish, and give up. These negative surprises cost you patience and trust in products, and sometimes even trust in yourself.
Research in human-computer interaction has shown since the 1970s that systems that behave differently than expected increase mental effort and lead to errors and drop-offs. This principle applies not only to software, but also to websites, devices, and even interactions between people. Whether you use an app, visit a website, or talk with colleagues, unexpected behaviour interrupts your flow.
You are not incapable when you struggle with a badly designed interface. The problem is the design, not you. When products go against mental models, confusion follows. That is normal and predictable.
In this article, you will learn what the Principle of Least Astonishment, or POLA, means and how it affects everyday life. I will share practical examples from apps, websites, and work tools. You will also get strategies for recognising frustration as a user and avoiding it as a designer.
What is the Principle of Least Astonishment?
The Principle of Least Astonishment, or POLA, says that systems should behave as users expect. When you click “Save”, your work should be saved, not interrupted by a pop-up window. When you see a link, it should be blue and underlined because that is what your brain has learned to recognise.
POLA comes from software development, but it applies everywhere. It relies on your existing mental models. These are predictions your brain forms from experience. You have learned that a shopping basket icon takes you to the products you selected. If it deletes those items instead, it breaks your expectation. You feel cheated.
Imagine ordering something online and clicking “Checkout”. Suddenly all the items disappear from your basket. You are confused and frustrated, so you shop elsewhere. That violates POLA. Good design avoids such surprises and makes interactions predictable.
Why does it happen?
Your brain makes predictions. It uses experience to anticipate what will happen next. When you open a familiar app, your brain expects menus and buttons it recognises. These predictions reduce cognitive load. You do not have to relearn how something works every time.
When systems break those expectations, mental effort increases. Your brain has to learn new patterns, which takes time and energy. This leads to frustration and mistakes. Studies regularly show that inconsistent interfaces create negative experiences. People leave because they feel overwhelmed.
This mechanism resembles the psychological idea of “learned helplessness”. When behaviour is unpredictable, you can lose a sense of control. You give up because you do not know what works. That is why consistent, predictable designs matter. They create a sense of security and trust.
Everyday examples
You are working on an important project and click “Save” in your software. You expect it to overwrite the current version automatically, as other programs do. Instead, a complicated menu opens with unclear options. You lose time, feel annoyed, and wonder whether your work is even saved. This is POLA in action: the software behaves differently than you expected.
Or imagine sharing a file in a team app and expecting everyone on the team to get an automatic notification, as you are used to in Slack. Nothing happens. Your meeting fails because nobody saw the file. The app did not meet your expectation. You feel let down and look for alternatives.
POLA also appears outside the tech world. You meet a friend for coffee and expect things to go as usual. This time, without warning, things work differently. You are surprised and wonder whether something is wrong. It breaks your pattern and makes you feel uncertain. Consistency builds trust. Unnecessary surprises get in the way.
With and without awareness of POLA
Without awareness of POLA: You click “Buy” in an online shop and expect a confirmation. Instead, an advertising pop-up opens. You close the site in frustration and buy from another seller. The shop loses you as a customer because it broke your expectation.
With awareness of POLA: The “Buy” button takes you straight to a secure confirmation, as you expect from other shops. You complete your purchase quickly and easily. You feel safe and are likely to return because the experience met your expectations.
How to respond
If you are a designer or developer, you can apply POLA deliberately. As a user, it can also help you understand and explain your frustration. Here are practical steps:
- Write down moments of frustration. When an app or website annoys you, ask, “Was that what I expected?” Check whether the problem is a violation of POLA.
- Test with real users. Before releasing a design, let people from your target audience use it. Watch where they get stuck.
- Follow established conventions. Use standard navigation patterns, underlined links, and familiar icons. Build on what users already know.
- Make expectations clear. If something works differently than usual, explain it clearly. Tell users, “This button works like this.”
- Measure drop-off rates. Track where users leave. High drop-off rates often point to behaviour they did not expect. Make changes and test again.
Key takeaways
- The Principle of Least Astonishment says that systems should behave as users expect.
- Unexpected behaviour increases mental effort and can lead to frustration and drop-offs.
- Good design uses existing mental models and follows familiar conventions.
- POLA applies to software, websites, devices, and interactions between people.
- Try this week: note one frustrating experience with an app and ask whether it violated POLA.