Two takes on the same idea
There is a book on the shelf called Team Intelligence. There is also a platform called QuestWorks that is built around the same idea from a different angle. This piece sits the book and the platform next to each other for readers who have already heard the term and want a practitioner read on how they relate. The canonical QuestWorks definition lives in What Is Team Intelligence? Definition + Framework. The short version: team intelligence is what a team knows about itself, what its leader knows about it, and what it does with that knowledge automatically. QuestWorks builds all three. The book takes a different cut on the same territory and is worth reading on its own terms.
What the book argues, in fair summary
Behavioral scientist Jon Levy published Team Intelligence: How Brilliant Leaders Unlock Collective Genius with Harper Business in October 2025. He defines team intelligence as "the collective ability of a group to reason, focus, and draw on its full range of skills to solve problems faster than any individual could alone" (Mindvalley interview).
The book is organized into three parts: "Leadership: Unburdened" (chs. 1-3), "Teams: Unlocked" (chs. 4-9, the heart of the book, with the three pillars at chs. 6, 7, and 8), and "Organizations: Unleashed" (chs. 10-11). Each chapter ends with an "Ideas in Action" section so leaders can convert reading into practice.
Levy's central paradox is the line that the book turns on. "The smallest unit of effectiveness at work isn't a leader or an individual. It's a team" (Mindvalley). That sentence does a lot of work, because the title of the book promises brilliant leaders unlocking collective genius and the body of the book argues that focusing on the leader is exactly what produces the best leaders. The leader matters because the team matters more.
The case library is strong: LEGO's turnaround under Jørgen Vig Knudstorp, Pixar's story room, the failed two billion dollar Quibi launch, the 1998 DaimlerChrysler merger, the 1980 U.S. Olympic basketball team, and the Miami Heat's journey from the disappointing 2010 superteam to the 2012-13 championship dynasty after Shane Battier joined. He also revisits William Muir's chicken study, the experiment in which a flock of high producing "super chickens" pecked each other to death while the average flock thrived. He calls the same dynamic in human teams the "too much talent problem." Quibi is the human version of the chickens.
The character at the center of the book is the Glue Player. Shane Battier is the archetype. "Glue players might not be the stars that shine the brightest, but their gravity is so strong that they pull everyone else in" (Mindvalley). In a Wall Street Journal piece republished by NASMM, Levy puts it this way: "A glue player is the team member who multiplies everyone else's results, helping the team win. They have unusually high emotional intelligence and know how to move the group forward" (NASMM republication).
The empirical anchor he leans on most is Anita Woolley's c-factor research and Google's Project Aristotle. In a Boston Globe op-ed, Levy summarized Aristotle as having "examined 250 attributes across roughly 180 company teams, identifying psychological safety as the strongest predictor" (Boston Globe). The reception has been strong. Both Publishers Weekly and Kirkus gave starred reviews. Critical readers have noted that the book occasionally prioritizes breadth over depth on complex psychological safety dynamics, and that the corporate slant may not land for non-business readers. Worth knowing going in.
Where we agree, fully
The overlap is real and worth naming clearly. Levy is right about several things that the rest of the team development industry still gets wrong, and his book is the cleanest mainstream articulation of these claims to date.
The team is the unit of effectiveness. The book opens on this and closes on this. "The role of a leader is very limited in terms of its impact. Most of the work happens between team members" (Chad & Cheese podcast). That sentence is the foundation of the entire field. Tools that target individual performance in isolation cannot reach the layer where most of the work actually happens.
Stacking talent does not produce a team. The Super Chickens chapter, the Miami Heat 2010 case, and the Quibi case all carry the same message. A roster of stars without an environment that makes pro-social behavior pay can perform worse than an average roster that knows how to play together. The Battier hire is the corrective. He raised the ceiling of every other player on the floor.
Glue players matter more than star players. This is the philosophical heart of the book and it maps almost exactly onto the QuestWorks XP design. Inside QuestWorks, players earn XP for the strengths-based behaviors that move the team forward, including the contributions that conventional measurement misses. Levy arrives at this conclusion by studying elite teams that already exhibit it; the QuestWorks design started from the same conviction and built a practice environment around it.
Standard measurement systems cannot see what matters. The Battier line in the book lands hard. "Shane Battier is a no stats all star because the current statistic system doesn't understand how to measure his behavior. It's not that he's not a star. It's just we're measuring stars wrong" (Chad & Cheese). In the WSJ piece republished by NASMM, Levy is even more direct: "Most evaluation systems measure what is obvious. Sales closed, code shipped, campaigns launched. Glue work doesn't show up in those metrics, so it goes unnoticed" (NASMM republication). Both of those lines could sit on the QuestWorks measurement page word for word.
Pro-social behavior beats pure performance incentives. The Muir chicken study is the cleanest evidence in the book. Selecting only the high producers destroyed the flock. Selecting whole flocks for productivity preserved the social fabric and outperformed. Levy applies the same logic to compensation, promotion, and recognition. We agree. Performance management and team development cannot be the same instrument.
Where QuestWorks defines team intelligence differently
The definition we use is one sentence. Team intelligence is what a team knows about itself, what its leader knows about it, and what it does with that knowledge automatically. QuestWorks builds all three. Unpacked into layers it looks like this. Intelligence FOR your team is self-knowledge surfaced through play. Each person sees how they actually show up. The team sees itself. Intelligence ABOUT your team is the patterns no survey can catch. How they handle pressure. Where friction lives before it costs you. Intelligence IN your team is muscle memory. Behavior change that becomes second nature without anyone being told to change.
The two frames sit next to each other. Levy's pillars (Reasoning, Attention, Resources) describe cognitive properties of a team, while the QuestWorks layers (FOR, ABOUT, IN) describe how intelligence flows through one. A team that scores well on the pillars is a team in which the FOR, ABOUT, and IN layers are working. Both views can be held at the same time. The reason we use the layered version is that it tells you where to put the work, which is the question a manager actually asks.
Here is the substance of the delta, laid out plainly:
- Levy's frame is leader-centered. The title says it: How Brilliant Leaders Unlock Collective Genius. The QuestWorks frame is distributed across team, leader, and behavior-as-default.
- Levy lists three cognitive pillars of the team. QuestWorks lists three flows of intelligence between team, leader, and habit.
- Levy studies elite teams that already have team intelligence and reverse engineers the habits. QuestWorks builds team intelligence in normal teams through engineered practice.
- Levy diagnoses the measurement problem. QuestWorks productizes the measurement tier. Pattern signal is the deliverable.
- Levy's evidence is habits-and-cases observational. QuestWorks runs a living simulation environment week over week.
- Levy's source pool skews elite (Nobel laureates, Olympic captains, Fortune 500 CEOs). QuestWorks is built for mid-market and distributed teams.
- Levy treats AI as augmenter and potential real-time team-EQ coach. QuestWorks treats AI as facilitation infrastructure.
- A book is a finished artifact; a platform produces a fresh artifact every week the team plays.
These are the next questions a builder asks once Levy's premises are on the table. None of them function as corrections of the book.
What the book diagnoses but does not solve
Three places where the book points at a real problem and stops short of an operational answer. None of this reads as a knock against the book; these are the questions a builder picks up after the book closes.
The measurement gap. The Battier and glue work quotes above are the cleanest articulation of the problem you will read this year. Standard measurement systems are blind to the behaviors that move teams. Levy's recommended substitutes are qualitative. Ask. Run peer-nominated awards. Highlight glue behaviors in meetings. Those are useful. They are also exactly what most companies have been doing for twenty years, and the measurement gap persists. The next step is a system that can see those behaviors at the team level and surface them as a pattern. That is the layer QuestWorks productizes, and it is one example of how the gap can be closed. Other tools will follow.
The remote and distributed team gap. Levy's read on remote work is candid and pessimistic. He calls it the airport problem. "When you go to the airport, even if you have the same captain and crew, we generally do not talk to the people around us. If you take a bunch of people who don't know each other and shove them into a building, they're basically at an airport waiting for their turn to go home" (Chad & Cheese). He has said he has not seen companies larger than fifty thousand achieve strong remote culture. The diagnosis is sharp. The book offers no engineered solution for distributed teams, which is where most knowledge work now lives. An engineered practice environment that pulls a distributed team into shared, high-stakes conditions on a recurring cadence is one path through the airport problem.
The engineered-practice gap. The book is observational. It studies elite teams and reverse engineers what they do. Valuable and necessary work. It also leaves the question most managers actually ask, which is "how do I get my team to do it." The lineage that picks up here is forty years of evidence behind simulation training in aviation and medicine. The mechanism is well established: pressurize teams, observe behavior, debrief, improve. Crew Resource Management in the cockpit and high fidelity simulation in the operating room are the canonical cases. QuestWorks applies the same mechanism to the work of working together, and it is one example among several of where the field is going.
What to pair the book with
If you are running a team and you want a serious operating stack for team intelligence, the recommendation is straightforward.
Read Levy for the conceptual framing, the case library, and the Glue Player vocabulary. The book will sharpen how you watch your own team. The Ideas in Action sections at the end of each chapter give you starting points that any manager can run on a Monday morning.
Add a measurement and practice layer. QuestWorks is one example of this layer. There will be others. The shape of the category is becoming clearer: short, structured, recurring sessions that put a team in pressurized conditions, surface real behavior, and produce pattern-level signal back to the leader. Whatever tool you pick, the criteria are the same. Does it actually pressurize the team or just talk about pressure? Does it produce signal the leader can act on without violating the privacy of individual coaching? Does the behavior change persist between sessions?
For the empirical backbone, go to the primary sources. Anita Woolley's 2010 c-factor work in Science is the foundational paper. Project Aristotle is well documented. Amy Edmondson's work on psychological safety, while not directly central in Levy's book, is the third leg of the stool and worth reading first hand.
Together that gives you the conceptual frame, the operational layer, and the academic ground. Each one does work the others cannot.
Honest credit
Jon Levy named team intelligence in mainstream business discourse. That is real work and it matters. The fifteen years he spent running the Influencers Dinner, convening Nobel laureates, Olympic captains, ISS commanders, military leaders, and Fortune 500 CEOs, gave him a source pool no other writer in the space has. The book lands because the cases are real and the synthesis is clear. Anyone working on team intelligence who pretends the book did not move the field forward is not paying attention.
QuestWorks is one of the platforms the field needs to make Levy's argument operational. We define the term differently because the work of building forces a different question, which is what the team does tomorrow morning and the morning after that. Both kinds of work belong in the same conversation. A book hands a leader the why and the what; an operational layer answers the recurring how that comes after.
Try it free
