Belbin Team Roles: The 9 Roles and How to Use Them

Belbin team roles are nine clusters of behavior that people show at work: Plant, Resource Investigator, Co-ordinator, Shaper, Monitor Evaluator, Teamworker, Implementer, Completer Finisher, and Specialist. Dr. Meredith Belbin argued that effective teams need all nine covered, and that each role comes with a predictable "allowable weakness."

Most people know their job title. Fewer can say how they actually behave when a team is stuck, rushed, or arguing. That gap is what this model tries to close. It gives you a shared vocabulary for the way people contribute, so you can stop asking "why isn't Sam more like me?" and start asking "what is this team missing?"

What are Belbin team roles?

A team role, in Belbin's terms, is a tendency to behave, contribute, and interact with others in a particular way. It isn't a job function and it isn't a fixed personality type. Belbin's own site says its assessment "measures behaviour rather than personality," and that distinction matters. Behavior shifts with the situation. A person who is a quiet Monitor Evaluator in a budget review might turn into a loud Shaper when a deadline slips.

The roles fall into three groups:

• Social roles (Resource Investigator, Teamworker, Co-ordinator): they keep people connected and pointed at the same goal.
• Thinking roles (Plant, Monitor Evaluator, Specialist): they generate ideas, test them, and supply deep knowledge.
• Action roles (Shaper, Implementer, Completer Finisher): they push work forward, turn plans into output, and catch errors.

Each role has strengths and what Belbin calls allowable weaknesses. The idea is that a weakness comes bundled with the strength. You can't have the Plant's creativity without some carelessness about details. So the goal isn't to remove the weakness. It's to make sure someone else on the team covers it.

Key Facts

Key Facts

• Meredith Belbin and his team observed international management teams at Henley Management College over roughly nine years in the 1970s, according to Belbin's own history page.
• The model first appeared in Belbin's book Management Teams: Why They Succeed or Fail (1981) with eight roles. The ninth role, Specialist, emerged only after the initial research was done, when Belbin began applying the work in industry.
• A review of 43 empirical studies by Aritzeta, Swailes and Senior (2007) in the Journal of Management Studies found the model and inventory have adequate convergent validity but weak discriminant validity among some scales.
• A multitrait-multimethod study of 1,434 participants by van Dierendonck and Groen (2011) found good discriminant and convergent validity for a revised measure, with observer ratings from at least four raters per person.
• Belbin reports reliability scores of 0.67 to 0.84 across the nine roles, with Specialist the lowest.

Where Belbin team roles came from

In the 1970s, Belbin and his research team at Henley Management College set out to observe teams. According to Belbin's history page, participants took a battery of psychometric tests, and the team watched how personality and behavior affected how groups performed on a management exercise. Over about nine years, a pattern emerged: successful teams weren't the ones stacked with the highest scores. They were the ones with a useful spread of behaviors.

The first published account came in 1981 in Management Teams: Why They Succeed or Fail. That edition described eight roles. The Specialist role was added later, after Belbin began working with real organizations and saw that deep knowledge of a key area was a distinct and essential contribution.

The 9 Belbin team roles explained

The descriptions below follow the strengths and allowable weaknesses published on Belbin's site. The "what to watch for" notes are practical interpretation, not Belbin's wording.

Social roles

Resource Investigator. Outgoing and enthusiastic. They explore opportunities and develop contacts, bringing outside ideas back to the team. Allowable weaknesses: over-optimism, and losing interest once the initial excitement fades. Watch for: great kickoffs, weak follow-through.

Teamworker. Co-operative, perceptive, and diplomatic. They listen and avert friction, and they hold the group together with versatility. Allowable weaknesses: indecision under pressure and avoiding confrontation. Watch for: a team that feels pleasant but never has the hard conversation.

Co-ordinator. Mature and confident, they identify talent and clarify goals. They focus the team on objectives, draw out contributions, and delegate. Allowable weaknesses: can come across as manipulative, and may over-delegate. Watch for: a chair who hands off their own share of the work.

Thinking roles

Plant. Creative, imaginative, and free-thinking. They generate ideas and solve difficult problems through unconventional thinking. Allowable weaknesses: overlooking details and difficulty communicating ideas. Watch for: brilliant concepts that nobody else understands yet.

Monitor Evaluator. Sober, strategic, and discerning. They see all the options and judge accurately, weighing choices dispassionately. Allowable weaknesses: lack of inspirational drive, being overly critical, and slow decisions. Watch for: a team that never commits because the evaluator is still weighing options.

Specialist. Single-minded, self-starting, and dedicated. They provide specialist knowledge and skills. Allowable weaknesses: a narrow focus, and dwelling on technical detail. Watch for: expert opinions that don't connect to the team's actual goal.

Action roles

Shaper. Challenging and dynamic, they thrive on pressure and have the drive to overcome obstacles. They keep momentum and focus. Allowable weaknesses: prone to provocation, and may offend others. Watch for: speed gained at the cost of trust.

Implementer. Practical, reliable, and efficient. They turn ideas into actions and organize the work that needs doing. Allowable weaknesses: inflexibility, and slowness to embrace new possibilities. Watch for: resistance to a new method simply because the old one works.

Completer Finisher. Painstaking and conscientious. They search out errors and polish the result to a high standard. Allowable weaknesses: excessive worry and reluctance to delegate. Watch for: a deliverable that's perfect but late.

Belbin team roles vs. other team and personality frameworks

People often lump Belbin in with personality tests. It's closer to a team-composition tool. The table compares it with frameworks you'll meet in the same conversations.

The practical takeaway: these tools answer different questions, so they stack well. Tuckman tells you the phase, Belbin tells you who's contributing what, and RACI tells you who owns each deliverable. Using one in place of the others is where teams get into trouble.

What the research says (and where it's criticized)

Belbin's model is popular, and it's also been criticized. A fair reading needs both.

On the supportive side, Aritzeta, Swailes and Senior (2007) reviewed 43 empirical studies and concluded that the model and its inventory have adequate convergent validity. In plain terms, scores that should relate to each other do. They also found weak discriminant validity among some scales, meaning some roles overlap in what they measure, and the evidence linking roles to other cognitive or behavioral traits was mixed. And van Dierendonck and Groen (2011), working with 1,434 participants and observer ratings, reported satisfactory interrater agreement and good discriminant and convergent validity for a revised instrument.

On the critical side, academic critics have long questioned the old self-scored questionnaire. Belbin's own response, on its reliability page, is that some of those studies examined "the old, self-scoring version of the inventory" that isn't used for its current individual reports. Whether you find that persuasive or not, the sensible conclusion is the same one the reviewers reach: the framework is a useful vocabulary for conversation, not a precise measuring instrument.

So how should you hold it? Treat a Belbin result as a starting hypothesis. Check it against what you've seen the person do. And never use it for hiring or firing decisions on its own.

How to use Belbin team roles: a step-by-step process

Here's a process that works for an existing team of four to ten people.

Step 1: Set the purpose. Tell the team why you're doing this. "We're mapping how we contribute so we can fill gaps" lands very differently from "we're sorting you into types." Say explicitly that nobody's role is a verdict.

Step 2: Gather data from more than one angle. Have each person list the two or three roles they believe they play. Then ask two or three colleagues to name the roles they see. A self-view alone is the weakest source. If you use a formal assessment, treat its output as one input, not the answer.

Step 3: Build the team map. Put everyone's top roles (and a couple of secondary ones) into a single table. The template in the next section is ready to copy.

Step 4: Look for gaps and clusters. Which roles have nobody? Which have three people? A team with four Shapers and no Teamworker will struggle in a different way than a team with no Completer Finisher. Note that Belbin's own guidance says the range of useful behaviors is finite, so you're looking for a manageable list of gaps, not an endless one.

Step 5: Cover the gaps on purpose. You have four options: ask someone to stretch into a secondary role for a defined period, share the role between two people, bring in someone with that strength, or build a process that compensates (a mandatory review gate stands in for a missing Completer Finisher, for example).

Step 6: Make the weaknesses discussable. Agree on how the team will respond when an allowable weakness shows up. If the Shaper snaps in a meeting, what's the signal? If the Plant sends a vague idea, who translates it?

Step 7: Revisit at each team change. Roles are behavior in context. When the project changes, or someone joins or leaves, rerun the map. It takes twenty minutes once you've done it the first time.

Ready-to-copy team role map template

Copy this table into a doc or spreadsheet. Put a "P" for a primary role and an "S" for a secondary role.

And here's a second table for the gap plan once the map is filled in.

Belbin team roles by business function

The roles don't map to job titles, but certain functions tend to lean on certain contributions. These are illustrative scenarios, not data about real companies.

Take the sales row as an example. Imagine a hypothetical five-person sales team of three Resource Investigators, a Shaper, and a Co-ordinator. Pipeline creation is strong. But nobody naturally owns the unglamorous work of keeping records accurate and proposals error-free. The fix isn't to replace anyone. It's to name an owner for that work and add a checklist.

Do's and don'ts

Common mistakes with Belbin team roles

Assuming everyone needs every role. No. Belbin's point is that the team collectively covers the nine, not that each person is well-rounded. Most people have two or three strong roles, some they can stretch into, and some they should avoid.

Treating "allowable weakness" as permission. The phrase means a weakness comes with the strength, not that it's free of cost. If a Shaper regularly leaves colleagues bruised, the team needs a way to handle that. That requires psychological safety, which is a precondition for honest conversations about weaknesses.

Over-indexing on the quiz result. The research itself shows overlap between some scales. Use observation to confirm.

Ignoring the leader's own role. A leader with strong Shaper and Co-ordinator tendencies can crowd out Teamworkers and Plants without noticing. Understanding your own pattern is partly an emotional intelligence skill.

Forcing a perfect nine on a tiny team. A three-person team can't have nine primary role-holders. Each person will cover several roles, and some gaps will stay open. Choose the gaps that carry the most risk and cover those.

How Belbin team roles connect to other leadership ideas

Belbin's model works best when you pair it with ideas about how authority and influence are shared. In a team that practices shared leadership or distributed leadership, different people take the lead as the task changes. That's essentially what Belbin describes: the Plant leads at the ideation stage, the Implementer at planning, the Completer Finisher at quality control. The model gives that rotating leadership a vocabulary.

It also helps with one-to-one dynamics. Leaders who read leader-member exchange theory know that managers form different quality relationships with different people. Knowing someone's likely role can help you notice when you're consistently overlooking a Plant or a Monitor Evaluator because their style differs from yours.