Team Behaviour
Team Behaviour indicates which roles a person can play in a team.
What is this dimension analysing, and why does it matter?
It builds on Belbin’s nine team roles, whose central finding is that high-performing teams contain all nine roles, but not necessarily from nine different people. Where the talents allow it, one person can cover several. The research position is that the average person can take on three team roles while maintaining their expected performance.
That three-role figure is the most practically useful number in the entire report. It sets a ceiling on what any individual can cover, and it means a team of five can, in principle, cover all nine roles, but only if they were selected to.
The nine roles, in three groups:
| Group | Roles |
|---|---|
| Action Oriented | Starter, Closer, Communicator |
| People Oriented | Administrator, Coordinator, Contact Creator |
| Thinking Oriented | Analyser, Creative, Specialist |
Why it matters:
- This is the team-composition dimension. Every other part of the report describes an individual. This one describes what they contribute to a group, which is how work actually gets done.
- Missing roles are predictable failures. A team with no Closer ships late and rough. No Analyser, and bad options get chosen confidently. No Contact Creator, and friction accumulates until something breaks. These are not personality clashes; they are structural gaps.
- Duplicated roles are equally costly. Three Administrators is not three times the drive, it is a standing conflict about who is in charge.
- It changes hiring questions. Instead of “who is the best candidate”, it allows “which roles does this team not have, and who covers them”, a much better predictor of whether a hire will work.
- Each role has a defined allowable weakness. Belbin’s framing, retained here: every role’s strength comes packaged with a specific cost, and the cost is to be accepted rather than corrected.
How do I read the chart?
The navy bars show how strongly the respondent can play each of the nine roles.
Look at the top three. That is the person’s realistic coverage. Anything beyond three is theoretical, the research position is that performance degrades past that point.
Look for absent roles. A role scoring near zero is one this person will not cover under any circumstances. In team composition that is more actionable than their strengths.
Then map the whole team. The dimension delivers most of its value in aggregate. One profile tells you what a person contributes; five profiles tell you what the team cannot do.
The orange bars show the same roles under disempowerment. Roles that collapse are ones dependent on the person having their talents available; roles that rise are what they fall back on under strain.
Action Oriented
Starter
Uses their inquisitive nature to find ideas and bring them back to the team. Perceived as outgoing and enthusiastic. Great at exploring opportunities, developing contacts, and understanding how to get started.
Allowable weakness: over-optimistic; loses interest once the initial enthusiasm has passed.
What the team gets: external connection and momentum at the front end. This role is the team’s interface with the outside world, the ideas, contacts and opportunities that would otherwise never arrive.
How to apply it: take the opening phase, the exploration, the network. Hand over deliberately at the point where enthusiasm fades rather than drifting away from it. Bring things back, the value is in the return, not the exploring.
Mitigation: name the handover point in advance so the drop in interest is planned rather than experienced as abandonment. Test the optimism against someone with an Analyser role before the team commits.
Working with them: give them the front end and expect to place someone else behind them. Treat the enthusiasm as information about possibility, not about probability.
Closer
Most effective at the end of tasks, polishing, scrutinising for errors, applying the highest standards of quality control. Perceived as conscientious and anxious. Great at searching out errors, polishing, and completing.
Allowable weakness: worries unduly; reluctant to delegate; can take perfectionism to extremes.
What the team gets: things that actually finish, and finish properly. This is the role that protects the team’s external reputation, because it is the one that catches what would otherwise reach a customer.
How to apply it: own final quality and delivery readiness. Get involved before the last week, being brought in only at the end and then held to the timeline is the standard frustration of this role. Agree the standard in advance, or the work expands.
Mitigation: the anxiety is a feature of the role and does not need curing, but it does need a defined finish line. Delegation is genuinely hard here; start with the parts where an error is recoverable.
Working with them: define “finished” explicitly. Do not change scope late. Recognise the finishing work, it is chronically under-credited relative to starting.
Communicator
Focuses on the team’s objectives, draws out team members, and delegates work appropriately. Perceived as mature and confident. Good at identifying talent and clarifying goals.
Allowable weakness: can be seen as manipulative; might offload their share of the work.
What the team gets: clarity of objective and the right people on the right parts. This is a leadership role in function regardless of formal title, the person who makes sure the group knows what it is doing and who is doing what.
How to apply it: take the chairing, the goal-setting, the allocation. Draw out the quiet members deliberately; this is the specific contribution nobody else makes. Be explicit about delegation reasoning, since unstated allocation is what reads as manipulation.
Mitigation: the “offloads their own work” perception is best pre-empted by holding a visible piece of delivery yourself. Say why you allocated something the way you did.
Working with them: let them chair. Give them the team’s objective to own. Do not confuse their coordination for a lack of individual contribution.
People Oriented
Administrator
Provides the drive to ensure the team keeps moving and does not lose focus or momentum. Perceived as challenging and dynamic; thrives on pressure. Has the drive and courage to overcome obstacles.
Allowable weakness: prone to provocation; may offend people’s feelings; risks becoming aggressive and frustrated in attempts to get things done.
What the team gets: forward pressure. This is the role that prevents comfortable drift, and it is the one most likely to be resented while it is working.
How to apply it: take the stalled project, the team that has lost momentum, the deadline nobody believes in. Direct the pressure at the obstacle rather than the person, the distinction is invisible from the inside and highly visible from outside.
Mitigation: assume your impact is greater than intended. The role requires provocation to function; what it does not require is provocation aimed at individuals.
Working with them: give them something to push against. Push back directly, they respect it. Do not put two of them in the same team without a defined split.
Coordinator
Plans a workable strategy and carries it out as efficiently as possible. Practical, reliable and efficient. Turns ideas into actions and organises the work that needs doing.
Allowable weakness: somewhat inflexible; slow to respond to new possibilities; slow to relinquish plans in favour of positive change.
What the team gets: the conversion of intention into an executable plan. Without this role, good ideas stay ideas and the team confuses agreement with progress.
How to apply it: take the planning and the operational structure. Be the person who turns the workshop output into a sequence with owners and dates. Build a review point into your own plan so the inflexibility has a scheduled release valve.
Mitigation: the resistance to change is the cost of the reliability. Distinguish explicitly between a change that improves the outcome and one that is merely new.
Working with them: give them the plan to own. Bring changes with reasoning attached. Do not spring reprioritisation on them without notice.
Contact Creator
Helps the team together, using versatility to identify the work required and complete it on behalf of the team. Perceived as co-operative, perceptive and diplomatic. Listens and averts friction.
Allowable weakness: indecisive in crunch situations; avoids confrontation; hesitant to make unpopular decisions.
What the team gets: cohesion, and the invisible work that holds a group together. This role’s contribution is almost impossible to see and immediately obvious when it is absent.
How to apply it: take the connective work deliberately and make it visible, it is real and it is systematically under-credited. Use the trust for the difficult conversations others cannot have.
Mitigation: the avoidance of confrontation is the allowable weakness, not a fault to be fixed, but it means this role should not hold the decision in a crunch. Pair with an Administrator or Communicator for that.
Working with them: notice the work. Do not put them in the position of making the unpopular call alone. Ask what they are picking up.
Thinking Oriented
Analyser
Provides a logical eye, making impartial judgments and weighing the team’s options dispassionately. Perceived as strategic and discerning. Great at seeing all the options and judging them accurately.
Allowable weakness: may lack the drive to inspire others; can be overly critical; slow to come to decisions.
What the team gets: decision quality. This is the role that prevents the team from confidently choosing the wrong option, and its value is almost entirely in mistakes that did not happen.
How to apply it: take the evaluation, the options paper, the pre-mortem. Ask formally for the challenger role. Present the options with the reasoning rather than the verdict alone, the impartiality is the contribution, and it needs to be shown to be trusted.
Mitigation: slowness is inherent; set the decision date externally. The critical perception is reduced substantially by naming what is sound before naming what is not.
Working with them: give them the options and the time. Do not ask for a view in the room without notice. Set the decision deadline explicitly.
Creative
Highly creative and good at solving problems in unconventional ways. Perceived as creative, imaginative and free-thinking. Good at generating ideas and solving difficult problems.
Allowable weakness: might ignore incidentals; may be too preoccupied to communicate effectively; can be absent-minded or forgetful.
What the team gets: the option nobody else would have produced, and a route through problems that resisted ordinary effort.
How to apply it: take the hard, undefined problem rather than the volume of work. Bring ideas back to the team in a form others can use, the translation is where the value is realised. Capture ideas in a system, since they arrive faster than they can be applied.
Mitigation: the poor communication is the allowable weakness, the mitigation is a Communicator or Coordinator alongside, not an instruction to be more organised.
Working with them: give them the problem, not the process. Do not rely on them for the incidentals. Have someone else carry the idea into execution.
Specialist
Brings in-depth knowledge of a critical area. Perceived as single-minded, self-starting and dedicated. Provides specialist knowledge and skills.
Allowable weakness: contributes on a narrow front; dwells on technicalities; may overload others with information.
What the team gets: genuine depth in one thing that matters. This role is the reason the team can do something its competitors cannot.
How to apply it: own the domain and keep it current. Calibrate the depth of your contribution to the audience, the overload is real and it costs you influence. Connect the expertise to the commercial outcome explicitly.
Mitigation: narrowness is inherent to the role and is the point of it. What needs managing is the interface: a two-sentence version of every explanation, with the detail available on request.
Working with them: ask about the subject substantively, it is the primary retention lever for this role. Ask for the short version first. Protect their immersion time.
Using the dimension for team composition
A simple three-step method:
- Map the team. Each person’s top three roles, plotted against the nine.
- Find the gaps. Any role nobody covers is a predicted failure mode, not a preference. Name it out loud.
- Find the duplicates. Three people covering the same role will conflict over it, particularly with Administrator and Communicator.
The most common patterns and what they produce:
| Pattern | Result |
|---|---|
| No Closer | Ships late, ships rough, quality reaches the customer as complaints |
| No Analyser | Confident bad decisions, discovered by implementing them |
| No Contact Creator | Friction accumulates until someone leaves |
| No Creative | Solves this year’s problem with last year’s method |
| Multiple Administrators | Standing conflict about who is in charge |
| All Thinking Oriented | Excellent analysis, nothing delivered |
| All Action Oriented | Enormous activity, avoidable mistakes |
A note on hiring: the strongest individual candidate is frequently the wrong hire, because they duplicate a role the team already has three of. Running this dimension before the interview changes what you are looking for.
Summary
- Lead with the three-role ceiling. It reframes the whole dimension: the question is not which roles someone could play, but which three they actually cover.
- Give equal weight to the absent roles. For team composition, what someone does not cover is the more actionable half.
- Present the allowable weaknesses as inherent, not correctable. They come packaged with the strength; the team’s job is to cover them, not to coach them away.
- Use it in aggregate. One profile is interesting; a team map is a diagnosis.
- Cross-read with Work Behaviour. The two dimensions describe the same underlying reality in different vocabularies, and inconsistency between them is worth examining.