From my real experience, talk about the security design of B -side products

Edit Introduction: The sense of product experience is very important for users, and a good product experience can better improve the user retention rate. The author of this article analyzes the security design of B -side products, tells the principles and sources of the security design of the security sense of B -side, and the principle of security design. Let's learn together.

Keywords: B -side products, security design.

This week, due to the needs of learning business, I experienced a B -end product (informal environment), and there were many problems in the experience. The task that I could do immediately, I finally did it for a few hours (my mood was collapsed).

Through this incident, I think, if this is the formal environment, the user performs a task through the system and encounters various problems in the middle, and cannot solve it by themselves; if they report to their own IT department, I think this product may be It was replaced by similar products from other manufacturers.

Since I am a product manager born in the experience designer, my user experience of B -end products may be more concerned and sensitive than product managers born or other positions born.

In my opinion, a product has seriously reduced the efficiency and accuracy of information understanding of the user's execution tasks due to the error of the experience side (perhaps unintentional). There is no optimized space.

We must not ignore the experience (think that as long as the business rules are fine), let users switch from their own mental model to the design model of adapting to the product, and let users adapt to various problems of the product. of.

At the same time, some friends recently consulted me about the design of the security sense of B -end, which also inspired me.

I think in the process of experiencing the product this week, to a certain extent, as a user, I lack a sense of security (on the one hand, it is difficult to identify some elements of the interface, and on the other hand, the resolution rate is low. I do n’t know who to ask for help to solve it as soon as possible).

Therefore, I plan to start with my product experience this week with the security design of the B -end, and talk about my thinking about the design of the security sense of B -end.

1. The poor experience I encountered

Let's talk about the three events seen on the Internet in the near future:

First of all, in the first half of 2022, there were some problems with the China Merchants Securities Trading System. One is that on March 14, some customers did not receive the transaction return information on the client on March 14, affecting the withdrawal transaction.

And due to the unable to quickly locate the problem, the operational side has failed to resolve the failure in time. One is on May 16, and the system has a downturn, and some customers log in abnormal. The two incidents of China Merchants Securities should be very serious from the level of user experience, giving investors extremely distrust and insecurity (mainly economic losses).

Followed by June of the same year, the trading software of the Guoyuan Securities Mobile Client also failed, which was a warning letter for supervision.

Finally, it was pointed out in the report of the "2021 Data Data Report" and "An Analysis Report of the 2021 Data Leakage Situation" that the frequency of data leakage also increased at the same time as the industry's digital transformation accelerated, involving medical information, personal information, email content Wait for various information. Data leakage evokes people's concerns about the privacy security of the software system.

The above three incidents are very serious for users' insecurity. But the example I want to talk about below is not as serious as the above three, but it is also what we need to avoid as much as possible in our product design to avoid causing users to recognize the system's insecurity.

1. No response to the input box

Description: Generally speaking, when the input box is prohibited in the interface, the content in the input box is usually not filled in by the user, but is jointly produced by other fields. But this time I tried the product that two surprised points happened: one is that when I fill out all the information of the form, the input box still has no content to be filled in automatically; "Please enter" text.

Feeling: When I didn't notice the "Please input" text in the input box at the beginning, I thought I did not fill in a field that linked to the input box, so I tried it and found that there was no input box none of the input box. response. As a result, I began to doubt whether it was my ability or a system. Psychologically, I started to be a bit unwilling to trust this system, and it threw all the problems to users.

2. Field expression is unclear

Description: I have encountered unclear expressions of B -end product fields before, and this is very common in B -end products. The reason for the fact that the person who defines the field thinks that he is clear, and the user will certainly be clear. Or these fields are professional terms in the industry. We don't need to make changes.

As everyone knows, there are historical reasons for any situation. If we do not understand the reasons behind the phenomenon, we will easily learn from use.

This time, I found that some fields in the system did not express their own meanings, causing me to doubt when I filled out. So I consulted the relevant personnel. It is said that if the field is clearly expressed, 6 Chinese characters will be used, and 4 Chinese characters are used when the expression is almost clear. The interface will be neat.

From my perspective, I don't agree with this explanation. For B -end products, the clear expression of fields is more important than so -called neat. Only the fields are expressed clearly can the user's operating efficiency be improved.

Feeling: Although it is only a problem with unclear field expression, it seems very detailed, but often the professionalism is often seen. Psychologically, I will feel that there are many fields, menus, errors and other text descriptions in the system. When I was using the system later, I didn't trust this system so much. 3. Table fields are inconsistent with table fields

Description: Originally, I finished the task after filling in the form, but I later wanted to see which interface of the form of the form. So I found a small secret. The form of the form field and the form field was different, but they were something. It is said that this is a problem left over in history and will not adjust it for the time being.

Feeling: In the formal environment, if the user cannot know that the two are the same thing, they will think that their operation is not successful, which will cause users to repeatedly operate or confirm the facts from others. Obviously this bad experience.

4. Basic components are used at random

Description: For B -end products, basic components have basically been determined, but if we do not understand its usage and scenes, we will use random use. I am also the first time in this scene. When you click on TABS, the query field above TABS will be switched. I also explored this "special usage" and discovered it for a while.

Feeling: I couldn't complete the operation through normal use. After exploring it, I found how to use it. My feeling is that the product team's understanding of B -end basic components needs to be strengthened.

5. There are tips, but it is incomparable to find out

Description: This is also a relatively strange problem that I encountered. I was interrupted when I operated a task. It was reminded that the XXX task was unfolding. I must terminate the XXX task before performing the current task.

So I clicked the quick link to enter the details of the XXX mission, and there was no "termination task" button on the details page. Helpless, I can only find a way to find this record and try to terminate it, but after finally tossing, I found that the XXX task was not found on the page.

Feeling: This is a system throwing a problem, but it cannot guide users to solve the problem. I was really confused on the interface, and I looked for West Search east. I don't know where the problem is. In the end, you can only seek experienced friends to solve it.

6. The next step can be seen everywhere

Description: In my experience, there is a task that can be completed through multiple steps. It stands to reason that the process design of this form should be very common, but an exception can appear in this process.

There are 6 steps, and the "Next Step" button is designed below each step. When I finished the first step, I found that the button was not activated, so I had a question. Fill in.

After understanding, I found out that I didn't fill in it. The actual situation was that the "next step" button was activated after all steps were completed. The current steps enter the next step, which is controlled by another button (very hidden and not found at the beginning).

Feeling: Step Form is a very common B -end scene. We can completely design these scenes. The applicable scenarios are directly used. The unusual scenarios are adjusted on this basis. If a general scene experiences so badly, the user's feelings can be imagined.

7. The same function, different positions

Description: This question is not big and small. Why do you say that? Because the functions are provided, there are no big problems. But we can think about it. If you get a product, the same format setting function, why is one in the upper right corner and one in the lower left corner? What I can think of is that the product has no design specifications and guidance, and the R & D team adds functions at will.

Feeling: I saw this in the product experience this time. As a user, my feelings are not good, and I have a little doubt about the professionalism of the product in some aspects.

Some of the tiny use experiences listed above, through the accumulation of less successful ways, finally accumulated the psychological insecurity of this product. This kind of unsafe is not as serious as the leakage of privacy data, but it also erodes a little bit of my awareness of the product itself.

In fact, the details of a product are ignored (such as the field that is not paired, the field expression is blurred, the process breaks, etc.) will cause the professionalism of the product to decline, thereby giving the user's sense of insecurity.

Imagine, standing in front of you, two lawyers, one wearing a sloppy, and the other in a suit. If neither of them speak, will you trust the professionalism of the suit and the lawyer. It will give you a sense of security in a professional field. You think it is assured to give him to him.

The same is true for B -end products. The visual elements on the interface are like products of the product. The copy on the interface is like a product. The interaction on the interface is like a product behavior.

If our product manager ignores these, users may slowly disappoint this product and no longer trust this product.

Second, the source of user insecurity

Where does the user's sense of insecurity from using B -end products come from? I summarized the following points (where I thought about it, some examples used the C -end, but it was connected with the B -end):

1. Inadequateness of privacy leakage

For example, if you open the asset interface, the asset quota is not hidden and the display button, then you will open this interface in the future or there is no place around you, or you are afraid of others (as much as possible to see the interface as much as possible). 2. Unable to traceable insecurity in key information

For example, every fee we paid through bank cards or Alipay, we hope to find the details of the bill when needed.

3. Error inseparable insecurity

For example, when we delete photos, Apple mobile phones will help us save the deleted photos first into "recently deleted" to prevent us from being retrieved because of mistakes. For another example, the B -end products are basically configured with log operation functions to avoid in case of what happens, users can find out the problem through the log.

4. Insertation that cannot be solved by emergency problems

For example, we operate on the interface and have been stuck many times. Not only can we not solve it ourselves, but we can't even find the assistance of the document/appropriate assistance, whether it will be very angry.

5. Unreasonable insecurity of permission design

For example, the unreasonable authority design leads everyone to view certain privacy data of others, which is worrying.

6. Unable to understand the insecurity of copywriting

For example, you need to do one thing very much, but the copywriting on the interface cannot be understood at all. You don't know how to operate step by step, it will be helpless.

7. Unknown insecurity

People are inherently like a familiar environment. When we are in a familiar environment, we will feel secure. If the product interface is separated from conventional design methods and mavericks, it will make users feel insecure for B -end products. If we must have some characteristics, we can transplant the familiar elements into special points.

8. Unparent sense of backwent

B -end products need some data security and benchmarking enterprises. This is an effective way to improve the market share. Alibaba Cloud's official website shows the use cases of benchmark customers in different industries, cases of safety compliance infrastructure, etc., which can endorser Alibaba's trustworthy and security.

9. Insertation of messy information

Humans like neat, symmetrical, and beautiful things are natural, and because of the appearance of things, we will also be more willing to trust. The same is true of B -end products. If the information is arranged neatly and orderly, the interface component comes from the same component library. The interface element design is beautiful, which will make users feel that the product has a professional team in design and is trustworthy.

10. You can enter the insecure insecurity

I wonder if you have encountered a similar situation to me, entering a certain interface, and suddenly you can't go back. This is a manifestation of the insecurity in the process. There are neither return buttons nor navigation components such as bread crumbs on the interface. We can only exit the system and re -enter.

11. Inserture without prompts to complete operations

Regarding the deletion of a data, transfer, recharge, processing, etc., whether it is successful or not, it must be clearly and feedback to the user in time, and give the reasons and the next operation prompts. And confirmation anxiety.

Third, the principle of security design

As mentioned above, so many users can use the source of insecurity in the product, we can find that the main manifestation is a psychological sense and controlling sense. The certainty of things and the sense of control that the user perceive are the source of the sense of security.

Therefore, the principle of security design can be expanded from the aspects of certainty and control. Any design on the interface can be tested with certainty and security.

1. Determissality

The opposite of certainty is unstable. For humans, we have been pursuing a state of relative determinism so that we make decisions.

When using the product, you have missed operations, it will prompt you in time, and tell you how to correct it. This is the certainty; when using the product, some difficult fields have a corresponding explanation to help you understand the meaning behind the field. This is the certainty; when the product is used, the current task is progressing, and there is a corresponding progress display; if the task is interrupted, there are corresponding remedial measures, which is the certainty; these are the performance of the product to give users a certainty performance. Essence

2. A sense of control

The sense of control is the face of our surrounding environment. I believe that we can decide our inner state or external behavior, and finally achieve the expected results.

When using the product, even if you delete any data, you can calmly find it from the recycling station. This is the sense of control; when using the product, even if you don’t know what the specific data name is, you can vague Search and find it, this is the sense of control; when using the product, even if you do not save it in time, the interface is stuck. You have to restart the program, because the product starts the automatic preservation function, which is the sense of control; these are the products, all of which are products, all of which are products. Give users a sense of control.

Fourth, the last words

When I really experienced a product that has a bad user experience, I know why we can provide users' available, easy -to -use, and easy -to -use products.

Users should not pay for unprofessional products. We should not allow users to pay more time and learning costs for learning products because they are unprofessional.

Today, it is an era of experience in the economy. A good experience is one of the reasons why users choose your product.

When there is no similar product in the market, you can say that the user has no choice, and can only choose the function to satisfy them. It is not important.But when there are more similar products in the market, experience is a very important factor for users to choose your product.

Let's pay more attention to the user experience of B -end products together.Because, we are also users ~

#Columnist#

Zhiguo, public account: Zhiguo diary, everyone is a product manager columnist.A master's degree in brand design at Zhejiang University of Technology, author of "B-end Thinking-Product Manager's Self-cultivation" author.There are rich experience in product design process, product design principles, product design methods, product design specifications

This article was originally published in everyone's product manager, and reproduced was prohibited without the author's permission.

The question map is from UNSPLASH, based on the CC0 protocol.

- END -