They are all Web pages, why should they be artificially divided into "foreground" and "background"?

There is a reason for this: Forms and web site control hubs that require special security must in some cases be centrally designed and deployed. Administrators, content editors, authorized users... These content creators are a group of special users who need to be taken care of; under the general trend of "user-created content", the concepts of "front desk" and "background" are becoming more and more blurred, which can be It is certain that software like SNS will also have a so-called "background"; whether to rigidly distinguish "front and back" is not in the scope of this article, and only provide some feasible experience optimization principles for the special group of "background users".

How to improve efficiency and reduce the error rate has become the key indicator and principle of the website operation planning we described:

Principle 1: The work that can be done on one page will never be done on two pages!

In fact, this involves a form problem. Usually, our principle in front-end design is to allow users to fill in the least content and obtain the most satisfactory information. But in the background design, it is just the opposite. One more step of saving is a waste of time, and one more step of page jumping is an increase in the probability of an error rate! Especially in product maintenance, if you need to jump to maintain a piece of data, you have to go over mountains and mountains to modify that field, how to ensure its efficiency?

Principle 2: If possible, don't forget to batch operations!

For our customers, batch operations will undoubtedly increase the learning cost of using the customer system, but when designing the background system, our data operators should have received system training, so there is no need to worry about the learning cost. The batch operation of products undoubtedly greatly saves the time and cost of operators;

Principle 3: The design of the form should be more in line with the actual business!

Usually when we design a form, we design a form from the perspective of its integrity or the logic of its structure, but we must not ignore the user's usage habits, operating specifications, and process rules. Our form design should be consistent with It is more practical. For example, data entry personnel usually enter data according to the documents given by the product manager, so our form design should be consistent with the documents as much as possible, so that the data entry personnel will greatly reduce the data entry time. Judging time, greatly increasing work efficiency and reducing the error rate to a certain extent;

Principle 4: If the system can do it, don't use the human brain!

This is mainly reflected in the functional design. Many functional designs can be obtained through automatic reading or calculation of data by the system, instead of automatic recognition by the human brain, which will greatly improve its work efficiency;

Principle 5: The system design should be realistic and not increase the complexity of the work!

Many systems cannot be designed to achieve complete assembly line operation, and still require manual offline operation. It is necessary to judge whether our system design hinders its offline work, and ultimately affects the efficiency of actual work and operation;

Principle 6: Backstage design also needs to be beautiful!

Many developers usually think that as long as the background is usable, it doesn’t matter if it’s ugly to use anyway, but our background operators will spend more than 60% of their time on the use of the background every day. If you often use an extremely ugly background , not only is it difficult to guarantee his work efficiency, but his work mentality will change over time, which will affect all business operations;

Principle 7: Please carefully place key buttons and identify them differently!

This principle is mainly applicable to reducing the error rate. Usually, errors are often generated and deleted, and there will be a high error rate when saving in batches. Therefore, it is necessary to find out the location and functional design where errors are prone to occur, and consider whether the location is reasonable and whether the reminder information is complete. , whether it is possible to distinguish colors and gradually optimize them;

Principle 8: Do not forget about information, interaction and feedback in background design!

Reasonable functional design and friendly design will greatly improve the efficiency and error rate, and a small design may play an extraordinary role;

The purpose of an enterprise building a website is to make money. The front office is responsible for how to build a customer base to increase sales, while the back office or operating platform focuses on reducing costs. Both are very important for enterprises!