The emotion and efficiency of the technical team

Why the efficiency of engineers is so obvious that the peak trough. What is the relationship between negative emotions and work efficiency? Team Leader How to ensure the overall efficiency of the output and the growth of everyone. Why do students who are addicted to technology always run out of the project. For engineers, there are often obvious efficiencies, sometimes a day to get a few modules in, plus several new skill points, and sometimes a simple function is two or three days and no different. Although the task is not complicated, but can not help brush will be micro bo, chat will QQ, even if the bite the bullet to do, often inefficient and even introduce some new low-level bugs. This difference has nothing to do with skill level and work attitude, which is seen by most engineers. There are many factors affecting efficiency, first, anxiety. 1. Anxiety, execution collapse, GTD when the task is single, everyone's efficiency is often high, such as "Today before work only to provide a user access to the interface on the line, the city code, paging back to users," this to the vast majority of students have no psychological burden. But the reality is not so simple, especially in the entrepreneurial company, every day will have a variety of tasks, may be operating a will want a data, the product will report a Bug, or the boss has raised several new optimization points, these tasks to see a small amount of work, but the continuous and disorderly task to an engineer, Can completely destroy his day's efficiency and mood. In particular, research and development need attention, frequent task switching will waste a lot of time and energy. "Stress does not come from the task itself, but from the blockage of the task in the brain, the anxiety and the psychological resistance," things in GTD. When a task is not completed, the new task will bring great psychological pressure, not strong enough, it can easily lead to the collapse of execution, into a task how to do all the desperate state. Knowing why, and naturally there is a solution, GTD provides a very workable implementation plan. The simplification is as follows: 1. Put the task in the "to be categorized" "today to Do" "Schedule" "Waiting" in a few boxes of 2. Collection: Every time you receive a new task to make a judgment, if the task 5min can be done directly kill, otherwise all placed in the "to be categorized" box. 3. Finishing: Start every day from the "to be categorized" box to start filtering tasks, pick out today need to do 3 things, put into "today to do." If you don't need to do it today, put it on the schedule or wait in the box, depending on if there is no clear execution time. 4. Executive: Just stare at "today to do" and then have new tasks to perform the collection steps. 5. Review: Regularly organize your own "schedule" "Waiting" box. Complete Flowchart: This solution will be able to clear the clutter of the task, to some extent to reduce psychological pressure. Tools: A lot of time management tools to meet GTD, Doit.im is one of the best, full platform coverage,Highly recommended. OmniFocus is the most powerful, support the unlimited level of directory functions, but only support mac/iphone/ipad, and expensive. You can also use impression notes/onenote to plan your own management, which is relatively flexible. Doit.im: The above is about what individuals can do in the face of task stress, and as a company/Project Manager/Product Manager, it is also necessary to do something to avoid the "execution collapse", which is to keep the pace of development. 2. Rhythm, emotional strength the first time you hear the "Development rhythm" is in the micro-blogging scrum Project Process training, this concept explains the previous university in our student outsourcing team encountered many problems. Jane has been able to quantify a physical value for everyone's emotions. This physical value is consumed by each development task/meeting/report, which may take a few days to recover from the physical overdraft (which is also what we call Recovery Drive), which can lead to worse emotional problems when the overdraft is excessive. So a healthy team needs to maintain the rhythm of development, the specific operation can be every 1-2 weeks for a cycle, a large project planning, research and development tasks occupy the best time is not higher than 80%, after everyone can have a rest/self-charging time, at the beginning of the next cycle, the team can enter the state of full physical value. Specific to my current team, we take a week as a unit, weekly product manager to complete this week's demand, we carry out the division of labor after digestion, deposit into the demand system. During the rest of the week, the product should minimize disruption to development, and review and summarize last week's tasks next Monday. This set of programs played a certain effect, team members do not have a clear sense of exhaustion, a weekly free control of some time (task can be completed early, free fitting time more). Tools: Team Requirements Management system we have tried OneNote multi-person collaboration/TEAMBITION/TEAM.OSCHINA/C Zen, but generally not ideal, or function too complex, or can not integrate the BUG system, is currently using open source Cynthia, Cyntia is also our team's bug management system. The choice of specific tools have time to pull a blog to say #.# cynthia:3. Another problem of emotional impact efficiency is emotional, emotional problems are very harmful, the most direct is: 1. Emotions are easy to generalize: problems caused by a single inducement can affect all aspects: enthusiasm, work efficiency, quality of work, etc. 2. Emotion is very easy to infect: within a small circle, the emotion is very easy to infect (QQ group work cannot not) 3. The mood is not good to eliminate: Later will see, causes the emotion the question many is before the small problem cumulative accumulation, or is the present stage is difficult to solve the problem. There are many factors that affect the mood, simply enumerate a few very common: 1. Research and Development RhythmToo compact: In the previous section it was mentioned that when the emotional strength of development is constantly overdrawn, there will be bad emotional problems. This is not uncommon in the development team. When the development of the pace is too tight, the team does not pay attention to rest, the team is very easy to diffuse negative emotions, and emotions once the formation of the impression, it will not be so good to dissipate. 2. Pay upside down: This is also criticized hr/leader important reason, when a team salary internal growth is too weak, internal staff will have outflow, the team needs to recruit new people, and the market on average treatment has been different from before, so the new recruits to the treatment will often rise. This is very lethal and difficult to dissolve. HR is too cost-saving and often has a fatal impact on the team. 3. Leader ideas/habits. 4. Improper placement of work, too difficult or too simple, or inconsistent with career development planning. 5. Pure vent. ...... After the emotional problem is exposed, it is not impossible to solve the problem, when there is a clear appeal, directly to solve the problems themselves. The lack of a clear appeal may be complaining about character or the direction of the company, which can not be forced. What's really scary is that the team Leader (or the person responsible for the problem) has no knowledge of the team's own emotions. When everyone's private QQ group/discussion group did not you, the party did not participate, there will be no real words to communicate, only the work of routine contact, it is a very dangerous signal, members leave to look for the reason is already too late. 4. Tangled Leader Leader This word is not too apt, this position's responsibility should be the service team's development schoolmate, finds and solves everybody development unpleasant place, completes the technology and the business structure, guarantees the overall research and development output quality and the time point. And Leader is not really easy to be. To obtain the respect of the engineer, one or more of the following items needs to be met 1. Technical skills, can solve all the technical problems encountered by the team. 2. Emotional quotient against the sky, have the ability and willingness to perceive team members ' emotions, and can constantly give positive feedback, the team to maintain a strong cohesion. 3. Have a deep experience, the industry has the influence or forged the company's inheritance, to win resources for the team. And without the full respect of engineers, the implementation of the various measures will be affected, the technical decision-making discussions to fully respect the views of the people. 5. Technology-driven technology-driven business is one of the drivers of disruptive innovation, engineers know better where the boundaries of technology are, and which scenarios can be solved by mature (or semi mature, but manageable) technical solutions that will pull the company and competitors apart in one or half technical times and output cooler products. This era for engineers is the best era, the rise of GitHub and other open source community, so that the learning costs of new technology become very low. Data mining, natural language analysis, graph database, data visualization, virtualization, mobile interconnection and other technologies to the business has brought unlimitedPossible, and the U.S. market and the Chinese market still has a 5-10-year lag, but also provides us with a lot of templates can be referenced. Technology drivers have more practical things to do, put in the second-hand car industry, for example, when other products rely on users to fill out the needs of their own cars, you achieve through the user's behavior trajectory mining user needs; When the other product or several pictures to show the condition, you achieve a low-cost panoramic picture, When other products are still in need of the dealer to maintain their own relationships, you through the graph database to calculate his possible friends circle ... So the question is, how should we push the production of more technology-driven products 1. Relaxed Learning atmosphere: technology-driven generally with the help of relatively avantgarde technology, most students do not have much experience in these technologies, rely on continuous learning, and learning needs to have a learning atmosphere, especially the protection of time. 2. A good engineer: technology driven requires more of the requirements of the engineer's self-realization, and only wants to complete the existing task. Engineers who don't want to do things clearly don't fit. 3. The combination of technology and business: the ideal is that the engineers themselves have business thinking, can take the initiative to combine new technology and business to find the best value of the combination of points, followed by the engineers regularly preach technical results, and product students to discuss together. For example: "We have all 200,000 dealer data into the map database, support width traversal, depth traversal of these query methods, their time complexity is O (n+e)" "We can analyze these hundreds of thousands of comments, to distinguish between positive or negative, but also to match our database in the brand car system, Accuracy can be 60% "technology drivers have some mishap, or engineer students lead the project is easy to appear in the mishap: priority, time point, task management." Priority: Students who are addicted to technology will be attracted by the problem itself, for example, "MongoDB also supports data fragmentation, so I'm going to try a cluster." "I'll try to load the 1w QPS pressure here." Although I'm watching ibeacon, but Ardunio is cool Wow, I'll do a demo first "and so on, In this attraction, it is difficult for engineers to be interested in the task of having a page and fixing the data, which may be higher in priority for the project. There is a similar conclusion in psychology that when the difficulty is reduced to a certain degree, the intensity of the motivation decreases. Time control: At the same time because many of the use of the technology is not used by everyone, the technology itself may be immature, we are not much experience, sometimes some pits for a long time to be buried, so fixed point of time is difficult to ensure output. Task management: Many students who are eager to solve problems are also small diggers, they can foresee a more elegant solution, but there is no time and energy to complete, in the process also dug more new pits, so these pits have no time to bury ... Because of the above reasons, we will find that many students who are addicted to technology will be in the process of doing the project, the total end of the appearance. This situation requires technical studentsPay attention to determine the overall direction of the team, regular reporting, weekly or monthly reports. How to improve the efficiency of individual and team. Will be accompanied by the development of long-term problems of the industry, each team to find their own answers, we work together.