We should imaging software design into a good working partner.

First, a software should be "Polite" because courtesy is a common behavioral feature of humans.

If a software can only provide a small amount of information and behavior is obscure, it often forces the user to find some common functions and impose faults and responsibilities in the design process on any user, the user will not like the software and the experience will be unpleasant. If the interaction process shows that the system is respectful, generous, and helpful to people, the user will like the software because the operation process gives him a pleasant experience.

Repeat, this has nothing to do with the composition of the operation interface; even the command line operation interface of the black and white screen, people will like it, as long as the software can meet the above points.

Courtesy software should be able to provide you with the necessary tips or help.

Most software simply answers the questions I asked. They do not take the initiative to provide other information to me, even if some information is clearly related to my goal.

When I asked my word processing software to print documents, it never told me that there was not enough paper, or that there were 40 documents waiting to be printed before me, but people could do that.

Indeed, the computer will never give an approximate amount of bank deposits. But it takes a tenth of a second to tell you that the bank deposit is "about $500", or 17 minutes to tell you that the bank deposit is "exactly $503.47" (an early banking system ), it is no different for computers. A polite and user-friendly software will immediately tell you about $500 in bank deposits, and then tell you that more accurate data will be provided in a few minutes.

As an operator, you can choose whether to spend more time obtaining more accurate data. This is the principle of peer-to-peer payment. If you need more information, you will agree that it should take more time.

Polite software should have some common sense.

Most software places buttons for some common functions next to buttons that are never used.

You may also find that simple and frequently-used functional buttons are placed next to dangerous, professional, and unrecoverable seat ejection buttons. This is like placing your dining table next to the oven.

Polite software can predict my needs.

While reading the webpage, my browser basically does nothing. It can easily anticipate my needs and do some preparation work, rather than quietly wasting time.

Why does it not use free time to download those webpages with links in the screen in advance? It is very likely that I will read those webpages.

It is easy to interrupt an unwanted request, but it takes time to open a webpage. If the browser can expect me to download the relevant webpage in advance in free time, it will be more responsive and does not require faster network connection.

Polite software can always solve your own problems.

The software always requires confirmation dialog box to complain to me and show off to me with unnecessary status bars.

I don't want to know how hard my computer works. Just as I don't want to know about the divorce of a bar boss, the failure of a beautician's car, and the support of a doctor.

The software should not only keep silence on its own problems, but also be confident and capable of solving its own problems.

Writing polite software is no more difficult than writing rude software. We need someone to design interactions that can simulate the sensitivity and care of friends.

It is most practical to bring behavior closer to people. All courtesy features have no conflict with the actual goals of other more obvious business processes.

We should imaging software design into a good working partner.