Design of fault tolerance

We 8630.html "> sometimes cannot afford to face a product error. No matter how carefully designed, no matter how many tests have been done, users will still encounter errors and problems.

Even if your product is running well 90% of the time. But they won't forget it if they don't want help. --"Getting real"

Since error is unavoidable, how to design fault-tolerant is the key.

Fault-tolerant design is the interface that people see when errors occur.

Just like dealing with mistakes that shouldn't happen, the key to fault-tolerant design lies in "doing defense." Product designers must constantly look for error points that may create confusion and dissatisfaction among users. Good defensive design determines the quality of the user experience.

For example:

Has anyone noticed that entering the bank http://www.aliyun.com/zixun/aggregation/19235.html ">ATM machine can have how many kinds of card way." The answer is eight kinds! There is only one way to get right.

How to avoid user errors from design, restrictions are a very necessary way.

The SIM card, if made into a chamfer, avoids the error of inserting a rectangle with multiple inserts.

The matching of the three sockets and the corresponding Jacks avoids the possibility of users using two or more socket errors.

Ash is a good way to restrict certain actions on the interface.

Flickr Photos Upload Wizard, prevent users from skipping the first step directly into the back operation, using the way of ash. On the one hand, it tells the user that it can do the current operation, on the other hand.

Subscription button and unsubscribe are visually distinguishable from the wrong action, depending on the subscription and subscription.

If errors inevitably occur, reasonable and appropriate hints can reduce the frustration of the user.

1. Early warning of certain operations may cause errors.

When you enter a password that needs to be case-sensitive, the CAPS LOCK key opens to make a prompt to avoid error.

2, to prevent user errors, prompt confirmation after operation.

When the user clicks to send the message without the message, prevent the user from sending the email without the topic.

3, not only to feedback errors, but also to the user to answer.

It is best to tell me where the cause of the mistake is, the question of the words and words.

4, to give users appropriate guidelines and suggestions.

When users search for people without results, lead the user to continue to find or invite friends.

When a user searches for no results, intelligently guesses the cause of the user's error or gives other guidance.

How to err, who can not. The user is God of the product, how to reduce the frustration after the user's error by design. Always wrong is product, tolerant user error, do not tolerate product errors

Thanks for the seven documentation.

Source: http://www.zhangyq.com/fault-tolerant-design/