Product Manager's Product Requirement Analysis (1), product manager's Requirement Analysis

Product Manager's Product Requirement Analysis (1), product manager's Requirement Analysis

I haven't calmed down for a long time to write something. The busy work in the past month has made my mind much more peaceful.

I have been thinking that the specific work methods and ideas between creating new products and revising old products should be replicated. Through the recent revision of a product of the company, learn the differences. When the old rule is usually decided by the upper layer to revise a core product, there are not many rational and specific reasons. What we can hear is that there are many problems in user experience, stability, and ease of use, in addition to getting some user survey data from the Operation Department, there are no other specific suggestions for reference. However, as of today, all the user survey data has been completed. Provide a summary to remind you.

Under normal circumstances, when product planners begin to execute product revisions, it must be that everyone has reached the level of tolerance for this product, and the operation cannot be promoted. There are very few USER usage and online duration, it wastes operation costs and brings a test of user acceptance in the secondary promotion industry. As long as a member of the company can spit on this product, at this time, it makes no sense to investigate the initial responsibilities.

First, we need to figure out why we need a new version? What problems should we focus on?

A. in the first round, I got some data from the Operation Department. We can see that the promotion intensity and number of user registrations are in the normal range, but the online time is very short during the product use process, that is, from this point on, most users rarely enable the second use;

B. in addition, the core features and auxiliary features of the product are independent of the primary and secondary features. There are many additional features and the features are scattered. The core features of publicity are buried, and users are blocked, some information necessary for the computer IT industry should also be set up. Even though common users do not know how to configure this information, IT is difficult to use the products for general standards and relevant guidance mechanisms, if there is only one message, you cannot continue to use a function;

C. Unpredictable errors and interference with verification code information often occur during use due to technical and information sources of products;

Overall, the above points lead to user loss, which is basically the same as the user feedback information. Currently, changes are urgently needed, which can at least solve the problem of insufficient user volume and user viscosity.

Next, we need to further embody the analysis of a function and a certain point, and evaluate the version workload and version update schedule.

The best way to solve the problem of a wide range of product features and weakening core functions is to make it happen quickly. When things tend to be unsatisfactory, it is best to cut the lines, you cannot cut down the menu or use the business data module. Since it is an Internet product, the characteristics of Internet products are that they are suitable for rapid promotion and Quick Start, reduce user learning costs, increase the number of users, and make recommendations and delivery between users clear and clear, in the final analysis, it must be very refreshing to solve a user's needs. In the end, we have met the user's actual A-level requirement, are the requirements below B necessary to be pushed to users all at once. However, the product itself belongs to the industrial software products and the Internet. This was slightly different in its initial positioning. Therefore, the technology and functions of the software in the user industry were promoted using the Internet product promotion strategy. It is also a problem.

I use a very basic example to analyze the product requirements;

If you are thirsty now, it is obvious that the only requirement you need to satisfy is to drink water. At this time, I will provide you with a cup of water, should it be defined as a natural requirement, it can also be one of the core needs, which can be understood without too much in-depth analysis. For such natural needs, there is no need to do user research and data statistics, and there is not much significance, in practice, there is too much time to struggle here.

Continue with the example just now. OK meets your needs for drinking water. Physically, you do not need to drink too much water, however, some users have met their natural needs. Some users want to drink sweet water, salty water, bitter water, and so on ..., However, this is a Level B or subconscious requirement, either because we have targeted ourselves, or the user will propose it. If the functional requirements are prioritized, A-level requirements must be satisfied first. Of course, you are really thirsty. I will give you a cup of bitter water and you will also drink it, although you have met this requirement, the user will be uncomfortable.

I think the problem should be solved here. If we follow the above ideas, our products will send these requirements to users, but before users want to drink water, the fact is that we don't give a cup of water, but a well, here we are talking about the information that needs to be configured in front of the user. At this time, the patient user will make his/her own bucket and make a sling, then fetch water. OK. The user has done all this well. He threw the barrel into the well and found that the well water fluctuates from time to time. It takes a lot of effort to reach the water (product stability and ease of use, when I found that water was bitter, I thought he was not in a good mood. It was a world of difference from the pure natural water that we had been promoting and promoting, that is to say, during the promotion, we chose one or two points from the various primary and secondary features of this product. We thought that the core features were the main promotion points.

I don't think he will come here to fetch water next time.

Analysts and product managers are the same thing.

No. Big difference

How can I choose Internet product manager and communication analysis?

In fact, the tangle cannot be selected, indicating that the two companies are equally attractive to you, and there is no absolute advantage.

So you can see which industry you like, and the Internet industry is more relaxed. After all, it is a new industry, and there are not so many rules, and most of them are young people. There are many rules in the Communication Industry and the work system is strong, but there are many seniority issues.

You should be familiar with the Internet product work, mainly including system, module, and function design. The work scope includes project initiation, resource coordination, system design, interaction with development and design, and resource coordination among multiple positions.