When Strengths Go Too Far: The Line Between Useful and Destructive

Every behavioural strength has a limit, and it can be crossed in two ways. The strength itself can be overused, or used at the wrong moment. Or the associated weakness that comes with it can become too expensive. Belbin Team Roles calls that weakness allowable while the strengths of the same role outweigh it. Pushed too hard, or left without those strengths in use, it becomes non-allowable - and the team starts working around the person instead of with them. The line shows before anyone names it: in the pattern over time, and in how the team reacts.

I asked clients whether they could see inflexibility as a positive trait. Few did at first. Given a moment to think, some of them got there: a strength, used in a specific situation - which is how every strength should be used. Then one client asked the obvious next question: is inflexibility always positive?

I said no. When used at the wrong time or pushed too far, it becomes an obstacle. He was surprised - he knows me as someone who usually sees quirks and peculiarities as strengths. I explained it this way: these quirks are like pepper. Used well, they make the dish spectacular. Used too much or on the wrong dish, they ruin it entirely.

This is the part of strengths-based leadership and teamwork that most people skip. They identify the strength, celebrate it, and stop there. But every behavioural strength carries an associated weakness - and that weakness has a limit.

What is the difference between an allowable and a non-allowable weakness?

Every Belbin Team Role comes with strengths and with what the reports call associated weaknesses. The associated weakness is not a flaw. It is the predictable cost of a useful contribution - and whether the team can live with it depends on what sits on the other side of the scale.

Belbin’s own definition: an associated weakness is termed allowable if it is outweighed by the strengths of the same Team Role. The weakness earns its place only while the strength is in use. The Monitor Evaluator’s scepticism slows decisions down; the team accepts that because the same person prevents bad decisions. The Implementer’s inflexibility blocks the occasional good idea; the team accepts that because the same person keeps proven processes running.

The weakness stops being allowable in two situations. The first is overuse: scepticism applied to every idea regardless of merit, inflexibility that shuts down all discussion of improvement, not just unnecessary change. The second is quieter and more common: the strengths of the same role are not being used. A sceptic whose analysis the team never asks for is left with only the cost of the behaviour. An Implementer nobody lets implement is left with only the resistance. Same person, same behaviour, nothing on the other side of the scale.

Belbin draws the Monitor Evaluator’s line in two phrases. The allowable version is “scepticism with logic at its core”. The non-allowable one is “cynicism without logic”.

How do you spot the line?

Watch behaviour over time, not single incidents. Everyone has a bad day. The question is whether the pattern has shifted. Is the scepticism now applied to everything, even ideas that deserve consideration? Is the resistance now blocking conversations, not just protecting processes?

Watch the team’s reaction. When one person’s behavioural pattern starts crossing the line, the team signals it before anyone names it. Enthusiasm drops. People stop sharing ideas. Frustration becomes visible. If the most creative person in your team has gone quiet, something in the environment has changed - and it is usually someone else’s overused strength that caused it.

Have the conversation directly. Not about personality. About behaviour and its effect. Most people who overuse a strength do not realise it. Their intention is protective - they are trying to safeguard quality or prevent mistakes. The impact is the opposite, but they cannot see it from where they sit. I use observer feedback through Belbin profiles to give people a view of themselves they cannot get alone. When someone sees that three colleagues independently described the same behavioural pattern, the conversation changes. It is no longer opinion against opinion. It is a pattern that needs attention.

This is why observer feedback changes everything. Only 17.7% of people have a coherent self-view. Read Self-Awareness: You Think You Know Yourself. Your Team Sees Something Different.

What to do when the line has been crossed

Help the person see the impact - not as blame, but as information. Often the most effective intervention is showing them what their behaviour costs the team in concrete terms: ideas not shared, decisions delayed, people disengaged.

An overused strength - or an overused allowable weakness - is a demotivator in its own right, on top of the five in Before You Motivate, Remove What Demotivates. It rarely drains the person who overuses it. It drains the people around them.

Adjust the timing, not the trait. A sceptical thinker does not need to stop being sceptical. They need to hold their analysis until the idea has had room to develop. A detail-focused contributor does not need to stop checking quality. They need to trust the process enough to let others contribute before the final review.

Use the team as the solution. If one person’s strength is overwhelming the team, the answer is rarely to suppress it. The answer is to balance it with complementary strengths - someone whose natural energy can absorb the scepticism without being crushed by it, or someone whose adaptability can work alongside the inflexibility without resentment.

Which strengths get called problems most often?

Six behaviours usually get labelled “difficult”. Each one has a use that works for the team and a use that works against it:

• Scepticism - the team’s best decision-checker, or the brake that never lifts.

• Arguing - the sharpening of an idea, or the contest that exhausts it.

• Perfectionism - the guardrail on quality, or the bottleneck that ships nothing.

• Inflexibility - the keeper of a practical, stable process at the agreed level of quality, or the wall that blocks the turn.

• Manipulation - reading the room and moving the team toward the agreed goal, or moving it for the wrong end.

• Silence - the held space that lets others speak, or the withdrawal that withholds.

These six are examples, not a complete list. Each is usually read as a negative trait, and each is a positive one when used properly. The reason is that none of them stands alone. Every one is part of a much larger cluster of behaviours - a Team Role - and it makes sense only next to the rest of that cluster. Scepticism on its own looks like negativity. Next to the Monitor Evaluator’s judgement, it is the reason the team does not walk off a cliff.

Once a team sees that, the question in the room changes from “how do we stop this person?” to “how do we get the good use of this?”

Where scepticism slides into pessimism, there is a one-sentence test for telling the two apart in The Two People You Call Difficult Are the Two You Can’t Decide Without.

Is inflexibility always a weakness?

Inflexibility gets the worst press of all the associated weaknesses, because it looks like plain refusal. It is the Implementer’s allowable weakness, and it is protecting something: a strong motivation to keep safe what has been proven to work.

Look at when it appears. Most often it is a reaction to a sudden change that somebody says is needed - announced without information, without explanation, without any sign that the person announcing it knows what the current process costs to run. The Implementer is not resisting change. They are resisting change they have not been given a reason to trust.

The best approach is direct and soft at the same time. Not “we are changing the process on Monday”, but something closer to: “I have a few ideas for a change that could make the process more efficient. It is not a final decision yet. Would you discuss it with me? It might be good for the process.” The reason is on the table, the decision is still open, and the person who knows the process best is invited in. Approached that way, the same person becomes very good at implementing the change. The trait did not change. The approach did.

The personal test

I know this pattern from my own life, not just from coaching others. My most trusted partner is behaviourally my opposite - analytical where I am intuitive, structured where I am spontaneous, precise where I am broad. We have strong and sometimes heated discussions. We see the world differently on almost everything. But the combination produces decisions that neither of us could reach alone.

I know my own pepper too. I talk a lot. My observers say so, and the data says so. I have not changed that much. I have accepted it and learned to use it in a controlled way: when the room needs energy and information, I talk; when it does not, I switch it off. Sometimes I simply ask the people around me whether they want the long version from me, or would rather I sat back as a silent observer, thinking. I can do both.

That silent observer is my second gear - a supporting role that helps other people think and discuss. It is not where I live by default. I have to switch it on consciously. Everybody brings something into the room. The skill is knowing which gear the room needs.

That is what happens in teams too. When people understand that their colleague’s annoying trait is the flipside of a genuine strength, the conversation changes from “why are you like this?” to “how do we use this well?”

For the full framework of nine roles and their associated weaknesses, read Belbin Team Roles: The Practitioner’s Guide to What Teams Actually Need. For the broader argument on managing weakness, read Let’s Talk About Weakness.

The balance is the work. Not finding perfect people. Finding the right way to use the people you actually have.

Every strength has a line. Crossed once, it can be pulled back. Crossed often, it becomes the thing your team works around instead of with - and the line moves earlier than most people realise. See your own profile →, then ask the colleagues who know you best where your pepper has tipped from sharpening into ruining. The answer will be specific - and that specificity is what you can adjust.

Frequently asked questions (FAQ)

What is an allowable weakness in Belbin Team Roles?

Every Belbin Team Role carries strengths and associated weaknesses - the predictable cost of that role’s contribution. An associated weakness is called allowable when it is outweighed by the strengths of the same Team Role. The Monitor Evaluator’s scepticism slows decisions down, and the team accepts it because the same person prevents bad ones. Allowable weaknesses are managed, not fixed.

What is the difference between an allowable and a non-allowable weakness?

An associated weakness stops being allowable in two cases. Overuse: scepticism that rejects every idea regardless of merit, inflexibility that shuts down any talk of improvement. And disuse: the strengths of the same role are not being used in the team, so only the cost remains. Belbin describes the Monitor Evaluator’s allowable version as “scepticism with logic at its core” and the non-allowable one as “cynicism without logic”.

Is inflexibility a weakness?

It is the Implementer’s associated weakness, and it usually protects something that works. Most inflexibility is a reaction to a change announced without information or explanation. Approach it directly and softly: share the reason, say the decision is still open, and invite the person to discuss it. Approached that way, the same person becomes very good at implementing the change.

How can you tell when a strength has gone too far?

Look at the pattern over weeks, not one bad day, and watch the team rather than the person. When a strength has crossed the line, others signal it before anyone names it: enthusiasm drops, ideas stop coming, the most creative person goes quiet. Observer feedback from four to six colleagues makes the pattern visible to the one person who cannot see it from inside.

How do you talk to someone who is overusing a strength?

Talk about behaviour and its effect, never personality. Most people who overuse a strength mean well - they are protecting quality or preventing mistakes - and cannot see the cost. Show it in concrete terms: ideas not shared, decisions delayed. Then change the timing, not the trait. A sceptic does not need to stop questioning. The questions need to arrive after the idea has had room to develop.

Should you train away an allowable weakness?

No. An allowable weakness comes bundled with the strengths of the same Team Role. Train it down to neutral and you lose those strengths with it - the Monitor Evaluator who stops questioning also stops catching the expensive mistake. It is far more useful, and more motivating for the person, to learn to use the weakness wisely: at the right moment, in the right dose, next to the strengths that justify it.

Photo by Mats Soomre · #MomentsBySoomre · moments.soomre.com