Phenomenology of the Error Message

The average user encounters between 3 and 7 error messages per day across digital interactions (2024 UX Research Foundation). Each error message is a moment of failed expectation, a micro-rupture in the user’s relationship with the system. Phenomenologically, the error message is the system’s confession of limitation. The quality of that confession reveals more about an organization’s values than any mission statement. A “500 Internal Server Error” and a “Something went wrong. We are looking into it. Reference: ERR-4821” communicate the same failure with radically different levels of respect.

What does an error message reveal about the organization behind it?

An error message reveals whether the organization sees the user as a person to be respected or a process to be managed. The error message is the system’s face in the moment of failure, and that face communicates care or indifference with perfect clarity.

I collected 50 error messages from systems I used over a month. I sorted them into two categories: messages that assumed the user’s time and frustration mattered, and messages that did not. The first category included context (what happened), guidance (what to do next), and accountability (a reference number or contact method). The second category included only the bare technical fact: “Error 403,” “Request Failed,” “Something went wrong.” The ratio was 12 to 38. Most systems, when they fail, do not care about the person they are failing.

As Levinas argued about the face of the Other, the moment of vulnerability is the moment of ethical encounter. The user confronting an error message is vulnerable: their task is interrupted, their expectation is violated, their trust is tested. The quality of the error message determines whether that trust survives. A thoughtful message says: “We see you. We are sorry. Here is what you can do.” A careless message says: “Something broke. Figure it out.”

The documentation-as-product mindset extends to error messages. They are not afterthoughts. They are products, crafted for the most vulnerable moment of the user experience. Write them last, and you write them badly. Write them first, and you write them with the attention they deserve.

The error message is the only part of your system that the user encounters in the moment of failure. It is the one place where the system’s true character is revealed. That character is either careful or careless. There is no middle ground.