13.2 Team Development Models: Tuckman and Belbin

13.2 Team Development Models: Tuckman and Belbin

Definition (APM BoK7 glossary): A team is a group of people working in collaboration or by cooperation towards a common goal. BoK7 pairs this with temporary organisation (team), "a generic term used to describe a specific project, programme or portfolio team brought together specifically to implement project-based work" — the contrast with the permanent organisation is the whole reason project teams need deliberate development.

High-performing project teams do not materialize spontaneously. In permanent organizational departments, colleagues often work together for years, gradually establishing familiar routines, cultural norms, and interpersonal trust. In sharp contrast, project teams are temporary social systems. They are assembled rapidly from diverse disciplines, functional departments, geographic locations, and external supplier organizations. Team members frequently lack a shared history, speak different technical dialects, and owe conflicting loyalties to their functional line managers.

Left to chance, newly formed project groups quickly fragment into defensive silos, resulting in interpersonal friction and stalled execution. To forge a collection of disparate specialists into a unified, high-performing unit, the project manager must understand the proven psychological models that govern group dynamics. The APM Body of Knowledge highlights two foundational frameworks: Bruce Tuckman's Stages of Team Development and Dr. Meredith Belbin's Team Roles.

---

Tuckman's Stages of Team Development

Originally published by educational psychologist Bruce Tuckman in 1965, and later expanded in 1977 with Mary Ann Jensen, this model identifies five distinct, sequential stages through which teams evolve as they mature:

+-----------------------------------------------------------------------------------+
|                         TUCKMAN'S TEAM DEVELOPMENT LIFECYCLE                      |
+-----------------------------------------------------------------------------------+
|  1. FORMING    --->  2. STORMING   --->  3. NORMING    --->  4. PERFORMING        |
|  (Orientation)       (Conflict)          (Cohesion)          (Autonomous Delivery)|
|       |                   |                   |                     |             |
|   Directing            Coaching           Supporting            Delegating        |
|     (S1)                 (S2)                (S3)                  (S4)           |
|                                                                     v             |
|                                                             5. ADJOURNING         |
|                                                             (Disbandment/Closure) |
+-----------------------------------------------------------------------------------+

1. Forming (Orientation & Tentative Exploration)

• Team Behavior: Team members come together for the first time. Interactions are typically polite, formal, and cautious. Members are anxious to make a positive impression and avoid controversial topics. Uncertainty surrounds the project scope, individual responsibilities, reporting hierarchies, and acceptable behaviors.
• Interpersonal Dynamics: Trust is superficial; members act as independent individuals rather than an integrated group. There is high emotional and operational dependency on the project manager for direction.
• Project Manager's Role: Directing (S1). The project manager must take center stage, establishing a clear project charter, articulating the vision, defining explicit roles and responsibilities, setting ground rules, and conducting thorough onboarding to remove ambiguity.

2. Storming (Conflict, Power Struggles & Resistance)

• Team Behavior: As the initial veneer of politeness fades, authentic personalities and opinions surface. Team members begin to challenge the project manager's authority, contest the chosen methodologies, dispute schedule estimates, and jockey for status and influence. Frustration over workload distribution and boundary overlaps becomes vocal.
• Interpersonal Dynamics: Tension, defensiveness, and polarization into informal cliques. Team productivity frequently dips as cognitive energy is diverted toward interpersonal friction.
• Essential APM Insight: Storming is not a sign of managerial failure; it is a vital, unavoidable phase of team growth. Without storming, teams never develop genuine mutual trust or authentic communication; they remain trapped in superficial politeness. Suppressing storming drives conflict underground, leading to cynicism and passive resistance.
• Project Manager's Role: Coaching & Mediating (S2). The project manager must remain composed and impartial. They must facilitate open, constructive dialogue, guide the team through disagreements, clarify ambiguous roles, reaffirm the shared project vision, and establish psychological safety so team members can air differences without fear of reprisal.

3. Norming (Consensus, Cohesion & Standard-Setting)

• Team Behavior: The team successfully negotiates past the storming phase. Disagreements are resolved, and members establish mutually agreed operating standards, technical protocols, communication rhythms, and decision-making criteria. Individual differences are accepted and valued.
• Interpersonal Dynamics: Emerging camaraderie, mutual trust, and team cohesion. The language shifts naturally from "I" and "my tasks" to "we" and "our project." Team members actively help colleagues who are falling behind, and constructive peer feedback is welcomed.
• Project Manager's Role: Supporting & Facilitating (S3). The project manager transitions from an authoritative figure into a facilitator. They encourage the team to take collaborative ownership of decisions, reinforce positive behavioral norms, praise cross-functional teamwork, and foster an environment of continuous improvement.

4. Performing (Synergy, Autonomy & High Productivity)

• Team Behavior: The team reaches the peak of operational effectiveness. Members operate as a cohesive, highly functional unit with shared leadership. The focus is squarely on problem-solving, innovation, and achieving project objectives with minimum friction.
• Interpersonal Dynamics: Deep mutual trust, fluid competence, and high psychological safety. Team members anticipate bottlenecks, support one another instinctively, and resolve emerging challenges autonomously without needing managerial intervention.
• Project Manager's Role: Delegating (S4). The project manager steps back from day-to-day execution, granting the team operational freedom. The manager's focus shifts upward and outward: removing organizational roadblocks, securing strategic resources, shielding the team from external disruptions, and managing senior stakeholder relationships.

5. Adjourning / Mourning (Completion, Dissolution & Transition)

• Team Behavior: Added by Tuckman and Jensen in 1977, this stage occurs as the project deliverables are completed and handed over to operational users. The temporary project organization is disbanded, and members prepare to transition back to functional departments or new project assignments.
• Interpersonal Dynamics: A complex mix of emotions: satisfaction and pride in delivering project goals, accompanied by sadness, grief, or anxiety regarding the dissolution of close working relationships and future career uncertainty.
• Project Manager's Role: Facilitating Closure & Recognition. The project manager must formally celebrate team achievements, recognize individual contributions, conduct comprehensive lessons-learned retrospectives, archive project assets, and support the orderly, dignified demobilization and redeployment of personnel.

Master Comparison Table: The Five Tuckman Stages

The following table synthesizes the operational characteristics of Tuckman's model aligned with the APM PFQ examination standard.

---

Belbin's Team Roles

While Tuckman explains how teams develop over time, Dr. Meredith Belbin's research explains how individual behaviors affect team capability. In his landmark research at Henley Management College, Belbin discovered a profound paradox: teams composed exclusively of brilliant, highly analytical individuals (termed the "Apollo Syndrome") routinely failed because members engaged in destructive intellectual combat, neglected practical execution, and ignored detail. Conversely, teams that exhibited a balanced mix of complementary behaviors consistently outperformed their peers.

Belbin defined a Team Role as: "A tendency to behave, contribute, and interrelate with others in a particular way."

Belbin established a critical distinction between an individual's functional/technical role (their professional title, such as Civil Engineer, Software Developer, or Financial Analyst) and their team/behavioral role (how they interact, communicate, and solve problems within a group). Furthermore, Belbin identified the concept of "Allowable Weaknesses"—natural behavioral blind spots that accompany specific strengths. Effective leaders manage these weaknesses rather than attempting to eradicate them.

Belbin identified nine team roles, classified into three functional clusters:

+-----------------------------------------------------------------------------------+
|                         BELBIN'S NINE TEAM ROLES BY CLUSTER                       |
+-----------------------------------------------------------------------------------+
|  1. ACTION-ORIENTED ROLES    |  2. PEOPLE-ORIENTED ROLES  |  3. THOUGHT-ORIENTED ROLES|
|  • Shaper (SH)               |  • Coordinator (CO)        |  • Plant (PL)             |
|  • Implementer (IMP)         |  • Teamworker (TW)         |  • Monitor Evaluator (ME) |
|  • Completer Finisher (CF)   |  • Resource Investigator   |  • Specialist (SP)        |
|                              |    (RI)                    |                           |
+-----------------------------------------------------------------------------------+

1. Action-Oriented Cluster

• Shaper (SH): Dynamic, highly driven, thrives on pressure, courageous, and challenging. Shapers possess immense energy and determination to overcome inertia and drive the team forward toward deadlines.
  • Contribution: Challenges complacency, spurs momentum, breaks deadlocks, and drives delivery.
  • Allowable Weakness: Prone to provocation, short-tempered, impatient, and can inadvertently hurt colleagues' feelings in the pursuit of results.
• Implementer (IMP): Practical, disciplined, highly organized, systematic, and reliable. Implementers turn abstract strategies, ideas, and decisions into workable, executable tasks.
  • Contribution: Translates concepts into operational plans, creates structured schedules, ensures practical feasibility.
  • Allowable Weakness: Somewhat inflexible, slow to respond to sudden changes or unproven innovative concepts.
• Completer Finisher (CF): Painstaking, conscientious, anxious, and detail-obsessed. Completer Finishers search out errors, omissions, and defects, polishing deliverables to the highest quality standards.
  • Contribution: Ensures perfection, enforces quality control, detects obscure technical flaws before handover.
  • Allowable Weakness: Inclined to worry excessively, reluctant to delegate work, and may struggle with "perfection paralysis."

2. People-Oriented Cluster

• Co-ordinator (CO) (APM and Belbin both spell this with a hyphen): Mature, confident, trusting, and an excellent chairperson. The Co-ordinator is the role to pick when a question describes someone who focuses the team on its objectives and draws out other team members. Coordinators clarify project goals, promote balanced decision-making, identify talent, and delegate work effectively.
  • Contribution: Aligns disparate viewpoints, maintains focus on strategic objectives, brings out the best in others.
  • Allowable Weakness: Can be perceived as manipulative or inclined to offload their personal share of work onto colleagues.
• Teamworker (TW): Cooperative, diplomatic, perceptive, gentle, and empathetic. Teamworkers listen actively, defuse interpersonal conflict, support struggling colleagues, and build emotional cohesion.
  • Contribution: Fosters team harmony, prevents friction during storming, maintains morale under stress.
  • Allowable Weakness: Indecisive in critical moments, hesitant to confront difficult individuals or deliver unpopular decisions.
• Resource Investigator (RI): Extroverted, enthusiastic, communicative, and inquisitive. Resource Investigators explore opportunities, develop external networks, negotiate resources, and bring outside ideas into the team.
  • Contribution: Secures external stakeholder support, introduces innovative industry practices, uncovers commercial opportunities.
  • Allowable Weakness: Over-optimistic, and loses enthusiasm rapidly once the initial novelty of an idea wears off.

3. Thought-Oriented Cluster

• Plant (PL): Highly creative, imaginative, unconventional, and visionary. Plants generate original ideas and devise radical solutions to highly complex, intractable technical problems.
  • Contribution: Breakthrough innovations, creative problem-solving, conceptual breakthroughs.
  • Allowable Weakness: Tends to ignore practical details and protocol, preoccupied with abstract ideas, and often poor at communicating pragmatically.
• Monitor Evaluator (ME): Sober, discerning, analytical, critical, and objective. Monitor Evaluators dispassionately assess options, evaluate feasibility, weigh pros and cons, and make shrewd judgments.
  • Contribution: Prevents the team from pursuing flawed ideas, provides rigorous critical analysis, evaluates risks accurately.
  • Allowable Weakness: Lacks drive and the ability to inspire others; can appear overly skeptical, cynical, and emotionally detached.
• Specialist (SP): Dedicated, single-minded, and self-starting. Specialists provide rare, in-depth technical knowledge, expertise, and precision that the team otherwise lacks.
  • Contribution: Delivers highly specialized technical expertise, solves niche engineering or legal hurdles.
  • Allowable Weakness: Contributes strictly on a narrow front; dwells excessively on technicalities at the expense of overall project objectives.

---

The Power of Role Balance in Project Teams

A critical takeaway for the APM PFQ examination is that a team does not require nine separate individuals to cover the nine roles. In typical project settings (e.g., a core team of five or six people), team members fulfill primary, secondary, and tertiary roles.

What matters is behavioral role balance. An imbalance in team roles leads directly to project delivery failure:

• A team of only Plants generates brilliant ideas but executes nothing.
• A team of only Implementers executes tasks with flawless efficiency, but may diligently deliver an obsolete or strategically flawed solution.
• A team of only Shapers descends into continuous, destructive conflict and power struggles.
• A team lacking a Completer Finisher produces deliverables containing preventable defects, failing quality audits at stage gates.

By assessing Belbin profiles during team formation, the project manager intentionally balances behavioral roles, leverages individual strengths, mitigates allowable weaknesses, and builds an adaptable, high-performing delivery team.