Presentation: The Human Scalability Problem: Why Your Teams Don't Scale Like Your Code

Charlotte de Jong Schouwenburg · presentation (conference talk transcript) · 2026-05-09 source ↗ Reader 🖥️

Coordination Cost Orchestration Tax / Human Review Bottleneck Psychological Safety Team Autonomy Trust

When organizations scale, technical systems scale but human cooperation breaks down due to communication overload, loss of shared context, and the non-replicability of trust — and the fix requires deliberate investment in communication architecture, engineered trust, distributed cohesion, and leadership that addresses relational dynamics rather than just content.

practical · presentation (conference talk with Q&A) — A practitioner talk by a business psychologist specializing in tech companies. Blends applied psychology theory (Dunbar's number, psychological safety, trust) with concrete interventions. Includes audience interaction and real company case studies (LeanIX, Spotify, Google). Primarily prescriptive — diagnoses the human scaling problem then offers a toolkit.

Structure

Part	Role
Opening: client pain points	Grounds the talk in lived experience — decisions took 10x longer, people stopped cooperating despite technical systems holding up
LeanIX case study (12 to 500 employees)	Provides a researched longitudinal example of scaling breakdown — role ambiguity, cross-function overlap, slower decisions
Three root causes: communication overload, loss of shared context, trust non-replication	Diagnoses the psychological mechanisms underlying scaling failure
Spotify squads and Google Project Aristotle examples	Illustrates that even companies famous for team design hit trust-replication failures; autonomy without trust fails
Monitoring dashboard: human latency, error rates, engagement, cultural drift	Provides observable indicators so leaders can detect scaling breakdown early
Solutions toolkit: communication architecture, engineering trust, distributing cohesion, leadership behaviors	Prescriptive interventions — the core practical payload of the talk
Q&A: team formation speed, layoff anxiety, transparency trade-offs	Surfaces edge cases and real-world complications; enriches the prescriptions with nuance

Key terms

behavioral scalability Coordination Cost
The ability of human cooperation patterns — communication, trust, coordination — to remain effective as team size and organizational complexity grow
human latency Orchestration Tax / Human Review Bottleneck
The time it takes to move from problem identification to solution to action; analogous to system latency but for human decision-making and coordination
relationship bank account Trust
A metaphor for accumulated relational capital in any interpersonal connection; positive deposits (personal connection, understanding) allow withdrawals (feedback, criticism) without destroying the relationship
trust (in this context) Trust
The belief that others will act with integrity and reliability even when you're struggling; enables open feedback and honest communication without fear of exclusion
psychological safety Psychological Safety
The shared belief that one can take interpersonal risks within the group — make mistakes, propose ideas, admit ignorance — without punishment; described as the 'funnel of trust' requiring trust as foundation
cultural drift
The divergence of shared identity, norms, and definitions (e.g., 'done', 'moving fast') across locations and subcultures as an organization scales, especially internationally
communication architecture Coordination Cost
The deliberate design of how information flows across teams — which channels, what frequency, what content — as opposed to ad hoc or emergent communication patterns

Propositions

explicitTechnical systems scale readily, but human cooperation does not scale automatically — it actively degrades without deliberate intervention.conf: high
explicitHumans can sustain approximately 150 social relationships (Dunbar's number), which imposes a hard cognitive limit on organizational scaling through informal coordination.conf: medium
explicitTrust cannot be replicated by copying organizational structure; even if you duplicate an autonomous team's structure perfectly, the new team must build trust from scratch.conf: high
explicitestablishedPsychological safety requires trust as a foundation but goes further — it is the belief that interpersonal risk-taking is safe within the group.conf: high
supports ←How the Best Leaders Shape Conversations · p5 — Near-identical claim structure: both state that psychological safety requires interpersonal trust as a foundation but is a distinct, further, group-level property, not reducible to trust itself.
supports ←Maya Knight's Post · p1 — Independently restates the same Edmondson-derived definition (psychological safety = the belief interpersonal risk-taking is safe), corroborating an already-corroborated proposition from a different source (talk) with a different register (LinkedIn post).
explicitcorroboratedTeams given autonomy cannot harness it productively until trust and psychological safety are established.conf: high
supports ←The New Rules for Becoming an Enterprise Leader · p12 — Watkins's claim that psychological safety and trust are the essential foundation of an adaptive organization matches this piece's claim that autonomy is unusable without trust and psychological safety first.
extends ←Your AI strategy has a trust problem, not a tooling problem · p8 — Adds a precondition for usable autonomy beyond trust and psychological safety: employees may have been trained out of exercising agency and cannot simply absorb it when granted.
explicitcorroboratedMost organizational firefighting addresses symptoms (missed deadlines, non-collaboration) rather than root causes (trust deficit, lost shared context, communication overload).conf: high
supports ←Pascal BORNET's Post · p3 — Both name the same failure mode — organizations firefighting symptoms (missed deadlines, workarounds) instead of addressing root structural causes.
explicitRepetition of core messages across multiple channels and times is essential because information overload means single-transmission communication reliably fails at scale.conf: high
explicitNew teams must invest in relationship-building before task work; going directly into project deadlines creates negative relational bank accounts that produce conflict and poor collaboration.conf: high
explicitLeaders must model the vulnerability and transparency they want from their teams — walking the talk is non-negotiable for building trust.conf: high
explicitRituals and predictability calm the human brain and create the conditions for trust; they function as social infrastructure that persists even when team composition changes.conf: medium
implicitAddressing fear and emotional concerns directly (e.g., layoff anxiety) by providing space for conversation — not by solving the content problem — restores enough regulation for people to function.conf: medium
explicitThe leader's primary job at scale shifts from content/task management to facilitating the human system — ensuring teams can do their best work rather than directing the work itself.conf: high

Arguments

Organizations must deliberately invest in human scalability, not just technical scalability

You can't replicate trust by replicating structure

Relationship investment must precede task work for new teams

Leaders should address relational dynamics rather than just content/symptoms

Narratives

→ Provides the primary case study and makes the abstract problem concrete and research-backed
→ Demonstrates that even best-practice structural solutions fail without relational investment — the 'you can copy-paste autonomy but not trust' lesson
→ Shows that trust is fragile and tied to specific social configurations, not transferable
→ Illustrates cultural drift as a concrete, vivid example of lost shared context
→ Real-world validation from the audience; shows the trust-then-safety progression in practice

Questions addressed

⭕ Why do organizations slow down and become more dysfunctional as they add more people, even when their technical systems scale fine?
⭕ Can you replicate a high-performing team by copying its structure?
⭕ What concrete interventions can leaders use to maintain team effectiveness during scaling?
⭕ How do you know when human scaling is failing?
⭕ How should new teams be set up to build trust quickly?

Gaps

practicalNo quantitative framework for when to invest in human scalability interventions. The talk says companies often come to Bravely at 100-150 people when employee surveys flag problems, but offers no guidance on investment timing, budget, or ROI metrics.
theoreticalThe relationship between AI/automation and human scalability is acknowledged ('AI is doing a lot') but immediately dismissed ('this will still always be true'). No exploration of how AI tools might change the communication overload or shared context problems — or whether they introduce new trust challenges.
closed byYour AI strategy has a trust problem, not a tooling problem — Explores what the talk dismissed: AI agents distribute context and shrink the middle-management translation problem, shifting the binding constraint of scaling from communication overload to trust and permission structures.
evidentialThe talk relies heavily on the Spotify squad model and Google Project Aristotle as examples, but these are well-known cases that may not generalize. No counter-examples are discussed — organizations that scaled human cooperation successfully without these specific interventions.
theoreticalDunbar's number is presented as a hard cognitive limit, but the speaker herself notes it was 'measured on neurotypical people' and is 'a guess.' The implications of neurodiversity for organizational scaling are raised but not explored.
practicalThe interventions (communication architecture, trust engineering, distributed cohesion) are presented as a menu of techniques without a theory of sequencing or prioritization. Which matters most at 50 people vs. 200 vs. 1000? The talk doesn't say.

Closes gaps elsewhere

7) Stine Haugseth: Insourcing, retning og strategi på en ølbrikke · g3 — Addresses how an organization acquires the preconditions mission command assumes: trust must be deliberately engineered via relationship-building before task work, repeated core messages, leader-modeled vulnerability, and rituals as persistent social infrastructure.
9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team · g8 — Supplies concrete mechanisms for building the safety Brede Moe treats as foundational but unoperationalized: relationship-first team formation, leaders modeling vulnerability, rituals that persist across changing team composition, and direct handling of fear.