How do I apply the idea that teams think collectively?

The most direct way to practice is through a focused exercise: In your next team meeting, conduct a 'collective cognition audit.' At the end of the meeting, ask the team three questions and record the answers: (1) 'What did we decide today, and who made each decision?' — if the team cannot clearly identify decisions and their makers, the collective thinking process is opaque. (2) 'Did anyone hold a concern they did not voice? If so, what prevented them?' — anonymous written responses work better than verbal ones. (3) 'What assumption did we all seem to share that was never stated explicitly?' — this surfaces the invisible shared mental models that drive group behavior. Document the answers and share them with the team. The document itself is the beginning of designed collective cognition.

Common pitfall: Assuming that hiring smart individuals automatically produces smart teams. This is the composition fallacy — the belief that team intelligence is the sum of individual intelligences. Research consistently shows that team performance correlates weakly with average individual IQ and strongly with interaction patterns, communication norms, and the distribution of conversational turn-taking. A team of brilliant individuals with poor collective cognitive processes will be outperformed by a team of good individuals with well-designed collective thinking. The second failure is the opposite: treating 'teamwork' as a soft skill or personality trait rather than as a cognitive architecture that can be engineered. Teamwork is not being nice to each other. It is designing how the team thinks together.

This practice connects to Phase 81 (Team Cognition) — building it as a repeatable habit compounds over time.