UI hints that prevent user errors [closed]

Question

What UI/GUI guidelines should be followed that subtly (or not so subtly) direct users so they don't shoot themselves in the foot.

For instance, you might want to give power users the ability to "clean" a database of infrequently used records, but you don't want a new user to try out that option if they've just spent hours entering new records - they may lose them all because they're 'infrequently used'. Please don't address this specific issue - it's just here to clarify the question.

While one could code a bunch of business logic in place to prevent some issues, you can't account for everything a user might do.

• What are some common techniques, tips, and tricks that prevent improper usage?
  • ie, How should I design the interface to alert users that a function or action is to be taken with care
• What should I design in that limits risk and exposure if a poor action is taken?

-Adam

Answer 1

Everything can be undone. Don't erase - deactivate. Back up before every destructive operation, and give the user a way to restore.

That's the path. It's hard to follow it all the way, but it's what you're aiming for.

Answer 2

Make it possible to undo dangerous actions.

If it's a reasonably big application or system, require separate admin access for dangerous operations as well.

Answer 3

Don't Make Me Think

And you can, in fact you HAVE to account for everything they might do. Because you (as the designer) as the one who gives them the ability to do all those things.

Before putting ANY item on a gui as yourself "Can this be misused?" and if it can, you might want to go with a lower level of customizability. Example hierarchy

• Button - Can be clicked.
• T/F Radio Button (mandatory) - Only two options.
• Combo Box - Many options, possibly "no option". more confusing.
• Text field - Myriad of wildly inconsistent options. More confusing for user, more dangerous for coder.

Basically, if the user doesn't need extra options, then don't give them extra options. You'll only confuse them.

Answer 4

This is an old article, but it's still a great one:

Microsoft Inductive User Interface Guidelines