Internet product operation flow chart and refined operation mode

This article is a record of my operation workflow based on the classic model and my own work experience. In my actual work, I just follow this process to carry out my work. I have to mention that the habit of summarizing has really helped me a lot, from the completion of my first version of the framework diagram of operational knowledge system to the current operational flow chart, refining the operational model. What I've always wanted to do is to precipitate my work experience, combine some classic methodologies, and finally perfect it into my work framework. This process takes time, and I will stick to it. The ultimate goal can of course create a new theoretical framework by itself. I. Internet product operation flow chart Piracy model (image source network) Based on the piracy model and the current company products, I designed my own operation SOP. Of course, the flowchart is iterative, and I currently set it to version 1.0. This picture was drawn in visio. My original intention is to design a general version of the process, but some details have to be fine-tuned according to different product characteristics, and the general direction is basically the same. Key points: The design of operation strategy should be closed-loop. The actions of pulling, activating and transforming should be designed as a whole. Operating strategies designed around local separation usually have limited impact. Channels that provide stable traffic sources are called stable channels, and vice versa. Unstable channels need continuous development and operation before they can be transformed into stable channels. For example, Zhihu is not a stable free channel, and it takes considerable operational effort to bring a certain amount of traffic, and the transformation takes time (using the new term now, private domain traffic is called stable channel and public domain traffic is called unstable channel). The main steps of refined operation: data collection and sorting-user stratification-hierarchical user differentiated operation strategy retention and calling mechanism: active state judgment-lost user recall mechanism 2. Refined operation is the core of user operation, and so is SOP. Visio drawing: indicator examples (there are more detailed examples in my 2.0 article): user attribute indicators, user behavior events, user rating level, collection name, video-on-demand frequency, city use coupons, gender search, registration time, birthday reading volume, province submission order, channel source browsing page, email friend's recent visit time registration, and refined user operation are a strategy to promote survival, which may not be so obvious in the initial stage of the product. However, it is the main growth source and internal driving force in the growth period and maturity period, and its role is greater than that in the mature stage of innovation. It is necessary to form a complete set of refined operation strategies and processes. However, in the initial stage, various technical means are not perfect, so there is no need to spend too much energy to design complex and elaborate strategies. At this time, the number of users is not large, and the direct one-to-one and one-to-many communication efficiency of operators is higher. At this time, it is more important to accumulate feedback from seed users. Unfinished, to be perfected. Markcorn20 18-6-8 is not easy to make. Welcome everyone to like, collect and comment. About this article 1.0, there are many things that need to be revised, which I summarized in this article 2.0. Of course, 2.0 has also added some new contents. Please comment and correct me (2020- 1 1-24):