How to scale social systems in software organizations

Charlotte de Jong Schouwenburg's presentation tackles a fundamental challenge of the modern tech industry: the tension between hyper-growth and human cohesion. Her central thesis reframes scalability from a purely technical concern to a sociotechnical imperative. When a team or organization expands quickly, its "human architecture"—the implicit norms, trust networks, and communication pathways—is stressed and often breaks down before the technical systems do. This analysis explores the deeper logic, context, and practical implications of her insights.

The Core Problem: Trust and Safety Depletion

The metaphor of "trust" and "safety" tanks that need refilling is powerful. It visualizes a dynamic resource, not a static state. In stable teams, these resources are built slowly through repeated, reliable interactions. Rapid expansion is the equivalent of drilling new holes in the tank; the existing reserves leak out faster than they can be replenished.

• The "Onboarding" of the Social System: It's insufficient to just onboard new hires into their tasks. The entire existing team's social fabric must also adapt. New members bring new communication styles, unspoken assumptions, and relationship patterns. The old system of understanding must evolve, which is a non-linear, time-consuming process often ignored in fast-scaling companies focused on immediate output.
• Human Scalability Defined: The speaker defines it as maintaining consistency and psychological safety across an ever-expanding web of interactions. This is the ultimate goal—not just moving faster, but preserving the ability to collaborate effectively and take risks without fear as complexity increases.

Strategy 1: Intentional Redundancy in Communication

The advice for "redundant" communication is a direct antidote to the fragmentation caused by growth. The goal is not just information dissemination, but contextual alignment.

• Why Redundancy is "Golden": In a small team, information travels organically. In a scaled one, it gets filtered, lost, or delayed. Repetition across multiple channels (meetings, docs, Slack, email), formats (visual, verbal, written), and times is necessary to overcome the "inattentional blindness" of busy people. It ensures that even those who are "disengaged" (perhaps overwhelmed) still receive the message.
• Accommodating Cognitive Diversity: Different people absorb information differently—some are visual learners, some prefer written documents, others need conversation. Redundancy creates multiple on-ramps to understanding, preventing knowledge silos where critical context exists only in one person's head or one specific document. This directly fights the "disconnected" state that leads to errors and rework.

Strategy 2: Building Bridges to Combat Silos

De Jong Schouwenburg rightly identifies that trust is built on familiarity, which requires contact. As organizations scale, they naturally form specialized teams (squads, tribes) that optimize for local efficiency but risk creating "us vs. them" mentalities.

• The Purpose of Cross-Team Rituals: Activities like multi-team workshops, virtual coffee chats, and shared demo sessions are not "nice-to-haves." They are social infrastructure. They create low-stakes environments where individuals from different domains build personal rapport before they need to collaborate on a high-stakes, stressful project. This pre-built relational capital makes conflict resolution and cooperation significantly easier during crises.
• Structural Mitigations: Implementing buddy systems across locations or teams and rotating facilitators are specific, actionable techniques. A buddy system guarantees a direct, maintained link between groups. Rotating facilitators decentralizes the role of "information hub" or "bridge," reducing the organization's dangerous dependency on a few overloaded individuals (the "human single points of failure").

The Leadership Imperative: Modeling, Not Just Managing

The most profound part of the talk centers on leadership behavior. In scaled systems, a leader's influence becomes magnified and symbolic.

• Leadership as a Performance: People don't follow memos; they follow examples. When a leader openly says "I was wrong," asks for help, or admits uncertainty, they are not showing weakness. They are performing psychological safety. This act gives permission for others to do the same, transforming it from a risky individual act into an