UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

How bad error messages are harming your users

Do’s and don’ts for better error messages.

Kayla J Heffernan
UX Collective
Published in
5 min readJul 20, 2021

Person looking at computer with hands on their head in frustration
Photo by Elisa Ventur on Unsplash

In 2015, before I wrote on Medium, I wrote this article on my personal website https://www.kaylaheffernan.com/blog/2014/12/9/error-messages. For some reason, according to the analytics on kaylaheffernan.com, this has had a recent spike in readers so I thought I would cross-post to Medium to reach more people. Slightly updated from the original to flow better.

Research from 2009 (Riedl, R et al, 2009) showed error messages can increase cortisol (the stress hormone) levels in individuals when they were interacting with computers that faced a system breakdown. Our error messages are increasing stress and anxiety. This has been illustrated before by Jennifer Aldrich of User Experience Rocks (see comic below).

Section one — a user interacting with a computer. The computer presents a generic “Error” message. The user, depicted stressed with their hair standing on end, is yelling “Agggh! An error! Close the browser! Shut it down!” Section two shows a user interacting with a computer. This time the computer gives them a more meaningful error message. The user, with a smile of their face, says “Silly website. I’ll refresh my screen”
UX and Error Messages: “Stop Scaring Your Users” by Jennifer Aldrich of Userexperiencesrocks.com

We have a responsibility to carefully consider our error messages as to not harm our users. Good error messages are particularly important as they:

  • Increase speed of use;
  • Increase users subjective satisfaction with our sites; and,
  • Reduce repeat errors and complaints while increasing the learnability of the system.

These three mean that users can ‘self-serve’ and correct errors allowing them to complete their goal (and give your company money!). This also saves on support costs if fewer people are raising tickets or calling a help centre. Thanks to James McGinty for reminding me to make this explicit.

So, how do you write good error messages?

I’ve put together a list of some do’s and don’ts for good error messages.

Errors happen. But the golden rule should be prevention first. Make it easy for your users to input the data in the correct format and explain to them exactly what they need to do. Errors should be a last resort. Then, when you do need to show error messages follow these do’s and don'ts.

Do the following

  • Be explicit and indicate something has gone wrong

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Written by Kayla J Heffernan

Head of UX. Passionate about solving ambiguous problems with solutions that are accessible and inclusive. I write every couple of months about design.

Responses (2)

Write a response

Two ways to look at this - understand the error and write it in a simple manner.
If the error is complex, write a generic message.
Eg - Oops! Our servers have encountered a problem at the moment. Please try again later.
I enjoyed reading this article.

--

Still great points from the original. As ‘a programmer’, I think you have undersold the benefit it is to the organisation to have clear and helpful error messages. The benefit is twofold: 1 - the user has a chance to 'self serve' and fix the problem…

--