Before Your Team Can Use AI Together, You Need to Know What Kind of Team You Are

I run a Belbin debrief at the start of almost every team programme I deliver.

I ask participants to review their profile — the nine team roles, the natural behaviours, the allowable weaknesses — and then I ask them to plot where they sit on a shared team map.

What happens next is always the same. Someone points at the map and says: “We have no one in that role.”

And the room goes quiet.

Because they have just seen, in one image, why a particular meeting always goes off track. Why decisions that should take twenty minutes take two weeks. Why the follow-through on every initiative dissolves somewhere between the idea and the execution.

They have been working with each other for years. But this is the first time they have seen their team clearly.

That moment is what I want to talk about — and why it matters more right now, in Singapore, than it ever has before.

---

What Belbin Actually Tells You

Dr Meredith Belbin spent nearly a decade studying why some management teams succeed and others fail. What he found was not about intelligence, experience, or seniority. It was about roles.

Every high-performing team, he discovered, needed a spread of nine behavioural contributions: the Shaper who pushes through obstacles; the Coordinator who orchestrates toward goals; the Plant who generates original ideas; the Resource Investigator who brings in external possibilities; the Monitor Evaluator who analyses without rushing to conclusions; the Implementer who turns ideas into workable plans; the Completer Finisher who sweats the detail; the Team Worker who holds the relationships together; and the Specialist who contributes deep technical knowledge.

You do not need nine people. People carry multiple roles. But you do need the functions covered — because a team without a Completer Finisher will always ship late, and a team without a Plant will keep solving new problems with the same old thinking.

This is not a personality test. It is a functional map of how work actually gets done.

Singapore Teams Are Being Asked to Digitise Without This Map

Since Budget 2026, I have spoken to more HR leaders, L&D managers, and department heads about AI workforce transformation than in any previous year combined. The language is urgent: AI Nation, job redesign, SkillsFuture, productivity uplift.

The intent is right. The urgency is warranted. Singapore genuinely needs this.

But most of the organisations I encounter are trying to build a digital workforce the wrong way around. They are rolling out AI tools first and hoping the team dynamics sort themselves out later.

They will not.

Because AI does not replace a team. It reshapes what each person in that team is for.

And if you do not know what each person is for — if the team has never seen its own map — adding AI tools into the mix does not accelerate the work. It accelerates the dysfunction.

The Shaper starts using AI to move faster, which creates pressure on the Completer Finisher who is still checking what the Shaper has already published. The Plant generates twenty AI-assisted ideas in a morning, but there is no Monitor Evaluator in the room to interrogate them, so the team chases all twenty and finishes none. The Team Worker, who held the informal relationships that made the team function, is now three steps behind on tools they were never given space to learn, and quietly starts to disengage.

Good intentions. Wrong sequence.

The Right Sequence: Identity Before Integration

The teams I have seen adopt AI successfully — genuinely, sustainably, not just in the first month — all shared one thing. They started with who they were as a team before they asked what AI could do for them.

That starting point does not have to be Belbin. But Belbin is one of the clearest lenses I have found for this work, because it maps the functional dimension of a team rather than just the personality dimension. It tells you where your team naturally excels and where it structurally underdelivers — and those insights map almost perfectly onto how different team members should be integrating AI into their individual contributions.

A Completer Finisher should be using AI to catch what they would otherwise obsess over manually — proofreading, consistency checks, version control. It frees up their attention for the quality judgments only they can make.

A Resource Investigator should be using AI for market scanning, trend synthesis, and first-pass research — because their strength is in the connection and interpretation, not the retrieval.

A Coordinator should be using AI to draft, summarise, and circulate — keeping the orchestration function human while delegating the documentation overhead.

The point is not that everyone does the same thing with AI. The point is that each person’s highest-value contribution is more available when AI absorbs the routine work around it. Belbin tells you where the highest-value contribution lives.

What This Looks Like in Practice

In Team Intelligence — a programme built around this idea — we run the Belbin or DOPE diagnostic before we introduce a single AI tool. Teams map themselves first. Then they face a live AI challenge together, using AI tools to solve a real business problem.

What we see, consistently, is that the teams who have been through the diagnostic work with AI differently. The Shaper does not take over the prompt. The Team Worker does not sit back. Everyone has a role — because they understand their role.

Then, in the afternoon, we redesign their workflows together. Not as individuals, but as a team that now knows itself. Who integrates AI into what? Where does the human judgment stay? What does the Implementer’s workflow look like, versus the Specialist’s?

They leave with a Team AI Charter — specific commitments, owners, and accountability pairs. Not a playbook handed down from management. Something they built themselves.

That is what sustainable digital workforce adoption looks like. It starts with the team knowing who they are.

The Question Worth Asking Before Your Next AI Rollout

If you are planning to introduce AI tools to your team this year — and in Singapore right now, most organisations are — try this before you open a single platform.

Ask your team: who is our Shaper? Who is our Plant? Who is our Completer Finisher? And then ask: do we have the full spread, or are there roles we have been compensating for without realising it?

You might find the answer to why your last three initiatives stalled.

And you will have a much clearer picture of what your AI rollout needs to account for before it starts.

“AI doesn’t replace your team. It reshapes what each person is for.”