Internet product optimization Experience Sharing

After the product is launched, there is a lot of room for optimization regardless of whether it meets expectations. The following are some of the product optimization experience for your reference only:

1. Establish a product monitoring system

From a macro perspective, the product should focus on the major points and split them. If real-time monitoring is the best, you cannot put all the points in the report in real time. You can view them once a day, you can find out if there is a problem with the product at a large point!

For example, the number of successfully registered users invited back can be set to a conversion rate here. If there is a sudden major change at a certain point, it can be detected in time.

Here, why is it that only the column is big! If split is separated, there are too many points. During local optimization, you can split the big point into small points.

2. Actively discover product problems
If most users do not take the core interests of the product, they generally do not take the initiative to report problems in the use of the product. If they passively receive problems, they will miss a lot, unless you do not want to make the best of the product.
Common methods to actively discover problems include:
1. online (offline) Questionnaire Survey: General email, insite email, links, street visits, and other methods are used to allow specific users to participate in the questionnaire. It is best to ask users too many questions, mainly based on selection items, don't let users enter too many things. Important things are placed in front of the questionnaire, because it may be annoying for users to choose! In addition, if you don't give a prize, don't give it. Otherwise, the user may be filled with a prize and the questionnaire cannot ask the correct answer.

2. Telephone Survey: Call the user directly to ask the user's problems during use. It is best to call the user in real time. Otherwise, the user will forget any problems. For example, if you are optimizing the payment success rate, you add a piece of code in the background, and if the user fails to pay the payment five times over and over again, then an email will be sent to you, after sending the user's account, you will immediately call the user and ask him what's wrong !?

3. door-to-door interviews: the advantage of door-to-door interviews is that they can chat with users face to face, it is impossible to observe the user's use scenario, how the user uses the user in a specific scenario, and what behavior the user's body shows, you can see more things behind it.

4. User Testing: door-to-door interviews can be used as a kind of user testing. Here we talk about user testing in a small room for everyone to see outside. Before developing a product, you can test its prototype to find problems with the product. After the product is launched.

5. analysis of competing products: a user may use multiple products at the same time and need to know the competitor's products so that the pain points can be found during the chat with the user, it will also have a deep understanding of why the opponent does this. On the contrary, it can also know which functions the opponent does not want to do, because it is not what the user wants.

6. data analysis: during the development process, developers are required to deploy all the data points that should be distributed. In this way, why are users stuck here later? What are their behaviors at that time, it will be very helpful. The data won't be panic, but the response is the fact that the user may say that I will definitely use your product after it is launched, but this may not be the case for the data.

7. trial in person: We should all be product users. Otherwise, we do not know what users will think. It is really difficult to simulate users' behaviors in various scenarios and transform them into users, you need to have a wealth of life experiences, or you cannot simulate it.

8. Internal team collection: the team needs to have developers, design, operation, customer service, and other Members. They often need to list the problems they see in various ways.

9. Customer Service feedback: send questions you need to know to customer service so that they can ask questions you are concerned about while chatting with users.

10. Listen to the user's call recording: the real-time listening efficiency is too low. You can ask the customer service to release the recording. You can listen while you work!

Iii. Fast iteration and agile development

The advantage of rapid iteration is that users can feel that your products are constantly improving, without losing confidence in the problematic products. At the same time, they can quickly correct the products.

Agile development allows everyone in the team to understand what we are doing, what our goals are, and to turn traditional developers from mechanically receiving needs into perceiving users, better understanding of requirements.

4. Do not fall into local optimization too early

Optimization is important, but do not enter too early. Major changes will often lead to a revolutionary leap, whether in flight or in flight, but this is a very good way to test. In a backend, there are many methods to reach a target. The current method is not necessarily the best. You need to try again, so do not enter optimization too early on the same road, there is also a better way to do it at noon.

5. processes are important, products are more important, and user performance is more important.

For some commercially available Internet products, such as Qiyi members (just an example), you may have to register, agree to the agreement, select a package, and pay for the purchased members. We regard membership as a product, define the purchase process as a process, and determine whether a user will buy it as a user's performance.

Users who want to buy a product cannot afford it. This is a problem in the process. Sometimes I will fall into the process too early and get stuck with small details, but the optimization is final, you will find that even if the process is converted to 100%, There will be so many people to buy.

The user pays more attention to whether the product itself is what he wants. The process itself is only a purchase process. If he focuses on the product itself and the user, the breakthrough will be even greater. Of course, I am not saying that the process is not important, everyone should understand it.

6. Review products on a regular basis

There are two main aspects: one is the strategic layer, focusing on the short-term and long-term development of current products, what are the possible future trends, and whether they are in a correct direction. On the other hand, it is the tactical layer. Let's take a look at whether the method and method we reach the target are correct, whether it is wrong, and how to correct it. Make sure that the server is not cut by mistake.

7. Do not challenge users' habits

With their own products do not feel too much, with a feeling of others products come out, as early as a few years ago, blue ideal (http://bbs.blueidea.com) This site has had a revision, my usage habits have changed over the past few years. At that time, I began to scold my mother, scold the blue, and almost left. The optimization process is also the same. There are usually some changes that will affect old users. We recommend that you use Quick iteration or make users have a choice.