Designing for emergence between people, not just within them.
But here’s what surprised me in my research: some foundational principles stay remarkably consistent.
Cognitive load theory still applies. You’re managing collective cognitive load across the team system. Teams can only hold so much in active coordination at once, just as individuals have working memory limits. The difference is now you’re watching for bottlenecks in the team’s shared attention, not just individual overwhelm.
Worked examples and deliberate practice still matter. Teams need to see what good team performance looks like. The “worked example” might be observing how another team navigates a handoff or integrates diverse perspectives. Then they need to practice the specifically challenging coordination moments, not just run through the whole workflow.
Transfer of learning remains hard. Teams struggle to apply what they learned in controlled exercises to messy reality, just as individuals struggle to transfer classroom learning to real contexts. The design principles for transfer – authentic contexts, varied practice, explicit reflection – apply whether you’re designing for one mind or multiple minds working together.
Here’s the key insight:
You can’t aggregate individual learning and get team capability. You must design for relationships, communication patterns, shared representations, and coordination mechanisms that allow individual knowledge to become collective capability.
That’s a different design problem, even as it rests on many of the same principles.