Seven ways to build a high-performance technical team

I recently read the book "Seven Habits of high-performance people" twice. In my opinion, this is a good book, but it is not as good as I think. Although the seven creden mentioned in the book are really pure and correct principles of life, the process of actually mastering and integrating your beliefs is much more complicated than the methods mentioned in the book, this is what we have always said.

Wang Yangming, the great philosopher of the Ming Dynasty, proposed the "integration of knowledge and behavior" several hundred years ago. With this post-reading experience, this article will talk about some of my views on the high-performance technical team. The theory still comes from this book, but the scenario is embedded in our software technical team.

In the IT industry, no matter whether it is Internet products, mature enterprise-level applications, or mobile tablet computers, there is a team behind them, so I think personal high performance is not terrible, only when an individual is in a team that is highly efficient is terrible. If the potential of each person in the team is discovered, the ability is enormous and the team is invincible.

The seven habits of high-performance people divide individual growth into three stages: dependency, independence, and interdependency. Coincidentally, a team member has to go through these three stages in the team. At the beginning, new members may not be familiar with the technology and business of the team. They must rely on the help of other Members to do things. I call it the dependency period. When they are familiar with the technology and business, after several projects, you can complete some functional modules independently, which can be called an independent period. For large projects or challenging projects or products, you can only complete them through the sincere cooperation of all the members, members need continuous cooperation, which is called the interdependency period. This is the process of a Member's growth in the team. How can they achieve high performance? I think we need to do the following seven things.

First, each member of the technical team must be proactive.

So how can the technical team members be proactive. The following lists some other active examples.

1. Proactive members encounter technical problems rather than being powerless, but want to find other solutions.

2. Proactive members focus on the Influence Circle rather than the circle. If you do. net enterprise-level development. Asp.net css js SQL is something that affects your sphere. What cloud computing, Iot, game development, and so on are things that you care about, active members should do what affects the circle, rather than distracting your energy from focusing on the circle.

3. Keep your commitment. If you have made a commitment to and the given project plan, you must finish the plan as promised.

4. Before writing documents, writing code, and performing verification, you must be clear. Think twice before doing so. Once confirmed, you must take the attitude of breaking the sandpot and asking the question to the end.

5. Be brave enough to bear the burden. A little setback is nothing. Ren zhengfei, the 43-year-old Chinese top entrepreneur, owns only 1.4% of Huawei's shares. The last half of life is suffering from fate, but he uses his own story to tell us how much suffering a setback can bring to you and how much survival energy it will bring to you. Therefore, we need to assume that.

The second technical team must start from the end.

Beginning with the end, it seems a little difficult and understandable. Simply put, individuals and teams must have a vision and a goal, and persistently persevere. Let's take a look at the following visions:

Vision of Apple Computer Company-Give everyone a computer

Microsoft's corporate vision-computers enter the home, put on every table, and use Microsoft's software

Vision of Huawei -- enrich people's communication and life

Vanke vision-becoming the leader in China's real estate industry

Big companies have the vision of big companies, small companies have the vision of small companies, and our technical teams and individuals should also have their own vision.

For an individual, you can become a Web Front-end technical expert within three years. For a team, you can: create the best Mobile ERP in China.

Third, do things first

This principle tells us that we should plan things and give priority to important things.

In the two quadrant Law, we divide things into: I urgent and important, II important and not urgent, III not important and IV not urgent or important.

Whether it's a team or an individual, we should do a good job of II important and not urgent, to avoid I urgent and important things, from III not important urgent things to squeeze out time.

In addition, both our team and our team members need to develop annual, quarterly, weekly, and daily work plans and put important things at the forefront.

Important things should never be sacrificed by the trivial things of sesame bean.

The fourth team member is not a competition, but a win-win situation.

The members in the team are not competitive. We need to achieve a win-win situation. There are infinite resources in the world, not your possession. I will lose it. We should share more resources together. We do not need to blow off others' lights to make ourselves brighter. A win-win person regards the team as a stage of cooperation rather than a battle.

Fifth, let us know ourselves and ourselves.

This is not a question about "how to listen" and "how to say" in Sun Tzu's Art of War. Members need to communicate deeply, this kind of in-depth communication is to truly understand each other. When a team member encounters a problem, they first use empathy to repeat the meaning and feelings of each other in your own language. The purpose is not to suggest, consult, analyze, or judge. Instead, let the other party express their true thoughts and listen with sincerity. Listen with the goal of understanding each other. After fully understanding, give suggestions.

Sixth, achieve 1 + 1> 2 using integrated dashboard

The overall effect of team members is:

"If a person with great intelligence has different opinions from me, the opinions of the other party must be a secret that I have not yet understood. It is worth understanding ."

"The most important thing to work with people is to pay attention to the different psychology, emotions, and intelligence of different individuals, as well as the different worlds they see in their eyes ."

"It is no benefit to communicate with the people who have already seen each other. If you have any difference, you will be rewarded ."

We want to share differences between team members. For example, if both of them are very familiar with the IOS skill, the effect is at most 1 + 1 = 2. They can only be used as a single-host mobile application. If you know iOS, I understand. net, then we can make 1 + 1> 2, can make a variety of applications.

The seventh member needs to constantly update himself.

Update yourself on four levels every day.

1. Physiology: Strengthen physical exercise. IT staff lack exercise, and a lot of people are too busy. The body is the capital of the revolution, and the brothers should strengthen their exercise.

2. Social/emotional: Expand the social circle and keep deposits in important emotional accounts

3. Mind: read more, write more, and learn more.

4. Mind: Serve, clarify values, meditate, and nature.

Every day, we update ourselves from these four levels to achieve small success in our personal field.

 

After writing so much, the most important thing is to say "integration of knowledge and practice". Maybe you have a lot of efficient methods and experiences, so I 'd like to share them with you!