About PM don't want to know technology-pm and Rd Relationship _ life essay

"About PM don't want to know about technical pm and RD relationship,"

Let's talk briefly about my opinion.

First of all, I think PM is need to understand some technology.

Although the more you know, the better, but not necessarily very knowledgeable.

Because PM in the communication with Rd, a focus on products and markets, a focus on technology implementation, if there are some basic technology as a bridge, can be more convenient communication.

In addition, PM is planning to develop MRD (market requirements document), involving specific implementation issues, but also with RD communication confirmation. If you do not have some basic technical background, often communication can not be in-depth.

In fact, PM for the mastery of technology, although the more the better. But you don't have to be as deep as Rd, and you just need to have some superficial understanding.

Second, there are two more important requirements than the PM Master technology:

(1) PM to the product users and the market grasp and awareness level.

Can really grasp the needs of users, and their planned products have a strong understanding of the experience. This is more important than the technology itself.

PM for a product or function, to have their own unique understanding. Have a precise grasp of product quality and user experience.

Because more Rd often takes orders from PM's requirements planning, and Rd in concrete implementations, there are times when it comes to achieving fast, sacrificing quality and effectiveness. These times are the test of the PM on the product positioning of the cognitive level, but also assessment of the PM judgment time.

Each rd has a deep heart that wants its technology to be used and approved by more users. If the user needs and market positioning is not clear enough to become "virtual workers", for Rd and PM will be a great "sorrow."

(2) PM communication and coordination skills

From product demand to product realization, in fact, there will be a continuous process of communication and coordination.

First of all, PM can't "Just say not listen". If you don't have enough skills, you can still communicate by listening to some rd advice. PM can try to get Rd to explain the technology more clearly. At the same time, PM also patiently the user needs and market positioning, functional requirements, such as explain clearly. This is useful for cooperation. and Rd as a developer or an ordinary user, he also has his own product experience, you can communicate with each other.

In short, for the demand target and market user positioning, PM and Rd must reach a consensus. Work together, not so clearly as "division of Labour". is not a simple one side of the final. PM and Rd have an unshirkable responsibility for whether a product or function can achieve the desired goal.

Probably this view, write a bit of a mess. Very welcome to discuss this topic together, hehe.