Errors are not exceptional events in the life of a digital product; they are inevitable ones. Every interface will be misread, misused, or misunderstood by someone, at some point, for reasons that rarely have much to do with the user's intelligence. The question is not whether errors will occur, but how well the product is designed to handle them when they do.
Two of the most instructive error types to design around are misconceptions and misunderstandings. They are related - both involve a gap between what the user expects and what the system does - but they operate differently, and they call for different design responses.
Misconceptions
What are Misconceptions?
A misconception is a gap between a user's mental model and the way a system actually works. The user is not confused about what happened; they have a clear belief about how something functions, and that belief is simply wrong.
The oven dial is a well-worn example. Many people turn the dial to its maximum temperature expecting it to heat faster. It doesn't; the heating element operates at a fixed rate regardless of the target, but the design of most dials gives no indication of this, so the mental model persists. The user is not careless or inattentive - they are applying a reasonable model to a system that does nothing to correct it.
Designing for Misconceptions
In digital interfaces, misconceptions tend to cluster around anything that behaves differently from convention.
Users carry expectations built from hundreds of previous interactions with similar products; when an element looks like it should behave one way and does another, the misconception is almost always a design problem, not a user one.
Designing for misconceptions means closing the gap between expectation and reality: showing current state rather than target state, providing feedback that confirms or corrects the user's model in the moment. The goal is not to educate the user about how the system works; it is to make the system's behaviour obvious enough that no education is required.
Misunderstandings
What are Misunderstandings?
A misunderstanding error is different in character. Here, the user does not have a false belief about the system - they have incorrectly connected an action to an outcome; two things happen in sequence, and the user assumes causation where there is only coincidence.
The classic scenario: an app closes, then the computer crashes. The user's first thought is that closing the app caused the crash. It almost certainly didn't, but without a clear account of what actually happened, the user builds a story from proximity. Most of the time, they blame themselves.
Designing for Misunderstandings
A significant proportion of users assume that friction, failure, and confusion in a product are consequences of their own inexperience rather than problems with the product itself; the effect is that poor design not only frustrates users, it quietly undermines their confidence. They leave with the wrong lesson. Designing for misunderstandings means making cause and effect legible: when something unexpected happens, the user needs enough information to understand why - not a technical explanation, but a clear, honest account of what occurred and what to do next.
Error messages that say "Something went wrong" are not neutral; they leave the user to fill in the gap, and users rarely fill it generously. A message that explains and offers a path forward is not just more useful, it is more respectful.
In summary
The most useful framing for error design is not "how do we stop errors happening" - errors are going to happen. It is "how do we make the product easy to recover from, and honest about what went wrong".
Misconceptions and misunderstandings are most often symptoms of a design that does not communicate clearly enough with the person using it; the fix is almost never about the user.
