Why Remote Teams Fail at 15 People (Dunbar’s Law)

You’ve probably experienced it: the moment a team grows from eight people to fifteen, communication suddenly breaks down. Meetings become chaos. Decisions take longer. Trust erodes. You can’t quite put your finger on why a once-cohesive group feels fragmented, but something fundamental has shifted. The culprit might not be management style or corporate culture. It might be something more fundamental: you’ve crossed an invisible threshold rooted in human social capacity.

Practical Strategies: Working Within the Dunbar Constraint

Understanding Dunbar’s Number is useful primarily if you can act on it. Here are evidence-based strategies I’ve observed in high-performing remote teams:

Explicitly Limit Core Collaboration Groups

If you’re building a product or managing a project, keep the tightly-collaborated group to 5–8 people. This is your working team. Beyond that, create clear communication channels rather than trying to maintain the same depth of collaboration. This is uncomfortable for leaders who want everyone involved in everything, but it’s how trust and speed actually work.

Use Dunbar’s Nested Circles as Your Org Structure

Design org structures around the nested circles, not around arbitrary functional departments. A team of 6–8, a department of 15–20, a division of 40–50. At each level, change the communication cadence and formality. This alignment to natural social cognitive capacities reduces the friction of scale.

Invest in Async-First Communication for Anything Beyond the Core Team

The research on remote work is clear: synchronous meetings don’t scale. They feel inclusive but are cognitively expensive. Instead, use written updates, recorded video updates, and documentation as your primary communication method for anything involving more than 10–12 people (Cumming & Worley, 2005). This costs more upfront but saves enormous time and actually distributes information more equitably.

Protect the Intimate Circle: 1-on-1s and Core Team Cohesion

As remote work scales, the temptation is to scale meetings, not to scale the structure. Instead: protect your core team’s meeting time. Have fewer, deeper 1-on-1s with people on your core team. Have a genuinely functional team meeting, not a broadcast. Keep these as intimate spaces where trust and understanding actually build. This isn’t a nice-to-have; it’s what enables everything else to scale.

Create Transition Rituals When Teams Grow

When a team crosses the 8–10 person threshold, the collaboration dynamic fundamentally changes. Acknowledge this explicitly. Talk about it. Change the meeting structure, reduce the expectation of total visibility, and establish new norms. Teams that pretend they’re still operating at the 5-person level when they’re now 12 spend enormous energy fighting the cognitive constraint rather than working within it.

Measuring Your Team Against the Model

Here’s a diagnostic: If you’re leading or part of a remote team, ask yourself these questions:

• How many people can you have a meaningful 1-on-1 with per week without feeling rushed?
• In your main team meeting, does everyone speak, or do the same 3–4 people dominate?
• Do decisions get made quickly, or do they require multiple rounds of async discussion?
• Do people feel they understand what others are working on, or is there consistent surprise about priorities?
• How much of your communication is about clarifying what people are working on versus actually collaborating on the work?

If your team is 10 people and you’re seeing slow decisions and unclear information flow, it’s probably a sign you’ve hit the Dunbar constraint before the “official” size limit. If your team is 6 and communication still feels hard, the constraint isn’t size—it’s clarity.

Conclusion: Size as a Design Choice, Not a Constraint

The relationship between Dunbar Number and remote work teams isn’t a limitation to resent. It’s a design parameter to use. The teams that function best remotely aren’t the ones that pretend size doesn’t matter or that try to overcome cognitive limits with more meetings. They’re the ones that structure around natural social units, align communication style to group size, and trust that smaller, tightly-coordinated teams can accomplish more than larger, loosely-coordinated ones. [4]

If you lead a team, you have a choice: You can grow the team until it hits friction and then add process to manage the friction. Or you can design the structure around natural cognitive limits from the start, nesting teams within larger organizations in ways that respect how humans actually work together.

The evidence suggests the latter approach gets better results: faster decisions, higher trust, less meeting load, and better information distribution. Not because small teams are inherently better, but because they’re aligned with how human collaboration actually works.

Last updated: 2026-03-24

Related Reading

• Static Stretching Before Exercise Is Wrong: 2026 Research Explains Why
• How to Teach Problem-Solving Skills [2026]
• How Astronauts Sleep in Space: The Science of Sleeping