About the meeting.

Just on the line of the project, during the most recognized is when facing a variety of demand side, how to communicate each "break" and let them all satisfied.

A good article, said that the product manager needs analysis is higher than the demand side, the general meaning is:

First of all, people are standing in their own perspective to see the problem, but the product is often to integrate different business needs, a large pile of demand does not do analysis, sorting integration together, users must be very disgusting.

Second, some of the needs of the demand side may be narrow, and he usually only tells you that I need a quick horse (not a new product called a car)-Henry Ford, which requires you to innovate and reprocessing.

If you believe in decisive, communication skills, in the meeting for different needs, if the appropriate use of communication methods, may achieve a common win effect.

(a) Avoid professional "Sando Mamang"

The longest delay in a meeting is often not due to too much content, but a point of contention ...

You talk to me about the user experience, I'll talk to you about data analysis, you and I talk about data analysis, I will negotiate the business plan .... In short, in my professional, no one than I authority, this is my major, you dare to challenge me, I professional or you professional. Finally who can not challenge who's professional, discussion also no solution ...

Some colleagues also illustrate this map:

Analysis：

Psychologically, everyone hates others in their own areas of expertise, if everyone in their own professional to a problem, the different direction of rambling, their professional sacred inviolability, the communication most long tangled, finally no fruit.

Good communication is built on the basis of both sides ' expertise coverage. Communication is not exclusive to the professional, but wide to wide. As the virtual core of the project team, the product manager is to study as widely as possible professionally, the second is to trust the teammates professionally, to understand the learning actively and to balance the whole.

(ii) give the opposite party a victory that doesn't matter

A lot of people have been confronted with the problem that there is always a class of eloquent people at the meeting who disagree with you on a particular detail.

"Why do I not use the input box directly?"

"I think the dropdown is the most common style in design, the user is more familiar with"

"But don't you think it would be a lot of trouble to pull through?"

"... yes, but I think the direct input will cause a lot of checksum problems, such as: full angle half Corner"

"I think the front end has a way to solve it, and it can be turned into half a corner." And, Blablabla ...

“.........”

It's a waste of time to start arguing about this irrelevant thing, but if you're talking back to a new wave of discussion, do you want to do user testing and data analysis for this stressful project? is that necessary?

Ask yourself, if the product is fatally harmed by their methods, will the user not understand or be angry or frustrated? If not, what about handing over this indifferent victory to the other party? The negotiations also let the other party "accounted for the cheap", may be on the road after the other side will have concessions on the key points.

(iii) Focus on the taciturn people in communication

There are always taciturn people who seem to be more likeable than chattering conductors, but these are often the "deadly mines" of project delays.

It's all right. Demand side

This video you must have read: Girls most of the mouth expression does not matter, psychological a bunch of standards.

In the face of such a girlfriend, such a demand side how to deal with? Online whining a bunch of ...

Say half of the demand side

The common language is "in short, you know ..." This type of person is characterized by the words are not clear, always have reservations. Either he didn't realize that you didn't know anything about it or that you were busy ignoring it. At this point, a lot of details in the project still need to be confirmed ... What to do?

The development of the "Bridging game" is the best example of such communication problems:

Each group constructs the whole bridge half, the request not only conforms to the mission book the request, simultaneously in the bridge modelling, the height, the width, the decoration and so on each aspect all must agree completely, finally spelt into a complete bridge. During the bridge-building process, the two teams had only three communication opportunities.

Sounds simple, there are wood! But everyone thinks the contents of their respective project books it's "You know, I know, everybody knows ..." the confusion in the communication is not timely to find out, finally found that their respective cognitive completely different, the bridge can not butt successfully, for this seemingly simple reason for the failure of the product ...

This shows that the way to communicate is very simple: to be positive, to strive for, to listen to each other's description, and timely ask different understanding, to achieve common cognition.

Finally, say something about the management of the project outside the recognition.

Be careful, procrastination and nice.

In the project, the estimate time and the reminder are the management "attributes". If someone is normal on weekdays, it seems that they are absent-minded and have been procrastinating. Even if you do not have a level of relationship with him to take the initiative to care about whether there are some situations, do a good job of risk prediction and record-keeping measures. These seemingly uncontrollable, but predictable factors often result in project delays.

Another seemingly harmless "jolly good" is also dangerous. They tend to be in the way of human feelings, take unreasonable demands, or are subject to "human" rather than normative, not angry or informed. On the one hand, they do not express their opinions and suggestions even if they disagree with each other. Third, often they are high-pressure people, the team, their own negative thoughts. This is very detrimental to the formation of a unified, transparent team atmosphere, they often need to guide, private more communication.