Team jell is DeMarco and Lister's term for the phenomenon of a team becoming more than the sum of its parts — a qualitative shift in collective performance, identity, and cohesion that cannot be reduced to the capabilities of the individual members. The concept first appears in peopleware (1987) as a counterpoint to the dominant management model of treating software teams as collections of interchangeable productive units.
Characteristics of a Jelled Team
DeMarco and Lister describe jelled teams by their observable properties rather than by mechanism:
These characteristics are mutually reinforcing: low turnover enables shared identity, shared identity produces joint ownership, joint ownership creates enjoyment, and enjoyment sustains low turnover.
Management's Role: Creating Conditions, Not Managing Process
The most important and counterintuitive claim about team jell is about the appropriate management response to it. DeMarco and Lister argue that management cannot engineer jell directly — attempts to manufacture team spirit through mandated activities, retreats, or forced team-building typically fail. What management can do is create or destroy the conditions under which jell might occur spontaneously.
Conditions that enable jell:
Conditions that prevent or destroy jell:
Team Assassination
DeMarco and Lister name the breaking-up of jelled teams "team assassination" and treat it as one of the most expensive management errors in software. The typical scenario: a team jells over a project, delivers something exceptional, and then management — seeing a group of talented people — distributes them across other projects to maximize coverage. The result is that the jelled team's capability, which was a property of the group and not simply the sum of individual abilities, is destroyed. Each individual carries their own skills to the new assignment; none carries the jell.
The economic argument is that jell takes time to accumulate and cannot be accelerated by management fiat. Destroying a jelled team to optimize short-term resource allocation sacrifices a long-term asset that may take years to rebuild.
Connection to the Coding War Games
The coding-war-games data provides indirect support for team jell. The matched-pair analysis showed that performance varied substantially among people from the same organization — and DeMarco and Lister observed that organizations with better environmental conditions (the same factors that enable jell) produced better individual performers. While the Coding War Games measured individuals rather than teams, the environmental factors that enable jell and the environmental factors that produce high individual performance are largely the same.
Later Development
The concept appears in adrenaline-junkies-and-template-zombies (2008), where team dynamics in crisis-driven and process-driven organizations are analyzed through the lens of patterns. The pathological team patterns in that book are largely recognizable as anti-jell conditions: constant urgency, template compliance as a substitute for judgment, and management by pressure rather than by trust.