All good! As always, a little about us: the “Development Manager” course , despite its novelty for being a not quite clean “programmer” course, turned out to be very successful in terms of the number of graduates: only more than thirty people dropped out of four people learning related reasons. So having finished one stream, we start now the second one, having slightly updated and added now open lessons, where you can get acquainted with the teacher - Stanislav Mikhalsky , and in general with what is given on it.

Well, also, as always - a small article-article from a teacher about typical mistakes that he, and probably everyone had to face.

Go.

“Always honestly admit your mistakes, it will dull the vigilance of the authorities and allow you to mess things up new.” Mark Twain

1. Easier to do everything yourself than to explain

This is probably the most common mistake. For some reason, many people think that it is more difficult to set a task than to solve it yourself. Especially in the situation of the approaching deadline. Often, managers are justified that "now is not the time to teach others, you just have to do business." And in the next project they are again in the same situation.

Output: conscious willful effort not to allow yourself to perform the tasks of the performers. The key competence of a manager is to achieve results not by himself, but by the whole team. A leader who cannot do this is not a very good leader.

2. I now head and I do not want to get into the details

The leaders who came “from outside” are inclined to this extreme. Some do not dive into the business at all. This is as bad as the previous error. A good salesperson himself necessarily participates in transactions. The leader of the evangelists must speak well himself. The programmer must understand the code.

Truth is in the middle: a good manager needs to know how a business works, in detail. But not to try to do all the work for your employees - it will not work anyway, sooner or later he will rest on natural limitations, and the team will not develop.

3. I want to control everything

The situation is similar to the first one, but the emphasis here is different. The head seems to give the task to the performer. But at the same time wants to see almost every character code! The employee is constantly “under the hood” while the manager asks him to put himself in a copy of all the tasks, asks for daily work reports, and so on.

Naturally, the employee does not feel responsible for the result. The leader delegated to him the execution, but not the responsibility. Not only that micromanagement great reduces the efficiency of labor and the performer, and the head. It also completely deprives of motivation.

4. I am not interested in what is happening.

Reverse situation: the head is fully transferred and the performance and responsibility of the employee. But not even interested in the progress of the project or the implementation of the task. In this case, the contractor does not feel that the task is important for the manager, does not have the opportunity to ask for advice, does not receive feedback from the manager and, as a result, makes mistakes or at least does not achieve the maximum result.

Exit: you need the right balance. Extremes do not work in either direction. Search for the right balance, individual for each employee.

5. Confused loyalty and loyalty

We recall Shakespeare and "King Lear." Novice executives often confuse loyalty and dedication. This is a very dangerous mistake. After all, far from always those who agree with you will be with you in difficult times. And those who argue with you do not always give pleasant feedback and save you from error, often turning out to be your most loyal companions. Not to distinguish loyalty from loyalty is a big mistake, since not always the absence of loyalty means loyalty.

The consequence of this error is to recruit managed employees to the team. Who will treat you loyally. And the obstinate, having their own opinion - to avoid. A special case: to avoid people stronger than yourself, for fear that you will “sit down”. This is a very big mistake. The caliber of a manager is determined by the caliber of the people who work for him.

BONUS: The biggest mistake

Not to admit one's mistakes, to be ashamed of them, to hush up them, not to be willing to discuss them is the biggest mistake. In fact, there is nothing wrong with them. They are the best indicator that you are developing. Is it possible to learn to ride a bike without ever falling? Is it possible to learn how to fry pancakes without making at least one pancake lumpy?

On the contrary, if you do not make mistakes, then you have stopped in development. So please mistakes. Thank those who point them to you. Do not be offended, do not argue and do not make excuses. Draw conclusions and grow above yourself.

THE END

We are waiting, as usual, for comments and questions, and we invite you to an open lesson where the first mistakes of a specialist will be considered.