Contemporary models of team building

Groups studied

Most of the groups analyzed in Tuckman's research were not teams of any kind, as that term is commonly understood today. The studies he synthesized primarily examined therapy and counselling groups or training groups (such as T-groups used for sensitivity or leadership development in that era), plus a few laboratory groups assembled for research purposes. These were typically temporary or focused on personal development, interpersonal relationships, or experimental observation, rather than ongoing collaboration groups or teams working toward shared performance objectives.^[40]

Stage 1: forming

This stage describes the beginning of the group’s development path. Here the behaviors of members in the new group can be summarized as orientation, testing and dependence. “Testing” and “dependence” are group structure behaviors whereas “orientation” refers to task activity behaviors.

When group members are “testing” they are trying to discover what interpersonal behaviours the group will accept based on two touch points. First, the therapist’s or trainer’s or leader’s reactions (if there is one present) and, second, the responses of fellow group members. This testing leads to the setting of initial behavioral boundaries or norms.

“Dependence” takes place while the testing is going on. Here members relate to the therapist, trainer or some other powerful group member – or perhaps an existing norm if one already exists – in a dependent way. Members look to this person or people or standard for guidance and support in this new and unstructured situation.

“Orientation” is also happening at this stage. Members try to identify the task’s parameters and how they will use their colleagues’ know-how and experience to complete the task. They also decide what information they will need to address the task and how they will get it. While this orienting is going on, the members are discovering the task’s “behavioral ground rules”. Thus, in this way, “orientation” covers both interpersonal and task behavior.

Overall, being new to the task and one another, the group members behave cautiously while seeking clarity in what they experience as a fluid situation.^[41]

Stage 2: storming

This second stage centers on the conflict emerging from the group’s lack of unity.

As the initial politeness and superficial civility of the Forming stage fades, deeper differences emerge. Group members begin to express their individuality and often resist being overpowered by what may feel like a formal group structure. Now we see internal group conflict between members and, also, from members towards the therapist, trainer or leader, if one is present. Power struggles become common – often over roles, goals, priorities and methods.

Each member may have different emotional responses to the group’s task. The depth of their reactions can vary according to how difficult the task feels for them individually. Tuckman commented that intragroup conflict will be more obvious when the common goal centers on self-understanding and self-change, which is what you find in therapy and training groups, and less visible (but no less present) in groups working on purely intellectual tasks.

Although uncomfortable, this stage is needed if members are to move beyond merely superficial harmony towards effective functioning.^[42]

Stage 3: norming

By now members accept that the group exists and that it has become a recognizable entity. In recognizing it, their desire to maintain and perpetuate it grows, leading to establishment of new group-generated norms. In this stage, harmony becomes the top priority and members will begin to avoid task conflicts to ensure it. They will also accept – or start to accept – the idiosyncrasies of fellow members.

Regarding task activity, we start seeing what Tuckman called “the open exchange of relevant interpretations”. In therapy and training groups, this takes the form of discussing oneself and other group members. In the laboratory-task context, it takes the form of members expressing their opinions. Now you see members acting on the information they possess to arrive at common tentative interpretations and plans for action. Thus, openness to other group members and their interpretations is becoming a feature of this stage.

Overall, Norming is the stage when members begin to cooperate and establish informal norms to continue that collaboration.^[43]

Stage 4: performing

Having become a functioning entity during the third (Norming) stage, the group now morphs into what Tuckman described as a collective "problem-solving instrument".

Having learned to relate to one another successfully in the previous stages, the members start adopting and playing consistent roles to enhance the group’s task activities. Energy and task focus builds, creativity rises and solutions start to emerge as the group pushes to complete its task. Now the group looks cohesive and effective.^[44]

Stage 5: adjourning

This is the termination stage that Tuckman added in 1977 with Mary Ann Jensen. They felt this stage was overlooked in the original paper.

“Adjourning” recognizes that many groups will complete their task and disband, meaning that members will separate. For some members, this will feel like the “death” of the group and can be a powerful, difficult emotional stage to navigate. This is why modern organizations may help group members process the ending by listing the lessons learned and noting any personal growth.^[45]

Practical application of Tuckman's model

Although Bruce Tuckman's original papers (1965, 1977) describe the stages of group development, they do not prescribe or recommend specific leadership actions or interventions for each stage. This gap has been addressed by later practitioners and consultants, who advocate targeted facilitation at each stage to help teams progress effectively. Here are brief syntheses of their advice:

• Forming: Leaders should clarify the team’s purpose and objectives, facilitate introductions, define roles and responsibilities, and create opportunities for team members to get to know each other through structured activities or icebreakers.^[46][47]
• Storming: Encourage open, respectful dialogue about differences. Explicitly agree on conflict resolution processes and communication norms while helping members articulate their individual needs and concerns. Leaders should foster psychological safety, moderate conflicts, and set ground rules for productive debate.^[48][49]
• Norming: Recognize progress, celebrate achievements, and reinforce team spirit. Provide opportunities for feedback and self-assessment, give the members room to adjust roles and working methods, and surface problems for group discussion and solution.^[50][51]
• Performing: Maintain high morale, encourage autonomy, and capture learning points for future team development. Leaders should support continued collaboration, facilitate regular reflection, and remove organizational obstacles to allow peak performance.^[52][53]
• Adjourning: Facilitate reflection on achievements and challenges, celebrate individual and group contributions, and help the team draw lessons for future work or teams.^[54]

Critical analysis

Most reviewers see Tuckman’s stages of group development as a historically important, intuitively useful way to describe typical group dynamics. They also criticize it for weak direct empirical testing, overly linear staging, therapy‑group bias in its evidence base, and limited ability to explain how and why teams change over time. Despite these reservations, Tuckman’s model is widely referenced in textbooks, training and online HR materials.^[55][56][57]

A. Main positive assessments

Many educators and practitioners regularly point to three main strengths:

• It is clear and memorable: Commentators note that “forming–storming–norming–performing” (later with “adjourning”) is one of the most quoted and widely recognized models of group development, especially in practitioner‑oriented texts and training. It gives managers and students an accessible language for describing group dynamics.^[58][59]
• Its descriptive fit with many types of groups: Tuckman and Jensen’s 1977 review of 22 empirical studies concluded that published research broadly supported the four original stages and that a fifth “adjourning” stage should be added. Later applied writers say they “still find” the model maps reasonably well to many small work and training groups.^[60][61]
• It is a helpful teaching and reflection tool: University and HR materials (for example, MIT HR and Open University) present the model as a useful guide for helping leaders anticipate predictable tensions and normalize conflict. They stress its value in reducing any stigma around early conflict (“storming”) and highlighting that productive norms and performance usually take time to emerge.^[62][63][64]

B. Main criticisms

Academic commentators raise several recurring limitations:

• Limited direct empirical testing: In Tuckman and Jensen’s “Stages of Small‑Group Development Revisited” article (1977), they noted that only one of the 22 studies they reviewed set out explicitly to test the forming-storming-norming-performing sequence. That led them to call for more empirical studies. Later researchers repeatedly noted that, despite its popularity, the model’s sequence has not been rigorously validated across diverse team types.^[65][66]
• Therapy group and interpersonal sensitivity training (“T”) group bias: Tuckman’s 1965 meta‑analysis drew heavily on therapy and T‑group studies, a potential weakness he acknowledged. Later summaries (e.g. Bonebright’s 2009 review, cited below in the practitioner discussion) point out that this overrepresents groups whose primary purpose is interpersonal learning rather than task performance, raising questions about generalizing the model to work teams.^[67][68]
• Linear staging versus messy reality: Critics in group development research argue that real groups often do not move cleanly through the four or five stages in order. They say some skip stages, go backward, or cycle repeatedly, while others never reach a stable “performing” phase. The Open University’s teaching text warns that Tuckman’s model oversimplifies the complexities of group life and that multiple issues can coexist, meaning they do not always occur in a neat sequence.^[69][70][71]

Experienced field practitioners focus their criticism on practical application limitations:

• Inadequate explanation of the psychological mechanisms underlying the stages: Rickards and Moger (2000) argue that Tuckman’s model “lacks a complete explanation of how groups change over time” and does not address how teams move beyond “norming” to outstanding performance or what happens when storming never resolves.^[72]
• Narrow focus on “average” and “low creativity” groups: Rickards and Moger, writing from an innovation and creativity angle, also criticize the model for saying little about failures (teams that never stabilize) or exceptionally successful teams. They also note that the model neglects creativity in problem solving. Rickards and Moger therefore proposed an alternative, more innovation‑focused framework.^[73]
• The danger of misusing the model by treating it as a fixed reality: Modern critical pieces – for example, Oxford Review’s 2022 “debunking” report and a 2024 critique titled “Tuckman was wrong – what nonsense!” – believe that people often approach the model as a universal law of team life. This, they argue, encourages managers to “force‑fit” their teams into stages and ignore other variables such as organizational design, power and external pressures. They suggest seeing it simply as a historically significant teaching aid.^[74][75]
• No guidance on how to steer a team through the five stages: The original Tuckman model describes the five development stages but offers no suggestions on how to help a team navigate them, limiting its practical usefulness.^[76]

Alongside these critics, many university and HR sources continue to present Tuckman as “still the most used” or “most influential” model of small‑group development. However, they simultaneously flag its empirical question marks and the need to treat it as a rough guide, not a definitive model.^[77]

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators note that: (1) The model’s rhyming mnemonic makes it memorable. (2) It appears to fit the development phases of many training and small work groups. (3) It is a useful guide for anticipating and normalizing issues like group conflict.

• Limitations – (1) There is little reliable test data confirming the five stages theory. (2) The model was largely based on studying therapy and interpersonal sensitivity (“T”) groups, not work teams that must generate outputs and results. (3) It assumes a neat linear progression from stage to stage whereas in real life teams do not always follow such a predictable path. (4) The model does not explain the psychology underpinning a team’s transitions from stage to stage. (5) It does not explain unusually poor or successful teams. (6) It may encourage some practitioners to ‘force‑fit’ team experiences into the five stages, potentially causing misdiagnosis. (7) It offers no guidance to teams wanting to know how to navigate the five stages.

Further information: Tuckman's stages of group development

Development of the model

Belbin and his research team started their work with a simple question: why do some management teams succeed while others of apparently equal intellect fail? The question originated at Henley Management College in the UK in the late 1960s. The Henley staff noticed that repeatedly, when highly capable managers on their senior executive development courses were asked to form temporary management teams and compete in business simulation games, they produced surprisingly poor results. Over time, Belbin and his colleagues realized that the answer flowed not from attendees’ intellects or personalities, but from the mix of behaviors in those teams. This led to the more important longer-term question: what blend of behaviors will tend to yield successful teams?

Belbin and his colleagues spent nine years building their model by studying the participants at the Henley College courses.^[85] During the training, course members formed company teams to compete against one another in management games that delivered financial results with winners and losers. Before starting the games, each team member would complete a battery of psychometric tests.^[86] Throughout the games, Belbin observers sat in the teams’ meeting rooms and recorded who was contributing what behavior at each moment.^[87] The Belbin researchers then compared the psychometric and behavioral data with the teams’ financial results. By following which teams did well, which performed poorly, and what their compositions were, Belbin and his colleagues developed their ideas.

They did not begin with a fixed hypothesis but simply observed patterns that later informed their model and then paid attention to what was missing in teams that ran into difficulties or performed badly.^[88] Over time they discerned what they described as clusters of behavioral attributes that they would later term “team roles”. What follows is the sequence in which the team roles emerged.^[89]

They first noticed that winning teams had at least one person who was good at turning ideas into practical plans and ensuring disciplined action. From this emerged the first team role: Implementer.

However, teams formed entirely of Implementers typically lacked creativity and flexibility. That was because Implementers were not usually the people coming up with the best ideas, especially the most novel breakthrough solutions. Now they started to observe the team members who were good at coming up with new ideas and solving problems in surprising, even unorthodox, ways. These people were playing a second distinct team role, which they called Plant.

While watching out for team members who could offer solutions to problems, the researchers saw that Plants were not the only source of ideas. There were other team members – less intellectual, less imaginative, less introverted, more outgoing – who also brought in ideas. These ideas came from their contact with the outside world. Their suggestions and solutions were not as original as the Plants’ ideas, but they often made an important contribution. The researchers dubbed this third behavioral cluster the Resource Investigator.

By now, Belbin and his colleagues could see that the more successful teams had members who guided the task processes skilfully – people who were good at listening and including colleagues, who could discern good from poor advice, and could consistently guide the team towards wholeheartedly-supported decisions. They gave the name Coordinator to this fourth role.

The researchers noticed that it was not Coordinators who usually decided which of the suggested ideas to act on. Other members were often better at assessing the pros and cons, risks and benefits. This was another clear behavior cluster, which Belbin and his colleagues named the Monitor Evaluator.

As the study continued, it was clear that the less successful teams often descended into conflict and some even excluded members at certain points in the management games. In the better teams they noticed people who were good at helping their teammates knit together, especially at times of stress. For them, it seemed the team was more important than individual self-interest. This team role they named the Teamworker.

Further observation revealed that while some teams did well in the middle part of the game, they fell behind their competitors later because they were not paying attention to the finer points in their planning or execution whereas the winning teams showed more of an eye for detail and followed through relentlessly. Those winning teams had members who paid special attention to details and inconsistencies, so the researchers gave the label of Completer Finisher to this seventh behavior cluster.

As the study continued, the researchers noticed that many successful team leaders on the course were not displaying Coordinator behavior. But they were providing added drive, an extra will to win and a sense of urgency to their teams. They gave the name Shaper to people displaying this behavior. This was the eighth role.

As the years at Henley went by, the researchers realized that balance appeared to be the key to success among the teams they were studying. That is, a balanced blend of roles. It was better, they observed, not to have too many from the same behavioral cluster (team role). For example, they found that teams with no Plant struggled to come up with fresh ideas to move things forward. However, if teams had too many Plants, they could be awash in ideas, the bad ideas would swamp the good ones, and time-wasting solutions would receive too much airtime. As another example, teams without a Shaper often drifted and missed deadlines, but if a team had too many Shapers, the researchers would often observe infighting and team morale would suffer, leading to poor results.

The researchers became increasingly confident in their data and insights as the years unfolded and began forecasting which teams would win the games. After nine years of research, and before concluding in 1979, they were predicting with high accuracy the rankings of all the “companies” participating in the game.^[90]

The ninth role – Specialist – did not emerge during the nine years of research at Henley Management College. It only became visible afterwards in the mid-1980s when the Belbin researchers studied teams in business and realized that they sometimes needed in-depth technical know-how in certain subjects that were central to the team’s objectives.^[91]

Meaning of “team role”

Belbin and his colleagues defined a “team role” as “a tendency to behave, contribute and interrelate with others in a particular way” in a work group.^[92] In this sense, a team role is a recognizable behavioral pattern, not a personality type. In Belbin’s account, a person’s preferred team role can be influenced by the task context (for example, the team’s specific challenge), the organizational context (for example, turnaround, steady-state or high-growth) or accumulated experience over their career. Thus, one person’s preferred team role may vary over time or in different situations. This means that team roles are understood as flexible patterns of contribution that can evolve over time, not fixed personal identities.^[93]

Note that a “team role” is not the same as a person’s functional role. For example, in a management team, one person may be titled Sales Director – that is their functional role. Thus, Belbin was effectively saying that it is important to appoint team members based on their typical behavior in workgroups, not their job title. The implication being that if an organization appoints team members based on functional role (job titles) alone, it may end up with a significant imbalance in team roles.^[94]

The nine Belbin team roles categorized

The Belbin model groups the nine team roles into three categories according to their primary orientation in work groups: Action, People, and Thinking.^[95] This classification helps clarify how the nine behavioral contributions complement one another within a balanced team.​

The Action-oriented roles focus on translating ideas into results and maintaining momentum. They are Shaper, Implementer and Completer Finisher. Individual members displaying these behaviors are typically task-focused, disciplined, and concerned with progress, efficiency and deadlines.

The People-oriented roles center on building relationships, facilitating cooperation, and promoting communication both within the team and beyond. They are Resource Investigator, Teamworker, and Coordinator. Their contributions often involve motivating others, resolving differences, aligning individual strengths with collective goals and gaining enthusiastic consensus.

The Thinking-oriented roles – sometimes described as “intellectual” roles – are Plant, Monitor Evaluator and Specialist. These members contribute through imagination, analysis, or deep subject expertise, helping teams to form new ideas, assess choices, and apply technical knowledge.

Belbin proposed that successful teams typically achieve balance by drawing on contributions from all three categories.^[96] This ensures that tasks, relationships, and ideas are all represented in team functioning.

Belbin also stressed that the nine roles do not mean that every successful team needs at least nine members. That is because many people can play two roles and, occasionally, three roles well.^[97]

Team role descriptions including weaknesses

Each of the nine team roles brings a distinct beneficial contribution to the team’s functioning and success, as follows:

These positive aspects of each role’s cluster of behaviours are matched with what Belbin called “allowable” and “non-allowable” weaknesses.

Allowable weaknesses are the predictable, tolerable downsides that accompany a person’s team role strengths. They represent the natural accompaniment to the behaviors that give that role its distinctive contribution. For example, a Plant’s strength in creativity might be shadowed by absent-mindedness, or a Shaper’s drive by occasional irritability. These weaknesses are “allowable” because they arise directly from the role’s added value to the team – the same behavioral energy that fuels the strength can, when overplayed or viewed from another angle, appear as a minor limitation. Teams can accept these trade-offs as part of the balance of roles.

Non-allowable weaknesses occur when a person either:

• Displays weaknesses without the corresponding strength (e.g., a Shaper who is aggressive but avoids decisions or lacks direction).
• Overplays a strength to the point that it diminishes performance or trust (e.g., a Completer Finisher whose perfectionism causes delay).

In these cases, the weakness stops being a natural companion to the strength and instead becomes a behavior that undermines the team’s effectiveness and needs attention. This table summarizes each Belbin team role’s allowable and non-allowable weaknesses:

Again, bear in mind that the nine roles do not mean that all teams need at least nine members as many people can play two roles and, occasionally, three roles well.^[148]

Belbin's caveat

There is a caveat. Belbin’s original 1970s research revealed that he and his researchers could not find a viable added-value role for 30% of the participants on the Henley Management College courses.^[149] However, this was before the addition of the Specialist role, meaning the 30% figure is overstated in the context of the modern nine-role model. Also, one could argue that perhaps the test population, being biased towards intellectually oriented, ambitious, competitive people in their late 30s and upwards, was not representative of the wider population. Thus, we do not know what the “no viable role” percentage is today. The main point is that Belbin’s research showed that there are people who, although individually effective, struggle to work successfully and add value in a team context. That adds a layer of complexity in applying the Belbin model but, in doing so, arguably helps its claim to represent the real-world facts about people’s behavior in teams.^[150]

Applying the Belbin team roles model

Commentators describe the value of the Belbin Team Roles model as lying not simply in identifying nine behavioral patterns but also in how teams use them in practice. Thus, this section outlines the main ways the model is applied – to select team members, to improve their collaboration, and to balance their strengths and weaknesses in real work contexts.

An official Belbin-hosted webinar featuring practitioner advice sets out a four-part approach to applying the model with existing teams. According to this approach, successful application usually relies on four foundations.^[151][152]

First, the team creates, at least on paper, a balanced blend of team roles among members. It does so by using Belbin self-assessment and observer questionnaires to identify which roles each member can play well, which they cannot, and the overall team profile. From this come individual reports showing which roles members can play easily (typically a first and second role, sometimes a third). It also creates a team overview report mapping the distribution of roles, helping the team spot important gaps and potential overloads. For example, a team with no strong Implementer or Completer Finisher would suggest that a lack of action follow-through is a genuine risk. Or instead, a team with many Shapers but no Teamworkers, would probably find it harder to agree on priorities, goals or plans. The same practitioner discourse notes that such imbalances may lead teams to recruit extra members or encourage existing members to draw more consciously on their secondary or tertiary roles.^{[153][154][155]}

The same source identifies “Appreciating others’ roles” as a second foundation. Here, team members are helped to understand and value the roles they cannot naturally play well – roles that others play better. This helps them recognize when colleagues are supplying those behaviors and why they matter to the team’s performance. This in turn makes it easier for their teammates to bring in that role’s behavior when needed. The Belbin webinar recommends combining simple explanations of each role’s added value with experiential learning – for example, exercises in which quieter members can display their strengths. The idea is to build mutual respect and appreciation for different role contributions.^[156][157]

A third foundation is described as “Learning how to play roles well”. It focuses on clarifying what effective behavior in each preferred role looks like in action, including both what to do and what to avoid – the behavioral “Dos and Don’ts” associated with that role. This would include steering clear of non-allowable weaknesses. The same approach also stresses the importance of recognizing “trigger moments” signaling when to bring in specific role behaviors (as teams do not usually need every role all of the time). The webinar advice suggests pre-planned behavioral scenarios and facilitated feedback to help members practice bringing in their roles at the best moments rather than using them indiscriminately.^[158]

The fourth foundation in this practitioner framework is “Flexing roles while building relationships”. This centers on helping team members grow their skill in recognizing when to switch their focus towards their secondary roles (or third role if they have one) when changing circumstances mean a different role would serve the team better. In parallel with learning how to flex roles, this framework emphasizes trust and respect building to help members understand one another’s motives and believe in their ability to deliver. Scenario-based exercises are suggested as a way of quickening this phase.^[159]

Thus, even if, on paper, the team’s blend of roles looks good, team members are advised to apply a conscious effort until their attitudes to one another and behavioral skill in action becomes second nature. Also, teams experiencing significant changes in membership are advised to revisit these four application fundamentals to restore or maintain balance.

In practice, although the Belbin Team Roles model has these four foundations for effective teamwork, organizations and individual teams often emphasize only the first: the initial mapping and balancing of roles. Consequently, the elements of role appreciation, skill development, and behavioral flexibility may be overlooked. This can reduce the model’s intended payoffs.^[160]

Belbin in the wider context of team building

The Belbin team roles model is a tool for improving collaboration within teams through achieving a balanced blend of role behaviors. However, it represents only one part of successful team building.

A strong blend of roles may indeed boost the team’s problem-solving ability, creativity, and adaptability. Nevertheless, it does not, by itself, address all the key ingredients to lasting team success.

For example, most experts and commentators in the field of team building believe that teams also need a clear and motivating shared purpose to give them a unifying cause and to spark energy.^[161][162] Teams lacking such a purpose – even well-balanced teams – may lack focus, commitment or cohesion.^[163] Also, how a team organizes its work – such as its communication norms and ways of resolving conflict – is seen as having a big impact on its results.^[164][165] Furthermore, teams need to agree how they will reach decisions and navigate disagreements. This is essential if teams are to ensure all members speak up and prevent hidden dissent or false consensus undermining results.^[166][167] Equally essential, in the view of most team building consultants and coaches, is the feeling among team members that they can say what they are really thinking and feeling.^[168] The best teams, they argue, encourage honest conversations, allowing members to challenge one another constructively and surface differing opinions without fear of punishment.^[169] Therefore, team role balancing alone may not be enough to shape these team qualities.^[170]

Thus, while Belbin’s model contributes valuable insights into team composition and behavior, it is wise to view it as a key piece in a broader approach to team building, not as a complete solution.

Critical analysis

Commentators describe Belbin’s Team Roles model as a useful, easy‑to‑grasp way of thinking about how people contribute in teams, but some also note concerns about its psychometric robustness, theoretical clarity and performance claims.^{[171][172][173]}

A. Main positive assessments

Commentators highlight four main strengths:

• Clear, understandable team role labels: Practitioner and educational sources note that Belbin offers an easily understood language for describing preferred team role contributions (for example, Plant, Implementer, Coordinator). This can help people grasp, discuss and appreciate role strengths and associated “allowable weaknesses” without making many in-team behaviors seem inappropriate or extreme. These sources say this shared vocabulary supports self‑awareness, mutual understanding and conversations about role allocation in teams.^[174][175]

• Importance of a balanced blend of team roles: Belbin is widely credited with drawing attention away from individual “stars” towards the value of complementary roles within a team. Some applied studies, such as Aritzeta’s work on management teams and later empirical summaries, report associations between indicators of team‑role coverage or balance and ratings of team effectiveness, which supporters present as empirical backing for this emphasis on role complementarity. These findings are often used in teaching and training materials to illustrate how a spread of different role contributions may help teams handle complex tasks.^[176][177]

• Wide acceptance: Reviews of team role research point out that Belbin’s updated assessment tool and analysis system has seen extensive use in UK organizations and consultancies for training, development and, in some cases, selection. Authors interpret this broad uptake as evidence that many managers and field practitioners experience the framework as useful, even where academic opinion remains divided about its scientific status.^{[178][179][180]}

• Research‑based origins and predictive success: Practitioner writers and Belbin’s own accounts emphasize that the model was derived from a nine‑year research program at Henley Management College in the UK. This research combined intelligence tests, personality measures and detailed behavioral observation of management‑game teams. Belbin reports that, by the end of his research, he could predict with high accuracy which teams would perform best and worst in the exercises. One later practitioner summary claims that Belbin correctly identified winning and losing teams in 86% of cases.^[181] This predictive success is presented by practitioners as an important reason why many managers and consultants regard the model as valuable.^{[182][183][184]}

B. Main criticisms

First, academic – especially psychometric – criticism, which centers on concerns about the reliability and validity of the Belbin assessment tool.

• In 1993, using an early version of the Belbin questionnaire, Furnham et al reported that people’s scores did not line up in a clear and repeatable way with the nine roles described in the model, which led them to question whether that version of the tool was really picking out nine distinct roles in the data. Belbin replied that the Team Role Self‑Perception Inventory was designed primarily as a practical aid for management consulting and team discussions, not as a conventional psychometric instrument. He therefore questioned whether applying standard psychometric tests was appropriate. (Later materials from the Belbin organization argue that subsequent, more sophisticated versions of the inventory have improved its reliability and validity.)^[185][186]

• Some years later, a widely cited 2007 validation study by Aritzeta, Swailes and Senior examined Belbin roles using the Belbin questionnaire alongside personality and other psychological measures. They reached two conclusions. One that the model tries to distinguish more roles than the evidence supports. Two, that people’s Belbin profiles overlap so strongly with familiar “Big Five” personality traits that it is hard to show the roles are measuring something genuinely distinct and, by implication, that the model may add little beyond what well‑established personality frameworks already provide.^[187]

• In 2014, Paul Englert revisited Belbin’s Team‑Role Self‑Perception Inventory, drawing on Furnham and later psychometric studies, and argued that, despite subsequent revisions, the evidence for treating the inventory as a scientifically robust test remains limited. He concluded it should not be relied on for decisions about hiring, promotion or other important personnel choices.^[188]

Next, practical and application‑level concerns focusing on how – and indeed if – the Belbin model works in practice.

• Case studies and project management sources note that people often show more than one team role and may shift their preferred role over time. Also, they point out that organizational factors such as structure, culture, leadership style and task characteristics strongly shape team behavior, meaning that seeing the Belbin model as a fixed set of nine roles may encourage pigeonholing and oversimplify team dynamics. These authors typically recommend using the framework flexibly and avoiding rigid labelling of individuals.^[189]

• Empirical tests of Belbin’s core claim that teams covering all or most roles will perform better have produced mixed findings. Studies in work and educational settings frequently report only partial or context‑dependent support, leading researchers to caution that role diversity is not, by itself, a guarantee of higher performance. They suggest that task demands and situational factors also remain crucial.^[190]

These points illustrate how much of the academic discussion of Belbin has centered on psychometric evaluations of its assessment tool and on tests of performance claims, whereas practitioners emphasize the original Henley research, its predictive value and the model’s perceived usefulness in organizational settings. This had led to a generally more enthusiastic stance among users than among academic reviewers.

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators note that: (1) The model offers easy-to-understand role labels that flag up the complementarity between in-team roles and their difference versus “day job” functions, e.g. Sales Manager. (2) It has highlighted the importance of a balanced blend of team roles. (3) It was based on nine years of research which showed high predictive accuracy. (4) It has become widely used, especially in the UK, suggesting that managers, team members and field practitioners judge the model to be useful.

• Limitations – Critics say that: (1) The early version of the Belbin assessment tool had questionable validity. (2) The model may not add much beyond what some pre-existing personality tests could offer. (3) There is still some doubt about the updated Belbin inventory’s robustness. (4) Team members may be shown to have more than one viable team role, meaning that it is important not to misapply the model by pigeonholing individuals. (5) Belbin’s core idea that role diversity in a team is genuinely a predictor of its success is still debatable.

Further information: Team Role Inventories

Background and development of the model

Richard Hackman began studying team dynamics in the late 1960s and 1970s at Yale University, where he taught and conducted research. He continued refining his ideas over several decades – first at Yale and, from 1986 onward, at Harvard University.^[197] His research set out to answer the question of what makes teams successful drawing on empirical studies in industries such as aviation and music, and on fieldwork with collaborators.^[198]

Through these studies, Hackman developed his conditions-based approach, emphasizing the systemic features that leaders and organizations can establish in advance to foster sustainable, high-quality team performance. While outcome measures such as results and customer satisfaction had been widely used in earlier research, Hackman advanced the field by identifying and integrating the systemic and contextual conditions that support team effectiveness – clear team boundaries, ongoing support and enabling structures – as well as specifying three core criteria for judging a team’s success.^[199]

Although Hackman’s framework has been widely cited and adapted by other researchers and practitioners for varied team types, according to his published research the model itself was primarily developed and tested through studies of symphony orchestras, airline cockpit crews, economic analyst groups and manufacturing teams.^[200] There is limited evidence of Hackman conducting empirical research or refining his model in other settings, such as management or cross-functional project teams, before publication of Leading Teams (2002).^[201][202]

Today, Hackman’s framework is referenced in academic research and applied organizational settings as a guide for improving team effectiveness. It often appears alongside other foundational models such as those described in this article on "contemporary models of team building" but is distinct in its focus on the underlying conditions and context that drive team success, rather than on team maturation phases, interpersonal group dynamics, or prescriptive team building techniques.

Team effectiveness

Hackman lists three criteria for judging a team’s effectiveness:^[203]

1. Is the team delivering results that meet or exceed its customers’ expectations?
2. Is it becoming increasingly capable?
3. Is working in the team giving its individual members an experience of personal learning and fulfilment?

Hackman argues that these three criteria can be used to judge the effectiveness of any work team, regardless of its specific task or context.

However, he points out that the relative importance of the three criteria can vary according to circumstances. For example, if a project team is striving to accomplish an unusually important task, the second and third criteria would be less important in judging its effectiveness. Then again, if the task focuses primarily on the team members’ learning, the second and third criteria may be the key ones.^[204]

Core concepts and framework

Hackman’s central idea is that teams underperform or perform badly versus the three criteria when leaders pay insufficient attention to what matters most in designing and supporting them or, instead, fail to pay attention at the right moments. What matters most according to Hackman are the five enabling conditions that he believes drive team effectiveness.^[205] In his view, there is a greater likelihood of a successful team emerging when:

1. It is a real team, not a team in name only.
2. It has a compelling direction for its work.
3. It has an enabling structure that facilitates – not impedes – teamwork.
4. It operates within a supportive organizational context.
5. It has sufficient support from expert coaching in team building.

Hackman describes the first three as the core conditions for team effectiveness – they represent a good basic design – while conditions four and five are the supporting conditions.^[206]

Hackman contends that when leaders concentrate on creating and sustaining these conditions, teams can perform superbly. Thus, the model’s logic is that these conditions are enabling not determinative: they allow teams to perform well but do not ensure that every team will do so.^[207]

Hackman views the leader’s role as guiding the team onto a positive trajectory, making timely adjustments as necessary, rather than constantly intervening in response to team members’ behaviors. In Hackman’s model, the leader acts more as a facilitator than a controller. By focusing on shaping the right conditions, leaders can increase the likelihood of team success – but ultimate outcomes depend on how team members respond to those conditions, meaning success cannot be guaranteed.^[208]

Hackman stresses the importance of timing. Some leader interventions have their greatest impact at the start of a team’s life. Other actions may make the biggest difference at what we might call the midpoint of a team’s evolution and others when the team has completed a major task. In Hackman’s view, when leaders intervene with the wrong initiative at the wrong time, not only will they make little positive difference, they may make things worse.^[209]

As Hackman sees it, anyone who adds team-enhancing conditions or contributes to strengthening them is demonstrating leadership. That might come from the official team leader, but it could equally come from another team member or someone outside the team like an external manager, a coach or a consultant.^[210]

The challenge for team leaders, in Hackman’s view, is to grasp the complexities and subtleties of the five conditions and translate them into strategies for applying them even in organizational conditions that may resist teams and team building; for example, if the organization has a strongly individualistic culture.

For practitioners, Hackman positions the five conditions as essential requirements for team effectiveness, and recommends that those in team leadership or design roles attend to all five areas to create the foundation for team success.^[211]

Thus, Hackman’s model guides leaders to step back and build strong foundations through attention to the five foundations rather than simply react to intra-team problems.

Deeper dive into the five supporting conditions

A sixth condition?

Readers interested in Hackman’s Five Conditions model may notice if they search for more information on the internet that Hackman is often associated with a model delineating six conditions. This prompts the question, is there a sixth general enabling condition for effective teams?

In 2008, Hackman co-authored a book titled, Senior Management Teams: What it takes to make them great.^[219] With the help of his three co-authors, Hackman widened his attention to CEOs and their top teams. The result was a model with six conditions. However, on closer inspection, the six conditions resemble the original five except that the third original condition, Enabling Structure – in which team size and composition was a key element – has been broken into two conditions. Thus, the six conditions closely resemble the original five; the main difference is that team composition has been given extra emphasis as Hackman and his colleagues judged that it deserved more attention in the context of senior management teams.^[220]

Hackman and his colleagues called this sixth condition, “Get the Right People in Your Team – and the Wrong Ones off.” Essentially, this was a refinement of his earlier thinking on team composition. He challenged the idea that all direct reports of CEOs should automatically be on the top team and offered this advice for corporate leaders:^[221]

• Choose members that can understand and represent the entire enterprise and are ready to do so, meaning they are prepared to make decisions that benefit the whole company even if their part of it loses out.
• Ensure diverse viewpoints.
• Ensure that every member has sufficient empathy, enabling them to connect with and influence their teammates sensitively and skilfully.
• Ensure that every member has high-level conceptual thinking ability.
• Pay attention to onboarding of new members.
• Eliminate serious derailers.
• Plan for the future by having substitutes ready for when people leave or retire.

So for effective teams in general, there are still only five enabling conditions, but in the specific case of senior management teams, there are six, because Hackman believed their composition requires extra care.

Application of the model

Although Hackman, like Scouller, draws a distinction between “the leader” and “leadership”, arguing that anyone inside or outside the team who displays leadership behavior that influences the team is in fact leading, he mainly focuses on the official team leader when referring to “the leader”.^{[222][223][224]}

He stresses that team leaders are important to the team’s performance in the sense of what they do and fail to do. However, he counsels readers to be careful of what he calls the “leader attribution error” when the team performs either poorly or superbly as he feels there is too strong a tendency to explain the team’s success or failure as result of the official leader’s behavior.^[225] Nevertheless, Hackman maintains that official team leaders remain a key influence on results.

Hackman lists what he believes effective leaders do – be they the official leader, another team member, or an influential person outside the team – although he does not offer guidance on how leaders should address these points. In his view they should, above all, attend to the five basic enabling conditions (or, for senior teams, six conditions) as these set the stage for team success. They do not guarantee the team will be effective, but they do increase the likelihood that it will succeed.^[226] Therefore, he advises, they should do five things:

• First, make sure they have created a real team with stable membership over time. In doing so, they judge whether the central task really needs a team. Thus, they do not attempt to create a team if the main task does not demand a collective effort to which every member must contribute.
• Second, provide it with a compelling direction.
• Third, fine-tune the team structure so it fosters (not impedes) teamwork.
• Fourth, tweak (if they can) the supporting organizational structures and systems to provide the support and resources the team needs.
• Fifth, arrange for – or themselves provide – expert coaching to take advantage of the four conditions already in place.

Hackman cautions against a universal formula. He argues that every team leader must perform their role in his or her own unique way, staying true to themselves. Just as important, team leaders must intervene at the right times because acting at the wrong moments can be counterproductive. This means moving quickly and decisively when opportunities for action show themselves but not trying to force interventions when the time is not right. Hackman does not offer advice on how to make these timing judgements.^[227]

Hackman also advises team leaders to keep their eyes on all three effectiveness criteria in the long term – delivering results, becoming increasingly capable, providing learning and fulfilment – not just the first.^[228]

The overall key, in Hackman’s view, is to “stack the deck” by getting the first four conditions right before bringing in expert coaching. In his view, the sequence of interventions is all-important, with the first four being the most powerful. In this way, in his view, team leaders should see themselves more as team architects than team controllers.^[229]

Practical application of Hackman’s model therefore means periodically “auditing” existing teams and new team initiatives through the lens of his five conditions; diagnosing which are robust or deficient, and choosing interventions accordingly. He does not provide detailed templates, tools or checklists, instead putting all his emphasis on creating the right conditions before bringing in coaching.

Hackman closes his “application of the enabling conditions” advice by pointing out two “exogenous factors” that can sink even well-designed, well-coached teams. The first he labels the Co-Op Obstacle.^[230] He remarks that a surprisingly large number of failures occur among work teams in cooperative organizations. He attributes this to the overuse of teams when they are not needed or their ill-judged composition due to emphasizing personal relationships when selecting members over robust assessment of which skills are needed. The second he calls the Corporate Obstacle – he reference companies where the cultural emphasis is on individual achievement, meaning that teamwork and team building is unnatural in that environment.^[231]

Critical analysis

Many writers see Hackman’s Five Conditions model as one of the strongest, most research‑based frameworks for explaining what makes teams work well or perform poorly. But they also say it is hard to put into practice, pays only partial attention to how the wider organization shapes the team, and is better at helping leaders spot problems than at giving clear, practical guidance on what to do about them.^[232][233]

A. Main positive assessments

Writers drawing on Hackman’s Leading Teams book (and his later six‑conditions work with Wageman et al) emphasize three recurring strengths:

• Strong empirical and theoretical foundation: Reviews of Hackman’s work present the model as distilled from decades of research on teams, making it more evidence‑based than many consultancy models. It is often described, usually by academics, as “research‑backed”, “rigorous” and “one of the most influential” team‑effectiveness frameworks in organizational psychology.^[234][235]
• Conditions, not heroic single leadership: Commentators highlight Hackman’s shift from “fixing teams” to “designing five conditions for successful teams” (this later became six conditions). Reviewers praised this approach for giving leaders a systemic lens that focuses on team design and context instead of leader personality or leadership style.^[236][237]
• Predictive and practical diagnostic value: Reviews in healthcare and human-resources literature report that several of Hackman’s basic conditions – especially having a real team, a clear purpose and a workable structure – are associated with better team quality, learning and performance in a range of settings. For this reason, some commentators treat the model as a useful tool for diagnosing where a team may need attention or support.^[238][239]

B. Main criticisms

Conceptual or academic critiques of Hackman’s model usually come from authors who build on it rather than reject it outright. They tend to argue that it offers a strong foundation but does not fully capture the wider systems in which teams operate or the informal psychological dynamics that develop over time.^[240][241]

• Underemphasis of broader system issues: Some researchers who study how to embed new practices into organizations argue that, although Hackman does include organizational context as one of his five conditions (for example, reward systems, information systems, educational support, money and an absence of inter-team conflict), his model still mainly describes what is needed inside a single team. In their view, it says relatively little about how that team connects with other teams or with the wider organization, which matters because many real-world projects depend on several teams working together. They therefore keep Hackman's conditions as a useful core but embed them in broader frameworks that add cross-team links.^[242]
• Emphasis on design over emergent forces: Other theorists suggest that Hackman’s model concentrates on the parts of teamwork that team members can design – like goals, composition, structure and formal support – and gives less attention to informal forces that emerge over time, such as politics, identity and power relations. “Politics” refers to behind-the-scenes-influence tactics and alliances; “identity” to how people see themselves and others in the team and how those views shape who speaks up and is heard and who does not; and “power relations” to unequal influence over decisions and how that affects what members feel able or safe to say or do, and also their commitment. Thus, in those commentators’ view, Hackman’s conditions are a necessary foundation for effective teams, but do not fully explain how real teams behave once these less controllable dynamics start to influence members’ actions.^[243][244]

Field practitioners who adopt Hackman’s model also highlight limitations when leaders try to use it in real-life organizations:

• Resource-intensiveness versus organizational constraints: Recent practice pieces aimed at managers note that fully implementing all five conditions can be "resource-intensive" and "demanding". They say this is especially true where leaders have limited control over who is in the team, how stable the membership is, how people are rewarded, or how the wider organization is structured and managed. They note that Hackman’s model implicitly assumes a degree of design authority that many mid-level team leaders do not have.^[245][246]
• Complexity and perceived abstraction: Some leadership development writers say that, compared with simple visual models and personality-type tools frequently used in training, Hackman's conditions can feel abstract and theory-heavy. They add that it often takes skilled facilitation to turn the ideas into clear action steps. They explain that this is why some newer practitioner models offer short checklists “based on Hackman" to make the approach easier for managers to use.^[247][248]
• Limited “how‑to” guidance: While Hackman’s team effectiveness model and the later joint Hackman-Wageman paper on team coaching (2005) clarify when coaching is most useful, they are less prescriptive about specific techniques, so practitioners often combine them with other process tools..^[249][250]

Overall, most commentators view Hackman’s conditions as a rigorous, research-based foundation for designing effective teams. However, they also argue that it can be hard to apply fully in everyday team settings and underplays political and larger organizational realities.

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators note that: (1) The model is evidence-based following years of research. (2) It shifts the focus on team development away from the team leader’s qualities towards creating the right foundational conditions. (3) Research has shown that many of the model’s five conditions correlate with better team quality, learning and performance.
• Limitations – Critics say that: (1) The model ignores teams’ connections with other teams or with the wider organization, which matters because projects often depend on several teams working together. (2) Hackman’s model focuses on what team members can consciously design but gives less attention to forces like politics, identity and power relations than can influence a team’s success. (3) Applying the model may not be achievable as team members do not always control the forces affecting the team’s performance. (4) The model is conceptually strong but offers little how-to guidance, meaning it feels concept-heavy and abstract to some people in the field.

The big picture

According to Katzenbach and Smith, many people don’t easily adapt to – or welcome the challenge of – taking on responsibility for the performance of others.^[254] Nor, according to their research, do most people take easily to the idea of others assuming responsibility for them.^[255] They see this reluctance as a reason to focus on the “team basics” shown in the diagram, which summarizes their model.^[256]

The outer circle, broken into three segments, depicts what teams deliver – Collective Work Products, Performance & Results, and Personal Growth for the members.^[257] This, in other words, is how Katzenbach & Smith see every team’s fundamental purpose, its reason for being, regardless of its specific circumstances.^[258]

The three segments of the inner circle outline the three “discipline zones” (Skills, Accountability and Commitment) and what is needed below those headings (the basic disciplines).^[259] Katzenbach and Smith argue that if the team focuses on performance, results, and the three discipline zones, a genuine team will emerge. They note that this is different to trying to “become a team” by working on “teamwork” alone.^[260]

For Katzenbach & Smith, “teamwork” has a specific meaning. To them, the term refers to norms and values associated with helpful behaviors like listening, responding sensitively, skillfully and non-defensively to opposing points of view, supporting colleagues who need help, and publicly praising teammates’ achievements. In their view, “teamwork” helps members bond, communicate and work better together. However, Katzenbach and Smith argue that teamwork is not the sole province of teams and, even more important, it is not enough to guarantee superb team performance. Thus, Katzenbach and Smith contend, it is essential not to confuse teamwork with teams.^[261]

For them, a genuine team is distinguished by its deep commitment to its purpose, its specific goals, its strategy, its agreed working approach and, ultimately, performance and results. While Katzenbach & Smith believed that all successful teams focus on every segment of the outer circle – Performance & Results, Collective Work Products, Personal Growth – they regarded the performance challenge as the unifying driver behind these elements.^[262] Katzenbach and Smith operationalized the three discipline zones through six specific, observable basics that teams are expected to focus on, which they present as the core building blocks of real teams.

The six team basics

Before getting into the basics, Katzenbach & Smith define what they see as a genuine team because the word “team” connotes different things to different people. For example, some people think that any group that works together is a team. Others believe that a group practicing “teamwork” is a team.^[263]

The authors disagree. They define a team like this: “a team is a small number of people with complementary skills who are committed to a common purpose, performance goals and working approach for which they hold themselves mutually accountable".^[264] Katzenbach & Smith use the key phrases in this definition to identify the three ‘discipline zones’ – Skills, Commitment and Accountability – which in turn yield the six basic disciplines in their model. The disciplines are described in more detail below.

Katzenbach & Smith offer a useful checklist for assessing these six elements of a successful team.^[272]

Team performance curve

Building on these six basics, Katzenbach and Smith proposed a “team performance curve” to describe how groups can progress from loose working groups to real teams and sometimes onward to high-performance teams as they deepen their commitment to purpose, goals, working approach and mutual accountability.^[273] The curve (shown in the diagram here as a conceptual spectrum) is not a precise measurement tool; it illustrates typical patterns that Katzenbach & Smith observed across the teams they studied including business units at Motorola and Hewlett‑Packard, a Desert Storm logistics team and the Girl Scouts.

On the far left of the spectrum’s main development path, demonstrating the least unity, weakest results and poorest impact, is a working group. This is a collection of individuals who exchange information and sometimes coordinate activities, but whose primary focus is on individual rather than collective results because their purpose means there is no need for a genuine team. Such groups may share a broad company mission statement, but they lack shared performance goals, collective work outputs, a joint working approach and mutual accountability. They may meet to share information, best practices and updates, and perhaps reach collective decisions, but that is all.^[274]

A potential team shows greater promise than a working group born of need because it has a performance requirement that a working group approach will not deliver. Its members recognize the need for a common purpose, specific goals and a shared approach, but have not yet translated that intention into disciplined behavior. For example, the members will not have yet established collective accountability. However, with focused effort on clarifying goals, agreeing ways of working and confronting performance issues, potential teams can move towards becoming real teams.^[275]

A real team matches Katzenbach and Smith’s formal definition: a small number of people with complementary skills who are committed to a common purpose, specific performance goals and a shared working approach, and who hold themselves mutually accountable. At this level, real teams generate collective work products that go beyond the sum of individual contributions and achieve consistently higher unity, performance and impact than working groups. A real team is what many people would call a high-performing team.^[276]

At the far right of the spectrum is a high‑performance team. It meets all the conditions of a real (i.e. high-performing) team but goes beyond to an even higher level. It not only delivers outstanding collective results but also fosters unusually high levels of mutual commitment, learning and personal growth for its members. Katzenbach and Smith saw such teams as rare in the business world and argued that they emerge organically when people care as much about one another’s success and development as they do about the team’s performance outcomes.^[277][278] Special forces units such as the British SAS and the U.S. Army’s Delta Force are sometimes cited as examples of high‑performance teams.^[279]

A pseudo‑team sits below the spectrum as it is on a path of its own – a derailment path. It is a working group for which there could be a challenging performance need or opportunity that it cannot achieve with a working‑group discipline. However, it has not focused on collective performance. Its members may claim to be a team, yet they do not apply the basic disciplines. For example, there is usually no clear common purpose, no collective work product, no agreed performance goals and no mutual accountability. Katzenbach and Smith note that such groups may channel energy into “togetherness” or generic “teamwork” activities, but this does not translate into improved collective performance because that is not really their number one aim. As a result, their interactions tend to detract from each member’s individual performance without delivering any joint benefit. Thus, the pseudo‑team’s results usually fall below those of an ordinary working group. Of all five types of work group, pseudo‑teams offer the weakest performance impact, which is why Katzenbach and Smith regard them as a condition to avoid.^[280]

Applications and influence

Since the mid-1990s, Katzenbach and Smith’s framework has been used in management education, team‑building workshops and coaching programs to clarify what distinguishes real teams from looser working groups.^[281] Some practitioner guides and training materials present the six basics as a checklist for new project teams and as a diagnostic lens for teams struggling with performance or accountability.^[282]

The model has also been incorporated into project and program management frameworks, such as the Praxis Framework, which uses it to emphasize small, cross‑functional teams with clear goals and mutual accountability.^[283] Later writers on teams and leadership, including James Scouller, have drawn on Katzenbach and Smith’s research as one of the empirical bases for their own models, indicating its longer‑term influence on the team‑effectiveness literature.^[284]

Katzenbach and Smith’s six‑basics model emphasizes behavioral disciplines such as agreeing a working approach and practicing mutual accountability but offers little explicit analysis of underlying team psychology (for example, trust, power dynamics and psychological safety). Later frameworks, including those of Lencioni and Scouller, place such psychological factors at the center of their explanations of how teams develop and sustain effectiveness, while still acknowledging performance discipline and mutual accountability as important foundations. In this sense, Katzenbach and Smith’s work helped shape a practitioner discourse in which subsequent models sought to make the psychological underpinnings of teamwork more explicit.^{[285][286][287]}

Critical analysis

Many writers see Katzenbach and Smith’s ideas in The Wisdom of Teams as a clear, practical explanation of what makes a performance‑focused team different from an ordinary work group. They also describe it as a set of recommended “good practices” drawn mainly from case examples, rather than as a theory tested by formal research. They argue too that it lacks guidance on how team members’ feelings, relationships and learning processes develop over time. Critics also say the model says little about how to build trust, how people can handle fear of conflict, and how a group grows from a new team into a mature one, or regresses.^[288][289]

A. Main positive assessments

Supporters highlight four main strengths:

• Practical, performance‑centered focus: Writers say the model helps managers focus on demanding performance goals, mutual accountability and concrete shared work, rather than vague ideas of teamwork or harmony.^[290][291]
• Clear “team building basics”: Reviews describe the basics (small number of people, common purpose, specific performance goals, complementary skills, mutual accountability, common approach) as a straightforward discipline that helps decide when a team is needed (or not) and how to set it up.^[292][293]
• Useful distinctions: Practitioners and educators regard the performance curve (working group, potential team, real team, high-performance team) as a helpful way to label different work groups and recognize their advantages and disadvantages. It is also good for warning about “pseudo-teams” as they can perform worse than ordinary working groups.^[294][295]
• Grounded in rich case material: Business school and project management commentators point to the many examples from business and other settings as making the ideas easy to grasp for executives and project leaders wanting to apply them.^[296]

Warwick Business School’s 2024 article, for instance, calls the framework “a powerful bridge from observation to disciplined practice”, while project management writers report using the questions and basics as a practical checklist for high-performing work teams.^[297][298]

B. Main criticisms

Academically oriented critics point to limits in the model’s theoretical and research base.

• Limited testing: Some evidence‑based reviews of team models say that, although the Katzenbach and Smith framework is widely used, there is little scientific testing of its “team basics” or “performance curve” as a formal theory. This means managers cannot be sure, from research evidence alone, that following the basics will reliably produce better team performance in different settings. Thus, the reviews treat the model as practice‑based guidance drawn from case studies and consultant judgement, not a model whose cause‑and‑effect claims have been confirmed by controlled studies.^[299][300]
• Limited treatment of team psychology: Some authors point out that, compared with later work by Richard Hackman or Amy Edmondson, Katzenbach and Smith say relatively little about psychological safety, fear of conflict or other deeper emotional obstacles to team success. Instead, emphasis is on performance goals, complementary skills, agreed ways of working and mutual accountability.^[301][302]
• Over-simplified view of change: Some commentators argue that the team performance curve is too simple for describing how real teams change over time. They say it shows a one‑way path from working group to potential team to high‑performing team but does not really explain how teams sometimes regress as well as go forwards, or what happens when key people join or leave. These writers also point out that the curve says little about how teams behave inside complex networks of teams, where people sit on several teams at once. Because of this, they tend to treat the curve as a helpful way of labelling different kinds of work groups, not a strong, research-based explanation of how and why teams develop over time.^[303][304]

Experienced field practitioners who value the model also comment on how hard it can be to apply in real organizations or indeed how to judge when to apply it:

• Necessary but not sufficient: A widely cited 2008 review on an agile‑methods blog describes the six basic disciplines as “necessary but not sufficient” for producing a real team. It argues that personality clashes, culture and organizational barriers can prevent a team forming even when the basics are in place, meaning it is incomplete, that other keys are missing from the model.^[305]
• When not to use teams: Although Katzenbach and Smith warn that not all work should be done by teams, some training company commentators say that readers still treat their model as encouragement to create more teams everywhere. They argue that ignoring the “when to team and when to stick to a working group” guidance can lead to pseudo‑teams.^[306][307]

In sum, respected commentators see Katzenbach and Smith’s model as a landmark, performance-oriented team building model that sharpened thinking about “real teams”, “pseudo-teams” and ordinary working groups. They also see it as a largely case-based framework not a well-tested research-based model. These writers often recommend using it alongside newer, research-based models that focus more on how people relate and feel in teams – for example, on psychological safety – and how well team members understand and use each other’s knowledge.^[308][309]

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators note that: (1) The model highlights the need for would-be teams to focus on performance and doing creative and problem-solving work together, not abstract notions of harmony and “teamwork”. (2) It lays out the six basic disciplines all small work groups must apply to become and stay successful teams. (3) It helps people working in organizations to distinguish between working groups, genuine teams, high-performance teams and pseudo-teams and grasp their advantages, disadvantages and dangers. (4) It is based on research and grounded in numerous case studies.
• Limitations – Critics say that: (1) The model is based upon case studies and has not been tested through empirical studies. (2) It ignores psychological complications and challenges that can make a team’s application of the six disciplines more difficult – like a lack of trust, fear of conflict, or fear of holding one another accountable. (3) The performance curve is an over-simplification, meaning it does not fully explain how teams progress or regress over time, cope with member changes or operate in complex multi team systems. (4) The model is good as far as it goes but omits key factors that are also essential to building a successful team. (5) In describing the features, benefits and disciplines of teams it may inadvertently push people to focus on team building when a less demanding working group approach might be enough.

Origins and development

Lencioni developed the Five Dysfunctions model from his experiences as a management consultant and executive team adviser while working for his company, The Table Group.^[317]

Rather than emerging from a single formal research project, the framework grew out of patterns he observed across many senior teams that struggled to work together effectively.^[318] He noted recurring difficulties around interpersonal trust, conflict, commitment, accountability and the prioritization of collective outcomes over individual goals.^[319]

The structure of the model reflects Lencioni’s belief that team problems are often rooted in unspoken fears and interpersonal dynamics, rather than in inadequate strategy or unclear structures.^[320] His “pyramid” design emphasizes that the dysfunctions are layered: when teams lack trust, they are unlikely to engage in constructive conflict; without conflict, commitment is shallow; without commitment, mutual accountability is weak; and without accountability, attention drifts away from shared results.^[321] In later publications, workshops and tools, Lencioni and his firm, The Table Group, codified this approach into assessment questionnaires, facilitator guides and implementation programs.^[322]

The model is practitioner‑oriented.^[323] Lencioni drew on psychological concepts such as vulnerability, fear of conflict and group norms, but he chose to express them in accessible language aimed at managers rather than specialists.^[324] The fictional narrative format of his original book helped popularize the ideas among practitioners, and the companion field guide translated the fable into explicit concepts, checklists and exercises.^[325] Some commentators have welcomed the model’s accessibility while questioning its lack of systematic empirical validation and its status as a consultant‑derived framework rather than a tested theory of team effectiveness.^[326][327]

Overview of the five dysfunctions

Lencioni presented his model as a pyramid that describes five dysfunctions that, in his view, commonly impede teams. From the base upwards these are the dysfunctions:

• Absence of trust
• Fear of conflict
• Lack of commitment
• Avoidance of accountability
• Inattention to results

The model is illustrated differently in this article, but Lencioni’s essential idea behind the sequence of the five dysfunctions has been preserved.

Trust – or rather the absence of trust – is the foundation for all the other elements in Lencioni’s view. In this context, trust does not simply mean confidence in colleagues’ competence or reliability; it refers to vulnerability‑based trust, where team members feel safe enough to admit mistakes, acknowledge weaknesses and ask for help. Without such trust, Lencioni argues, team members will conceal disagreements, hide their weaknesses, avoid asking questions and hesitate to offer or accept feedback.^[328]

Fear of conflict is the second dysfunction. Lencioni believes that when team members do not trust one another, they tend to avoid frank, open debate about important issues. Instead of engaging in productive conflict over ideas and decisions, Lencioni says they resort to artificial harmony, back‑channel discussions or unresolved tensions. Lencioni suggests that such avoidance of conflict leads to poor decision quality and undermines commitment to whatever decisions are made.^[329]

The third dysfunction, lack of commitment, follows from conflict avoidance. For Lencioni, commitment is not about unanimous agreement but about decision clarity and enthusiastic buy‑in – even if individuals do not get their preferred outcome, they understand the decision and support it once the team has decided. If team members have not been heard and have not tested their views against one another, he argues that they are less likely to fully buy into the decisions emerging from discussions. That drives the team towards the next dysfunction.^[330]

The fourth dysfunction is avoidance of accountability. This reflects the difficulty teams have in holding one another accountable for their standards of behavior and performance. Lencioni argues that accountability among peers (rather than solely from the leader) is a feature of high-performing teams. He proposes that members of genuine teams confront one another instead of relying on the leader to hold everyone accountable. However, when there is insufficient commitment to clear decisions, he says that team members are reluctant to call out unhelpful behaviors or underperformance among peers. This means that accountability is left to the leader, resulting in weak peer‑to‑peer accountability, to the team’s detriment, Lencioni believes.^[331]

Finally, the fifth dysfunction: inattention to results. Lencioni argues that when individual members do not hold one another accountable for behaviors, commitments and performance, they tend to prioritize their own departmental interests, career ambitions or personal status over the team’s collective results. The ultimate dysfunction is therefore a drift away from shared, measurable outcomes at the team level.^[332]

Deeper description of each dysfunction

(1) Absence of trust

Lencioni suggests that in highly effective teams, members have enough confidence in themselves and one another to be frank about their personal limitations, thoughts and feelings. In such teams, people are willing to talk openly about their mistakes, weaknesses, doubts and fears, rather than trying to conceal them, because they trust their teammates.^[333]

Lencioni maintains that this kind of mutual trust is a central – indeed the first – condition for successful team building.^[334][335]

In Lencioni’s account, building trust involves people letting go of the impulse to protect themselves from embarrassment or loss of status in front of colleagues and instead accepting that some emotional exposure or vulnerability is necessary if the team is to function well. He believes that vulnerability-based trust reduces the chances of selfish or political behavior that can put the team’s results at risk. However, he recognizes that it is hard for team members to develop deep trust in one another. This is because most team members strive to uphold a positive self-image around their competence and can therefore dislike admitting their mistakes, flaws and omissions.^[336][337]

Thus, in Lencioni’s framework, absence of trust arises when team members are unwilling to be open about their mistakes, weaknesses or limitations. In other words, they are not ready to declare “I got that wrong” or “I don’t know the answer” or “I am sorry about that”. In Lencioni’s description, teams characterized by this dysfunction often display guarded communication, reluctance to ask for help and a tendency to interpret feedback as a threat rather than something helpful to the individual and team. Members may withhold concerns or questions for fear of appearing incompetent or vulnerable, which he presents as a form of self‑protection that can weaken attention to collective interests.^[338][339]

Lencioni emphasizes that this type of trust is built through intentional, often personal, interactions over time. He argues that the key characteristic in building trust among members is courage; courage, that is, in taking the risk of opening up before trust has been established as a team norm.^[340]

Lencioni advocates exercises where team members share personal histories, discuss their strengths and weaknesses openly and give each other feedback in a structured way. The idea is to normalize vulnerability within the team so that people feel safe enough to speak frankly and rely on one another’s strengths.^[341]

(2) Fear of conflict

Fear of conflict refers to the avoidance of frank, passionate debate and initial disagreement around issues, ideas and decisions that matter to the team. Lencioni asserts that sufficient trust among members must be established before overcoming this second dysfunction, otherwise a lack of trust may only exacerbate the fear of conflict.^[342][343]

Lencioni admits that in-team conflict can feel uncomfortable for team members. For example, it may trigger feelings of personal rejection or embarrassment if one member finds him or herself outargued by another. Alternatively, it may raise fears of reprisal if someone seeing themselves as lower-status is adopting a position that clashes with a higher-status member’s views.^[344]

Lencioni characterizes the typical reaction to this dysfunction as “artificial harmony” – teams avoid the open, sometimes uncomfortable debate he sees as necessary and instead sit near the “harmony” end of a spectrum that runs to “mean‑spirited personal attacks” at the other end. In his experience, this means real disagreements are often left unresolved and resurface outside meetings rather than being worked through in the room.^[345]

Lencioni argues that productive conflict is essential for uncovering the best ideas and key issues, for testing assumptions, for solving problems, preventing groupthink and making team meetings more interesting.^[346]

Lencioni distinguishes constructive, issue‑focused conflict from destructive, personal attacks. Healthy teams, in his view, engage energetically in debates about problems, plans, priorities and strategies while maintaining respect and goodwill among members. He portrays the leader’s role as encouraging such debate and modelling tolerance for emotional intensity during discussions, rather than avoiding conflict altogether.^[347]

Once they have developed sufficient trust, Lencioni suggests that teams could use instruments such as the Thomas-Kilmann Conflict Mode Instrument to profile each member’s attitude and approach to conflict and then encourage discussion around their differing stances before agreeing norms for dealing with intra-team conflict. He further proposes that leaders periodically bring semi‑buried conflicts into the open so that team members can practice applying their agreed conflict‑handling norms.^[348][349]

(3) Lack of commitment

According to Lencioni, lack of commitment shows itself when teams fail to make clear, timely decisions or when individual members do not genuinely buy into the decisions that are made because the discussions did not confront the conflict zones.^[350]

Lencioni explains that symptoms of a lack of commitment include repeated revisiting of the same issues, ambiguity about priorities, and slow or hesitant implementation. Alternatively, team members may leave meetings uncertain about what has been decided or quietly reserve the right to disagree outside the room.^[351]

Lencioni believes that its opposite – full commitment – shows when there is genuine (that is, honest) buy-in to important decisions even when team members had initially disagreed, plus full clarity on what the team has agreed. Teams achieve that when members express all their ideas, doubts and chief concerns, when everyone feels they have all been given full consideration, and they have removed any ambiguity or hidden assumptions around the decision.^[352][353]

Thus, for Lencioni, commitment is less about universal agreement and more about clarity and closure. He recommends practices such as summarizing decisions at the end of meetings, specifying who will do what by when, and explicitly surfacing where people disagree before the final decision. Lencioni also recommends that team members grasp the idea that people working in groups are less worried about their ideas or solutions triumphing and more interested in knowing that their thoughts have been heard and understood. For him, that is one of the keys to achieving team commitment.^[354]

Besides these pieces of tactical advice, Lencioni has one more recommendation for increasing team commitment: make sure that everyone in the team is clear on its chief collective priority by stating it in the form of a thematic goal and updating it when necessary. He uses the term “thematic goal” for a short‑term, unifying priority that sits above routine objectives, is intended to focus collective effort, and sets the context for any performance metrics.^[355]

Lencioni believes that these practices help ensure that even those who argue against a decision understand it and commit to supporting it in their actions.

(4) Avoidance of accountability

Lencioni argues that team members who commit to their chief collective goal, the decisions flowing from it, and standards of performance, will naturally hold themselves and their teammates accountable, not only for acting on those decisions, but their behavior in doing so.^[356]

Lencioni defines accountability as “the willingness of team members to remind one another when they’re not living up to the performance standards of the group”.^[357] This means that they will not rely on the team leader in applying that accountability. Instead, they will hold one another accountable directly.^[358]

Avoidance of accountability, according to Lencioni, refers to the reluctance of team members to confront peers when performance or behavior falls short of agreed standards, usually to avoid the unpleasantness of difficult conversations. In teams where this dysfunction is present, only the formal leader is expected to hold people to account, and peer feedback is rare or muted. This can, he argues, lead to lower performance standards, frustration among members and erosion of mutual respect.^[359]

Lencioni points out that, based on his observations, most people (especially leaders) find it easier to hold others accountable for their results than their behavior in the team because it involves giving critical feedback that may lead to arguments and tension. He argues that leaders – and, by extension, all team members – need to address this discomfort directly, because in his account poor behavior often precedes and contributes to weak results by creating what he sees as a low-performance atmosphere.^[360]

Lencioni suggests that mutual accountability among teammates is more powerful than top‑down control from the leader because it taps into peer pressure and individuals’ desire to not disappoint their colleagues.^[361] He believes that when expectations are clear and when team members have committed to them openly, it becomes easier and more legitimate for colleagues to challenge one another. However, he also recommends a “team effectiveness exercise” to help members get used to giving one another candid feedback in holding each other accountable.^[362]

(5) Inattention to results

Lencioni argues that teams with team members who trust one another, engage in conflict when needed, commit wholeheartedly to decisions, and hold one another accountable, are more likely to put aside their personal or department priorities and pay full attention to the team’s need for results.^[363]

Inattention to results, says Lencioni, shows itself as the tendency of team members to put their individual career goals, departmental metrics or personal status above the collective outcomes of the team. This fifth dysfunction can manifest in silos, competition among functions and a focus on visible personal achievements rather than shared success. Over time, Lencioni suggests that the team’s collective results suffer, even if some individuals appear to be doing well.^[364]

Lencioni argues that teams overcome this dysfunction by – having defined the thematic goal mentioned earlier – defining a small number of clear, collective metrics and by aligning rewards and recognition with those outcomes. He emphasizes the importance of simple, concrete goals that the team can track and discuss regularly. When team members see their own success as inseparable from the team’s results, attention naturally shifts towards what the group is achieving together.^[365]

Underlying psychological themes

Although Lencioni presents his model in accessible, non‑technical language, it rests on psychological themes that have been widely discussed in research on teams and organizations.^[366][367] His focus on vulnerability‑based trust connects with concepts such as psychological safety, where individuals feel safe to take interpersonal risks without fear of embarrassment or punishment.^[368][369] However, some commentators argue that Lencioni’s treatment of team dysfunctions, including fear of conflict, underplays how structural factors such as hierarchy, incentives and power distribution shape when and how disagreement occurs.^[370]

The model also highlights the role of social norms and implicit “contracts” within teams, such as expectations that members will be candid in debate, commit to collective decisions and hold one another accountable for results.^[371] These expectations depend on shared understandings of what is important and what is valued in the team. Lencioni argues that when such understandings are weak or contested, people tend to revert to self‑protection and local priorities.^[372] His emphasis on explicitly discussing expectations, behaviors and goals can therefore be seen as a practical effort to reshape team norms and shift the psychological climate towards greater openness and mutual responsibility.

By framing these issues as "dysfunctions", Lencioni offers practitioners a language that can help them discuss uncomfortable topics such as mistrust, avoidance and self‑interest. The vocabulary is deliberately simple and evocative, and practitioner accounts suggest that it provides a shared language that can make it easier for teams to recognize patterns in their own behavior and discuss them without resorting to more abstract psychological terminology.^[373] ​

Application in organizations

In practice, the Five Dysfunctions model is often used in facilitated workshops with intact teams, particularly senior leadership teams or cross‑functional project groups.^[374] Typically, team members complete a questionnaire that assesses the perceived strength of each of the five areas in their team.^[375] The results are then discussed in one or more workshops where the team explores its current patterns and identifies priority areas for change.^[376]

Facilitators commonly structure interventions around the dysfunctions pyramid, starting from the base.^[377] Work often begins with exercises aimed at building trust, such as personal histories, strengths and weaknesses discussions, or 360‑degree feedback sessions.^[378] ​ Once some trust has been established, teams may move on to practicing constructive conflict, for example by running structured debates on strategic issues or by revisiting recent decisions where people did not feel able to speak openly.^[379]

The model has also been integrated into leadership development programs and coaching engagements.^[380] Individual leaders use it as a checklist to assess their teams and to reflect on their own role in either reinforcing or addressing the dysfunctions.^[381] For example, a leader may examine whether his or her behavior encourages people to speak up, whether meetings routinely end with clear commitments, and whether there are mechanisms for peer accountability.^[382]

In addition, Lencioni’s framework has been applied in a range of organizational contexts, including non‑profit boards, educational settings and public sector teams. Practitioner accounts present the underlying ideas about trust, conflict, commitment, accountability and results as broadly applicable, while emphasizing that the specific exercises and examples must be adapted to local roles, missions and constraints.

Critical analysis

Overall, respected commentators typically describe Lencioni’s Five Dysfunctions model as a clear, useful, memorable practitioner-oriented framework.^{[383] [384]} They also criticize it for weak empirical grounding, its linear description, and limited treatment of other important issues that affect teams.^[385]

A. Main positive assessments

Both practitioner and academic commentators note three main recurring strengths.

• It is accessible and memorable: Commentators describe the model as simple, intuitively appealing and easy for managers to remember and use as a shared language (Trust-Conflict-Commitment-Accountability-Results). This simplicity is often contrasted with more technical academic models of team effectiveness.^[386][387]
• It is a diagnostic lens for assessing team dynamics: Practitioners treat it as a useful guide for structuring conversations about team behavior, especially around vulnerability-based trust and healthy conflict.^[388]
• Its popularity and influence in practice: Several writers highlight that, despite its drawbacks, it has become widely used in leadership programs, consulting, and team offsite work, which they take as evidence of its resonance with managers.^{[389][390][391]}

B. Main criticisms

These can be divided between more academic criticisms and application criticisms. First, the academic criticisms:

• Lack of empirical validation: critics comment on the Five Dysfunctions model’s “lack of evidence-based validity and rigor”, arguing that it rests primarily on Lencioni’s consulting experience and a fictional story, not systematic research or tested theory.^{[392][393][394]}
• Consultant-based, story-based origin: Commentators point out that Lencioni’s first book is “explicitly a work of fiction”; that it lacks the third-party references, case studies and quantitative evidence commonly expected in evidence-based management texts.^{[395][396][397]}
• Unsupported causal claims: critics question the idea that the five dysfunctions form a tightly interlinked causal chain and that addressing them sequentially will improve results. They note that Lencioni presents no experimental or longitudinal data to justify these assertions.^[398][399]
• Linear, hierarchical causation: A 2005 critique by authors from a complex systems background argues that the pyramid assumes an over-simple linear progression (Trust - Conflict - Commitment - Accountability - Results). They say this misrepresents the multidirectional dynamics of real teams and executive boards working in constantly changing environments.^[400]
• Static architecture versus fluid reality: The same systems authors contend that the model treats dysfunctions as a static architecture to be “fixed”, whereas complex adaptive systems theory emphasizes continual flux, membership change and emergent behavior.^[401]
• False universality: The complex-systems critique also faults the model for treating the five dysfunctions as universal truths across all contexts. It argues that this ignores how sector, governance differences shape team patterns and can produce “false precision” in diagnosis.^[402]

Now the more practice-level or application criticisms:

• Questionable effectiveness of some interventions: Some authors argue that Lencioni’s recommended trust-building exercises based on personal disclosures may not reliably build trust in seriously dysfunctional teams and may even have unintended negative results.^[403][404]
• Overreliance on interpersonal factors: One critique notes that Lencioni’s model stresses interpersonal trust and vulnerability while downplaying other factors that may have greater impacts on performance (e.g. workload, role clarity, resources, organization design and culture).^[405][406]
• Hierarchy and equal weighting: That same critique questions the assumption that each dysfunction is roughly equally important and that the hierarchical pyramid accurately reflects typical failure patterns. It suggests instead that one or two dysfunctions matter more than the others.^[407]

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators say that: (1) The model is plausible. (2) It is easy to understand. (3) It is memorable. (4) It provides a useful diagnostic lens. (5) It is widely known and applied. (6) It appears to resonate with its managerial audience.
• Limitations – Commentators say that: (1) The model is not based on systematic research or tested theory. (2) The causal links between the five dysfunctions have not been justified with data. (3) The model’s simple linearity from the base to the top of the pyramid ignores the more complex, circular, chaotic realities of workgroups. (4) It assumes a universality across sectors that isn’t backed up with research data. (5) Some recommended techniques for addressing the dysfunctions may not work or even backfire. (6) The model may over-emphasize interpersonal issues and under-emphasize wider organizational factors like culture. (7) It treats each dysfunction as equally important, but they may not be.

Team progression curve

This model maps six forms of work groups – Task Groups, Performance Groups, Potential Teams, Pseudo Teams, Real Teams, and High-Performance Teams – across two axes: group performance and group unity. It draws on and adapts Katzenbach & Smith’s data, but Scouller introduces additional distinctions and clarifications.^[415] The figure below plots these six forms against group performance and group unity to show their relative positions in simplified schematic form, but using a scatter diagram rather than the ascending S‑shaped progression curve Scouller used in his trilogy.

• Task groups uphold the status quo with minimal unity and performance, but enough to complete their job. For example, a parish council committee.^[416]
• Performance groups are hub-and-spokes models coordinated by a leader but lacking joint work output. They perform better than Task Groups because they must – they face more testing conditions – but are no more united. Their output is the total of the members’ individual efforts. Scouller argues that many so-called senior management teams are in fact Performance Groups.^[417]
• Potential teams are in an interim position – mentally they have started shifting from Performance Group to Real Team. They face a challenging common purpose, have translated it into a clear number one goal and realize that operating to a hub-and-spokes model (a Performance Group) will not deliver the results they need, that instead they must pool their efforts. But they have some way to go before they reach Real Team status.^[418]
• Pseudo teams have high unity but poor results. They chase the ideal of “team” for harmony’s sake because they think friendship and unanimity are the hallmarks of a team, but they lack joint outputs, fail to apply team disciplines, and end up underperforming, leaving the members ultimately dissatisfied.^[419]
• Real teams commit to a challenging common goal (like designing a new car or turning around a business) because they cannot achieve it by working individually even if the members’ efforts are skillfully coordinated by a leader. They blend the members’ abilities, apply joint accountability, learn key collective skills and develop a strong ethos, thus achieving good results, greater unity and a fulfilling experience.^[420]
• High-performance teams are, according to Scouller, a rare, exalted version of Real Teams. They show the highest unity and results. They have three differences versus Real Teams: members demonstrate huge dedication to the goal (which feels more like a cause to them), they display unusual dedication to supporting and pushing one another, and they share leadership responsibility to the point where it is hard to detect who is the leader when they are in action.^[421]

Scouller agrees with Katzenbach & Smith that Real Teams can be intentionally built, but High-Performance Teams only emerge organically.^[422] He therefore proposes that, when engaging in team building, the focus should be on achieving “Real Team” status. He also emphasizes that the Performance Group discipline is an appropriate choice in many contexts – for example, stable conditions or a less demanding goal. Thus, he argues, it is important for leaders, consultants and coaches to consider which discipline – Performance group or Real team – best suits the work group’s declared number one goal as genuine teams are not always needed.

Commit-Combust-Combine (C-C-C) psychological model

Scouller suggests that a work group can only develop into – and stay as – a Real Team if it resolves three recurring subconscious psychological issues that he calls Commit, Combust and Combine. The C-C-C model is based on William Schutz’s research into groups but adapted specifically to teams.^{[423][424][425]} Below is a summary of how Scouller outlines a work group’s three psychological challenges:^[426]

Scouller explains the psychological rationale behind this sequencing, drawing on Schutz’s FIRO research into group behavior.^[430] He argues that if members believe the potential team’s task or longer-term purpose is not important to them and therefore they do not fully engage in what the team is trying to achieve, the other two issues will not matter – members will not usually engage in power struggles or spend time trying to figure out who they can trust and whether they feel safe to say what they are really thinking because, quite simply, they do not care enough. Thus, says Scouller, Commit is the first team psychological issue.^[431] Having resolved that first issue, the question of roles, power and influence emerges as the dominant challenge for each member and therefore the group.^[432] This is Combust. Now team members want to understand how, together, they will get things done, how much individual power or influence they have over decisions and follow‑through, and whether they are comfortable with the team’s way of working and their personal influence. It is only after resolving the power-related issue of Combust, Scouller explains, again relying on Schutz’s group research, that members’ attention turns to the Combine issue.^{[433][434][435]} That is, in developing closer connections, building trust, figuring out how safe they are to say what they are really thinking and feeling, placing the team’s aim above their selfish interests, and seeking ways of raising collective performance.

Therefore, unlike Lencioni’s model, Scouller places trust within the third issue, Combine, meaning that, in his view, trust building is not a priority in the early stages of team building.^{[436][437][438]}

Scouller suggests that it is important not to see C-C-C as a three-phase linear version of Tuckman’s original four-stage model but with more underpinning psychology. Indeed, Scouller recommends that teams should view Commit, Combust and Combine as issues framed as questions, not sequential stages.^[439] That is because although team members usually address Commit-Combust-Combine in that order, they do not always. Scouller argues that there is a logic to the C-C-C sequence, which is why the issues typically arise in that order, but he claims they will not always do so. For example, occasionally teams experience a Commit problem while wrestling with the Combust issue. This is due to the phenomenon that Scouller calls “micro issues”.^[440]

Micro issues, according to Scouller, are temporary relapses to an earlier issue while the work group is on its way to becoming a genuine team. Triggers for micro issues include a change of leader, an unfamiliar group task, or individual members’ unresolved personal psychological issues. Micro issues occur because although at any point in the group’s evolution only one psychological challenge dominates its attention, all three issues remain below the surface. Thus, what can seem like resolution of one issue does not stop it reappearing in another guise later. This means, for example, that group members cannot address the Commit issue and assume it is forever dealt with.^[441]

Thus, the C-C-C model anticipates recycling of issues, meaning Committing, Combusting and Combining never truly ends in Scouller’s view. This is why he presents the model as an infinity loop; although the figure shown in this article shows an alternative simplified version of that depiction.

Seven-principle (7P) action model

Scouller’s seven-principle (7P) model provides a framework of interconnected actions. He emphasizes that each principle supports and amplifies the others. The idea behind the model is that if a Potential Team wants to climb the Team Progression Curve towards Real Team status, it should apply seven action principles:

1. Motivating purpose.
2. The performance group or real team choice.
3. Shared flexed principled leadership.
4. Task progress and results.
5. Group unity.
6. Attention to individuals.
7. Renew or end.

Because the 7P framework is grounded in the C-C-C model of team psychology, Scouller suggests that if work groups apply the principles skillfully, they will naturally address the three psychological challenges: Commit, Combust and Combine.^[442]

Scouller presents the 7P model as a heptagon-shaped jigsaw with seven interlocking pieces or slices to show that each principle is distinct but not separate.^[443] He explains that the model does not work in a simple linear sequence, meaning an aspiring team does not always start with the first principle and move around the model in a clockwise fashion.^[444] The figure here summarizes the seven principles and their interrelationships in simplified form.

Scouller comments that while every principle has a distinct payoff, every principle also affects the other six to build increasing momentum. Scouller describes this systemic effect in the form of a rising spiral. He explains that the spiral occurs because four of the principles directly tap into the four sources of intrinsic motivation, making them amplify one another.^[445]

Scouller remarks that this systemic effect has two other implications. First, teams should not overlook any one principle as they all have important roles to play. Second, there will be no single breakthrough moment when applying the principles – all seven matter.^[446]

Below are brief overview-style descriptions of Scouller’s seven team building principles:

While the seven principles offer strategic direction, Scouller further identifies 33 specific “action keys” that operationalize these principles. He regards 11 of them as primary (meaning they carry extra weight) and 22 as secondary. This additional level of detail is intended to bridge the gap between conceptual understanding and daily team practice, distinguishing his model from more abstract frameworks like Hackman’s.^[454] The next section will give more detail on the action keys.

Deeper descriptions of the 7P principles and action keys

The main idea, Scouller suggests, is that Potential Teams can resolve the three “C-C-C” psychological challenges by applying the seven principles, enabling consistent performance and a shift towards Real Team status. Here are the seven principles in more detail with the main action keys mapped against them:

Principle #1: motivating purpose

Scouller explains the difference between a work group's "basic purpose” and its “motivating purpose”. Its basic purpose is its charter, its reason for being. It explains why the group formed, enabling selection of members to start. However, Scouller argues that if the aim is to build a real team, knowing its basic purpose is insufficient – it must also know its specific motivating purpose. In practice, this means that the potential team must clarify its number one goal for the next 3 to 12 months to give it a means of galvanizing and uniting its members. From then on, it must always keep its number one goal in focus. Scouller describes a six-step sequence for defining and updating a motivating purpose, offers a worksheet tool to support it, and suggests 12 practical tips to aid the process.^[455]

Principle #2: performance group or real team

Having defined its number one goal, Scouller suggests that the group should use it to judge whether it needs to act as a Real Team or if working as a Performance Group is enough to achieve the target. This matters because, as Scouller explains, it is easier to learn to operate as a Performance Group. Therefore, Scouller argues, there is no need to strive to become a Real Team if it is not necessary. Scouller offers a structure for making the choice.^[456] He emphasizes that the choice need not be permanent – that it is possible to switch between disciplines.

Principle #3: shared flexed principled leadership

Above all, Scouller emphasizes, this principle involves every team member making a mental shift around the concept of “leadership”. Scouller suggests that team members see leadership as the process of addressing four dimensions simultaneously: Motivating purpose, Task progress and results, Group unity, and Attention to individuals. He argues that, in practice, by seeing it as a process, team members will no longer conflate “leadership” with the role of “leader”. Conflation of the two, he believes, can make the other team members behave too passively, causing the team leader to feel the need to be superhuman – as someone with all the answers. Scouller believes the collective mental shift results in co-ownership of decision-making, problem-solving, planning and team delivery – in short, shared responsibility for leadership. But for team leaders this third principle also means exemplifying the team’s ethos and standards (what Scouller calls “principled leadership”) while flexing their approach according to the situation; not applying a single style at all stages of the team’s growing psychological maturity. To help team leaders assess their progress against this principle, Scouller includes a worksheet with 18 self-reflection questions.^[457]

Principle #4: task progress & results

Essentially, as Scouller explains, this means turning the number one goal into action – making things happen. This is the principle with the most action keys. Below is guidance on the four primary keys:

• Team size and blend: Above all, as Scouller sees it, this is about getting the right people on board – meaning that together they provide the best possible blend of team role behaviors, that there are no vital skill gaps or unhelpful overloads. For example, he points out, a football team would not want 11 goalkeepers.^[458] Scouller draws on Belbin’s team roles research in outlining this key. He also recommends not taking the team size above 12 members, having discussed the findings of five research sources.
• Vision and strategy: As Scouller sees it, this means understanding why change is needed (the context), agreeing a vision for the team’s project, department or business unit, then devising a blueprint or plan to support it – having made clear choices about the actions the team will and will not take in the coming period to avoid doing too many things simultaneously and scattering its energy. Scouller stresses the importance of this Context-Vision-Blueprint (CVB) framework’s underpinning psychology in communicating the vision and strategy.^[459] The aims in each C-V-B stage are, first (in Context), to create dissatisfaction with status quo, second (in Vision), to inspire and bring hope, and third (in Blueprint), to banish doubts and grow people’s confidence in the goal and its supporting plan.
• Decision making: Scouller argues that it is important for the team to agree explicitly how it will make decisions – not assume that enthusiastically backed decisions will naturally and consistently emerge. In Scouller’s coaching experience, they do not. He states that most of the teams he has coached have experienced difficulties with decision-making, which affects team morale, unity, performance, and results.^[460] Scouller recommends an explicit team conversation leading to a choice on its preferred method of reaching decisions. He offers guidance by outlining and comparing six decision-making options.^[461]
• Joint accountability: Scouller remarks that the discipline of joint accountability is a hallmark of real teams.^[462] According to Scouller, joint accountability has two elements. The first is, “Owning responsibility for your part while holding others responsible for theirs, which means being ready to challenge underperforming teammates and give tough feedback if needed.” The second is, “Holding yourselves jointly accountable for the whole team’s results, meaning you hold the attitude ‘We succeed or we fail as a team’. He goes on to say, “This stops the first element morphing into finger-pointing, blaming and scapegoating. It also encourages the silent counterpart to direct feedback: peer pressure to deliver. This is often the more powerful accountability driver as it can mean blunt feedback isn’t always needed.” Scouller outlines seven pillars of joint accountability, many of which sit within the other six principles.^[463] The first is spelling out a clear number one goal. The second is defining clear team roles with personal (but team-supporting) objectives tied to each. The third is defining and living the team’s ethos and standards. The fourth is team members learning the art of challenging one another. The fifth is members learning to give tough (but skillful) feedback to one another. The sixth and seventh are sharing decision-making and applying a medley of six other tactics.

Principle #5: group unity

For Scouller, this is about creating and upholding a team identity, a sense of “us”, that “we succeed as a team or fail as a team”. From this, Scouller contends, the team can create a climate where members open up, develop close bonds, and trust one another, putting the team’s aims before their selfish interests. The two most important action keys here are (1) defining and living the team’s ethos (values) and standards of behavior and (2) building trust and therefore psychological safety by practicing openness behavior – in other words, by all members learning to say what is really on their minds. Scouller offers a worksheet to help teams define their ethos (or set of values) and standards of behavior and suggests a series of tips for team leaders on how to foster psychological safety because, he argues, their influence is greater than anyone else’s on the team.^[464] He also offers practical guidance on how the team can learn to recognize and handle conflict and how to encourage members to name the issues that are so big they can’t ignore them but no one wants to mention or discuss because they feel it is too risky. These are issues often known as “unnamed elephants” or “the elephant in the room”.

Principle #6: attention to individuals

While there are six action keys under this principle, for Scouller it means, above all, the team leader recognizing that every member is unique and distinct, taking the time to understand what makes them tick, and addressing their individual challenges and motivations. Scouller mentions an old saying among team sports coaches: “Keep your eye on the individual.” He argues that while the team is more important than a single member, and there is no ‘I’ in team, every team member has their own fears, needs, ambitions and background difficulties. Thus, he believes, if team leaders treat their colleagues on a “one-size-fits-all” basis they will fail to connect with many of them. To help team leaders, Scouller offers guidance on how to learn what motivates their colleagues. He also suggests simple models for practicing what he calls “powerful praising” and learning how to be skillfully assertive when engaging in what he calls “tough conversations”.^[465]

Principle #7: renew or end

For teams with infinite lifespans, Scouller explains that this is largely about renewing their cutting edge to make sure they don’t go stale or reviewing the basics if they feel themselves getting stuck – as evidenced by the same old internal problems recurring, giving the team members the feeling that they are “going around in circles”. Scouller suggests a 13-point checklist for revisiting the basics to discern which of them they need to address.^[466] For limited lifespan units, like project teams, this principle is about recognizing when to end and then doing so skillfully. Scouller offers guidance on what a “good ending” looks like.

Scouller illustrates the seven principles with examples from his coaching case history to make the model easier to grasp for leadership teams and cross-functional groups.^[467] He also shows them in action through the retelling of NASA’s 1970 Apollo 13 moon mission rescue.^[468]

Integration as a set

Scouller’s approach integrates these three models, which he presents as a framework for team development. In his post-publication writings he used the term "suite" to describe the three models but did not use that word in any of his books.^[469][470]

In most cases, Scouller recommends that work group members focus first on action principle #1 (Motivating Purpose) to decide the single most important goal they must achieve within the next 12 months. After that, he suggests, they should concentrate on principle #2 (Choosing between Real Team or Performance Group disciplines) to decide whether they need to operate as a Real Team or whether a Performance Group (a less demanding format) will be sufficient. After that, Scouller recommends using the Commit-Combust-Combine model to assess which psychological issue is to the fore and then mapping across to the Seven-Principle (7P) model to see which action keys are most relevant to that challenge. This can be done by using Scouller’s TeamFixer diagnostic tool, which he introduces in the third book of his trilogy.^[471]

Scouller characterizes his approach as ‘psychological thinking first, action second’, suggesting that diagnosing psychological issues before acting helps teams avoid wasted effort and select more targeted development steps.^[472]

Critical analysis

Critical discussion of Scouller’s integrated set of team‑building models is still emerging, reflecting its recent publication (2024) and mainly practitioner‑oriented readership.^[473][474] Available commentary concentrates on how reviewers see its strengths and ease of implementation, but the existing reviews do not discuss the models’ empirical reliability.^{[475][476][477]}

A. Main positive assessments

• Psychological insight: Literary and field practitioner sources describe Scouller’s set of team building models – especially his Dual Forces and Commit-Combust-Combine models – as unusually explicit about the “subterranean psychological forces” shaping team performance. They believe they highlight obstacles that might otherwise remain hidden from managers.^[478][479]
• Integrated models: Reviewers highlight the integration of the three practical tools described in this article: the Team Progression Curve, the Commit-Combust-Combine psychological model and the Seven‑Principle (7P) action model.^[480][481]
• Diagnosis and action: Supporters also highlight the three models' diagnostic clarity around psychological issues and how to select the best action responses, plus the distinction between “real teams” and “performance groups” at senior levels, along with the detailed how-to guidance.^[482][483]

B. Main criticisms

On the academic side, as of March 2026, no published studies (peer‑reviewed or otherwise) specifically test Scouller’s team building models, and no journal articles providing formal academic critiques have been identified. So far, discussion of Scouller’s set of models appears confined to literary reviews, practitioner lists, and interviews. Thus, its empirical support currently appears weaker than longer‑established academic team models like Hackman’s.

The available practitioner material suggests that applying Scouller’s tools may demand high levels of team leader self‑awareness, psychological insight and facilitation skill, plus steady commitment by the parent organization to the team‑building effort.^[484] Commentators infer that this level of sophistication may deter teams seeking rapid fixes for their performance problems and note that the number of action steps may make Scouller's set of models harder to adopt than simpler team‑building frameworks for groups wanting quick, easy‑to‑apply tools.^[485][486]

Critique summary

This summarizes the fuller critical analysis into shorter bullet points:

• Strengths – Commentators note that: (1) The models uncover the hidden psychological forces making it harder for teams to form and perform. (2) The models integrate and support one another. (3) They enable users to diagnose psychological issues and see which actions best address them. (4) The models highlight the important distinction between performance groups and real teams. (5) The 7P model outlines both action principles and detailed action keys.
• Limitations – (1) Due to their newness, little or no academic commentary on Scouller's set of models exists at this point. (2) Commentators note that the three models’ depth could mean that practitioners would need significant skill to apply them successfully. (3) Some practitioner sources imply that the time and effort involved in using the models may make them less attractive to organizations favoring lighter‑touch, quick‑fix team‑building approaches.

Comparative overview across key dimensions

The table below summarizes the main overlaps and differences across four shared dimensions:

(1) Origins and evidence base: (A) Whether the model stems mainly from academic research, consultancy work or practitioner synthesis. (B) Any research limitations, that is, major constraints or obvious weaknesses in the original data‑gathering designs (e.g. sample type, setting, measures). (C) What evidence has been gathered to support or challenge the model since its publication.

(2) Primary focus and level of analysis: (A) What each model mainly looks at (for example, stages, roles, conditions, dysfunctions, integrated psychology and action). (B) The level at which it sits, that is, individual, team, wider system. (C) How far it emphasizes psychological or relational factors.

(3) View of time and development: whether the model treats effectiveness in terms of stages, enduring conditions, recurring dysfunctions or psychological issues.

(4) Practical use and type of guidance: (A) How organizations typically use the model, for example, teaching, diagnosis, training, leadership development, team coaching. (B) The extent to which it provides practical guidance for application.

Shared ground and major contrasts

Across the six models one can see a common emphasis on certain themes. They include a clear shared purpose or goal, securing complementary contributions from members, agreeing ways of working and attending to relationships as part of sustaining performance. Yet they differ in where they place their main explanatory weight. Tuckman focuses on developmental stages. Belbin on individual behavioral roles. Hackman on enabling conditions and context. Katzenbach and Smith on performance disciplines and team types. Lencioni on stacked psychological obstacles. Scouller on the interplay between underlying psychology and carefully organized action over time.

Beyond these conceptual lenses, and as a way of closing this article, it is possible to locate the frameworks along three descriptive dimensions that commentators often highlight. The first is the relative strength of their empirical evidence base. The second is the depth of their treatment of individual and team psychology. The third is the degree of practical action guidance they provide. The labels in the table below are intended as neutral summaries of these tendencies, not as value judgements about which model is better or worse.^[487]

To be clear, the table’s content is drawn purely from this article and its secondary sources.

Practitioners and educators can of course use the six models together, not treat them as rivals. Depending on a team’s needs and context, they might, for example, combine a conditions-focused model with a more psychologically focused or action-oriented framework.^[488]