3 ms·
> It’s always best to help people avoid errors. When an error message is necessary, it should appear as close to the problem as possible, avoid blame, and be cl
by cratermoon 4y ago
> It’s always best to help people avoid errors. When an error message is necessary, it should appear as close to the problem as possible, avoid blame, and be clear about what someone can do to fix it.
Try designing with the idea in mind that the user will never see an error. First, instead of coming at it from the point of view "the user made an error", start from "the program was not useable enough". Much like a door with handle that cannot be pulled, but must be pushed, a program with a UI that appears to allow an action but really doesn't, the issue is not the person's fault. Respond to failures to complete the action the user attempted with alternates. Imagine how frustrating it would be if you went to buy coffee and the person working there simply said, "no, you've made an error" when you tried to order something they're out of. You'd right avoid doing business there ever again.