Why do sometimes product managers not understand the technology better?

Remember the previous article, "How do programmers and product managers look at each other?" Belittle or praise? , which talks about how the two roles I see in real life look at themselves and the job responsibilities of each other. In practice, I've heard a lot of complaints between programmers and product managers, and if I ask, is there any way to relieve the tension between them? A lot of people agree that only technical product managers can get along with programmers, they understand each other, and product managers don't go out of their way all day, because he knows that this is not going to happen with technology or that it doesn't.

Yes, I was very much in favor of this view, even in the mind to do a few years after the programmer if the opportunity to be a product manager to try. Until I read a little "thinking like a layman, practicing like an expert," I suddenly felt like I had made a serious mistake and reminded me of a conversation with a mentor last year that was planning to make a product that would help me out with some ideas.

Mentor: I think this piece is very important to the user experience, with this, the user just need to pay attention to his peripheral points and do not need to pay attention to the whole area of his basic contact, I found that there is no one to do such a thing, we can try it.

me: Such an important feature is now no one to do, or the user simply does not care about the need to do, or from the technical means difficult to achieve or simply can not achieve. We should belong to the latter, because from a technical point of view, ... (BlaBla said a bunch of technical difficulties, complexity, feasibility, etc.) that I think.
(not until I finish ... ）

Mentor: Wait, you don't look at these issues from a technical point of view, you first assume that none of these techniques are a problem, and that you are looking at the product from the perspective of the products, despite the idea that you feel the user experience is good or some of the necessary functions.
(When I was stunned and overwhelmed ...) ）

Mentor: We need to have a leap of thinking.

> I didn't really understand it at the time: even if I put forward a good idea, if it's technically possible, it's not a busy job.

> But when I read the book "Thinking like a layman, practicing like an expert," I thought my mind was completely overturned, and the book called Us to be like a non-technical layman when it comes to ideas. Despite thinking about interesting and cool ideas, let's not forget whether these ideas can be realized by technology. You first assume that no matter what technical problems can be achieved, because there is no relevant knowledge and experience constraints you can think of other ideas , which is the same as my mentor at the time, the root of our thinking should be "I want this" rather than "can achieve", It also makes me understand why a lot of technical people often have a lack of imagination, not creative . But when you have exhausted the idea, it is necessary to carry out the evaluation of the ideas of practice, this time you want to act like an expert, the full use of your technical level, research ability, communication and other means to assess the idea is not feasible, if feasible there are technical solutions, and then choose the best solution to start. This stage is also very important, you need not only according to your existing technical ability to judge the full investigation of the technology already, after all, the ability of each person is limited, perhaps you think the realization of a different person to achieve, it is also clear why the layman's thinking, If each of your ideas is kidnapped at a limited level of skill, how much innovation can this idea have?

According to the author's words, there are two necessary conditions to solve the problem: first of all, a good idea of the layman, if the direction is not correct, how hard can not reach the destination, at the same time, solid foundation, perseverance, efficiency is also very important, otherwise it can only be castles in the castle, armchair.

Some people may think that this is very empty, but it is not, the book used a lot of examples to illustrate this fact, such as the theory of continental drift is a good example of the original idea is just wishful thinking but ultimately the verdict. Of course there are other very interesting examples and worthy of thought and practical means, this is not a purely thinking and point of view of the book but a lot of examples, very practical books, look at the directory to know.

That's why I said, "Sometimes the product manager doesn't know the technology better," because he might think of more cool, flashy, human-like ideas than a thought-imprisoned programmer, and of course, if you have a programmer who thinks as a layman, it's definitely the perfect choice. After all, if his idea is not realized after a thorough evaluation, I believe that he can understand you better than the technical product manager.

Hope as a programmer of each of us have a rich leap of thinking, easier, come on.

Why do sometimes product managers not understand the technology better?