Tuckman's Forming-Storming-Norming-Performing: The Team Development Model With Weak Evidence

It is the second day of a two-day leadership offsite at a hotel conference center somewhere outside the city, and the facilitator has just clicked to a slide titled “Stages of Team Development.” Four boxes are arranged on a clean horizontal axis, each one connected to the next by a thin black arrow. Forming. Storming. Norming. Performing. The facilitator — a former HR director, now an independent organizational-development consultant on her second engagement of the quarter — walks the room through the framework with practiced cadence. The new team members were polite at first, she explains; that was forming. Then they had some friction about the project plan; that was storming. Then they worked out the norms; that was norming. And in the next quarter, if all goes well, they will be performing. There are nods around the table. The slide has been on screen for less than three minutes. The framework being presented as a settled scientific account of how teams develop is a memorable four-word mnemonic from a 1965 literature review of therapy groups whose empirical basis has been formally contested for nearly four decades, and the version of the model with the fifth stage added — adjourning — was based not on direct observation but on a graduate student’s follow-up literature search published twelve years after the original.

That four-word mnemonic is the Tuckman model, and the original paper is Bruce W. Tuckman’s “Developmental sequence in small groups,” published in Psychological Bulletin in 1965 (vol. 63, no. 6, pp. 384-399, DOI: 10.1037/h0022100). The follow-up adding the fifth stage is Tuckman and Mary Ann C. Jensen’s “Stages of small-group development revisited,” published in Group & Organization Studies in 1977 (vol. 2, no. 4, pp. 419-427, DOI: 10.1177/105960117700200404). Together these two papers are arguably the most cited empirical-looking framework in the corporate leadership-development curriculum. The forming-storming-norming-performing sequence appears in nearly every introductory management textbook published in the last forty years, in nearly every team-building workshop deck, in nearly every consulting-firm leadership-development module, and in the formal training curricula of the U.S. military, NATO, the British Civil Service, and most of the Fortune 500. The framework is so embedded in the language of corporate teamwork that the verbs themselves — “we are still in storming,” “this team has not normed yet” — are used as shorthand in executive conversations.

The empirical reality is more uncomfortable. The 1965 Tuckman paper was not a longitudinal study of work teams. It was a literature review. Tuckman, then a research psychologist working at the U.S. Naval Medical Research Institute, surveyed fifty published papers on group development — most of them descriptions of therapy groups, T-groups (training groups), and laboratory groups, with relatively few based on intact work teams — and synthesized the patterns he found across that heterogeneous literature into the four-stage sequence the world now knows. He explicitly described the synthesis as tentative and called for empirical verification. The 1977 follow-up with Jensen added the fifth stage (adjourning) based on a further literature review Jensen had conducted as part of her graduate work. Tuckman himself, in subsequent interviews, acknowledged that the framework was a heuristic synthesis rather than an empirically verified developmental theory.

Twenty-three years after the original Tuckman paper, Harvard organizational behavior researcher Connie J. G. Gersick published “Time and transition in work teams: Toward a new model of group development” in the Academy of Management Journal (1988, vol. 31, no. 1, pp. 9-41, DOI: 10.2307/256496) — a direct longitudinal observational study of eight actual project teams executing real work under real time constraints. Gersick did not find Tuckman’s four stages. She found a different pattern entirely: a “punctuated equilibrium” model in which teams settle into an initial behavioral pattern at the start of a project, persist in that pattern with relatively little change through roughly the midpoint of the project’s timeline, then undergo a sharp transition at the midpoint — often triggered by the team’s awareness of how much time remained — and then settle into a second, different pattern through the second half of the project. Two phases, separated by a midpoint transition. Not four stages, not linear progression, not the model on the offsite slide.

This article walks through what Tuckman actually claimed, what Gersick actually found, what the broader team-research literature has concluded since, and what an executive evaluating a leadership-development program built around forming-storming-norming-performing should actually do with the framework. Like the MBTI case, the CliftonStrengths case, and the Kübler-Ross stages case, Tuckman’s model is best understood not as settled science but as a memorable conceptual heuristic whose institutional dominance in corporate training is largely independent of its empirical foundation.

What Tuckman 1965 Actually Was

The Tuckman 1965 paper is fewer than sixteen pages of double-spaced text, and any careful reading of it makes clear what the paper is and is not. It is a synthesizing literature review. The paper’s opening sentence describes the work as an attempt “to review and synthesize the literature dealing with the developmental sequences in small groups.” Tuckman identified fifty studies, classified them by setting (therapy groups, T-groups/training groups, laboratory experimental groups, and natural groups), and tabulated the developmental patterns each study reported. From the tabulation he extracted what he argued was a recurrent four-stage pattern, which he labeled at the time using the phrases “forming,” “storming,” “norming,” and “performing” — the rhyming mnemonic that would later carry the framework into the corporate vernacular.

The sample of fifty studies is heavily skewed toward therapy and training-group contexts. Of the fifty, roughly half are studies of therapy groups (group psychotherapy populations, encounter groups, sensitivity-training groups) and another quarter are studies of T-groups conducted at the National Training Laboratories and similar mid-twentieth-century human-relations training programs. The “natural groups” category — actual work teams in field settings — accounts for a small minority of the underlying studies. The studies Tuckman synthesized were also methodologically heterogeneous: case studies, ethnographic observations, brief intervention studies, single-session laboratory observations, and a handful of longer-term observations. The studies did not use a common measurement framework, did not operationalize “stage” consistently, and did not in most cases conduct longitudinal observation of intact groups across the full developmental trajectory.

Tuckman’s synthesis was clear about its provisional nature. The paper’s discussion section explicitly notes that the four-stage model is hypothesis-generating rather than confirmatory, that the underlying studies are heterogeneous and not directly comparable, and that direct longitudinal observation of intact groups would be needed to test whether the stage sequence actually holds. He called for follow-up empirical work. The framework was published as a synthesis to be tested, not as a tested theory to be applied.

Two things are worth flagging from a methodological standpoint. First, the underlying studies were dominated by therapy-group and training-group contexts, which differ in important ways from work teams: they are voluntary, temporary, focused on interpersonal-relationship work rather than task accomplishment, and led by professional facilitators whose role is to shape group dynamics. Generalizing from therapy-group developmental patterns to corporate project-team developmental patterns requires assumptions about cross-context generalizability that the underlying studies do not test. Second, the 1965 paper was published in Psychological Bulletin — a respected peer-reviewed journal whose explicit editorial mission is review articles, which is what Tuckman submitted. The paper went through peer review appropriate for a review article, but a review article in a peer-reviewed journal is not the same as a confirmatory empirical study. It is a synthesizing analysis whose evidentiary status depends entirely on the quality of the underlying studies being synthesized.

The Four (Plus One) Stages As Commonly Taught

The corporate-training version of Tuckman’s model usually presents the stages as follows:

Forming. The team is new. Members are polite, somewhat reserved, and oriented toward establishing what the team is for and who the others are. There is dependence on the leader for direction. Task work is limited because attention is on interpersonal orientation. The stage is characterized as low conflict, low productivity, and high uncertainty.

Storming. Members begin to assert their preferences, raise objections, and contest the team’s direction. Interpersonal conflict surfaces. Subgroups may form. The team’s task performance is disrupted by relational friction. The stage is characterized as high conflict, moderate productivity, and high emotional intensity. This is the stage that, in the corporate-training narrative, requires active management — the leader must “facilitate the storm” so the team can move through it rather than dissolving.

Norming. Conflicts are resolved (or shelved), shared norms emerge, the team coheres around a common approach to the work, and cooperative behavior increases. The leader’s role shifts from arbitrating conflict to coordinating the now-aligned team. The stage is characterized as low conflict, increasing productivity, and emerging interpersonal trust.

Performing. The team executes effectively. Members work autonomously within the established norms, focus on task accomplishment, and resolve emergent problems without the relational disruption that characterized storming. The leader’s role becomes coaching and removing obstacles rather than directing. The stage is characterized as low conflict, high productivity, and high mutual trust.

Adjourning (added in Tuckman and Jensen 1977). The team’s work concludes, members disengage emotionally, and the team dissolves. The corporate-training version often emphasizes the importance of formal closure rituals and acknowledgement of the team’s accomplishments before disbanding.

The cleanness of the five-word sequence — and the rhyming structure of the original four — is part of why the model is so easy to remember and so easy to teach. A facilitator can introduce all five stages in four minutes. A trainee can recall the sequence weeks later. The mnemonic is, by the standards of corporate leadership-development content, extraordinarily well-engineered for retention.

The cleanness of the sequence is also part of why the model is misleading. Real teams in real organizations do not produce neat linear developmental sequences. Real teams sometimes never “storm” at all — particularly when the team is composed of professionals who have worked together before, or when the task structure is well-defined enough to obviate relational negotiation. Real teams sometimes storm repeatedly throughout the project lifecycle as new sub-problems emerge. Real teams sometimes perform from week one and never visibly storm or norm in any way an observer could identify. Real teams sometimes get stuck in storming and never reach a coherent norming phase. Real teams sometimes form, perform, and adjourn without any visible intermediate phases. The variance in real team developmental trajectories is large, and the linear four-stage model is a poor fit for most of the variance the team-research literature has subsequently documented.

Gersick 1988 — The Punctuated Equilibrium Alternative

The most important direct empirical challenge to the Tuckman model comes from Connie J. G. Gersick’s 1988 Academy of Management Journal paper, “Time and transition in work teams: Toward a new model of group development.” Gersick, then a doctoral student at Yale and later a faculty member at NYU and UCLA, conducted what the Tuckman 1965 paper had explicitly called for and that the corporate-training literature had largely skipped past in the intervening twenty-three years: a direct longitudinal observational study of intact work teams executing real tasks under real deadlines.

The Gersick design was methodologically careful. She studied eight actual project teams — drawn from a mix of MBA-program task forces, a community fund-raising team, a bank operations team, a university medical school faculty committee, a hospital administration team, and other natural work groups — observed each from formation through completion (or until the project ended), recorded team meetings, transcribed interactions, and analyzed the data without pre-imposing a stage framework on the observations. The teams worked on projects ranging from a few days to roughly six months. The observation was prospective and longitudinal, the analysis was inductive, and the project sample was diverse enough to provide some basis for generalization across project types and time horizons.

Gersick did not find the Tuckman stages. The pattern she found and labeled “punctuated equilibrium” — borrowing the term from evolutionary biology, where it describes the pattern in which species evolve through long periods of stability interrupted by short bursts of rapid change — was substantively different from a linear stage model. Specifically:

Phase 1 — initial pattern. Each team established a stable behavioral pattern within the first meeting or two. The pattern was idiosyncratic to that team and reflected the members’ initial orientations, the task structure, and the leader’s setup. Once established, the pattern persisted with relatively little change. Teams did not visibly progress through storming and norming during this phase. They settled into a way of working and stayed there.

Midpoint transition. Roughly at the temporal midpoint of the project — measured in calendar time, not in work-progress terms — every team in Gersick’s sample underwent a discrete and observable transition. The midpoint was often marked by an explicit team awareness of how much time remained, sometimes triggered by a calendar event or an external deadline reminder. The transition was sharp, occurred over the span of one or two meetings, and produced substantial change in the team’s approach to the work — sometimes including redefinition of the task itself, reorganization of subgroup roles, reset of the working norms, and renewed urgency about external coordination.

Phase 2 — second pattern. Following the midpoint transition, each team settled into a second stable pattern, also persisting until the project’s conclusion. The phase-2 pattern was often more externally oriented (more coordination with stakeholders outside the team), more task-focused, and more output-driven than the phase-1 pattern.

The pattern Gersick documented is not Tuckman’s four-stage linear progression. It is two phases of stability separated by a discrete transition triggered by temporal awareness. The implications are operationally different. A leader operating on the Tuckman model expects to manage a team through storming and into norming; a leader operating on the Gersick model expects to manage the team through the midpoint transition, which is the actual high-leverage intervention point. The Tuckman model says the leader’s job is to help the team work through conflict; the Gersick model says the leader’s job is to help the team make the most of the midpoint reset. These are different jobs.

The Gersick paper has been cited thousands of times in the academic organizational-behavior literature and is widely regarded as a foundational paper in team-development research. It has been replicated and extended by subsequent researchers — Seers and Woodruff (1997), Lim and Murnighan (1994), and Okhuysen and Waller (2002), among others — who have generally found broad support for the punctuated-equilibrium pattern in project teams with defined deadlines, while also documenting that real team trajectories are more heterogeneous than either Tuckman or Gersick fully captures. In the academic team-research discipline, the Tuckman stages are not treated as a settled descriptive model of team development. They are treated as a historical heuristic that has been substantially superseded by more empirically grounded frameworks.

Why The Tuckman Model Persists In Corporate Training

If the empirical literature on team development has moved substantially past forming-storming-norming-performing, why does the framework continue to dominate corporate leadership-development curricula? The answer is a mix of factors that, much like in the CliftonStrengths and MBTI cases, have very little to do with what the empirical literature says.

The mnemonic is unbeatable. Forming, storming, norming, performing. Four words, rhyming, sequential, easy to teach in four minutes and easy to recall weeks later. From a training-content-design standpoint, the mnemonic is brilliant. Any competing framework — including Gersick’s punctuated equilibrium, Hackman’s team-effectiveness model, or the team-effectiveness frameworks from the academic literature — is heavier and harder to teach. A facilitator can introduce Tuckman’s model in less time than it takes to make a cup of coffee. The competing frameworks require more setup, more vocabulary, and more cognitive effort from the trainee. In the marketplace for corporate training content, the framework that is easier to teach wins.

The framework provides actionable shorthand. “We are in storming” is a useful executive sentence. It explains observed conflict, it implies that the conflict is normal and expected, it predicts that the conflict will resolve, and it points the leader at a coherent intervention. The fact that real teams may not actually be in a stage called storming and that the predicted progression may not actually occur is operationally less important than the framework providing a shared vocabulary for the team’s experience. Vocabulary that is useful for executive coordination tends to persist even when the underlying model it implies has weak empirical support.

The framework is on the licensure curriculum. PMP (Project Management Professional) certification, the SHRM-CP (HR certification), various leadership-development credentials, and many MBA program syllabi include Tuckman’s stages as foundational content. Once a framework is embedded in a professional credentialing curriculum, the institutional cost of removing it is high — the certification body would need to revise the exam, the training providers would need to revise their materials, the textbook publishers would need to revise their books, and the practicing professionals would need to relearn the new framework. The status-quo bias in credentialing curricula is strong.

It does not visibly harm anyone. Unlike the reading wars case where the framework produced measurable harm to children’s reading outcomes, or the hormone-replacement therapy reversal case where the framework caused measurable harm to patients, the Tuckman framework’s empirical weakness does not produce visible harm. A team trained on Tuckman’s stages still works on its project; the project still gets delivered or fails for reasons mostly orthogonal to whether the framework correctly describes team development; the team members still go home satisfied with what they learned at the offsite. The framework being descriptively wrong does not produce a feedback signal that would cause practitioners to abandon it.

The framework feels true. This is the most subtle and most important factor. Anyone who has worked on teams can recall instances where the team was awkward at first (forming), then had some friction (storming), then settled into a way of working (norming), then performed well (performing). The framework is general enough that confirming instances can be found in almost any team experience, while disconfirming instances are interpreted as “we got stuck in storming” or “we skipped forming because we knew each other” rather than as evidence against the framework. This is the same confirmation-by-vagueness pattern that sustains Barnum-effect personality assessments and several other intuitive-feeling but empirically thin frameworks.

Tuckman’s own positioning was modest. Tuckman himself, in subsequent interviews and in the 1977 update, was relatively measured about the empirical status of the framework. He framed it as a useful synthesis of the available literature, called for further empirical work, and did not aggressively promote the framework as a validated theory. The aggressive corporate promotion of forming-storming-norming-performing came from training-content developers, consulting firms, and textbook authors who repackaged Tuckman’s modest synthesis as a confident developmental theory. The original author cannot be blamed for the marketing the framework received downstream of his publication.

None of these factors are reasons Tuckman’s stages are the best descriptive model of team development. They are reasons Tuckman’s stages are the institutionally dominant pedagogical framework. The two are different questions, and the gap between them is the gap this article documents.

Modern Team Research — What Has Replaced Tuckman

The academic discipline of organizational behavior has, over the four decades since Gersick 1988, accumulated a substantial body of empirical work on what actually predicts team effectiveness. The frameworks that have emerged from that work are more empirically grounded than Tuckman’s stages, more operationally specific, and more useful for an executive seriously trying to improve team performance. A few of the most important:

J. Richard Hackman’s team-effectiveness model. Hackman, a Harvard organizational psychologist who spent four decades studying real teams in field settings, developed an empirically grounded framework for what makes teams effective. The model (most fully articulated in Hackman’s Leading Teams, 2002, and refined in subsequent work) identifies a small number of “enabling conditions” that empirically predict team performance: a real team (clear boundaries, stable membership), a compelling direction (clear, challenging, consequential goals), an enabling team structure (right people, well-designed task, clear norms of conduct), a supportive organizational context (rewards, information, resources, education), and competent coaching (focused on team processes, delivered at the right time in the team’s life). Hackman’s model is the empirically dominant framework in academic team research and it is not a developmental-stages model. It is a structural-conditions model. The leader’s job is not to “help the team move from storming to norming.” It is to design the enabling conditions that empirically predict team effectiveness, and then to coach the team’s processes within those conditions.

Amy Edmondson’s psychological safety research. Edmondson, also at Harvard, has spent two decades documenting one of the most robust empirical findings in team research: psychological safety — the shared belief that the team is safe for interpersonal risk-taking, that members can speak up with questions, concerns, or mistakes without fear of negative interpersonal consequences — strongly predicts team learning behavior, team performance, and team innovation. The foundational paper is Edmondson, A. C. (1999), “Psychological safety and learning behavior in work teams,” Administrative Science Quarterly, 44(2), 350-383. Subsequent research, including Google’s well-publicized internal “Project Aristotle” study, has consistently identified psychological safety as the single most important team-level predictor of effectiveness. Psychological safety is not a stage in a developmental sequence. It is a team-level climate variable that varies independently of how long the team has been together. The leader’s job is to actively build and maintain psychological safety from day one, not to expect that the team will “norm” its way into it by stage three.

Wageman, Gardner, and Mortensen on team variation. Wageman, R., Gardner, H., & Mortensen, M. (2012), “The changing ecology of teams: New directions for teams research,” Journal of Organizational Behavior, 33(3), 301-315, DOI: 10.1002/job.1775 — a synthesizing review by three of the leading team researchers — documents the substantial variation in team types in modern organizations and argues that a single developmental model cannot fit the diversity of teams operating today. Virtual teams, multiteam systems, fluid teams with rotating membership, networks of teams, and rapidly assembled “swarm” teams have developmental trajectories substantially different from the co-located, stable-membership project teams that the Tuckman framework was implicitly built around. The Wageman et al. review argues that team research needs frameworks adapted to the specific team types and contexts modern organizations actually deploy, not a one-size-fits-all stage model derived from mid-twentieth-century therapy groups.

Goal-setting, role clarity, and other process variables. Decades of meta-analytic work in industrial-organizational psychology have established that several team-process variables consistently predict team performance: goal clarity, role clarity, communication frequency and quality, coordination mechanisms, and feedback availability. None of these are stages. They are continuous variables that vary across teams and across time within teams. The leader’s job is to actively manage them, not to wait for the team to develop them through a natural-stage progression.

The collective implication of the modern team-research literature is that the executive who wants to lead teams well should learn the structural-conditions framework (Hackman), build psychological safety (Edmondson), be aware of context-specific team types (Wageman et al.), and actively manage process variables. Knowing the Tuckman mnemonic is essentially irrelevant to actual team leadership. It is a vocabulary, not a tool.

The Strategist Takeaway

For a CHRO, COO, or CEO evaluating whether to continue using Tuckman’s stages as the foundation of the company’s leadership-development curriculum, the calibrated answer is:

Tuckman’s stages are a heuristic, not a validated model. The framework was published in 1965 as a synthesis of fifty heterogeneous studies, mostly of therapy and training groups. The author himself called for further empirical verification that has not, in the subsequent six decades, substantially confirmed the linear-stage progression in real work teams. The independent academic team-research literature has moved past the model. Treating the framework as a settled scientific account of team development is overstating what the evidence supports.

Continuing to teach the model is not catastrophic. Unlike frameworks that produce measurable harm, Tuckman’s stages are operationally benign. Trainees who learn the model do not, in most cases, make worse leadership decisions because of it — they just acquire a vocabulary that is somewhat disconnected from what the empirical literature on teams actually says. If the leadership-development program is already built around the model and the cost of replacing it is high, continuing to teach it as a “useful conceptual heuristic” rather than as a validated theory is a defensible compromise.

The opportunity cost is real. Time spent in leadership development on forming-storming-norming-performing is time not spent on Hackman’s enabling conditions, Edmondson’s psychological safety, or the team-process variables the empirical literature actually supports. If you are building a leadership-development curriculum from scratch, the right move is to skip Tuckman and anchor on the structural-conditions and climate frameworks the modern literature supports. If you are revising an existing curriculum, the right move is to add the Hackman and Edmondson content as foundational and demote Tuckman to a historical-context callout.

For evaluating leadership-development vendors, the question to ask is what frameworks their curriculum is built around. A vendor whose team-development content is entirely the Tuckman stages is selling 1965 content with a 2025 brand. A vendor whose content is built around Hackman’s enabling conditions, Edmondson’s psychological safety, and an explicit awareness of team-type variation is selling content that reflects the current state of the academic literature. The price differential between the two is usually small; the content quality differential is large.

Beware the mnemonic trap. Frameworks survive in corporate training because they are memorable, not because they are correct. The forming-storming-norming-performing mnemonic is one of the best-engineered memorable frameworks in management content. Hackman’s enabling conditions, Edmondson’s psychological safety construct, and the broader team-process variable set are harder to teach because they are more granular, more empirically grounded, and less amenable to a four-word rhyming summary. The mnemonic advantage is real; the empirical disadvantage is also real; the executive choice is which to weight.

The pattern this article documents is the same pattern documented for MBTI, CliftonStrengths, Kübler-Ross’s grief stages, Maslow’s hierarchy, and Goleman’s emotional intelligence: a memorable conceptual framework that became institutionally dominant in corporate training despite limited or contested empirical support, and that persists in the corporate ecosystem long after the academic literature has substantially moved on. The executive who reads only the practitioner literature on team development will conclude that Tuckman’s stages are settled science. The executive who reads the academic literature on teams will conclude that the stages are a historical synthesis whose empirical claims have been substantially superseded. The gap between the two is, as in the other cases, large, persistent, and economically consequential for organizations spending millions per year on leadership development.

Sources

Primary sources (Tuckman):

• Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384-399. DOI: 10.1037/h0022100
• Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of small-group development revisited. Group & Organization Studies, 2(4), 419-427. DOI: 10.1177/105960117700200404

Empirical alternative — punctuated equilibrium:

• Gersick, C. J. G. (1988). Time and transition in work teams: Toward a new model of group development. Academy of Management Journal, 31(1), 9-41. DOI: 10.2307/256496
• Gersick, C. J. G. (1989). Marking time: Predictable transitions in task groups. Academy of Management Journal, 32(2), 274-309. DOI: 10.2307/256363
• Seers, A., & Woodruff, S. (1997). Temporal pacing in task forces: Group development or deadline pressure? Journal of Management, 23(2), 169-187. DOI: 10.1177/014920639702300204
• Okhuysen, G. A., & Waller, M. J. (2002). Focusing on midpoint transitions: An analysis of boundary conditions. Academy of Management Journal, 45(5), 1056-1065. DOI: 10.2307/3069330

Modern team-effectiveness frameworks:

• Hackman, J. R. (2002). Leading Teams: Setting the Stage for Great Performances. Boston: Harvard Business School Press.
• Hackman, J. R., & Wageman, R. (2005). A theory of team coaching. Academy of Management Review, 30(2), 269-287. DOI: 10.5465/amr.2005.16387885
• Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. DOI: 10.2307/2666999
• Edmondson, A. C. (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Hoboken, NJ: Wiley.
• Wageman, R., Gardner, H., & Mortensen, M. (2012). The changing ecology of teams: New directions for teams research. Journal of Organizational Behavior, 33(3), 301-315. DOI: 10.1002/job.1775

Critical and synthesizing reviews:

• Bonebright, D. A. (2010). 40 years of storming: A historical review of Tuckman’s model of small group development. Human Resource Development International, 13(1), 111-120. DOI: 10.1080/13678861003589099
• Cassidy, K. (2007). Tuckman revisited: Proposing a new model of group development for practitioners. Journal of Experiential Education, 29(3), 413-417. DOI: 10.1177/105382590702900318
• Kozlowski, S. W. J., & Ilgen, D. R. (2006). Enhancing the effectiveness of work groups and teams. Psychological Science in the Public Interest, 7(3), 77-124. DOI: 10.1111/j.1529-1006.2006.00030.x (Comprehensive review of the team-effectiveness literature, including discussion of developmental-stages models.)
• Mathieu, J., Maynard, M. T., Rapp, T., & Gilson, L. (2008). Team effectiveness 1997-2007: A review of recent advancements and a glimpse into the future. Journal of Management, 34(3), 410-476. DOI: 10.1177/0149206308316061

Related

• /replication-crisis/ — Replication Crisis Hub home, covering 80+ canonical findings that did not survive independent scrutiny.
• /replication-crisis/kubler-ross-five-stages/ — The grief-stages model is the closest cousin of Tuckman’s: a memorable stage framework synthesized from interview observations, never empirically validated as a sequence, but institutionally dominant in healthcare and HR training.
• /replication-crisis/maslow-hierarchy-of-needs/ — Maslow’s pyramid is the foundational case of a memorable stage-like framework that was never tested as a sequence by its author but became management-curriculum orthodoxy anyway.
• /replication-crisis/myers-briggs-mbti/ — The corporate-assessment-product-as-management-fashion case. MBTI and Tuckman are both examples of frameworks that dominated leadership development through institutional momentum rather than empirical validation.
• /replication-crisis/cliftonstrengths-strengthsfinder/ — The other commercially polished leadership-development assessment whose independent academic validation is thin relative to its commercial scale.
• /replication-crisis/goleman-emotional-intelligence/ — Goleman’s framework is a parallel case: a memorable, executive-friendly synthesis whose strong-form empirical claim has not survived independent peer-reviewed scrutiny.

FAQ

Q: Should our company stop teaching Tuckman’s stages?

A: Not necessarily. The framework is a useful conceptual heuristic for introducing the idea that teams develop over time and that a team’s effectiveness today does not predict its effectiveness in three months. The problem is treating the four-stage linear progression as a settled scientific account of how teams actually develop. The right compromise for most companies is to teach Tuckman’s stages as historical context and then move to the empirically grounded frameworks — Hackman’s enabling conditions, Edmondson’s psychological safety, and the team-process variables the modern literature supports. If your leadership-development curriculum is entirely built around Tuckman, you are teaching 1965 content with a 2025 brand.

Q: Is Tuckman’s model as weak as MBTI?

A: Roughly similar empirical status, different failure modes. MBTI’s problem is poor test-retest reliability and weak construct validity — the instrument does not reliably measure what it claims to measure. Tuckman’s problem is different — the framework was a literature review, not a measurement instrument, and the empirical question is whether real work teams actually develop through the linear stages he synthesized. The independent observational evidence (Gersick 1988 and subsequent replications) suggests they generally do not. Both frameworks are commercially dominant despite weak empirical foundations; both persist for reasons largely independent of what the empirical literature says.

Q: What about the Tuckman and Jensen 1977 update with the fifth stage — is that more empirically grounded than the 1965 paper?

A: No. The 1977 update was based on Mary Ann Jensen’s review of additional literature published between 1965 and 1977 — primarily an extended literature search rather than direct longitudinal observation of intact work teams. The fifth stage (adjourning) was added to capture the end-of-project disengagement and dissolution phase the original four-stage model did not address. As with the 1965 paper, the synthesis is reasonable as a literature review and provisional as a developmental theory. It does not have the empirical foundation that direct longitudinal observation would provide.

Q: Is Gersick’s punctuated-equilibrium model the “correct” replacement for Tuckman?

A: Not exactly. Gersick’s model has stronger empirical foundations than Tuckman’s for the specific case of project teams with defined deadlines, but the broader academic team-research literature has documented that real team developmental trajectories are heterogeneous enough that no single developmental model fits all team types. The Hackman team-effectiveness model and the Edmondson psychological-safety framework — neither of which is a developmental-stages model — are arguably more useful frameworks for the executive trying to actually improve team performance. The right intellectual move is to retire the “what stage is the team in” question and replace it with the structural-conditions and climate questions the modern literature supports.

Q: Tuckman is on the PMP exam — do we have to keep teaching it?

A: For project managers preparing for PMP certification, yes — they need to know the framework because it is on the test. The right approach for an internal corporate leadership-development program is to teach Tuckman as exam content and as a historical heuristic, while also teaching the empirically grounded frameworks (Hackman, Edmondson) as the substantive content for actually leading teams. The two roles — passing the exam and leading a team well — can coexist in the curriculum, and clarifying the distinction reduces the risk that trainees overclaim what the Tuckman stages predict.

Q: Why has corporate training not absorbed the academic critique even though Gersick 1988 has been around for nearly four decades?

A: The same reason that other commercially successful but empirically thin frameworks persist — pedagogical convenience (the mnemonic is unbeatable), institutional momentum (Tuckman is in textbooks, training curricula, and certification exams), absence of visible harm (a team learning the wrong framework still delivers projects), confirmation bias (the framework is general enough that confirming instances can always be found), and the gap between practitioner and academic literatures. The corporate training market is driven by what is easy to teach and what credentialing bodies require, not by what the academic literature concludes. This pattern is documented across multiple cases in this hub.

Q: What is the single best alternative framework to teach in leadership development?

A: Hackman’s enabling conditions for team effectiveness, paired with Edmondson’s psychological safety construct. Hackman’s framework (real team, compelling direction, enabling structure, supportive context, competent coaching) tells the leader what to design before the team starts working. Edmondson’s framework tells the leader what climate variable to actively build and maintain throughout the team’s life. Together they cover the structural and climate conditions that the empirical literature supports as predictive of team performance. They are harder to teach than Tuckman’s stages — neither has a four-word rhyming mnemonic — but they are what the modern literature supports.

Q: What is the single best thing to read on this?

A: Read Tuckman 1965 and Gersick 1988 side by side. The two together are a clean illustration of how a 1965 literature-review synthesis and a 1988 direct longitudinal observational study can produce different accounts of the same underlying phenomenon, and how the corporate-training ecosystem can institutionalize the earlier and weaker account while ignoring the later and stronger one for nearly four decades. Then read Hackman’s Leading Teams (2002) for the structural-conditions framework and Edmondson’s The Fearless Organization (2019) for the psychological-safety framework. A reader who works through all four will have a substantially more calibrated view of team development than 95% of corporate leadership-development trainees.