Belbin team roles: the 9 types and how to assign roles in a team
Belbin Team Roles
6 November 2026
updated at: 6 November 2026
Key takeaways
core idea: nobody is perfect, but a team can be. Success depends not only on professional expertise (hard skills) but also on how people behave in a group (team roles);
an important nuance: a team does not need nine people. One strong employee typically covers 2–3 roles comfortably (for example, Monitor Evaluator and Completer Finisher);
how to apply it: do not hunt for the perfect nine. The key is to identify blind spots. For example, if your team consists only of Plants and Shapers, the project will burn out without Implementers and Completer Finishers. Use assessments and record roles in each employee's profile in your HR system.
Imagine you have hired a team of five brilliant senior developers. Each is a star and a source of ideas. Sounds like a dream team? In practice, such a group will most likely fail the project. They will design a perfect architecture and write a brilliant strategy, but no one will close a single ticket on time, because everyone will be busy proving their approach is best and no one will do the groundwork.
A project's success depends not only on the expertise (hard skills) of its members but also on the balance of their behaviors. To win, you need not just strategists but also people who will dig in, smooth over conflicts and see the work through to a polished finish.
British researcher Raymond Meredith Belbin spent nine years studying why some teams take off while others crash and burn. His key insight changed how HR thinks about teams: team effectiveness depends on getting the balance of roles right.
Today, Belbin's team role theory is a practical tool used by talent management experts and leaders of major technology companies to build balanced teams.
Drawing on hands-on experience of implementing HR practices, this article explains which Belbin team roles exist, how they interact and how to apply the framework so your team runs like clockwork.
The Belbin model: the core of the theory
The Belbin model holds that a team role is a person's consistent tendency to behave, contribute and interact with colleagues in a particular way.
It is important to understand the basic distinction:
a functional role is WHAT you do (for example, backend developer, accountant, marketer);
a team role is HOW you do it. The same developer may be a Plant (constantly proposing refactoring) or an Implementer (quietly writing code to spec and on time).
Belbin identified nine such roles. If all nine are represented in a group (even if not by nine different people), the team is viable.
3 groups of roles: action, people and thinking
For convenience, the Belbin classification divides the nine roles into three groups:
Thinking roles: generating new ideas, analyzing data, providing expertise. The team's brain.
People roles: team climate, external connections, coordination. The glue that holds people together.
Action roles: turning ideas into steps, meeting deadlines, ensuring quality. The project's engine.
Why one person can have 2–3 dominant roles
The secret is that you do not need to hire exactly nine people. The Belbin team role model recognizes that one strong employee usually combines two or three roles.
Each of us has:
natural (preferred) roles: behavior patterns that come easily and that we enjoy;
manageable roles: roles we can take on when a crisis demands it, though they drain a lot of energy;
least preferred roles: functions where we will be least effective (and that is fine).
Belbin team roles: who is who and how to recognize them
Let us look at each role through its strengths, allowable weaknesses and compatibility with other roles.
Thinking roles
1. Plant
strengths: creative, original, inventive. Sees unconventional solutions where others have hit a dead end. Proposes radically new approaches;
risks (allowable weaknesses): may have their head in the clouds and ignore practical details and deadlines. Often sensitive to criticism of their ideas;
when the role helps: at the start of a project or when the team is stuck and needs a way out;
works best with: the Monitor Evaluator (who assesses the idea) and the Implementer (who turns it into a task).
2. Monitor Evaluator
strengths: the team's level head. Can assess any idea critically and without emotion. Carefully weighs the pros and cons and spots risks;
risks (allowable weaknesses): may come across as dull, skeptical and unenthusiastic. Over-analysis can slow decision-making;
when the role helps: when making key strategic decisions and assessing risks;
works best with: the Plant (grounds their ideas) and the Shaper (channels their energy).
3. Specialist
strengths: has rare knowledge and skills in a narrow field. Takes pride in their expertise and gives the team a solid technical or subject-matter foundation;
risks (allowable weaknesses): tends to focus on the details of their own specialism and lose sight of the bigger picture. May overload colleagues with jargon;
when the role helps: when a project needs deep, specific expertise;
works best with: the Coordinator (who integrates their knowledge into the wider work) and the Implementer.
People roles
4. Teamworker
strengths: empathetic, diplomatic, a good listener. Prevents conflicts, maintains morale and keeps employee engagement high;
risks (allowable weaknesses): indecisive in a crisis. Struggles to make tough decisions that might upset someone;
when the role helps: in tense situations, during change and when onboarding new employees;
works best with: gets on well with everyone, especially the Shaper (softens their abrasiveness).
5. Resource Investigator
strengths: a sociable extrovert. Looks for new opportunities outside the team, builds useful connections easily, brings in ideas from the market and negotiates with suppliers;
risks (allowable weaknesses): quickly loses interest once the initial enthusiasm fades. May forget details and fail to follow up;
when the role helps: when the team needs new customers, investment, technology or contacts;
works best with: the Implementer (who picks up their contacts) and the Coordinator.
6. Coordinator
strengths: a mature, confident leader (often an informal one). Understands each person's talents and delegates tasks well. Organizes the process without trying to dominate;
risks (allowable weaknesses): can be seen as manipulative. Tends to delegate the lion's share of the work, keeping only the role of conductor;
when the role helps: throughout the project, to keep the pace and focus on goals;
works best with: works well with everyone, balancing ideas, analysis and action.
Action roles
7. Shaper
strengths: dynamic, driven, results-oriented. Challenges the status quo, overcomes obstacles and keeps the team from getting complacent. An excellent crisis manager;
risks (allowable weaknesses): prone to provocation, can be aggressive and impatient. May hurt colleagues' feelings and disrupt a comfortable team climate;
when the role helps: when deadlines are looming, the team is stuck or you need to break through bureaucratic barriers;
works best with: the Monitor Evaluator (who cools their ardor) and the Teamworker (who smooths over conflicts in their wake).
8. Implementer
strengths: disciplined, reliable, conservative. Turns abstract ideas and strategies into concrete plans and executes them step by step;
risks (allowable weaknesses): inflexible and slow to accept sudden changes of plan. Needs clear instructions;
when the role helps: every day, for the steady delivery of routine and operational tasks;
works best with: the Plant (makes their ideas real) and the Coordinator.
9. Completer Finisher
strengths: painstaking, conscientious, a perfectionist. Searches for errors, checks quality and makes sure everything is done flawlessly and strictly on time;
risks (allowable weaknesses): inclined to worry unduly about small things. Reluctant to delegate, not trusting others to do as good a job;
when the role helps: in the final stages of a project, before a release or handover to the customer;
works best with: the Resource Investigator and the Shaper (tidies up their loose ends and unfinished work).
How the Belbin model works: a visual overview and role matrix template
Knowing the theory is not enough; you need to apply it to your own situation. Map your current team.
Role matrix template
Create a simple table with team members in the rows and the nine roles in the columns. Mark each person's primary (for example, P) and secondary (for example, S) roles, identified through an assessment.
Role
Ian (Team lead)
Anna (QA)
Sam (Dev)
Ellen (UX/UI)
Peter (PM)
Plant
S
P
Monitor Evaluator
P
P
Specialist
P
Teamworker
S
P
Resource Investigator
P
S
Coordinator
S
P
Shaper
P
Implementer
S
P
Completer Finisher
P
S
Example insights from the matrix
Looking at this table, a manager immediately sees the blind spots:
strength: the team is good at generating ideas and implementing them methodically (Ellen as Plant and Sam as Implementer);
conflict risk: Ian (Shaper) may push Ellen (Plant) too hard for the sake of speed, but Peter (Teamworker/Coordinator) can defuse the situation;
gap: only Anna acts as Completer Finisher. If she goes on leave before a release, product quality will suffer badly. Solution: temporarily reassign quality control tasks to Sam (it is his secondary role).
How to assign roles in a team using Belbin
Building a balanced team is an analytical process that requires not only a leader's intuition but also objective HR metrics.
Diagnosis. Run an assessment (the Belbin questionnaire). A 360-degree assessment works best: the person rates themselves and colleagues rate them too.
Mapping to the task. Different projects have different needs. A startup at the MVP stage needs Plants and Resource Investigators. A mature enterprise maintaining legacy systems critically depends on Implementers and Completer Finishers.
Deliberate assignment. If you know an employee is a strong Monitor Evaluator, do not ask them to give inspiring investor pitches. Give them the task of working out the unit economics.
Covering weak spots. If the team has no Teamworker and conflicts start, the manager (if they are a Coordinator) will have to take on that role until the issue is resolved.
5 common mistakes when using Belbin's theory
Labeling people. A role is not a life sentence. Being a Plant does not mean someone cannot be given routine work.
Hunting for the perfect nine. Do not look for nine different types in a five-person team. The key is to cover the critical functions (ideas, action, control).
Ignoring hard skills. However good a Coordinator someone is, if they do not know Python, they cannot lead a team of backend developers. Roles do not replace professional expertise.
One-off assessment. Teams change and people grow. Reassess (with pulse surveys) at least once a year.
Ignoring the team context. Put an aggressive Shaper into a completely passive team of Specialists, and you will get outright sabotage rather than higher productivity.
How the Belbin model integrates with other team management tools
The Belbin methodology should not live in a forgotten Excel file on the HR director's computer. It only works fully when it is built into digital HR tools.
Moving people management into a single digital environment, such as an HRMS (Human Resources Management System), turns team profiling into a systematic process:
digital employee profile: the employee record can store not only the person's job title but also their Belbin assessment results. When assembling a project team, the manager immediately sees the role profile of the future group;
link to 360-degree feedback: when running regular reviews through the HR system, you can add questions that assess how team roles show up in practice;
predictive analytics: if HR surveys show engagement falling in a department, the HR specialist opens a dashboard with HR analytics. The matrix may reveal that the team has three Shapers and no Teamworker, and the system helps surface this structural imbalance quickly.
Conclusion
Belbin team roles are, of course, not a crystal ball that will solve every management problem. They are more of a powerful lens that lets a manager look under the hood of team dynamics.
Once you understand which of your people are Plants and which are Implementers, you stop asking fish to fly and birds to swim. You assign tasks so that everyone plays to their strengths. Everyone wins: employees burn out less, and the business gets a self-balancing team that can deliver any complex release.
What to do next
Do not shelve the theory. Run a basic questionnaire with your current team this week. Digitize the results with HR tools. You will be surprised how many hidden conflicts and process bottlenecks suddenly become clear.
