Managing someone who does not work the way you do
Most lasting tensions in a small team do not come from a lack of competence but from a difference in working style that nobody has named.
In a small company, the owner has built the organisation in their own image, usually without having decided to. Meetings run at the pace that suits them, decisions are taken in the way that feels natural to them, information flows the way they like it to flow. It works as long as the team resembles them. The day someone very different arrives, the friction is immediate, and it is almost always read as a problem with the person.
The symptom
The sentences are always more or less the same. You have to explain everything to him three times. She never takes any initiative. He rushes in without thinking. She drowns everyone in detail. He never says a word in meetings.
These formulations share one feature: they describe a deviation from an unspoken norm, which is the working style of the person speaking. Nobody says you have to explain everything three times to someone who absorbs information at exactly your own pace.
That obviously does not mean every deviation is legitimate, nor that genuine problems of competence or commitment do not exist. It means that before ruling, you have to separate the two, and that the separation comes down to one simple question.
The question that separates them
Ask yourself this: is the result achieved?
If the person gets the expected result, in the expected time, at the expected quality, but in a manner that irritates you, then you are dealing with a difference in working style, not a performance problem. The salesperson who never fills in the visit report but who sells, the meticulous technician who takes an hour longer but never has to go back, the colleague who says nothing in the meeting and sends a sharp note the next morning: these are ways of working, not failings.
If the result is not achieved, the next question is why. And here again, the answer is rarely laziness. It is far more often a misunderstanding about what was expected, missing information, an unsuitable framework, or a skill that was never acquired because nobody checked that it had been.
The four most frequent differences
The first concerns the pace of decision. Some decide fast, with little information, and correct afterwards. Others need to gather before they settle. The first finds the second slow; the second finds the first reckless. Both are right depending on the circumstances, and a team made up only of the first kind takes quick and sometimes costly decisions.
The second concerns the need for structure. Some need to know precisely what is expected, by when, following which procedure, and then produce remarkably well. Others wither inside a framework that is too tight. An autonomous owner assumes autonomy is natural, and mistakes for passivity what is in fact a need for bearings.
The third concerns the relationship to conflict. Some say things, sometimes bluntly. Others avoid direct confrontation and get their message across by other routes. The second type is often perceived as evasive when they are simply less frontal, and their information stops coming up altogether if they are criticised for the way they deliver it.
The fourth concerns how people recover. Under strain, some speed up and talk more; others close down and need to be left alone to get going again. Mistaking that withdrawal for disengagement is a classic error, and it gets worse when the response is more pressure.
What a manager can actually do
Name the difference, first, and name it as a difference rather than a flaw. Telling someone that they need more structure than you spontaneously provide is an observation; telling them they lack initiative is a judgement. The first opens a conversation, the second closes it.
Adjust what costs little, next. Many differences dissolve with tiny changes. Giving instructions in writing rather than verbally. Announcing a meeting topic the day before so that those who think ahead can do so. Accepting that a report fits in three lines if the essentials are there. These adjustments cost nothing and remove months of irritation.
Keep the standard, finally. Understanding how someone works is not excusing them. The result is still owed, the deadline is still owed, the quality is still owed. The difference is that you stop asking someone to be a different person and concentrate on what has to be produced.
The real benefit
A homogeneous team is comfortable and fragile. It decides quickly in the same directions, sees the same things and misses the same ones. A team made up of different working styles is more tiring to lead and markedly more robust, on one condition: that the differences are named and accepted rather than experienced as faults.
That is a manager's job, not a tool's. A behavioural report can supply vocabulary and stop the conversation turning into an exchange of accusations, because it is easier to talk about a documented need for structure than to accuse someone of not coping. But it replaces neither the observation, nor the decision, nor the act of saying things out loud.