Team management.

What managing a team really means

Team management is most often understood as control: making sure people work and correcting them when they do it wrong. But control is a consequence, not the essence. The essence is that people understand where they are heading and can make decisions without you.

It is easy to check. Ask several employees the same question: what is the company's main task right now and how does their work affect it. If the answers diverge, the problem is not discipline.

What follows are the four things management is made of: clear goals, honest communication, developing people and recognising results. None of them replaces the others.

Goals that actually work

The wording “work better” is not a task: it gives no idea what to do tomorrow. A goal becomes workable when it has a number, a deadline and an owner.

The second requirement is a link to the company's overall goal. An employee must see how their metric affects the business result. Without that link, the number is perceived as a means of control rather than a guide.

The third is that there should be few of them. Three tasks per quarter get done; ten never do. If everything on the list is important, there is no priority.

A separate frequent source of conflict is different definitions of the same result. The classic example: marketing counts every enquiry as a lead, sales counts only qualified ones, and an argument about performance is inevitable. How to bring this down to a single scale is covered in our article on aligning marketing and sales.

Communication: how to learn the truth in time

Bad news reaches the manager last - and that is exactly why decisions are made late. The point of open communication is not comfort but the speed at which information arrives.

Three simple mechanisms work. Regular one-to-one meetings - short, but in the calendar rather than whenever the mood strikes. Team meetings where you honestly report how things are going, including what is going badly. And a clear rule on whom to tell about a problem and how, without waiting for it to become noticeable.

The key condition is how you react to bad news. If the person who brings a problem gets a dressing-down, next time they will keep quiet. If they get help, you learn about the next problem a week earlier.

Asking is a skill too. The question “is everything all right?” almost always gets the answer “yes”. The question “what stops you working faster?” gets a list.

Development: why this is not about training for training's sake

Investment in employee development is often postponed because the effect is not visible immediately, while the risk is clear: we train them and they leave. The logic is understandable, but the result is the opposite - people leave precisely from places where there is nothing to learn.

Development does not necessarily mean courses. Most often it looks like handing over more complex tasks, reviewing other people's mistakes without hunting for someone to blame, mentoring within the team and access to information that previously only the manager saw.

A useful rule: every employee should have at least one task that is currently slightly above their level. That is where a person grows, and where you get a replacement for yourself in that function.

And write down exactly what the person should be able to do in six months. Without this, development turns into conversations about prospects that never lead anywhere.

Recognising results

Praise is the cheapest management tool and the most underrated. This is not about bonuses: a bonus settles the question of money, recognition settles the question of meaning.

Specificity works. “Well done” means nothing; “you found the error in the calculation before launch and saved us a month” means something. The person understands exactly which behaviour is valued and repeats it.

The setting matters too: recognition in front of everyone works more strongly than in a private message, while reviewing mistakes is the opposite - only in private. Getting the order mixed up produces the reverse effect.

It is also worth noticing not only the result but the attempt. If you punish failed experiments, people will stop experimenting - and improvements will disappear along with them.

What breaks a team fastest

• Different rules for different people. One person is forgiven for being late, another is not - trust in the manager vanishes within a week.
• Decisions without explaining the reasons. People fill in the gaps themselves, and usually fill in the worst.
• Taking tasks back. The manager takes the work back because it is quicker to do it themselves - and the employee stops taking responsibility. More on this in our article on delegation.
• Promises that are not kept. One broken promise devalues ten kept ones.
• The manager's silence in a hard period. Lack of information is harder to bear than bad news.

The team and how it is seen from outside

A company's internal workings have stopped being an internal matter. Candidates read employee reviews before an interview, and clients read them before a deal, and the two overlap more often than it seems.

This means that working with the team directly affects hiring. A company with a poor employer reputation overpays for every new hire, because strong candidates simply never reach it.

The mechanics are the same as with customer reviews: the response matters more than the review itself. How this works is covered in our article on reviews and reputation, and what the internal environment is made of - in our article on corporate culture.

If reviews of you as an employer are getting in the way of hiring, that is a practical task with a clear solution - reputation management. We start by gathering where and what has been written about the company, and only then suggest what to do about it.