From requirements to fall: how to become a product manager for research and development of trust?

01 R & D, product manager mistrust

Let us talk about what kind of development most hated product manager:

Often mention the word demand, not ask the details did not think that is not confirmed;

Often we need to change, do not say what he wanted;

Demand did not plan to do something not two months off the assembly line with no one out;

Demand worthless, led to the development for a year-end summary and eventually found nothing to say.

If you have more than four points at any one point incorrigible, basic research and development work with you too will pull you into the blacklist. Behind demand do not trust you not say that you weight and status in his mind has gone up.

In fact, these problems are not done because the needs analysis, needs analysis is not good, there is no good solution. Good requirements analysis is not received any suggestions and feedback as soon do it, but to consider at the height of the platform, analysis, planning.

02 correct posture needs analysis

For example in terms, I received a demand point operations intention proposed:

Background: When the authority expires, if the key is in operation, the process will result in failure, only manual processing;

Program: hope in the system before the user access expiry of seven days, pop reminded me of the need for renewal, and to prevent users from entering a critical process in the case of knowledge.

This requirement appears to point very clear, very reasonable, and the program will help you to think it over, very intimate. But is it really?

If each of your needs, put all this in the past, presented directly to the developers, the four cases that you mentioned above from far away.

What is the correct action is it?

First, take the first look at the data to see if this feature coverage of user groups is kind of how. Take a look at the data, there are seven days before the expiration of the students operation, only 3% of all users, and the users back 90% lost out. The data shows this little reminder of coverage, so the value is very small, low priority.

Second, re-sort the user process. From the landing platform users, access rights, use the function key to access expiry, re-apply, again finished combing discovery: the key to the interface has access expiry date display, so the core of mainstream users, resulting in less experience permission expired card the situation live.

Third, in terms of overall platform architecture, in addition to the user-side operations, rights management application side is made, the legacy application system is in use function, since the current system has been and permissions management structure abutting, so the current privilege can automatically apply, with regular day refresh mode tasks.

So this needs assessment findings are: a reminder not to, apply for permission to apply to automatic renewal.

Found yet, correct false needs analysis and demand analysis, the results are vastly different.

Specific reason: users, operators, customer service and other staff, standing just a point to see a phenomenon, even if the proposed scheme, also in the perspective of this point, non-product framework for thinking, proposed the "program" can not be directly research and development, can be understood as a dish of raw materials.

The product manager, if this time directly fried dish, equivalent to a direct boiled.

The correct approach is to assess the value, carding processes, product planning.

Means of assessing value, usually the data analysis. Whether the data binding function of this business look abnormalities, usage, number of users, user groups, the value is high enough, whether it is a common problem.

Carding process, in order to be able to look at from a macro point of what the nature of the problem is, if only from a user's action, rather than his antecedents and consequences to consider, and that is the elephant.

Product planning, referring to the program to have ductility and periodicity. From the perspective of the system architecture, a more high height to look at this problem, assess what should be made to optimize the system, which system should remain unchanged.

Without these three steps, proposed product solutions must be blind.

A substandard product manager, received 100 intent, demand is converted into 100 points.

A successful product manager, received 100 intention to integrate into a 10-point demand. Finally, a product plan.

03 better cooperation

You are thinking that enough? not enough. Typically, in the case did not question the value of process, product solutions, and not all have landing. Probably because of the situation the company's value-oriented, market changes, regulatory policy changes, leading to your program no longer applies, this time need to re-planning.

This is why I agree with the demand as the reason for the amount of output product manager for the KPI. I think the ability to do more is not a depth needs you and I know everything, if there is no amount of quality, is tantamount to digging.

So from requirements to product solutions, assessment schedule, floor, iteration, it is a set of ecology. One of your decisions, not only affect this function, but also affect other functions of the platform, and the company's overall user's other platforms, platform development.

Many start-up companies because of an unreasonable activity, wool party is hollowed out. So for product managers, must be higher perspective, we have a better solution, in order to create greater value.

So after doing a needs analysis, research and development and how to build trust with it? Here are a few suggestions:

First, a good product manager must put the needs of small, so the progress of work and the daily schedule, it is better to send a person to report weekly to the team, so we will not think you are indifferent. To expose their work, it is also an information synchronization and communication.

Second, the demand for on-line, periodic summary report issued to the developers responsible for synchronization, so that they see a return to form a positive incentive. Do things stay the course, be able to establish a sense of product image product manager.

Third, the encounter needs to change, R & D of the deviation, the first time to admit and correct. Most teams are not full-time project manager, so the research and development of quality assurance, is also one of the terms of reference of the product manager.

04 summary

Product Manager is developed by Upstream, direction and control of demand, while demand analysis is the product of the pre-mentioned demand action, is easily overlooked part of the primary product manager. So do a good job requirements analysis, research and development team is focusing on enhancing value.

In the process of demand analysis, not only on the issue of "point" analysis, but also the entire process of "line", to the platform of "face" and finally see the company, market value-oriented "body" in order to do a good product program.

R & D management process, the product manager is greater than the execution of a job analysis, analysis is often a whole week, output word 1000 document only, so to actively self-exposure work and thought process, to win the trust of R & D team. At the same time follow the development of good products, beginning and an end to iteration. To experience problems first time correction to ensure research quality.

Only: depth insight into the overall planning, clear communication, research and development in order to become a trusted product manager.

Guess you like