Why My Team Failed

I used to have the impression that people in some countries have a good performance in their work, but that's not entirely true. When you have the opportunity to work with them, you will find.

For more than a year and a team work, I've been observing how they operate, and I've found that a team can easily collapse if there is no experienced, responsible manager, or unfortunately an irresponsible manager. Especially when they are developing new products, and at this time their existing members are ignorant of the new skills.

When the team's managers start to recruit new work members for the team, the object is usually a well-experienced programmer who will contribute their views on the project and build a plan for the new product in the first phase of development. While managers at this time are excited to learn about these new technologies and possibilities, they often make a mistake by giving these new members too much reliance, allowing new members to assume that they are responsible for the project, and worse, they may think that the application is what they plan.

When development starts, the team's original staff will also join the development team, although they know nothing about this new technology, but for them, learning and development has become a habit, the project managers expect things as well as expected, in the scheduled time to get the predetermined results, but, He forgets to give members of the team their clear responsibility for assigning, who should be working on that part of the code, who should manage that part of the codes, and the result is that things are going in the direction that they can't be expected, and when new members start checking the code, they find that the code written by the old members is not as expected as they planned. , so they start to feel the need to negotiate with older members, talk, and constantly explain, trying to tell them what the app should be like.

It looks like they're trying to help, and they actually think they're helping, and they really want to get the team members to know about the new technology and the professional way the code is organized, but it's a mistake. Because they forget that these members have been working in their company for 5 years or more, they are accustomed to their own way of working, so you can't let them try to change, and don't expect them to listen to you.

And when this happens, things get ugly, and we can't deny that programmers are generally arrogant groups, and that arrogance is even like a professional disease, whether or not the programmer knows or knows these new skills, they have been working for years, have extensive experience and product development experience, So for the new members who are nagging in front of them, they are a bit of a professional insult. So at first they try to avoid the conversation, and then they may be rude to stop the conversation, when the new member realizes the problem.

When it comes to this stage, it is time for managers to show their charisma, and if a project manager is just obsessed with conflicting personal circumstances, such as unpleasant conversations, or rude, sharp words, and just trying to solve such problems, he will fail. Thought he did not recall the problem, and did not have a good thinking about the problem, it is clear that managers should not just expect the project to complete, product development, and then to sell, but focus on the development of the problem.

Personally, the solution is, for the new members, although they define the product, and have a wealth of experience, professional code skills, familiar with the new technology, but let them know that they do not dominate the whole development, for the team, first of all should select a development plan, Then regardless of the development plan, the new members should follow the development plan, and perhaps the development plan is not what they expected.

For the original members, they worked in the company for a long time, they should be responsible for the establishment of the plan, although they know little about the new technology, or think of a lot of it, regardless of the professional point of view, their plans may not be how, may seem stupid, but all the members should follow it, Because once the plan is selected, the product is determined. Not all companies are worth having a good product at first, but they are all growing up, and for the company, the most important thing is to maintain the stability of the team to maintain its products and business.

A team is easy to fail because if the manager doesn't look at the problem, it's just a matter of the individual plot, because all of these personal episodes, unpleasant things are not the reason, because of his plans are not thoughtful, or his mistakes, and he often denied the kind.

I usually got impression from different source about people in some other countries, and they is superior at their work, That's not all true. When you get the work with some of them, you'll know what they is ...

Being yearly working with a team and observing how it works, I found a team are easily to collapse if there are no experienc Ed and responsible manager, or there is an irresponsible manager. Especially when they is developing new product and all those previous member doesn ' t know it at all.

When the team manager is construct the team by recruit new members, those new members usually had good experiences on Their works, and from the first phrase of development, those new members would contribute their idea and build the plan for The new product, at this moment, team manager usually made a mistake, to give those new members too much credits, so they Is thinking they is responsible for the project, and the product should is the app what they has planned. 

As the development begin, those previous team members who don ' t know on those new skills well also joins in, and tea M manager expected that things going as well as what the he expected, he didn ' t clearly let all members knew about their posit Ion, who would be is in charge of the "what" of the work, so things start-to-run into an unexpected, those new Think they have planned the app, they think the app they is working on, should all follow their plan and when they fin D that those previous team the WHO didn's t do it, they the begin to negotiate with them, try-to-discuss with them, explain To them, as they think they is helping.

But they is wrong, indeed in their opinion, they is really trying to help others to understand the project well, to know How to is more professional in new skills, but they forgot all those previous members, most of them has been working at The company for about than five years, and commonly those people has get used to the the-the-the-they is working with their Team, and they won ' t change and listen to the other members.

When it happened, things would go ugly, we all can ' t deny a fact that programmers usually arrogant, it's like a decease roo Ted in programmers mind, whatever they know or don ' t know the new skill, if they has many years of experiences on program Ming, they would regard that those programmers who is telling them how to does, a bit insulting, at first they just ignore T He conversation, and later they would shutdown it, this time, the those new members start realize what happened.

Usually when a team go into this kind situation, it's time for Team manager to show his charming power to handle it, if a Team manager only focus on those personal issues like unpleasant conversation, being rude and sharp words, he'll be fail Ed, because he didn ' t track back to the real problem, and take a reasonable thinking about it, team manager should isn't be The guy's only push their members to being working efficiently, get the work do, and get the money earned, but see the PR Oblem of development.

Actually the solution is, for new members, even though they knew all on this new app, and they probably has a thorough Thinking and very good plan on it, professional and writing beautiful code on it, but they should know they is not in CH Arge of the development, and the whole team should pick a plan first, and to work on that plan whatever it is or not thei R plan, even its not good enough, they should follow.

Those previous members, who has been working at the company for years, they should is responsible and making the PLAN, Ev En its bad, awkward, or sometimes stupid from professional view, but all team members should stick on it, the the-the-the-app 'll be, the the-the-the-team chose, not all company deserve a great apps at beginning, but they was growing up, for the COM Pany, the most important part was, to sustain the stable of team, and maintain their business easily and well.

A team would be Failed, if the team manager didn ' t look into the real problem of the team, to discard all those personal are Sues, because all of them, is not the reason, the reason always happened on his PLAN, and he mistakes, and usually what He denied.

Why My Team Failed