Interpreting product managers should not understand technology

This title is a bit of grandstanding suspicion, so in the article on the frank and thoroughly take their own experience to say things ~ don't want everyone to criticize me is the title party, also sincerely hope that we can communicate more, to the qualifications of the products of light (in the watercress and know how many times to see the product manager should not understand technology, Finally pretending to cheat themselves understand why not understand the technology is no problem, the actual work only found that is not so, the truth heard more, also with a bad team.

I am a growing new, I hope that the great God of mercy, but also hope that you know the technology of product managers can come in more exchanges, so that more technology like me laymen know what technology, how to open siege Lion mode ~

------------------all of the following to work on your own practical experience, welcome to discuss-----------------------

As a product, logic and aesthetics are indispensable, no logic is not good to communicate with the program; without aesthetics, it is not good to communicate with the UI; Technical products, technicians will be very dislike you, whether you are very humble to wait for their advice (general discussion of technology will let you stay on the side, if you are pointing fingers, Likely to be granted a meal); a product that does not understand technology, there is no way to discover the problems of development, these may not be fatal problems, but will certainly affect you to become a good product (the delay of the development of the project has wood, some developers do not know the risk aversion, tell you a development time, at that point in time, rarely can be completed on time) ；

Whether the product manager wants to understand the technology, from my work experience, if you are a beginner of the product or you are surrounded by a group of junior developers, you'd better understand, this can avoid problems in technology; If you are a product of years of experience, there is no doubt that The developers around you should also be intermediate or even advanced levels, at this time you may need to pay attention to the product user experience, the development of the direction of the error should be less, but there may be a problem, the ability of research and development staff to a bottleneck, they hope that the leadership of the best to understand development, Bring them professional help, unless you are particularly prominent in one respect, otherwise you can only be despised; although I am a development idiot, or have a yearning to develop the heart.

The product manager must know the technology!!! But not a few years of experience in the development of products I do not feel qualified to speak the technology, technology in this era update speed, even if it is a professional development of all need to be very bothered to study how to make the code more robust, keep up with the pace of development of technology. Now many people interviewing products will ask the interviewer, do you understand the code? Although I also came from this process, until I really face the product does not understand the problems caused by technology, only to find this question is very funny. A lot of people will tell the interviewer that I've learned the language of XXX and I can read some, but are those people who can write for loops and bubble sort really help with product development? No, one is to understand these basic things do not have a say, and the second is that the tip of the iceberg of the code is not counted, also help not to any communication with the program ape.

I'm not sure whether the technology belongs to the product manager or the project manager, as far as I know, many times the product is the same person as the project. This time there will be a problem, you do not have the time to do progress assessment of working hours, inaccurate. And researchers themselves are hard to assess. If the product understands technology, the problem will certainly be easier to solve.

Product managers understand technology can also avoid a major problem, many projects developed for some time, technology found directional errors. This situation really happened to me, the project to submit the test, only to discover the ability of the project members, in the development of a major failure, resulting in one of the modules pushed to the back. For development, time is money ah, ah, how painful the understanding ~ Why will finally find the problem, because the product in the supervision of development, holding the page to click, found that the problem of the program are like to use a word to solve: this easy, late change on it. Because the product does not understand the technology, you do not know that he this change is simple or difficult, especially in the rush time, especially easy to ignore this problem.

Because the product does not understand the technology, sometimes may cause the project personnel to waste the effort. Like to let the program developed to see the effect of products to take the initiative to stand out, accept the organization's sanctions it ~ I sometimes will unknowingly do this let technology spray. Not I deliberately, sometimes feel that some effect is good, see others can use, let the technology also developed, developed to find not suitable for their products. And the development of the workload is wasted, and sometimes the development of the real competition is not the product ~

Do not understand the technology has too many drawbacks, but for the technology, I really can not do ah!

Do not understand the technology development of the product how to communicate with the technology. The easiest thing to do is not to get involved, let's develop them to discuss. Clearly tell them what your needs are and what you want to do; If you don't know how to describe it, the easiest thing to do is to cut a picture to a link and draw a gourd. My team program tells me to talk to the programmer the pattern should be this: xxx place should be xxx kind of, now is what kind of. If you have bugs, never tell the program in one piece, or they will crash. Write clearly, once said understand.

Do not understand the technology to use other aspects to make up. At least one thing is to make your developers feel good about you. No matter the user experience, UI, communication, affinity, can make up for your lack of development.

Do not understand technology how to find the technical errors of developers, do not understand the technology do not trust developers easily. I mean don't just trust what they say, see what they do, and let the people who understand it evaluate.

More ways to find out