Honey’s five team roles: a practical guide to better teamwork

Honey’s five team roles are a framework commonly attributed to psychologist and management development practitioner Peter Honey. The roles are leader, challenger, doer, thinker and supporter. They describe different contributions to teamwork, from setting direction and questioning assumptions to completing tasks and helping colleagues participate.

The most useful question is not “Which type of person am I?” but “Which contributions does this team need, and are we making room for them?” One person can contribute in several ways, and the same person may behave differently across tasks.

Used carefully, the framework can structure a team discussion or professional development activity. It should not be treated as a scientifically established personality classification or a proven recipe for high performance.

Where honey’s model comes from

Honey’s framework belongs to the commercial management-development and self-assessment tradition associated with his training materials. That context matters: a commercially published development tool is not automatically an independently validated psychological assessment.

The precise first publication date, original manual and model-specific validation history are not verified in this draft. Claims that Honey discovered five universal roles through extensive research across industries would therefore need supporting primary evidence before publication.

The framework is also distinct from Meredith Belbin’s model. Belbin’s official description sets out nine team roles, not Honey’s five. The two should not be combined or attributed to the same developer. Honey’s team roles should not be confused with the separate Honey and Mumford learning styles framework either.

Commercial origins do not make a framework useless. They do mean that claims about its effectiveness should be separated from promotional descriptions. Any associated questionnaire, scoring system or training resource may also be proprietary. Check the relevant licence before reproducing materials, and do not present an improvised quiz as an official Honey assessment.

Understanding the five team roles

The descriptions below are practical paraphrases for team discussion, not questionnaire items or formal scoring criteria. Think of each role as a contribution that people can make rather than a label they must keep.

Leader: helping the team find direction

The leader contribution involves clarifying the purpose, bringing people together around priorities and helping the team reach decisions.

Useful behaviours include asking what success looks like, summarising an agreement and checking who owns the next action. This contribution does not have to come exclusively from the line manager. A colleague with relevant expertise might guide one stage of a project.

Too much direction can become control. The aim is to create clarity without closing down other people’s input.

Challenger: testing assumptions

The challenger contribution involves questioning proposals and exposing weaknesses before the team commits time or resources.

Someone might ask whether a deadline is realistic, whose needs have been overlooked or what evidence supports a proposed change. Effective challenge focuses on the work, not on undermining colleagues.

Constant objection can stall progress. Challenge is most helpful when it explains the concern and identifies what would make a proposal acceptable.

Doer: turning decisions into action

The doer contribution moves work from discussion to delivery. It includes organising tasks, following through on commitments and making progress visible.

Examples include booking a training session, updating a process guide or testing a new reporting template. Doing is not a less skilled contribution than thinking or leading. Delivery often requires judgement, technical knowledge and negotiation.

The risk is acting before the team has understood the problem. Productive action needs a clear purpose and appropriate checks.

Thinker: developing and examining ideas

The thinker contribution creates space to understand a problem, explore options and consider consequences.

A colleague might connect several pieces of feedback, suggest an alternative process or work through why a previous solution failed. Thinking can happen in conversation, but it may also require quiet preparation.

Analysis can become a way of postponing decisions. Teams need to agree how much information is enough and when they must move forward.

Supporter: helping people work together

The supporter contribution strengthens cooperation. It includes listening, noticing when someone has not been heard and helping colleagues resolve misunderstandings.

Support does not mean agreeing with everything or avoiding difficult conversations. A supportive colleague may challenge an unfair workload or ask for an unresolved disagreement to be addressed.

This work should be recognised and shared. It should not automatically fall to the same person because they are seen as approachable or good with people.

What the evidence can and cannot tell US

Independent evidence for Honey’s specific five-role model appears limited. No model-specific independent validation study is cited here, so there is no basis in this article for claiming that a particular role balance predicts performance or that a questionnaire can reliably identify someone’s ideal contribution.

That is different from saying team behaviour does not matter. Research examines factors such as coordination, shared understanding and psychological safety. For example, Amy Edmondson’s research on psychological safety and learning behaviour in work teams is relevant to whether colleagues feel able to ask questions, acknowledge mistakes and raise concerns. It does not validate Honey’s five categories.

Similarly, the Health and Safety Executive’s Management Standards on role emphasise understanding responsibilities and avoiding conflicting roles. That supports the importance of clear expectations, not the need to allocate five behavioural labels.

The sensible distinction is between a useful conversation prompt and a validated assessment. A framework can help people notice neglected behaviours without proving that its categories are exhaustive or that using it causes better results.

If a supplier makes stronger claims, ask for independent research on the specific instrument, including its reliability, validity and relevance to your intended use. Testimonials and participant satisfaction are not substitutes for that evidence.

How to use the framework in a team discussion

Start with a real piece of work rather than asking everyone to choose a role. A project review, planning meeting or short development session provides a useful setting.

1. Define the task and constraints

Agree what the team needs to achieve, by when and within which limits. Include workload, budget, accessibility and any relevant quality or compliance requirements.

A role discussion will not resolve an impossible deadline or a lack of resources. Those issues need management decisions.

2. Look for observable contributions

Ask colleagues to describe what happened during a recent task:

• Who helped clarify the goal?
• Which assumptions were questioned?
• How were options explored?
• What turned decisions into completed actions?
• How were people helped to contribute?

Use examples rather than declarations such as “I’m the thinker”. Invite written reflections before the meeting so that quick or confident speakers do not dominate the discussion.

3. Identify missing behaviours, not missing types of people

A team may generate plenty of ideas but leave actions unowned. Another may deliver quickly while rarely questioning whether the original request makes sense.

The response need not be recruitment or restructuring. It might be an action log, a scheduled challenge point or preparation time before decisions.

4. Agree a small experiment

Choose one change for the next task. For example, rotate meeting facilitation or ask someone to test a proposal’s assumptions before approval. Keep formal accountability clear: contributing challenge does not transfer responsibility for a decision.

Review whether the change helped using relevant evidence, such as fewer missed handovers or clearer action ownership. Do not assume that improvement proves the model itself caused the result.

Two realistic workplace examples

These examples are illustrative scenarios, not documented case studies or evidence of the model’s effectiveness.

An FE team reviewing apprenticeship progress meetings

An FE provider wants progress meetings to be more useful for apprentices and employers. Tutors, assessors and administrators have different views about what needs to change.

The team uses the five contributions to structure its planning. One colleague clarifies the purpose and decision deadline. Another questions whether the proposed meeting length is realistic for employers. A tutor explores options using apprentice feedback. An administrator drafts a workable booking process. Another colleague checks that part-time staff and less vocal team members have had opportunities to contribute.

Nobody receives a permanent role. The administrator also challenges an assumption about staff availability, while the tutor helps prepare the pilot materials.

The practical outcome is a small pilot with named responsibilities and a review date. The team examines attendance, feedback and administrative workload before deciding whether to continue. The framework helps organise the conversation; it does not establish compliance or guarantee better apprentice outcomes.

A UK operations team improving shift handovers

A warehouse team has recurring handover problems between early and late shifts. The manager initially describes the issue as poor communication, but colleagues report unclear ownership and insufficient overlap time.

Using the framework, the team separates the contributions it needs. Someone sets a clear objective for the handover process. Colleagues examine where information is lost, challenge an overly complicated form and develop a simpler checklist. Staff from both shifts test it, with someone ensuring that concerns can be raised without blame.

An experienced operative contributes as both thinker and doer. The manager provides direction but also supports discussion by acknowledging that scheduling is part of the problem.

The team reviews missed actions and staff feedback. If overlap time remains inadequate, management must address that constraint. Assigning more supporter behaviour would not fix a staffing or scheduling problem.

Common misunderstandings and safeguards

You do not need five people. Several people can make the same contribution, and one person can make several. The mix required will change with the task.

Preferences are not competence. Enjoying challenge does not establish expertise in risk assessment. Someone who dislikes leading meetings may still be highly capable of coordinating a project.

Roles are not excuses. “I’m a thinker, not a doer” does not remove an agreed responsibility. Equally, someone known for delivering should still have opportunities to shape decisions.

Silence is not a personality diagnosis. It may reflect hierarchy, inaccessible meeting formats, language differences, lack of preparation time or concern about consequences. Ask what would help participation rather than assigning a label.

The framework should not decide employment outcomes. Without appropriate evidence for that purpose, it should not determine recruitment, promotion, redundancy selection or access to development. Use job-relevant criteria and fair, documented processes.

Most importantly, no role model replaces adequate staffing, technical competence, clear authority or respectful management.

A practical next step

Honey’s five team roles can offer accessible language for discussing direction, challenge, action, thinking and support. Their value is in helping a team notice what its work needs, not in sorting people into fixed categories.

For your next meeting, choose one live task and ask: “Which contribution are we overlooking?” Agree one observable change, name the person responsible for following it through and set a review date. Keep what helps, reconsider what does not, and stay modest about what the framework can prove.

Sources and further reading

• Belbin: The nine Belbin Team Roles. The model owner’s explanation, useful for distinguishing Belbin’s framework from Honey’s five roles.
• Amy Edmondson: Psychological Safety and Learning Behavior in Work Teams. Academic research relevant to speaking up and team learning, not a validation of Honey’s model.
• Health and Safety Executive: Management Standards, role. UK guidance on clear responsibilities and conflicting role expectations.

These sources support the distinctions and wider teamwork guidance above. They do not establish Honey’s original publication history or independently validate the five-role framework.