This article summarizes and compares six influential models in the team building field, presented in the chronological order in which they emerged. They are practical frameworks used to understand, build, or improve work teams in organizational settings. The models were selected on two grounds: either they have become wellâÂÂestablished in professional or academic circles, or they offer more recent frameworks that address aspects of team functioning not fully covered by earlier work. Accordingly, some models qualify through longâÂÂstanding citation or use in the field, while others do so by proposing a new conceptual approach based on academic insight or practitioner experience.
The models summarized in this article are:
These six approaches are commonly cited or discussed as models used to diagnose team dynamics, support improved performance, and inform team leadership and team building practice.
The article first describes and briefly critiques each model in turn. It then compares the models in terms of their origins and evidence base, their primary focus, their view of development over time, how they are typically used in organizations, and how much practical guidance they offer for diagnosing and addressing team needs.
Organizations rely increasingly on teams to deliver complex, interdependent work, yet many groups struggle with unclear goals, unhelpful norms, and persistent interpersonal tensions that can undermine results. TeamâÂÂbuilding models offer structured ways to understand these patterns, diagnose common obstacles, and target interventions rather than relying on intuition alone. Leaders, consultants and coaches use such frameworks to clarify purpose, improve collaboration, and accelerate a groupâÂÂs development into an effective team.
Beyond this practical guidance, some models also seek to explain the hidden influences that block or enable the formation of genuine teams. Tuckman and Belbin do this to a degree by highlighting predictable patterns of group development and the impact of membersâ habitual role behaviors, but without an extended account of the underlying psychology. Later theorists, including Lencioni and Scouller, have drawn on 20thâÂÂcentury work in psychology and sociology to explore why many work groups struggle to become real teams and why this often requires deliberate effort. On this view, teamâÂÂbuilding models are not just checklists or recipes; they are attempts to describe the deeper forces, mindsets and dynamics that shape how groups behave over time and suggest ways to address those issues on the way to becoming highâÂÂfunctioning teams.
A separate, recurring theme in the literature is the distinction between ordinary work groups and genuine teams. Authors such as Katzenbach & Smith and Scouller argue that not every collection of people reporting to the same manager qualifies as a team; they reserve the term for groups with a shared purpose, mutual accountability and interdependent work. This distinction underpins several of the models examined in this article and explains why some theorists have felt the need to define âÂÂteamâ carefully before proposing principles for team building. The next section briefly reviews these definitions to clarify their implications for contemporary team building practice.
Debates about what counts as a âÂÂreal teamâ have led several theorists to offer explicit definitions of the term. These definitions help distinguish teams from looser work groups and frame the assumptions behind different teamâÂÂbuilding models.
Five of the six theorists covered in this article believe that a team is a distinctive form of work group â one defined not simply by the presence of multiple individuals, but by specific, shared features highlighted by leading experts in the fields of organizational behavior and group dynamics. Reviewing these influential models reveals both variations in emphasis and important conceptual overlaps.
Notably, Bruce Tuckman, in his two papers, did not offer a formal, one-sentence definition of a team; he focused instead on group development stages.
These five definitions highlight four distinguishing features shared by most models. First, a common purpose or aim â each model underscores the centrality of an important shared goal. Second, collective accountability â in true teams, members are jointly accountable for their performance and results. Third, complementarity of skills or roles â most modern definitions emphasize the importance of combining distinct, balancing abilities. Fourth, interdependence â teams are more than coincidental collections of people; they are interdependent in their tasks and outcomes.
Some theorists, notably Katzenbach & Smith and Scouller, have defined other forms of work groups within organizations, including single-leader units (or performance groups), pseudo-teams and task groups. By contrasting these with âÂÂtrue teams,â they further emphasize the distinctive features that set teams apart from other groups.
These definitions present a view of teams as a particular kind of work group designed for complex, interdependent tasks in pursuit of shared aims and results. Many team building models incorporate these defining elements in their assumptions about what distinguishes teams from other groups.
Bruce Tuckman developed his original Forming-Storming-Norming-Performing model in the mid-1960s through a meta-analysis of published academic studies on group development.
TuckmanâÂÂs goal was to classify the phases through which groups progress in therapeutic and professional settings, identifying patterns around interpersonal relationships and task activities. His motive was to determine how groups could function more effectively and achieve cohesion, ultimately resulting in his highly influential, easy-to-memorize development stages model. Thus, Tuckman's goal can be described as providing a map of âÂÂhowâ groups develop rather than âÂÂhow they can be made to developâÂÂ.
This approach contrasts with models that emerged primarily from practitionersâ fieldwork or organizational consulting, such as those of Lencioni and Scouller, and with frameworks based on direct empirical research or team observation, as seen in the work of Belbin, Katzenbach & Smith, and Hackman.
While working at the U.S. Naval Medical Research Institute, as Tuckman described it, his boss handed him âÂÂ50 psychoanalytic articles on group developmentâ and suggested that, âÂÂI look it over and see if I could make anything out of it.â His meta-analysis led directly to the creation of his team development model, which he published in a 1965 article in Psychological Bulletin titled âÂÂDevelopmental Sequence in Small GroupsâÂÂ.
After publishing his paper in 1965, Tuckman, with Mary Ann Jensen, released an update in 1977 adding a fifth stage: Adjourning.
TuckmanâÂÂs model is fundamentally descriptive rather than prescriptive, but it provides managers, coaches and consultants with a simple conceptual map for understanding the behavioural journey that teams may undertake, as Bonebright notes in her historical review of the model. Beyond this descriptive and potentially diagnostic use, the model does not provide instructions, interventions or action steps for leaders aiming to move a team from one phase to the other, nor does it explain the underlying psychology (that is, why those stages arise, and in that order). Nevertheless, his model has become one of the most frequently cited frameworks in group dynamics and team development, influencing research and practice in management training, education, and organizational psychology.
His model identifies patterns in how groups typically evolve over time, split into five sequential stages. However, in the original 1965 paper, there were only four stages, and Tuckman did not suggest the memorable pneumonic by which the model is now known until near the end of the paper. The stages were originally labelled: (1) Orientation, Testing & Dependence (2) Intragroup Conflict (3) Development of Group Cohesion and (4) Functional Role Relatedness. Nevertheless, here we will use the more familiar labels to describe the stages.
In describing each stage, Tuckman distinguished between the developing of interpersonal relationships between group members and their corresponding behaviors (which he called âÂÂgroup structureâÂÂ) and how they interacted in tackling their main tasks (which he called âÂÂtask activityâÂÂ). Unlike later commentators on his model, Tuckman was relatively sparing in describing the behavioral content of each stage so this article will respect his brief descriptions of Forming, Storming, Norming, Performing and Adjourning.
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.
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.
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.
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.
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.
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.
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:
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.
A. Main positive assessments
Many educators and practitioners regularly point to three main strengths:
B. Main criticisms
Academic commentators raise several recurring limitations:
Experienced field practitioners focus their criticism on practical application limitations:
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.
This summarizes the fuller critical analysis into shorter bullet points:
Further information: Tuckman's stages of group development
The Belbin team roles model is a widely recognized framework that explains how different individual patterns of behavior contribute to team performance. It was developed by British researcher Meredith Belbin in the 1970s and offers a practical method for analyzing and balancing the mix of behaviors needed to build successful management and project teams. He first presented it in his book, Management Teams: Why They Succeed or Fail (1981).
Belbin proposed that successful teamwork depends less on the individual talents of members and more on the combination of the complementary roles they play. His research identified nine clusters of behavior, or âÂÂteam roles,â each representing a distinct way in which people interact and add value within a team. He argued that when teams contain the right blend of these roles, they are more likely to perform productively and sustain cooperation over time.
Since its introduction, the Belbin model has been adopted internationally in leadership development, organizational consulting, and team formation work, with applications reported across business and educational contexts. Although sometimes misinterpreted as a personality typology, Belbin maintained that team roles describe context-dependent patterns of behavior, not fixed traits or character types.
Before describing the model and its application in more detail, the next section will outline how BelbinâÂÂs research led to the nine roles. This may help explain BelbinâÂÂs conclusions and start to clarify the rolesâ differences.
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. 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. Throughout the games, Belbin observers sat in the teamsâ meeting rooms and recorded who was contributing what behavior at each moment. 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. 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.
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.
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.
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. 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.
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.
The Belbin model groups the nine team roles into three categories according to their primary orientation in work groups: Action, People, and Thinking. 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. 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.
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:
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.
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. 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.
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.
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.
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.
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.
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.
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.
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. Teams lacking such a purpose â even well-balanced teams â may lack focus, commitment or cohesion. 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. 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. 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. The best teams, they argue, encourage honest conversations, allowing members to challenge one another constructively and surface differing opinions without fear of punishment. Therefore, team role balancing alone may not be enough to shape these team qualities.
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.
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.
A. Main positive assessments
Commentators highlight four main strengths:
B. Main criticisms
First, academic â especially psychometric â criticism, which centers on concerns about the reliability and validity of the Belbin assessment tool.
Next, practical and applicationâÂÂlevel concerns focusing on how â and indeed if â the Belbin model works in practice.
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.
This summarizes the fuller critical analysis into shorter bullet points:
Further information: Team Role Inventories
Richard HackmanâÂÂs Team Effectiveness Model defines the core conditions that help work teams perform successfully and achieve valuable results. Developed over decades of research, this model emerged from HackmanâÂÂs work in organizational psychology, culminating in his 2002 book, Leading Teams: Setting the Stage for Great Performances. While HackmanâÂÂs direct influence is perhaps strongest within academic, research, and organizational development communities rather than mainstream executive practice, his model is referenced as one of the most validated frameworks in the team effectiveness literature.
What distinguishes HackmanâÂÂs framework is its âÂÂwide lensâ on team effectiveness: it brings into focus the preconditions that leaders and organizations can establish to make team success more likely. This approach builds on and complements other earlier influential models â such as those by Tuckman, Belbin and Katzenbach & Smith â which address developmental stages, team roles, member interactions, and group processes. HackmanâÂÂs model, however, emphasizes how the interplay of specific foundational factors and systems design shapes the probability of a teamâÂÂs long-term success.
His framework identifies five essential conditions:
While HackmanâÂÂs model may be less familiar than some popular models, including it in an article on contemporary team building helps bridge rigorous research with hands-on practice. It offers a broad âÂÂsystems perspectiveâ grounded in decades of scholarly study, highlighting how team design and context underpin effectiveness.
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. 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.
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.
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. 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).
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.
Hackman lists three criteria for judging a teamâÂÂs effectiveness:
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.
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. In his view, there is a greater likelihood of a successful team emerging when:
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.
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.
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.
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.
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.
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.
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.
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. 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.
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:
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.
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âÂÂ.
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. 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. Therefore, he advises, they should do five things:
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.
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.
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.
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. 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.
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.
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:
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.
Field practitioners who adopt HackmanâÂÂs model also highlight limitations when leaders try to use it in real-life organizations:
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.
This summarizes the fuller critical analysis into shorter bullet points:
Katzenbach & SmithâÂÂs team building model is a widely recognized framework for understanding and creating successful teams in organizations. It originated from the work of Jon Katzenbach and Douglas Smith, two management consultants. They summarized their research findings and thinking in their influential 1993 book, The Wisdom of Teams: Creating the High-Performance Organization.
Katzenbach and Smith studied 47 different teams in 36 organizations. Their research included business organizations such as Motorola and Hewlett-Packard but also drew on teams beyond the business world. For example, it included a âÂÂDesert Stormâ (the name given to the USA and alliesâ military operation in the 1991 Gulf War) logistics team and the Girl Scouts. Thus, while most of their sample was rooted in business contexts, their analysis extended to other team settings, strengthening their conclusions.
Their research identified six key factors behind team effectiveness:
Through these elements, Katzenbach & Smith distinguished genuine teams â capable of collective work products and superior results â from working groups, potential teams and pseudo-teams on a spectrum of team development. They also highlighted the two differences between highly effective successful âÂÂreal teamsâ and their rarer cousin, high-performance teams.
For consultants, coaches and executives in the modern team building field â although perhaps not academics â Katzenbach & SmithâÂÂs work has become a key reference. Their model has influenced contemporary thinking on team building in organizations over the past 30 years. For example, one later theorist, James Scouller, cited their research as one of the empirical bases for his own models.
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. Nor, according to their research, do most people take easily to the idea of others assuming responsibility for them. They see this reluctance as a reason to focus on the âÂÂteam basicsâ shown in the diagram, which summarizes their model.
The outer circle, broken into three segments, depicts what teams deliver â Collective Work Products, Performance & Results, and Personal Growth for the members. This, in other words, is how Katzenbach & Smith see every teamâÂÂs fundamental purpose, its reason for being, regardless of its specific circumstances.
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). 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.
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.
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. 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.
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.
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". 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.
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. 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.
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.
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.
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. 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.
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.
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. 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.
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. 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.
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.
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.
A. Main positive assessments
Supporters highlight four main strengths:
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.
B. Main criticisms
Academically oriented critics point to limits in the modelâÂÂs theoretical and research base.
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:
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.
This summarizes the fuller critical analysis into shorter bullet points:
Patrick LencioniâÂÂs Five Dysfunctions of a Team model is a widely used framework in management training and organizational consulting that explains how characteristic behavioral patterns undermine team performance. The model focuses on psychological and relational obstacles that prevent groups from becoming cohesive, highâÂÂperforming teams, rather than on structures, processes or technical capabilities. It is typically presented as a pyramid of five interrelated âÂÂdysfunctionsâ that build on one another, starting with an absence of trust and culminating in inattention to collective results.
The model first appeared in LencioniâÂÂs popular business fable, The Five Dysfunctions of a Team, (2002), which combines a narrative about a fictional executive team with a conceptual explanation of the framework. His later Field Guide (2005) set out more detailed diagnostic instruments and practical exercises for overcoming the dysfunctions.
Since their publication in the early-mid 2000s, the Five Dysfunctions framework has been widely adopted by leadership coaches, consultants and team facilitators, especially in North America and Europe. In contrast to models that describe stages of group development or clusters of team roles, Lencioni presents his framework primarily as a diagnostic lens and an agenda for behavioral change.
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.
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. He noted recurring difficulties around interpersonal trust, conflict, commitment, accountability and the prioritization of collective outcomes over individual goals.
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. 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. In later publications, workshops and tools, Lencioni and his firm, The Table Group, codified this approach into assessment questionnaires, facilitator guides and implementation programs.
The model is practitionerâÂÂoriented. 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. 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. 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.
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:
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.
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.
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.
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.
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.
(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.
Lencioni maintains that this kind of mutual trust is a central â indeed the first â condition for successful team building.
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.
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.
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.
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.
(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.
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.
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.
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.
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.
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.
(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.
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.
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.
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.
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.
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.
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âÂÂ. This means that they will not rely on the team leader in applying that accountability. Instead, they will hold one another accountable directly.
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.
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.
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. 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.
(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.
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.
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.
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. 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. 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.
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. 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. 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. âÂÂ
In practice, the Five Dysfunctions model is often used in facilitated workshops with intact teams, particularly senior leadership teams or crossâÂÂfunctional project groups. Typically, team members complete a questionnaire that assesses the perceived strength of each of the five areas in their team. The results are then discussed in one or more workshops where the team explores its current patterns and identifies priority areas for change.
Facilitators commonly structure interventions around the dysfunctions pyramid, starting from the base. Work often begins with exercises aimed at building trust, such as personal histories, strengths and weaknesses discussions, or 360âÂÂdegree feedback sessions. â 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.
The model has also been integrated into leadership development programs and coaching engagements. 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. 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.
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.
Overall, respected commentators typically describe LencioniâÂÂs Five Dysfunctions model as a clear, useful, memorable practitioner-oriented framework. They also criticize it for weak empirical grounding, its linear description, and limited treatment of other important issues that affect teams.
A. Main positive assessments
Both practitioner and academic commentators note three main recurring strengths.
B. Main criticisms
These can be divided between more academic criticisms and application criticisms. First, the academic criticisms:
Now the more practice-level or application criticisms:
This summarizes the fuller critical analysis into shorter bullet points:
Based on desk research and field testing over seventeen years, James Scouller proposed four frameworks in 2024: a Dual Forces model, a Team Progression Curve, a Commit-Combust-Combine (C-C-C) psychological model and a Seven-Principle (7P) action model. Unlike the others, the Dual Forces model is more academic and descriptive in nature. It has only one purpose: to explain the powerful hidden psychological forces that, in ScoullerâÂÂs view, make it harder for teams to form naturally, meaning that in his opinion conscious effort is required to maneuver around these forces if a work group is to become a genuine team. It is the other three models that concern us here as they integrate to offer a practical framework for team diagnosis and development.
Like Lencioni, who developed his model through consulting with teams, Scouller also created his frameworks based largely on extensive field experience â though in his case as a team member, leader, and coach instead of a consultant. This contrasts with thinkers like Tuckman, Belbin, Hackman, and Katzenbach & Smith, whose models primarily arose from academic research, literature reviews, or empirical studies.
According to Scouller, he perceived a gap in earlier team-development literature â the lack of an integrated approach combining the psychology of team formation with practical methods for consciously building and regenerating teams. To address that gap, he developed a set of three interconnected models, presented in his How To Build Winning Teams Again And Again trilogy (2024), to help work groups overcome hidden psychological barriers and form genuine, highâÂÂfunctioning teams at work.
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. 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.
Scouller agrees with Katzenbach & Smith that Real Teams can be intentionally built, but High-Performance Teams only emerge organically. 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.
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. Below is a summary of how Scouller outlines a work groupâÂÂs three psychological challenges:
Scouller explains the psychological rationale behind this sequencing, drawing on SchutzâÂÂs FIRO research into group behavior. 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. Having resolved that first issue, the question of roles, power and influence emerges as the dominant challenge for each member and therefore the group. 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. 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.
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. 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âÂÂ.
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.
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.
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:
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.
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. 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. 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.
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.
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. The next section will give more detail on the 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.
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. 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.
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:
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. 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âÂÂ.
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. 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. He also shows them in action through the retelling of NASAâÂÂs 1970 Apollo 13 moon mission rescue.
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.
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.
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.
Critical discussion of ScoullerâÂÂs integrated set of teamâÂÂbuilding models is still emerging, reflecting its recent publication (2024) and mainly practitionerâÂÂoriented readership. Available commentary concentrates on how reviewers see its strengths and ease of implementation, but the existing reviews do not discuss the modelsâ empirical reliability.
A. Main positive assessments
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. 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.
This summarizes the fuller critical analysis into shorter bullet points:
The six models overlap in several ways but also differ in their origins, what they focus on, how they view a groupâÂÂs change over time, and how organizations typically use them. All six aim to describe how work groups become more effective teams, yet each offers a distinctive lens: development stages, behavioral roles, enabling conditions, performance disciplines, stacked dysfunctions or integrated psychological and action frameworks. What follows is simply a comparison of the models, not a judgment of which are better or worse. All data is drawn from this articleâÂÂs preceding content.
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.
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.
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.