When many companies are building their own community systems, they often face a difficult problem, how to conduct community operations on a large scale.
When many companies solve large-scale community operations, there are three commonly used methods:
The first is through robots; the advantage of this model is that it greatly saves manpower and material resources, and one person can manage N groups through robots, but the most fatal point of this model is that there is no way to achieve refined self-operation of the community. Therefore, most of the groups managed by robots in batches are dead groups in the end. They only function as traffic pools and cannot generate any user stickiness.
The second is to increase employees through recruitment; the advantage of this model is that as long as the ROI of each community is clearly calculated, it can be recruited and copied at the same time, but the disadvantage is precisely because of the need to recruit people, when employees become more and more In many cases, once a problem or risk is encountered, if the steps are taken too far, it will easily threaten the company's cash flow.
The third model is the self-operating model that I want to share with you today. The advantages of the self-operating group management model are that the cost is low, the system has strong anti-risk capability, and it can achieve the refined operation of the community as much as possible.
Why does the self-operating group say the cost is lower? Because the people in the self-operation team are basically not employees of the company, they are all part-time or even free to assist the operation of the company, so the overall cost is relatively low.
Why is it said that the system has strong anti-risk capability? Because the community is managed by a group, no matter who is busy or quits in the group, other members can take over the work, and there will be no case of stopping operations.
Why can the refined operation of the community be achieved? Because the operation team is composed of people, and each team is responsible for a group, it is natural to communicate and interact with group friends.
Well, let's take a look at how to implement the self-operating group model, which is suitable for long-term interest-based operating communities;
Step 1: Run through the MVP operated by the community and extract the core functions
I have to run the MVP model of community operation first, and run it through my own refined operation. If I don’t get through it myself, the self-operation team can’t get through it either. Then we need to extract the most core functions of the content delivered by the community. How to define "the most core functions" is that even if everything is gone, the group can still continue to operate. For example, what we want to do is an industry Communication group, then the country email list core function of the community must be topic communication.
Step 2: Disassemble the core functions
If you are a professional community operation person, you may be able to output the entire core function smoothly, but when we want to hand over this core function to amateurs to manage, we need to operate the core function. The modules are cut to the smallest detail, so that a person with no experience in community operation can know how to operate.
Or take the industry exchange group as an example. Since the core function is topic communication, we will disassemble the main task of the operation group into topic initiation and topic discussion. If we disassemble it further, we will disassemble it to what we want to initiate. This kind of topic, when to post the topic, and how to guide the discussion after the topic is posted, this is actually an operation manual for topic communication.
The principle worth noting here is one, simple and easy to operate.