Table of Contents
Collective Intelligence in Teams: How Intelligent Is Your Team?
A team can be made up of highly capable people and still make poor decisions on a regular basis. That is less contradictory than it may sound. Collective intelligence in teams does not emerge simply by adding together individual abilities. What matters is what happens between people: Which information enters the discussion? Which differences are noticed in the first place? Which assumptions are made explicit? Which contradictions are explored? And which insights ultimately change the way the team acts?
This matters particularly in innovation. New ideas rarely emerge from complete agreement. They often arise when different perceptions meet. Whether that encounter leads to insight, conflict or simply a loss of information depends on the team’s ability to process those differences, and on the organisational environment in which it operates.
Collective intelligence in teams is a capability in its own right
Researchers have long explored whether groups display a form of collective intelligence that cannot be fully explained by the abilities of their individual members.
A widely cited study by Anita Woolley and colleagues found evidence of a general collective intelligence factor: groups that performed well on one type of task also tended to perform well on others. This could not simply be explained by either the average or the highest level of individual intelligence within the group. Factors associated with group performance included social sensitivity and a more even distribution of participation in conversation.
A later analysis drawing on 22 studies and more than 1,300 groups provided further support for the existence of such a general factor of collective intelligence. For organisations, one conclusion is particularly relevant: teams develop capabilities at the level of the group itself. You can therefore hire highly competent people and still create structures in which part of their knowledge and perception is systematically lost.
How much of their existing capability can the team actually use collectively?
Different ways of thinking in teams initially expand the information space
Imagine a product meeting. Engineering sees technical dependencies. Sales knows about a specific expectation from an important customer. Product management is thinking about scalability. Someone from customer support recognises a recurring problem that users already experience with the current product. A requirements engineer notices that everyone is discussing the same feature while apparently holding different assumptions about the problem that feature is supposed to solve. It would be premature to conclude that more perspectives automatically lead to a better decision. At this stage, there is simply a broader range of information available.
That distinction is central to research on different ways of thinking in teams. People perceive different aspects of a problem because of their role, experience, expertise and individual ways of processing information. Those differences can expand the potential space for insight. They also increase the need for translation. Information may be weighted differently. The same terms may carry different meanings. A technical risk may be central from an engineering perspective and appear secondary from a sales perspective. A strategic objective may seem unambiguous at board level while allowing several conflicting interpretations in day-to-day operations. Difference therefore provides raw material. Whether it becomes collective intelligence is decided in the next step.
Team diversity and innovation: the crucial mechanism lies in between
The relationship between team diversity and innovation is not linear. Difference can make more knowledge and more perspectives available. It can also increase social categorisation, coordination costs and misunderstanding.
The Categorization-Elaboration Model developed by van Knippenberg, De Dreu and Homan captures precisely this tension. Its central proposition is that diversity can support team performance when task-relevant information and perspectives are actually exchanged, discussed and integrated. This process is known in the research literature as information elaboration. That is more than participation.
If everyone in a workshop writes three ideas on a Post-it note, information has been collected. If everyone in a meeting is given the opportunity to speak, participation has been organised. But the team still does not necessarily know:
- how the observations differ,
- which assumptions lie behind them,
- whether apparently conflicting statements genuinely contradict one another,
- which information matters most to the decision,
- or what conclusion follows when the different perspectives are considered together.
Research on diversity beliefs similarly suggests that heterogeneous groups can make better use of differing information when diversity is regarded as a relevant resource and when more information elaboration takes place.
The mechanism is therefore not simply: Diversity → innovation.
It is closer to: Relevant differences in information → exchange and processing → changed shared understanding → a stronger basis for decisions or innovation.
Even that process offers no guarantee. Information may arrive too late, carry less weight because of status differences, or disappear again during implementation.
Information elaboration is the actual thinking work of a team
The difficult part begins after someone has spoken. A team cannot simply place different pieces of information alongside one another and expect a more complete picture to emerge automatically. Different observations have to be related to one another.
A common sentence in projects is: “The requirement is clear.” Five people may agree with that statement and still have understood five different things. A shared vocabulary is not the same as a shared mental model.
In complex projects, a substantial part of professional collaboration therefore consists of making implicit assumptions visible. What does “done” mean? What do we mean by “quality”? Which problem are we actually trying to solve? What are we treating as given? Under what conditions would our current assessment no longer hold?
This also shows why Requirements Engineering should be far more than documentation. Done well, Requirements Engineering structures collective understanding. It makes different representations of the problem, context, target state, constraints and success criteria comparable. This reveals an often underestimated capability: Translation is not a linguistic side task. It is part of collective information processing.
Psychological safety in teams solves only the first part of the problem
Before different perspectives can be processed, people must first be able to contribute relevant observations. This is where research on psychological safety in teams becomes important. Amy Edmondson describes psychological safety as a shared belief that interpersonal risk-taking within a team is acceptable. That includes asking questions, expressing doubt, acknowledging mistakes and challenging a widely held view.
This matters for learning. If someone expects to be socially penalised for raising an uncomfortable observation, the team has an obvious information problem. Psychological safety, however, is often expected to achieve something it cannot deliver on its own.
A person may be allowed to speak and still not be understood. They may be understood and still have no influence on a decision. And they may influence a decision while the insight gained is later lost in organisational processes or hierarchies.
Psychological safety therefore increases the likelihood that relevant information becomes visible in the first place. Processing that information requires additional organisational structures. These may include clear decision-making processes, explicit definitions, appropriate facilitation and ways of documenting assumptions so that they can be revisited later.
Team innovation needs difference, but not every form of conflict
When different perceptions meet, friction often follows. That does not make friction inherently valuable. Nor does it automatically make it a problem. Interpersonal conflict can obstruct collaboration without generating any new insight. Two departments may argue about responsibilities for months while holding exactly the same assumptions about the underlying issue.
Conversely, substantive disagreement can be highly productive. Research on minority dissent, for example, suggests that dissenting minority positions can be associated with team innovation, particularly when people also have meaningful participation in decision-making.
The relevant factor is therefore not disagreement for its own sake. What matters is whether the team can process it. For team innovation, this means that an intelligent system does not try to eliminate every relevant difference as quickly as possible. It first investigates what lies behind it.
Consider another hypothetical project. The project lead says: “We can go live in October.” Engineering responds: “There are still major technical dependencies unresolved.” Both statements may be correct if the two sides are working with different definitions of “go live”.
A weak discussion tries to decide quickly who is right. A stronger discussion asks: What different models of the situation underpin these two statements? That changes the role of friction. Rather than being treated purely as a disturbance, it becomes a potential signal for insight.
Friction can reveal where translation is missing
Organisations need standards. Without shared terminology, routines and expectations, coordinated work would be extremely difficult.But standards have a side effect: they also shape which forms of information an organisation can process easily. How must someone formulate a problem before it is regarded as relevant? How much must an argument be condensed? What counts as “objective”? Which data format is accepted at a particular decision-making level? How much context is someone allowed to require? When is a question seen as useful clarification, and when is it dismissed as unnecessary complication?
Many of these rules remain implicit. People therefore learn to make their own perception compatible with the surrounding system. To some extent, that is unavoidable. It becomes problematic when adaptation changes the information itself. What happens to relevant information when it arrives in a form that does not match the expected way of thinking or communicating? Is it translated? Or is it filtered out?
At this point, the relationship between friction and collective intelligence can be summarised in one sentence: Adaptation may reduce visible friction. Translation increases the chance of making existing intelligence usable.
How can you recognise a collectively intelligent team?
Collective intelligence cannot be read from the mood in a meeting. Harmony is not enough. Nor are equal speaking time or the number of ideas generated. More useful indicators concern the actual processing of information.
1. Do relevant deviations become visible?
What happens when one person notices something that contradicts the prevailing assessment? Do they need to present a complete solution before anyone listens, or is the observation itself allowed to be examined first?
2. Can different mental models be compared?
How do you find out whether two people really mean the same thing when they use words such as “customer”, “done”, “risk” or “priority”? The more complex the subject, the more dangerous apparent linguistic agreement can become.
3. Are contradictions investigated or socially resolved?
When different assessments emerge, does the team examine the underlying data and assumptions? Or does it mainly look for the position everyone can agree on? Consensus is one possible way of reaching a decision. It is no guarantee that the team has thought well.
4. Can new insight change an existing decision?
When did a conflicting observation last lead your team to revise a decision that had already been made? A team can discuss issues openly and still learn very little if its chosen course of action is effectively no longer open to revision.
5. Which information is regularly lost in translation?
Which roles, people or departments have to simplify their perspective particularly heavily before it becomes compatible with the rest of the organisation? That is worth examining. Not every instance of friction points to a systemic problem. Recurring friction at the same interfaces, however, is rarely meaningless.
Innovation is also a process of collective sense-making
The OECD does not define innovation merely as an idea. It explicitly distinguishes an implemented innovation from the many activities through which innovation emerges, including research, design, development, knowledge flows and innovation management. This is a useful perspective because it moves innovation away from the romantic image of the sudden flash of inspiration.
Before an organisation can implement something new, it often has to see something differently first. Someone notices a deviation. Another person interprets what it might mean. Additional information changes the framing of the problem. An existing assumption becomes questionable. An alternative becomes conceivable. An experiment generates new evidence. Eventually, that process may result in a decision, a product, a changed process or the well-founded decision not to pursue an idea further. Innovation is therefore also a process of organisational sense-making and collective learning.
The intelligence of a team is not demonstrated by how clever its cleverest members are. It is demonstrated by how effectively the team can turn distributed perceptions, knowledge and different ways of thinking into a more robust shared understanding. Difference is neither a guarantee of success nor a defect. It is information. Whether it becomes friction, insight or innovation depends on what the system is able to do with it.
Monika Wolff works at the intersection of neurodiversity and innovation management. As founder of Flow by Wolff, she designs systems that translate diverse cognitive styles into innovation capacity. Her approach combines psychological safety, structural clarity, and measurable performance impact within innovation processes.