Org, people & execution
Belbin Team Roles
A vocabulary of nine behavioural roles that people tend to adopt in teams, grouped into thinking, action and people clusters, used as a checklist for whether a team's composition actually covers the work in front of it and where the gaps and duplications lie.
Also known as Belbin's nine team roles, Team Role theory, BTRSPI (the associated inventory). First set out by R. Meredith Belbin in 1981; the primary source is cited in full below.
- Format
- Checklist / audit
- Level
- Team
- Best for
- Allocate resources · Plan execution
- Decision stage
- Diagnose · Plan
- Difficulty
- Introductory
- Time to apply
- An afternoon to map a team informally against the nine roles; two to three weeks if running the full inventory with observer assessments.
Plate · The model
The components
Plant
Thinking role. The creative source: imaginative, unorthodox, generates ideas and solves difficult problems, often from a slight distance from the group. Allowable weaknesses: ignores incidentals, too preoccupied to communicate effectively.
Signals of strength
Original proposals nobody else would have produced · Strongest contribution early and when stuck · Prickly about criticism of their ideas · Loses interest once the idea is accepted
Monitor Evaluator
Thinking role. The team's judgement: sober, strategic and discerning, weighs all options and rarely gets it wrong. Allowable weaknesses: lacks drive and the ability to inspire, can be needlessly critical.
Signals of strength
Speaks late in the discussion and changes its direction · Punctures enthusiasms with inconvenient facts · Slow, deliberate decision style · Rarely the source of energy or ideas
Specialist
Thinking role, and the ninth, added after the original eight when Belbin's work moved from the Henley exercises into real organisations where deep technical knowledge proved decisive. Single-minded, self-starting, supplies knowledge and skills in rare supply. Allowable weaknesses: contributes on a narrow front, dwells on technicalities.
Signals of strength
The person the team cannot proceed without on their subject · Defends professional standards fiercely · Limited interest in matters outside their field · Depth prized over breadth
Shaper
Action role. The driving force: challenging, dynamic, thrives on pressure and has the drive and courage to overcome obstacles. Allowable weaknesses: prone to provocation, liable to offend people's feelings.
Signals of strength
Injects urgency and hates drift · Argues to win and recovers quickly · Pushes the team past comfortable consensus · Leaves bruises under pressure
Implementer
Action role, originally labelled Company Worker in the 1981 book. Turns decisions into organised, practical action: disciplined, reliable and efficient. Allowable weaknesses: somewhat inflexible, slow to respond to new possibilities.
Signals of strength
Converts vague intentions into schedules and systems · Does what needs doing, liked or otherwise · Discomfort with frequent changes of plan · The team's work actually gets organised around them
Completer Finisher
Action role. The quality conscience: painstaking, conscientious, searches out errors and omissions, polishes and delivers on time. Allowable weaknesses: inclined to worry unduly, reluctant to delegate.
Signals of strength
Finds the mistake everyone else missed · Chases deadlines and loose ends unprompted · Anxiety rises as delivery approaches · Would rather do it themselves than trust it out
Coordinator
People role, originally labelled Chairman. The mature focal point: confident, clarifies goals, draws out contributions and delegates well, without needing to be the cleverest in the room. Allowable weaknesses: can be seen as manipulative, may offload their own share of the work.
Signals of strength
Meetings run through them and end with decisions · Spots what each member is good at and uses it · Calm under disagreement · Delegation occasionally shades into offloading
Teamworker
People role. The social glue: cooperative, perceptive and diplomatic, listens, averts friction and keeps the team working. Allowable weaknesses: indecisive in crunch situations, avoids confrontation.
Signals of strength
Tension drops when they are in the room · Notices who is struggling before anyone else · Fills gaps without being asked · Goes quiet when a hard call is needed
Resource Investigator
People role. The team's outside line: outgoing, enthusiastic, explores opportunities and develops contacts beyond the team's boundary. Allowable weaknesses: over-optimistic, loses interest once the initial enthusiasm has passed.
Signals of strength
Knows someone who can help with almost anything · Brings back intelligence the team would never have found · First excitement rarely survives to follow-through · Energy depends on external stimulation
When it earns its keep
- You are assembling a new team and want to check the mix of behavioural contributions, alongside the technical skills, before the composition sets hard.
- An existing team of able individuals keeps failing in a recognisable way, all ideas and no follow-through, or all execution and no scrutiny, and you want to name the missing contribution.
- Two members clash repeatedly and you suspect duplicated roles, two Shapers or two Plants, rather than a personality problem.
- You are distributing responsibilities within a team and want them to land with people whose natural contributions fit.
And when it doesn't
- For selection, promotion or any high-stakes judgement about individuals. The inventory's psychometric standing does not support it, and Belbin himself positioned the instrument as a development aid.
- When the team's problem is trust, conflict or commitment. Role balance says nothing about dysfunction; Lencioni's model or direct facilitation addresses that layer.
- When the team barely needs to be a team. Role theory assumes genuinely interdependent work; for a group of individual contributors, composition analysis is decoration.
- As a box to put people in. Belbin's own position is that most people carry two or three preferred roles and can flex; treating a role as a fixed identity misuses the model.
How to run it
Before starting, gather the inputs the analysis depends on:
- A clear statement of the team's task, since roles only matter relative to the work: a regulatory submission needs Completer Finishers in a way a blue-sky sprint does not.
- Role-preference data for each member, ideally the Belbin Self-Perception Inventory combined with observer assessments, which correct the known weakness of self-report alone.
- The team's recent track record: where work flows and where it repeatedly stalls, as a check on what the questionnaires claim.
- Willingness to act on the findings, whether by changing composition, borrowing a contribution from outside, or consciously assigning an unloved role to someone who can hold it.
- 1
Define the task and the contributions it needs
Before profiling anyone, ask which roles this piece of work will actually stress. A launch under deadline pressure leans on Shaper, Implementer and Completer Finisher; an ambiguous exploration leans on Plant, Resource Investigator and Monitor Evaluator.
- 2
Profile the members
Run the self-perception inventory and, wherever possible, add observer assessments from colleagues. Record each person's two or three strongest roles and their lowest, since the least-preferred roles predict what the team will quietly neglect.
- 3
Map the team against the nine roles
Lay the nine roles out as a checklist and mark who genuinely covers each, meaning it appears among their preferred roles, and who merely could at a stretch. Honesty here is the whole exercise.
- 4
Identify gaps and pile-ups
A role nobody holds is a gap the task will find; a role three people hold is a collision waiting for a trigger. Belbin's research at Henley found teams of similar, individually brilliant people (his 'Apollo' teams) performed poorly for exactly this reason.
- 5
Decide how to cover what is missing
Options in rough order of cost: assign the role explicitly to the nearest capable member, borrow the contribution from outside the team, or change the composition. Naming the gap out loud is itself worth much of the value.
- 6
Revisit as the work changes
Role demands shift across a project's life: exploration early, delivery in the middle, scrutiny and finishing at the end. Re-run the checklist at phase boundaries rather than treating the first map as permanent.
Reading the result
A checklist map of the team against the nine roles: who genuinely covers each contribution, which roles are missing, which are duplicated, and a plan for covering the gaps that the task will expose.
- Read the map against the task, never in the abstract. A team with no Plant is fine executing a defined build and in trouble on an open problem.
- Gaps predict failure modes with useful specificity: no Monitor Evaluator and bad options survive scrutiny; no Completer Finisher and the work ships at ninety per cent; no Resource Investigator and the team turns inward.
- Duplications predict friction: two Shapers fight for the wheel, two Plants compete for airtime. The remedy is usually explicit division of territory rather than removal.
- Treat individual profiles as tendencies with error bars, especially where self-perception and observer views disagree. That disagreement is itself worth discussing.
A worked example
A paint manufacturer's new-product team maps its roles before a critical launch
A UK trade and decorative paint manufacturer has formed a seven-person team to develop and launch a low-VOC exterior masonry paint within eighteen months, its answer to tightening solvent regulations and a rival's early move. The team is three formulation chemists, a production engineer, a marketing manager, a category buyer's liaison from sales, and a project lead promoted from the lab. Six months in, the formulation is ahead of schedule and everything else is behind. The project lead runs a Belbin mapping with observer assessments.
- Plant
- Covered. The senior chemist profiles strongly as Plant and it shows: the novel binder approach is hers. Observer scores confirm it, along with the allowable weakness; she has stopped attending the commercial workstream meetings entirely.
- Monitor Evaluator
- Partially covered. The production engineer carries it as a second role, but he applies it only to manufacturability. Nobody is scrutinising the commercial case, which still assumes a launch price the buyer's liaison privately doubts.
- Specialist
- Over-covered. All three chemists profile as Specialists. The depth is a genuine asset for the regulatory dossier, and it explains the team's centre of gravity: technical questions get answered in hours, commercial ones drift for weeks.
- Shaper
- Gap. No member profiles as Shaper, and the observer data agrees. The project has no source of urgency; deadlines slide by consent and nobody forces the priority argument with the factory. This is the map's most dangerous hole given a competitor already moving.
- Implementer
- Covered. The production engineer's first role. Scale-up trials, line time and filling schedules are the one non-lab area that runs to plan, which is consistent with the profile.
- Completer Finisher
- Gap, mostly. The junior chemist shows moderate strength but applies it only to lab records. The launch checklist, artwork approvals and datasheets have no owner with finishing instincts, an ominous sign for a regulated product launch.
- Coordinator
- Weakly covered. The project lead's own profile is Specialist first, Coordinator a distant third, and the observer scores are blunter than his self-perception. Meetings are technical seminars; goals and delegation are fuzzy. His least-preferred roles, Shaper and Resource Investigator, are precisely the team's other gaps.
- Teamworker
- Covered. The marketing manager holds the team together socially across the lab-commercial divide, confirmed by every observer. Her allowable weakness is visible too: she has smoothed over the pricing disagreement three times rather than let it surface.
- Resource Investigator
- Gap by neglect. The buyer's liaison profiles as Resource Investigator, but he attends one meeting in three and nobody has given him a defined brief. The contribution exists and is unused: merchant reaction, competitor intelligence and trade-body contacts are all a phone call away.
The read. The map explains the six-month pattern precisely: a Specialist-heavy, Shaper-less team led by another Specialist will produce excellent chemistry and a drifting launch. The responses are cheap. The commercial director agrees to chair a monthly challenge session, importing the missing Shaper and Monitor Evaluator pressure from outside. The buyer's liaison gets an explicit Resource Investigator brief and a seat at every meeting. The junior chemist takes ownership of the launch checklist, a deliberate assignment of the Completer Finisher role. The composition barely changes; the coverage does.
Pitfalls
- Using role labels as personality verdicts. The model describes behavioural contributions in a team context, and most people can hold more than one role; 'she is a Plant' said as identity closes down the flexibility the model depends on.
- Relying on the self-perception inventory alone. Self-report and observer assessments frequently disagree, and the observer data is generally the more useful; Belbin's own practice adds observer input for this reason.
- Mapping roles without reference to the task. There is no universally balanced team, only teams balanced for particular work.
- Hiring or restructuring on the strength of the profiles. The instrument was built as a development and discussion aid, and its measurement properties will not carry selection decisions.
- Forgetting that coverage can be conscious. A missing role does not always mean a missing person; a capable member can deliberately hold an unloved role once it is named.
What the critics say
The first independent psychometric assessment of the Team-Role Self-Perception Inventory found low internal reliability, and factor analyses that failed to recover Belbin's roles as distinct constructs, concluding the instrument fell short of conventional psychometric standards. Belbin's published reply argued the inventory was a practical aid never designed for such testing, an exchange that itself illustrates the gap between the model's popularity and its evidence.
Furnham, A., Steele, H. and Pendleton, D. (1993) 'A psychometric assessment of the Belbin Team-Role Self-Perception Inventory', Journal of Occupational and Organizational Psychology, 66(3), pp. 245–257; with Belbin's reply and Furnham's response in the same volume.
A later comprehensive review of 43 empirical studies found conflicting evidence across the literature: adequate convergent validity for the model overall, but mixed support for the discriminability of the nine roles, several of which overlap substantially with each other and with Big Five personality dimensions.
Aritzeta, A., Swailes, S. and Senior, B. (2007) 'Belbin's Team Role Model: Development, Validity and Applications for Team Building', Journal of Management Studies, 44(1), pp. 96–118.
The model's central practical claim, that role-balanced teams outperform unbalanced ones, has weaker direct support than the role taxonomy itself. Studies testing the balance hypothesis report mixed results, and the original Henley evidence came from management-game exercises whose generalisation to real organisational teams is uncertain.
Reviewed in Aritzeta, Swailes and Senior (2007), Journal of Management Studies, 44(1).
Sources and further reading
- Belbin, R. M. (1981) Management Teams: Why They Succeed or Fail. London: Heinemann.
- Belbin, R. M. (1993) Team Roles at Work. Oxford: Butterworth-Heinemann.
- Belbin, 'The Nine Belbin Team Roles', belbin.com. ↗
- Furnham, A., Steele, H. and Pendleton, D. (1993) 'A psychometric assessment of the Belbin Team-Role Self-Perception Inventory', Journal of Occupational and Organizational Psychology, 66(3), pp. 245–257. ↗
- Aritzeta, A., Swailes, S. and Senior, B. (2007) 'Belbin's Team Role Model: Development, Validity and Applications for Team Building', Journal of Management Studies, 44(1), pp. 96–118. ↗