Each case has undergone in-depth information search, sorting and summary, striving to review the overall operational starting point and strategy. It doesn’t represent all the truth, but I hope you can gain something from it. One concept that has always been emphasized is that all operations belong to product operations . Execution without a deep understanding of the product can easily deviate from the real goal. For example, when doing channel promotion, one must not only consider the purchase cost of traffic, but also understand the conversion path and subsequent user behavior in order to evaluate the fundamental value of the channel. Operations and products are inseparable. Today, let’s talk about the product perspective from the operations perspective and how to get along with product people. What is a good product I do not agree with the statement that "even if the product is as bad as shit, operations must still make it flourish." This is an shirking of product design responsibility and an extreme waste of operational resources. There is a classic proposition: What kind of product do you think is a good product? In the operation’s answer, it might be “a product with a good reputation”, “a product with great user volume and DAU”, “a product as awesome as WeChat ”, or “a very profitable product”. These answers are based on two reasons. The first is that the reasons described represent, to a certain extent, that this product is doing very well. The second is that after deeply experiencing the pitfalls on the opposite side, I feel more and more that this is the product I want to operate. Good products have some common basic characteristics, such as meeting user needs and providing a good experience, but in the eyes of operations, these standards are useless because they cannot distinguish. A demand analysis will be conducted for every product, and good design and experience are standard. The key difference is the way and degree to which the needs are met, which leads to different potential energies of the products. Reflecting from an operational perspective, a product that is well operated is a good product. What is considered a “good operation”: 1. Low user education cost; 2. What you see is what you get; 3. Adequate marketing support. Taken together, it means "users can clearly and conveniently participate in the product experience, are satisfied, and are appropriately willing to participate in interaction and dissemination." "Good operation" reflects that the way of meeting demand is reasonable and low operation cost can leverage high growth. Of course, this does not mean that the operation requires less investment, but that the input-output ratio is reasonable based on the phased goals. Generally speaking, operations lack the professional perspective of a product manager , and the basis for controlling products mainly comes from user feedback, detailed analysis of data, growth needs, and accumulated operational concepts. The above makes three judgments on the product from the operational perspective. Based on these three points, we can understand how operations participate in the control of the product. User education costs The cost of education is actually the cost of new users, which includes several meanings: 1. Product definition from the user’s perspective When promoting a product, we tend to confuse the professional concept of the product with the definition given to users, or list technical functions in the product's promotional copy . The copy's stance must be carefully considered, otherwise it will not be possible to stimulate users' interest and imagination in the first place. 2. User Expectations of the Product The first is the product’s design concept, especially whether the core services are intuitively presented and meet publicity expectations. If you are not the only one in the industry, you should be cautious when making rules. Do not mistake rule innovation for product innovation , which may cause discomfort to users. 3. Guide the first experience In terms of concept, it is reflected in whether there is sufficient content, data, and timely response, and whether the product is active and efficient in conveying it to users. The problem of education costs is mainly reflected in the user's front-end link, and it is easy to get feedback at the operational execution level: 1. Establish a user base, collect the most basic feedback, and determine whether the main types of product problems are bugs, experience, or fundamental concept issues. 2. From data observation, if the education cost is high, the retention rate , click and usage data of the core business will be significantly low. There is no need to blindly extrapolate the product before it is launched, and only focus on the download and registration cost data. Operations may not know how to specifically design and improve products, but they must be able to determine the direction of product problems. What you see is what you get It means that the service experience of the product is obvious enough, that is, the needs are met. To give a simple example, tool products such as Qichacha and Chelai, the query results are the demands, which is very direct; UGC communities are a virtuous growth cycle, with less content and fewer people in the early stages, so the experience is poor. Obviously, the former is easier to operate. This example is more about the choice of model, and is not a product control issue in a narrow sense. It just illustrates the impact of "what you see is what you get" on operational difficulty. Then we can summarize the operational equilibrium point: when the marginal cost of core services does not increase with the growth of users, the problem is solved. For example, in the UGC community, when the operating mechanism and environment are improved, as the number of users increases, UGC will also grow naturally, and there will be no need to increase manpower investment, thus achieving a balance. It is similar to the PMF concept in growth hacking. Returning to the operational level, focus on 2 points: 1. Thoughtful service, coverage and experience 1. It is impossible for a product to satisfy all users. For example, "Qichacha" may not include some company information, some users on the e-commerce platform may not be able to search for their favorite products, and some users in "Xuebajun" may not be able to search for questions. The lack of coverage may bring fatal reverse psychology to new users. We need to use data to track the proportion and path of such behaviors, provide guidance and recommendations on products, and optimize click-through rates. Reduce user churn caused by coverage loss. If it is a platform-based product, such as a community or C2C service, it is usually necessary to take care of the key end, and even use technical means to achieve automation. For example, C2C picture communities can solve early problems by automatically generating users and content by grabbing beautiful women’s portraits and pictures. Of course, this is just a small trick that cannot be put on the table in operations. 2. Experience is reflected in the optimization of links that may cause user service interruption. For example, in the UGC question-and-answer section of the technology community CSDN, when a user asks a question, historical questions and answers are recommended to the questioner through calculation. Reduce the waiting time of questioners to a certain extent and improve satisfaction. Including error pages, loading pages, and concept descriptions, all of which may cause users to panic and become annoyed, so detailed copywriting, guidance, or automatic jumps are required. In general, these are all aimed at driving product optimization through operational conversion funnel analysis. 2. Demand Exploration For example, the merchant side of an e-commerce platform initially only had functions such as listing and delisting, editing management, and financial settlement. As the number of users grew, it became necessary to explore the marketing needs of merchants and to provide stratification of buyers, flexible promotional support, etc. Pay attention to users' concentrated behaviors through thermal analysis and interactive analysis. For example, if users frequently click on the "experience" details, you can analyze and try to design activities around the experience. Operations require sensitive data observation and analytical thinking about the cause and effect of user behavior. Marketing support This should be the most common demand raised by operations, involving many types: interactive functions, points, sharing, invitations, activities, etc. For product managers and technology, it may not be a priority for core business, but it is indeed the weapon on which operations depend for survival. Here are a few key points from an operational perspective: 1. Scene Integration Many of the current standard marketing functions are no longer profitable. It is not the case that data will increase rapidly just by providing an entry. Take the sharing function for example. How to embed it in the appropriate path, provide corresponding interest stimulation, use H5 interaction or direct download when traffic flows back, and even combine it with "rewarded invitations" are all worthy of a refined design strategy. 2. Reduce technology costs When making demands, fully understand the difficulty and cycle of the technology, and while maintaining core rules, consider third-party tools and compromise solutions, and even increase cooperative resources through the introduction of third parties. 3. Documentation and Follow-up Sometimes, it is not possible to fully and constantly understand the key significance of marketing products, so corresponding explanatory documents are needed. And you must always believe that "only when there are no bugs online can there be real bugs". The bug-free in the test environment and in the technical staff's mouth is only for reference, so try to go online early or conduct small-scale testing. Product people in the eyes Operations are the common parents of products, but parents may not know each child’s talents and growth patterns. They may be short-sighted, eager for quick results, or only care about their own business. The product manager is like a steward, coordinating and supervising the overall product and controlling the technical expenditure for each requirement. Operations help you grow stronger, while product managers help you shape your business. 1. Indispensable We have always emphasized that operations should control products, which is a requirement for operations. In fact, product managers also pay close attention to data, conversion, and user behavior. They have professional knowledge of user analysis, a better understanding of the cause and effect of user behavior, control the overall design of the product, and are responsible for part of the product data. Another ability of a product manager is to help operations transform abstract requirements into logically clear product requirements and produce visual models. And coordinate design and development resources to follow up on demand. To a certain extent, the product manager is the Aladdin's lamp in the hands of operations. 2. Friends and enemies Good product managers like to study products and users, so they will not reject operational needs and may even like operational work. , but they are troublesome to operate: 1. Making unrealistic and blind demands without considering product scalability and overall planning; 2. Making and changing demands at short notice like a mole; 3. Not understanding the technical principles of the product and talking to a cow. Likewise, product managers are also “hateful”: 1. Ignore operational needs, design according to the needs on their own, and be proud that XX product also does this. Please, it is obvious that user psychology is different; 2. Blindly lower the priority of operational needs; 3. Have you done any testing? There are so many bugs. 3. How to cooperate In most cases, operations are responsible for user growth, activity and retention data, while product managers are responsible for product iteration, demand launch and testing. Different companies have different structures, which leads to different focus goals. There is nothing much to say about this, and we can only talk about daily cooperation. 1. Balanced abilities and empathy. Operations personnel must understand product principles and processes, have the spirit of proactively researching and experiencing product details, and be well-reasoned when making demands, rather than being clueless. Product managers need to be familiar with changes in user behavior in a marketing environment. Only when the capabilities of both parties are balanced can they have empathy and reduce communication costs. 2. Product documentation. The product manager produces complete product iteration functions and parameter descriptions, which operations need to know and review. On the one hand, they should be clear about the degree of product optimization, correspond to different promotion plans and promotional copy, and deal with user communication; on the other hand, they should not raise unnecessary operational demands and generate arguments over changes in demands. 3. Needs assessment. When there are too many requirements and the priorities cannot be unified, regular communication meetings on the requirements are needed to reach a consensus. 4. Communication methods. In addition to silently looking at the data, product managers can listen to feedback from operations, proactively propose product improvement suggestions based on operational issues, and use automated product methods to reduce operating costs, and even form regular meeting documents. The user feedback and problem summaries collected by the operation must be presented in the form of a document, and both parties must agree on the format of the document. 5. Mutual KPI thinking. It is advocated to understand each other’s KPI or goals and promote each other in a benign environment. For example, one of the KPIs of a product manager is to reduce user churn rate. From an operational perspective, adding other service entrances to the service-free page rather than a single copy can not only reduce the churn rate but also improve business data. Product managers are also happy to participate. There is no harm done to each other, just because we care about the product in different ways, we exchange and improve each other's skills, cooperate with each other's working methods, and understand each other's language. Harmonious relationship Let’s summarize the relationship between operations and products. We emphasize that operations must have a product perspective: on the one hand, when planning and executing operational methods, we must fully consider the attributes of the product, measure the overall cost, and feed back into product improvements. On the other hand, respect collaboration and product principles, have a big picture perspective, and don't operate in a way that can only solve needs through quarrels. To like is to possess, to love deeply is to restrain. Mobile application product promotion service: APP promotion service Qinggua Media advertising The author of this article @天佐 is compiled and published by (APP Top Promotion). Please indicate the author information and source when reprinting! |
With the rapid development of the Internet, onlin...
China's mobile game industry developed rapidl...
The concept of growth has a long history in Silic...
I just spent some time counting and found that th...
Perfect Diary was founded in 2016, but it only op...
After writing about the three axes of Douyin, man...
When a star falls from grace and is embroiled in ...
During this year’s Double 11, many leading snack ...
From sharing overseas shopping to establishing it...
Some operators may feel puzzled. Why do they spen...
Tutorial Introduction ├─Part 1: Basics│ 1.1 To le...
Private domain traffic is now a "battlefield...
If you want to increase the number of readers of ...
1. Team Building In terms of team building, the c...
After the App Store list was updated at 23:00 on ...