Brief discussion on the collaboration and communication skills of product design team

In fact, the design of communication and collaboration, this topic a throw out, it will make me feel very big.

A lot of bad stuff between the demand side, Product Manager, program,uiue, test. The difficulties of communication are compounded by the difficulty of communicating with a third party or even a few companies. If it comes to collaboration with the government, it's 2012 of a disaster.

And even internal communication, but also take into account the internal interest group game, each other to undermine such a thing is also the market, which basically may be completely unable to communicate, and then can only rely on means to check and balance.

Therefore, if we really want to discuss the communication and collaboration involved, we must set up a relatively satisfactory environment, that is, we are all in the wrong, and we can discuss it. Otherwise, we should use the specific problems of dialectical analysis. And I wrote the following questions about communication, also based on the idealized environment, because I am a product manager, so I am in the role of product manager to understand and deal with these issues.

Communication, collaboration is a Pangu open heaven and earth when left over the problem, the same, also left over five must kill artifacts:

1: Do you have a design I know?

2: This question is not considered at this stage;

3: This is not necessarily a problem, is a person's opinion;

4: This cannot be achieved;

5: This our bottom is not supported;

These five artifacts were picked up by art, products and technology. Artifact One, seconds kill, you depressed to shrink Yang also useless. In UCD Zhuhai BOOK FRIENDS MEETING, Jinshan students The first problem is technology resorted to kill: this we can not achieve.

For the five major artifact, I really met many times, in fact, will kill can be broken, only see you willing to. The law of the dead must be killed, I sum up to five points:

1. Equal dialogue

Art, technology, testing is our most important work partner. For their work of knowledge, we have to dabble, do not become experts, but must have some understanding, it is best to have their own hands-on ability. In this way, to establish an equal dialogue with them, said the words will not be despised, will not be secretly scolded as SB.

If as a product manager, but do not know what is the bottom of their business, the basic code, data principle is how to be lost to kill skills is deserved.

Quote a front: "I absolutely refuse to work with a product manager who doesn't even understand HTML, which is the bottom line." ”

2, whether they think clearly, whether it is really necessary;

When you ask someone for a demand, you must think clearly whether it is necessary or not. Find ways to convince others, it is best to have data to show that your needs are really necessary, can shorten the user query time, improve the installed rate, reduce the unloading rate, improve online time and so on. The Product Manager completes the analysis work beforehand, is to own the work the respect, is also to the cooperation partner's respect.

It's best not to make a decision to pat your head. After all, we downplay a few words, technology, art may be for you these words busy for a few days or even weeks.

3. When others refuse, find out why;

About this point Jinshan Sword three director Tang Hongliang is a good analogy: toilet ground water, why there is water? Because the bridle drips, why drip? Why didn't you close the door? Because the bridle is not very good, why not close it? Because of the design of the bridle, why buy this bridle ...

Encounter problems, not shrink, to be serious, to ask, to break the sand pot to ask the end.

Programmers have a belief that in this world, there is no code that can't be done. If he says it can't be achieved, he must not. Why not, either the cost of the modification is too high, or your needs he thinks that there is no need, or that he does not see you at all. Find the root of the problem, and then the right remedy, can always solve.

4, to confirm that others understand, is what you want to say;

You think is a, speak out is B, others listen to C, after understanding into D, and finally processing to make an E, netizens see, said: This silly x company, make an F, is fuck meaning.

Communication becomes wavelength, what will the world be? To avoid this situation, so before communication must ensure that information symmetry, demand background, research data, user data, etc., lest you suddenly say a decision, others inexplicable, how to communicate?

After that, make sure that the other person accepts your message and understands it as much as you do. So need to let him repeat to you again, like the assembly number of millet to the head to repeat the order, the information sent and receive need match once, confirm correct, this communication is finished.

5. How is his personality and mood?

Generally speaking, solve the above four problems, the basic communication is not a problem. But compare us is human, not machine, all process execution complete, match once, confirm correct OK. People, there will be emotions, will be related. So when the demand is rejected, but also need to consider human factors, such as: "Stock loss, wife Ran, lover blew, others hair ..." Wait a minute, you are hot in the face to find someone else to communicate, others will only give you the butt.

No matter how perfect your company system, looking for technology, art and other partners eat more food, go hiking or something, exchange some personal space, become friends, so there are things, you can understand me, I can understand me, build a harmonious new society.

As for the communication skills such as listening, expression, equality, and so on, do not say here, in fact, many times the problems encountered are system problems, if everyone's interests bundled together, can solve a lot of communication problems.

All of the above are peer or cross-sectoral communication issues, in addition to the problem with the boss communication, and subordinates to communicate problems. This is not the design of the communication and collaboration category, but I saw an article, feel that said well, a simple summary, is three points:

First, the upward communication is not brave: subordinates to superior communication without guts, lack of positive initiative.

Second, the level of communication is not lungs: the department and peer communication between the lack of sincerity, no heartfelt words.

Third, the downward communication is not heart: superior to subordinates do not have too much mood or time to communicate, can not be the shift of subordinates timely guidance and correction, has caused the current enterprise managers spend one months to recruit new personnel, do not want to take 2 days to communicate with subordinates.

Said so much, and then introspection: anything, know more theory, should pay attention to the unity of knowledge and work.