User Experience

Writting helpful error messages

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

21 Mar 2002

The job of an error message is to inform the user of a problem and help them solve it. "Could you repeat that in English?" has examples of poor error messages, an analysis of why they don’t do their jobs, and outlines four rules for error messages.

Comments

RickySilk
March 22, 2002 4:09 PM

Microsoft error messages are the worst! Especially when you're working with vb/ado argh!

abhay
July 26, 2003 6:50 PM

yeah it is quite right

This discussion has been closed.

Recently Written

Micromanaging and competence (Jul 2)

Providing feedback or instruction can be seen as micromanagement unless you provide context.

My productivity operating system (Jun 24)

A framework for super-charging productivity on the things that matter.

Great product managers own the outcomes (May 14)

Being a product manager means never having to say, "that's not my job."

Too Big To Fail (Apr 9)

When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.

Go small (Apr 4)

The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.

Start with a Belief (Apr 1)

You can't use data to build products unless you start with a hypothesis.

Mastery doesn’t come from perfect planning (Dec 21)

In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.

The Dark Side of Input Metrics (Nov 27)

Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.

Writting helpful error messages

Related Reading

Comments

Recently Written

What I'm Reading