# Belbin Team Roles — the long version

Ever wondered why some teams just *click*, while others — often stuffed
with obviously brilliant people — hit the rocks? I have, plenty of times.
It turns out somebody spent a decade figuring this out properly, with
data, and the answer is not what most managers assume.

Back in the late 1960s, Meredith Belbin went looking at high-performing
teams at Henley Management College. He started where you'd expect: take
the smartest, most analytical people you can find, put them in a room, and
watch them win. Except they didn't. These teams argued endlessly, picked
holes in each other's ideas, couldn't agree on anything, and quietly
neglected the actual work. They usually did *worse* than an ordinary team.
Belbin called it the [Apollo Syndrome].

Now, most of us would find that infuriating. Belbin got excited, and spent
the next nine years pulling apart what actually makes a team work.

## This is evidence, not another personality fad

I want to be clear about this up front, because "team roles" sounds like
exactly the kind of airport-bookshop nonsense you should run away from.
It isn't. Belbin's work is grounded in real observation:

- Nine years of watching real management teams at Henley, with every
  single participant put through a battery of psychometric tests, so you
  could actually measure behaviour against team outcomes. Not vibes.
  Numbers.
- The headline finding, and it's a good one: **the difference between a
  team that wins and a team that fails is not intellect — it's
  behaviour.** The Apollo teams, built entirely from the cleverest people
  in the room, spent all their time debating and hole-picking, forgot to
  do the work, and lost.
- Out of all that observation fell nine recurring clusters of behaviour —
  the **Team Roles**. A Team Role is just "a tendency to behave,
  contribute and interrelate with others in a particular way."

### Where the research came from

This wasn't a weekend workshop. The framework fell out of nine years of
study — roughly 1969 to 1978 — at Henley Management College, built around a
business simulation called the **Executive Management Exercise (EME)**.
Belbin didn't do it alone either: the team included the psychometrician
Bill Hartston, the anthropologist Jeanne Fisher, and Roger Mottram. They
put participants through psychometric instruments, deliberately *composed*
the teams rather than leaving it to chance, and then watched which
compositions won and which lost.

And here's the bit that makes it worth taking seriously: they eventually
got good enough that they could **predict which teams would win or lose
before the exercise even started**. That's the whole game. Anyone can
explain a result after the fact — being able to call it in advance, from
the composition alone, is what separates this from the usual airport-
bookshop personality fluff.

The clever bit is the idea of the **allowable weakness**. Every role has a
strength, and every strength drags a predictable flaw along behind it —
the flipside you put up with *because* of the strength attached to it. The
creative Plant is scatty and forgetful. The driving Shaper ruffles
feathers. The quality-obsessed Completer Finisher won't let go of anything
long enough to delegate it. You use the strength and you manage the
weakness. Simple enough.

And here's the subtle part Belbin was insistent on: you *tolerate* the
weakness, you don't try to stamp it out. Go hunting for the flaw and you
usually kill the strength attached to it. Train the scattiness out of a
Plant and you often train the creativity out too. The flaw is the price of
the gift; pay it.

But — and this matters — each role *also* has a **non-negotiable**
weakness, one you do not tolerate. A Shaper who provokes people is fine.
A Shaper who can't recover the situation afterwards with a bit of good
humour or an apology is not. Know the difference.

One more thing: everyone carries 2–3 **preferred roles**, a couple of
**manageable** ones they can cover at a push, and some **least-preferred**
roles they should basically never be asked to play. Playing against type
costs a fortune and delivers very little. If the work needs a role you
haven't got, don't force someone to fake it — go and find someone who has
it naturally. This, incidentally, is why a small team can still be
balanced: those manageable secondary roles are the slack that lets four or
five people cover all nine behaviours between them.

One caveat on measuring any of this. The headline tool is the
**Self-Perception Inventory** — you rate your own behaviour — but the full
method doesn't stop there, because self-perception is unreliable (we all
flatter ourselves). Belbin pairs it with **Observer Assessments**:
structured feedback from the colleagues who actually work with you. It's
the half of the method people quietly skip, and skipping it is how you end
up with a room full of people who *think* they're Plants.

## The nine roles at a glance

Here's the whole cast, grouped the way Belbin grouped them. Note the last
column especially — that's the line you don't cross.

### Thinking / cerebral roles

| Role | Contribution | Allowable weakness | Not allowed |
|------|-------------|--------------------|-------------|
| **Plant** | Creative, imaginative, unorthodox. Solves hard problems. | Ignores details; too wrapped up to communicate well. | Strong ownership of an idea when collaborating would get a better result. |
| **Monitor Evaluator** | Sober, strategic, discerning. Sees every option and judges it accurately. | Sceptical; lacks drive; can be over-critical. | Cynicism without logic. |
| **Specialist** | Single-minded, self-starting, dedicated. Brings knowledge in short supply. | Contributes on a narrow front; dwells on technicalities; misses the big picture. | Ignoring things outside their own patch. |

### Action-oriented roles

| Role | Contribution | Allowable weakness | Not allowed |
|------|-------------|--------------------|-------------|
| **Shaper** | Challenging, dynamic, thrives under pressure. Drives through obstacles. | Provokes people; hurts feelings. | Can't recover the situation with good humour or an apology. |
| **Implementer** | Disciplined, reliable, efficient. Turns ideas into practical plans. | A bit inflexible; slow to pick up new possibilities. | Obstructing change. |
| **Completer Finisher** | Painstaking, conscientious. Hunts down errors and omissions; delivers on time. | Worries too much; won't delegate; a nit-picker. | Obsessive behaviour. |

### People / social roles

| Role | Contribution | Allowable weakness | Not allowed |
|------|-------------|--------------------|-------------|
| **Co-ordinator** | Mature, confident. Clarifies goals, spots talent, delegates well. The natural chair. | Can offload their own work; may be seen as manipulative. | Taking credit for the team's effort. |
| **Teamworker** | Co-operative, perceptive, diplomatic. Listens, builds, calms the waters. | Indecisive in a crunch; easily influenced. | Avoiding anything that might involve pressure. |
| **Resource Investigator** | Outgoing, enthusiastic. Explores opportunities, builds contacts. | Over-optimistic; loses interest once the novelty wears off. | Letting people down by not following up. |

## The team is the unit of performance, not the individual

Here's the part that should change how you hire.

Belbin's control experiments all land in the same place: **teams of clones
fail, and they fail predictably.** He tried them all:

- **All A-players (the Apollo team):** endless debate, no decisions, poor
  results. You've met this team.
- **All Implementers — the "perfect workers":** diligent, well-organised,
  and mediocre. No ideas, thrown by any change, executing beautifully in
  possibly the wrong direction.
- **"Pure" personality teams** (all stable extroverts, or all anxious
  introverts, and so on): each one brilliant in exactly one situation and
  hopeless in all the others.

The teams that actually won were made of **different and compatible**
roles. The ones that lost were full of people with the same tendencies,
elbowing each other for the same job.

Balance is the whole mechanism. No Plant and there's no initial spark;
too many Plants and the bad ideas bury the good ones. No Shaper and the
team ambles gently past its deadlines; two or more and the in-fighting
starts. So the very same person can be a star in one team and dead weight
in another — which means picking and designing a team is a leadership act,
not an HR box-ticking exercise.

## Building a team that actually works

### How many people?

**Six is the sweet spot.** Fewer than six and everyone's stretched across
too many roles, duties overlap, and things get dropped. Seven or more and
social loafing creeps in — a seven-person team does roughly the same
amount of work as a six-person one, just with an extra salary attached.

And no, you do *not* need nine people to cover nine roles. Since everyone
carries 2–3 preferred roles, a well-chosen team of four can represent all
nine between them.

### Balance the wheel

The nine roles sit in three domains on the Belbin Team Wheel, and a
balanced team has credible cover in all three:

- **Thinking:** Plant (ideas), Monitor Evaluator (judgement), Specialist
  (deep knowledge).
- **Action:** Shaper (drive), Implementer (turns ideas into plans),
  Completer Finisher (quality control).
- **Social:** Co-ordinator (goals & delegation), Teamworker (cohesion),
  Resource Investigator (outside contacts & opportunities).

The exercise is dead simple and genuinely worth doing: draw the wheel, drop
each person's **top two roles** into the segments, then read the gaps and
the pile-ups out loud. *"Three Teamworkers and no Shaper — lovely
supportive atmosphere, but we're going to drift and miss every deadline."*
Say it aloud and the problem names itself. Gaps tell you what to recruit or
consciously cover. Duplicates tell you where the fights will start.

And make no mistake — **duplication is every bit as dangerous as a gap**,
especially in the loud roles. Two Shapers lock horns. Two Plants fight for
airtime, each in love with their own idea. Two Monitor Evaluators will
debate the thing forever and never conclude.

### Which roles do you actually need first?

For a small team, three are must-haves:

- **Co-ordinator** — clarifies goals, spots talent, delegates well. Your
  natural chair.
- **Implementer** — this was the one role Belbin found in *every* "pure"
  team that still managed to succeed. Works for the company rather than
  themselves, and reliably turns decisions into done work.
- **Plant** — the source of the original idea. No Plant, and the team
  stagnates.

Fill the remaining seats to suit the job in front of you. And add a
**Monitor Evaluator** the moment success hinges on a handful of crunch
decisions — that's the impartial arbiter who's seldom wrong, and in a
tight spot they earn their keep several times over.

Match the emphasis to the phase, too: Plant early or whenever you're stuck;
Shaper to keep momentum up; Resource Investigator to stop the team going
inward-looking; Completer Finisher at the end, to polish and error-check
before it ships.

Finally, mind the known pairings. Plants are best managed by a
Co-ordinator, backed by a Monitor Evaluator as a sounding board and an
Implementer to make the ideas real. Shapers need a Teamworker alongside to
smooth the feathers they ruffle — and they'll happily clash with
Co-ordinators and other Shapers if you let them.

### Combinations that pull their weight

Balance across the three clusters matters more than any single pairing —
but some combinations show up in the winning teams again and again, and
they're worth building around deliberately:

- **Co-ordinator + Plant.** One of Belbin's strongest findings. A patient,
  facilitative Co-ordinator who can draw out and harness the ideas of a
  *single* creative Plant. The Co-ordinator gives the Plant room and cover;
  the Plant supplies the spark.
- **Plant + Monitor Evaluator.** Creativity paired with cold, critical
  judgement. The ME filters the Plant's output so only the viable ideas go
  forward — the trick is doing it *without* crushing the Plant's morale.
- **Shaper + Implementer + Completer Finisher.** Drive, disciplined
  execution, and attention to detail: a proper delivery engine. This is the
  trio that gets things shipped.
- **Resource Investigator + Teamworker.** External networking plus internal
  cohesion. The RI drags opportunities in from outside; the Teamworker
  keeps morale and relationships healthy inside.

### Combinations that blow up

- **Too many Shapers.** Aggressive competition for dominance, arguments,
  in-fighting — one of the most reliably dysfunctional patterns Belbin
  found.
- **Co-ordinator + a strong Shaper.** Constant leadership struggles: the
  Shaper's drive undermines the Co-ordinator's facilitative authority.
  Teams do better with *one* clear style of leadership, not two fighting
  for the chair.
- **Multiple Plants.** Each promotes their own idea and criticises or
  ignores everyone else's. Ideas proliferate; nothing converges.
- **All Monitor Evaluators — the Apollo Syndrome.** The famous one. Fill a
  team entirely with clever, analytical people and they finish *last*: all
  their energy goes into destructive debate and poking holes in each
  other's arguments, and they never decide or act coherently.
- **All action, no thought.** A team of Implementers and Completer
  Finishers is efficient but rigid — it can't innovate or adapt when the
  ground shifts under it.
- **Plant + Completer Finisher friction.** Big-picture carelessness against
  perfectionist detail-focus. Managed well it's a useful tension; left
  unmanaged it's mutual frustration.

### The gaps that sink a team

Duplication is one failure mode; absence is the other. Watch for:

- **No Plant** → a shortage of original ideas; the team stagnates.
- **No Completer Finisher** → errors slip through and deadlines slip past.
- **No Teamworker** → friction goes unresolved — lethal in a Shaper-heavy
  team where the feathers are already flying.
- **No Co-ordinator or Shaper** → drift, and no clear direction.

### The whole philosophy, in one line

There's room for everyone in the team. Nobody is well-rounded, but a team
can be — so use each person's strengths, manage their allowable
weaknesses, and never, ever staff a team on brilliance alone.

## The winning-team blueprint

Across hundreds of Henley teams, Belbin found the winners kept turning up
in roughly the same shape:

0. **A good *spread* of mental ability — not uniformly high.** This is the
   counter-intuitive one, and it's the direct lesson of the Apollo teams:
   you want a couple of clever people and the rest merely capable, not a
   room full of A-grade minds all fighting to be right.
1. **A Co-ordinator in the chair.** Calm, trusting, focused on drawing
   contributions out of people rather than dominating the room. Someone who
   *runs* the team instead of trying to out-think it.
2. **Exactly one strong Plant as the creative engine.** One. None and
   there's no spark; two or more and you've got competing ideas and open
   warfare. The team is deliberately built to get the best out of this
   person, with the Co-ordinator giving them space and cover.
3. **A Monitor Evaluator as the designated critic.** The Plant–ME pairing
   *is* the creative engine — the Plant generates, the ME coldly
   stress-tests. And let the ME arbitrate the big calls, because "the
   person who is rarely wrong is the one who scores in the end."
4. **Supporting roles with clear demarcation.** Everyone else covers the
   rest of the wheel — Implementer and Completer Finisher to execute and
   polish, Resource Investigator to keep the team looking outward,
   Teamworker for cohesion — with jobs matched to natural roles so nobody's
   scrapping over the same contribution.
5. **Self-awareness beats raw balance.** A team that knows its own profile
   can still win through **role sacrifice** — someone deliberately playing
   their second, manageable role to plug a gap the team has openly named.
   An unaware, unbalanced team fails. An aware one adapts. Knowing your own
   shape is half the battle. Just remember role sacrifice is a *loan*, not
   a gift: fine for a sprint, quietly draining over the long haul, because
   the person is running against their natural grain the whole time.

A few more strategies from the wider methodology:

- **Known good pairings:** Plant managed by a Co-ordinator and backed by
  an Implementer; Shaper paired with a Teamworker to smooth feathers;
  Resource Investigator backed by a Completer Finisher to chase down the
  loose ends the RI starts and then wanders off from.
- **Match the composition to the work:** Shaper-heavy for turnarounds and
  change; Plant/RI-heavy for innovation; Implementer/CF-heavy for steady
  execution and delivery.
- **Recruit for suitability, not just eligibility.** *Eligible* means
  qualified and experienced. *Suitable* means bringing the behaviour the
  team is actually missing. Hire the missing role — not another copy of
  the strongest one you've already got.

## Projects vs. operations: the same roles, different rhythm

Here's where this stops being a workshop exercise and starts earning its
keep. Projects and operations have fundamentally different *rhythms*, and
the role mix that makes one sing can actively sabotage the other. Projects
move through phases, each with changing needs. Operations want sustained
consistency with the occasional burst of controlled panic. Staff them the
same way and you'll feel the friction.

### Roles across the project lifecycle

A project doesn't want the same behaviours all the way through, which is
exactly why a fixed team struggles as the work matures:

| Phase | Roles most needed | Why |
|-------|-------------------|-----|
| **Initiation / concept** | Plant, Resource Investigator | Original ideas; scanning outside for options, contacts, precedents |
| **Feasibility / options** | Monitor Evaluator, Specialist | Sober appraisal of the alternatives; deep technical judgement |
| **Planning** | Co-ordinator, Implementer, Monitor Evaluator | Clarifying objectives, delegating, turning strategy into a workable schedule |
| **Execution / build** | Implementer, Shaper, Teamworker | Disciplined delivery, drive through obstacles, cohesion under pressure |
| **Testing / quality** | Completer Finisher, Monitor Evaluator | Error-hunting, perfectionism, dispassionate review |
| **Delivery / closure** | Completer Finisher, Co-ordinator, Resource Investigator | Finishing properly, tying off loose ends, stakeholder handover |

What that means in practice:

- **Early-phase teams that overstay cause trouble.** The Plants and RIs who
  owned ideation turn disruptive during execution — generating shiny new
  ideas exactly when the team needs to *freeze scope*. That's a behavioural
  explanation for scope creep sitting right there.
- **Late-phase roles look useless early.** A Completer Finisher in the
  planning workshop seems pedantic — right up until delivery, when their
  absence shows up brutally.
- **Shapers shine in troubled projects.** When a project stalls or hits
  resistance, a Shaper's drive is priceless. Drop the same person into a
  smoothly running project and they'll manufacture urgency and friction
  because that's what they do.
- **"Project manager" isn't one role.** The PM job spans Shaper-style drive
  and Implementer/CF-style process discipline. Belbin's point: know which
  you naturally are and consciously cover the rest — a Shaper-PM should pair
  with a Teamworker or Co-ordinator deputy to repair the relational damage
  they leave behind.
- **Rotate people, not just tasks.** Some organisations deliberately shift
  team composition at phase gates — bringing in delivery-minded people for
  execution — rather than expecting the same individuals to change their
  spots.

### Operations and support: a different animal

Ops and support work — service desks, infrastructure, maintenance, BAU app
support — has a very different profile. The natural backbone:

- **Implementer** — the core of ops: reliable, process-driven, follows
  runbooks and standards, turns policy into routine.
- **Completer Finisher** — vital for change control, patching discipline,
  documentation accuracy, and making sure tickets are genuinely *resolved*
  rather than just closed.
- **Specialist** — deep expertise in specific systems; usually the
  escalation point. Ops teams tend to accumulate these.
- **Teamworker** — sustains morale in work that's repetitive, thankless and
  interruption-driven, and smooths the handoffs between shifts.

And the roles ops teams typically *lack*, with the price they pay:

- **No Plant / Resource Investigator** → the team keeps doing things the
  same way, workarounds fossilise into permanent process, and nobody asks
  whether the toil could be automated away. This is the behavioural root of
  the "firefighting forever" trap.
- **No Monitor Evaluator** → poor prioritisation in a major incident: every
  ticket treated as equally urgent, symptoms chased instead of stepping
  back to think.
- **No Shaper** → chronic problems never get escalated forcefully; the team
  absorbs the pain rather than pushing back on whoever upstream is causing
  it.

### When it all catches fire

A major incident temporarily *inverts* the normal ops profile:

- **A Shaper or Co-ordinator cuts through the paralysis.** Pure
  Implementer/Specialist teams can freeze — stuck in analysis, or dutifully
  following a runbook that doesn't apply.
- **Monitor Evaluators earn their keep in the post-incident review** —
  dispassionate analysis, no blame, no defensiveness.
- **Completer Finishers make sure the remediation actions actually happen**
  — the single most commonly dropped ball in incident management.

### The project-to-ops handover

This is a classic Belbin friction point, and naming it as such tends to
defuse it:

- Project teams (Plant/Shaper/RI-heavy) see ops as slow, bureaucratic
  obstacles. Ops teams (Implementer/CF-heavy) see project teams as reckless
  people lobbing half-finished systems over the wall.
- **Neither is wrong.** They're each exhibiting precisely the behaviours
  their work selects for. Framing the clash as a *role difference* rather
  than a competence or attitude problem takes most of the heat out of it.
- **Mitigations:** embed an ops Implementer/CF in the project during build
  (they'll ask the operability questions early), and keep a Completer
  Finisher through handover so documentation and knowledge transfer
  actually complete.

### DevOps and blended "you build it, you run it" teams

Modern teams try to hold both profiles in one group, and Belbin's model
explains why that's hard: you need Plant/RI energy for feature work *and*
Implementer/CF discipline for reliability, and very few individuals supply
both naturally. Practical responses:

- Hire deliberately for the missing cluster — usually CF/Implementer in a
  developer-heavy team.
- Rotate people between feature work and on-call/maintenance so the role
  sacrifice is *shared*, not dumped on one person forever.
- Recognise that the person who loves polishing the CI pipeline and the
  runbooks is doing high-value Completer Finisher work, even when it isn't
  glamorous.

> **Caveats:** this is an *application* of the model, not something Belbin
> validated phase-by-phase — the lifecycle mapping is a widely used
> practitioner extension. A team that knows its own profile can adapt
> across phases without swapping personnel. And don't use roles to
> pigeonhole ("Specialists can't lead incidents") — they mark comfort
> zones, not ceilings.

## Common misconceptions (worth heading off early)

People misuse this framework in fairly predictable ways. A few to swat
down before they take root:

- **It's not a personality test.** Team Roles describe *behaviour in a team
  context*, not fixed personality. Your role can shift with the team, the
  task, and over time. It's not your horoscope.
- **You don't need nine people.** You need the nine *behaviours* covered.
  Four well-chosen people carrying two or three roles each will do it.
- **No role is "better" than another.** Every role wins games. In practice
  organisations forget this — they lionise Shapers and quietly undervalue
  Teamworkers and Completer Finishers, which is exactly backwards when
  those are the roles holding delivery and cohesion together.
- **A role label is not a box — or an excuse.** Belbin was sharp about
  this: your result is a starting point for a conversation, not a permanent
  exemption. "I can't do detail, I'm a Plant" is a cop-out, not an insight.

## Is any of this actually true? (the academic argument)

Fair question, and worth being honest about — because the framework has
taken real fire over the years.

- **The main criticism** came from Furnham, Steele and Pendleton (1993),
  who went after the psychometrics of the Self-Perception Inventory: low
  internal consistency, and a forced-choice (*ipsative*) format that makes
  it awkward to validate statistically. Belbin published a rebuttal.
- **The picture since is kinder.** Later work (Swailes and McIntyre-Bhatty,
  among others) found better reliability than the early critiques
  suggested, and studies mapping the roles onto the Big Five personality
  factors turned up meaningful overlap — so there's *something* real being
  measured.
- **The big claim is genuinely mixed.** Whether balanced teams actually
  outperform unbalanced ones in real organisations is not settled: some
  studies back it, others find weak or no effect. Don't oversell it.
- **The usual defence, which I think is right:** the tool was built for
  *development and discussion*, not as a rigorous selection instrument.
  Judge it as a way to get a team talking honestly about who does what and
  it earns its place; judge it as a hiring gate and you're using it for
  something it was never meant to do.

> **Source caveat:** this section leans on Belbin's books (*Management
> Teams — Why They Succeed or Fail*; *Team Roles at Work*) rather than the
> PDFs in this directory. Only the ME-as-arbiter point and the role
> pairings show up in the local sources, so verify before you quote the
> specifics.

---

## Source notes (from the PDFs in this directory)

- `belbin_2_pager.pdf` — "Team Roles in a Nutshell": research history,
  how each role emerged, allowable weaknesses, the balance argument, and
  the team-of-four-covers-nine point.
- `belbin_overview_awesome.pdf` — the Apollo team story, the three role
  domains, the 6-member ideal, the CO/IMP/PL must-haves, the "pure team"
  experiments, and the Implementer finding.
- `belbin_roles_1_pager.pdf` — one-line contribution + allowable weakness
  per role.
- `belbin_roles_long_form.pdf` — per-role spotlights: objective, strengths,
  weaknesses (including the non-negotiable ones), compatibility, handling.
- `belbin_roles_characteristics_strengths_weaknesses.png` — the full
  characteristics / strengths / allowable / not-allowable table (that's the
  one reproduced above).
- `belbin_team_wheel_*.pdf` — the Team Role Circle (Social / Thinking /
  Action), the top-two-roles mapping exercise, and a worked example.

[Apollo Syndrome]: https://en.wikipedia.org/wiki/Meredith_Belbin#Apollo_Team_Syndrome