How technical people fall in love with product managers

"This is a product manager to think about, I just write the code is good", I had this idea. The product manager will consider all the product logic and then deliver the PRD to the developer for development, waterfall or iterative development milestones. But the idea is always good, the reality is that everyone is always a sword to opposite.

How product managers annoy developers.

Business is not clear, research and development personnel do not understand the business language, product managers can not understand the business;

Product depth is too shallow to withstand scrutiny, research and development personnel feel is perfunctory, not professional;

Product flow is not smooth or even complex, user experience is bad;

Do not listen to the developer advice, think they do not have product thinking;

State design is not complete, but also adhere to their opinions;

No complete PRD, the idea of the development of the direct start Code code, no review;

There is no data index, disorderly Pat head to set things;

Such a simple function, how it takes so long;

Hurry online, do not give developers to think about time, in fact, not so anxious;

The need to throw to the developers to ignore, do not pursue progress, do not look at the effect;

Non-functional requirements are not considered at all;

......

How the developers annoy the product manager.

Blindly pursue technology, do not learn business language, do not learn the field of knowledge, listen to do not understand the needs;

Review PRD when not to ask questions and risks, and so on the project on the line to be exposed;

Code codes before bad read PRD, a problem directly blame products;

Think that technology is omnipotent, not to refuse some unreasonable demand, and finally do a smash;

Data status and exception flow it needs to be sorted out with the product manager, and the product manager is not what we think it is. This is certain, do not blame them;

Responsible for the code only, the user experience is not what we want to consider, in the network, equipment and other aspects of the user experience, we know more than the Product manager;

Encounter problems do not find product communication, random set plan;

Code is a mess, can not be maintained, not scalable, new requirements are slow to do;

Old problem, blame product manager design unreasonable, consider not full;

It is obvious that the product experience problem, do not propose, do not solve;

......

The product should spend most of the time on the business canvas, product planning, product logic, product operation, user experience. The specific function point should be roughly given the direction of research and development, otherwise there is no direction, it is likely to lead to continuous rework.

Business developers, system developers, SRE or operators, in fact, already have product thinking, such as we comb the business architecture, system architecture, function points, system flow, exception flow, data flow, data status, system configuration, etc., these are not all part of the product. But these are more closely related to technology.

Product managers are likely to be less developed than developers in terms of product details, abnormal processes, and data status. This time we need to sit down and talk and comb together. My point is: the more transparent, the more efficient.

We should be a product manager first, then a developer. And we are a team, we should consider how to do a good product. However, we should improve their professionalism, otherwise the output of the scheme can not withstand scrutiny, always output defective, everyone's trust crisis, who can not convince who, break the fight, the final product failure.

Little Marco said: Product managers want to treat themselves as a "most critical user." Developers need to think hard about products, not business-minded attitudes. You need to know that users, peers will focus on your products, in this drive developers have a sense of responsibility to take the initiative to complete. Can not say that wait until the product is done, the assembly line sent to before to do. The final experience of the 40%~50% product should be determined by the developer.

Product Good Book Recommendation | Programmer's Road must read series