Insufficient products must be supplemented by operations. It is said that this is a famous saying within Shanda.

1) Never expect to be able to operate a useless product, let alone imagine that such a product can be brought back to life or even succeed because of operation;

2) Never assume that the design of a product It is so perfect that no operation is required. Even if the product can be self-operated, it still requires continuous operation guidance.

Returning to this issue, I personally feel that operation supplement for insufficient products is not applicable to all Internet products. For products with a large proportion of operations, such as communities and e-commerce, if the product experience is not affected, or if it does not affect the use of the product, more interesting activities or large discounts and interactive activity operations can very well improve the user experience. Stickiness allows users to ignore the shortcomings of the product itself. However, for functional tool products, social products that focus on product design, and technology-focused products such as system tools, collaborative office software, etc., if the product itself cannot bring a basic user experience to users, it cannot solve user problems. , then operations can only be the icing on the cake. No matter how good the product is, it still needs to use operational means to keep the product alive. Operation work is relatively easy. There is no need to consider the most basic problems of the product itself. It only needs to continuously summarize, summarize and provide true feedback during the process of contacting users with operations. A closed loop can be formed by providing experience and improvement optimization suggestions in preparation for product updates and iterations. For a product that everyone who has used it says bad about it, no matter how much operation and promotion is done, it will be in vain and will have the opposite effect, because the more people know about it, the more people try it, the more people discover it. Problems will form a huge bad reputation, and then no matter how to recall this batch of users who were initially curious and hopeful. The creativity of this operation and promotion may be good, passionate, and full of joy. Once you come into contact with the product, all subsequent actions may come to an abrupt end, and in the end it can only become self-pleasure. The bad products I am talking about here are products that have poor functionality and cannot really solve practical problems for users. Therefore, product and operation cannot be separated. Product managers must do research before making products. They must be satisfied with their envisioned products. The logic must be clear. They must think clearly about the entire process, not only for different users. The experience process, as well as its own backend workflow, are a set of systems that are linked to each other. If the product is not ready yet, it is launched online, and it is always waiting for operational feedback. In the end, the product's own needs and operational needs conflict with each other, and there are more and more problems to be solved, which cannot be scheduled and cannot be sorted out. , then it will only be half the result with twice the result! Maybe it was merit or demerit, what a painful realization. I think all work is similar. To do something, you must first have a purpose, why you are doing it, what effect you want to achieve by doing it, that is, the goal, what to do next, and set an executable plan. Scheduling, what resources are needed, internal and external resources must be coordinated, and any problems encountered during the process must be reported and solved in a timely manner. Finally, when it is completed, how is it completed? You must analyze and summarize it, and propose improvements that can be made. Place, continue...I have talked so much in vernacular. This series of processes is PDCA! Everyone works hard towards the goal, does their part well, does a little more outside work, and communicates and gives feedback in a timely manner. It shouldn't be as difficult as imagined to accomplish something.

I hope that every product manager can be known by everyone, and when they hear your name, they will say: He, just him, the product called ~~~ he made is great! The product concept and user experience are both great!