This requirement, the developer says we don’t want to do…….

It’s not about winning or losing. It’s about being serious.

– Mr Luo

In product work, the last thing you want to do is have no voice in the product. Especially when developers say, “I don’t think you can do this either,” the product manager has to go to the boss.

Although with a “manager”, the product students are just like other development students, there is no hierarchy. It’s just that because the work process is upstream and downstream, most of the time we are in an Internet development team with a “say”, the demand of the product manager will be implemented quickly. But even such a team. Product managers and development managers or product managers and project managers will argue their own reasons for doing and not doing because of tight lead times, unknown development difficulties, or product managers’ desire to add new requirements.

Recently, I am in charge of the basic account system requirements, but the company’s product line involves different product lines. Although based on the account system, each login registration function has the same mainline function. However, the STYLE and specification of UI are two sets of products, and the development suggestion is: “We hope to use a set of design, which can reduce the development cost and later maintenance cost.”

On hearing such advice, the product of his own immediately refused to go. And we hope that the products can be delivered according to the previous review meeting. It is quite normal for us to have sudden changes in demand in a start-up team or a small Internet product team. After all, the business model or the needs of users are unknown.

In fact, the suggestion put forward by the developer above is very simple. Although it is two sets of products, one of them will be abandoned or even discontinued in the future. Is it still necessary to iterate on this product alone? Since the same account system has the same function and logic, why not just use one?

If you were a product manager, what would you choose?

My answer is to use their own, since they are two different sets of products. There should be two account systems, not one. Even if the product dies later or is discarded, the user or team is given a product that is as complete and polished as possible. We may have launched the product because the business model or user needs were difficult to grasp.

So we ran into development saying: “This need, we don’t want to do…..” The product manager will have no choice but to rise to the BOSS.