Writing Better Error Messages
Why technical jargon frustrates users and how to craft actionable, empathetic error states.
Emma Watson
Content Designer
Turn points of friction into moments of guidance.
An error message saying 'NullPointerException at line 42' helps developers but alienates users. Good error states explain what went wrong in plain language, avoid blaming the user, and offer a clear path to resolution.
This approach has far-reaching implications for how we design and build digital experiences. By prioritizing structure, clarity, and user needs from the very beginning, we create products that are not only more usable but also more resilient to change over time.
“An error is a failure of the system, not the user.”
The Path Forward
As we continue building more complex applications, returning to fundamental principles of design and architecture becomes essential. It allows us to create scalable, maintainable products without sacrificing the end-user experience. The craft lies in the details.
By adopting a structurally sound approach — whether through semantic HTML, thoughtful component architectures, or refined typography — we ensure our applications not only look premium but feel durable, performant, and genuinely useful.