Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

More useless error messages

Freshness Warning
This blog post is over 20 years old. It's possible that the information you read below isn't current and the links no longer work.

1 Jul 2003

User frustration rides high when a program gives a useless error message. Not only is the error message unhelpful, but sort of scary. “Money can’t be closed?” Do you mean not now because there was an error, or ever?

Perhaps it would be better to give the user some clue as to why they are getting the error so that they can fix the problem.

Adam Gaffin
July 2, 2003 7:15 AM

As long as we're at it, let's get rid of all the popup boxes that make you click "OK" when there's no other option.

Adam Kalsey
July 2, 2003 8:40 AM

I once got an error window that had "Error" in the title and the only other thing on the window was an OK button. I wish I'd thought of taking a screen shot.

Dan
July 2, 2003 10:57 AM

Amen. Error messages that have error codes that you don't know actually create a worse situation because you have to take time to learn what error description correlates to the error code. No doubt, the findability of that data table is ultra low.

This discussion has been closed.

Recently Written

The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.
Tyranny of Outcomes (Aug 19)
An extreme focus on outcomes can have an undesired effect on product teams.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2023 Adam Kalsey.