Trust and Psychological Safety: The Hidden Architecture of Scaling Organizations

As organizations scale, communication overload, loss of shared context, and trust gaps emerge, Charlotte de Jong Schouwenburg mentioned at Dev Summit Munich. Trust must be built team by team; it can't be replicated. Trust is interpersonal, while psychological safety is among people and fuels learning. Leaders must deliberately design structures, rituals, and metrics that reward transparency and cohesion at scale.

The Scaling Paradox

With scaling organizations come a lot of challenges, De Jong Schouwenburg said. We get communication overload, there's a loss of shared context, and trust is a problem, she explained: You communicate well with 12 people. You know each other. It doesn't happen with 500. Humans have cognitive limits; you can't really scale humans like you scale systems.

This fundamental truth about human cognition creates what might be called the scaling paradox: the very mechanisms that make small teams effective—deep personal relationships, shared context, implicit trust—become liabilities as organizations grow. The Dunbar number suggests we can maintain stable relationships with roughly 150 people, but modern organizations often exceed this by orders of magnitude.

Trust doesn't replicate automatically. Just because you have high trust in your existing teams, when you build another team just like it, it won't automatically have high trust and high psychological safety, De Jong Schouwenburg said: As teams scale, you can't copy-paste trust from one group to another. Each new team has to rebuild it; it has to grow.

Trust vs. Psychological Safety: A Critical Distinction

Although trust and psychological safety are closely linked, they are not the same; and understanding the distinction helps teams scale more effectively, De Jong Schouwenburg explained: Trust is between people; psychological safety is among people. Trust is earned; psychological safety is enabled. Trust supports individuals; psychological safety supports innovation, learning, and collaboration across groups.

This distinction matters because it changes how we approach organizational design. Trust is built through repeated interactions—shared experiences, reliability, consistency. In small teams that work together longer, this develops more naturally because people have time to form individual relationships. Face-to-face time and focusing on strengthening the relationships before talking about work helps to increase this.

Psychological safety, by contrast, is about the collective climate. It's the shared belief that the team is safe for interpersonal risk-taking. It's about the social norms of the system, not any single relationship. This makes it more amenable to architectural approaches—you can design for psychological safety even when trust hasn't fully developed.

Architectural Approaches to Scaling Trust

Building trust and psychological safety at scale isn't accidental, but it's architectural. You can architect environments that create psychological safety from day one, De Jong Schouwenburg said. It requires consistent behaviors, deliberate systems, and environments where people feel both connected and coherent across teams.

Companies can benefit from having a strong sense of connection and a shared purpose across teams. The cohesion that we normally find in one team, we want to get across teams, distribute it, De Jong Schouwenburg explained.

Practical approaches include:

• Retrospectives that focus on team dynamics and cross-team dependencies
• Virtual coffees when physical gatherings are impractical
• Global all-hands with shared storytelling to build context
• Rotating meeting facilitators across regions to distribute voice and perspective
• Cross-site pair programming or demos to build relationships across boundaries

Rewarding the Right Behaviors

We want people to have trust and psychological safety, and need them to feel free and comfortable and be rewarded for being honest and transparent, De Jong Schouwenburg said. She suggested fostering a system that rewards transparency and reliability instead of heroics and secrecy.

This requires examining what behaviors your organization actually rewards. If people believe they need to hide uncertainty, overwork silently, or rescue projects through last-minute heroics, trust erodes. Instead, reinforce:

• Asking early questions
• Making asking for help and providing help normal rather than a nuisance
• Sharing unknowns
• Predictable follow-through
• Discussing risks before they become fires

A system that rewards honesty creates both trust and collective intelligence. You can build fast psychological safety through norms, not familiarity. You can't scale personal trust quickly, but you can scale psychological safety by setting clear expectations: "It's okay to ask for help." "We critique ideas, not people." "Mistakes are data." "Everyone contributes, especially the quiet voices."

You can also use meeting strategies to encourage equal sharing of speaking time (for example, everyone gets one minute speaking time to express their ideas or opinions while the others listen in silence). These norms create immediate safety even before relationships fully form.

Leadership's Critical Role

Leadership really is very important in this, De Jong Schouwenburg said. You need to make sure that the social system is reliable when stress hits.

She suggested monitoring human metrics, like how long decisions take, how often teams speak openly in retrospectives, and how much cultural drift there is between sites or functions, she concluded.

Leaders must model the behaviors they want to see. This means being vulnerable about their own uncertainties, admitting mistakes publicly, and creating space for others to do the same. It also means being consistent—psychological safety requires predictability in leadership behavior, especially during times of stress or change.

The Architecture of Human Systems

The insights from Dev Summit Munich point to a fundamental truth about scaling organizations: we need to think about them as human systems that require architectural design, not just as collections of individuals or teams.

Just as we design technical systems with scalability, reliability, and performance in mind, we need to design our organizational systems with trust, psychological safety, and human connection as first-class concerns. This means being deliberate about the structures, rituals, and metrics we put in place, and being willing to invest in the human infrastructure that makes scaling possible.

The alternative—hoping that trust and psychological safety will emerge organically as organizations grow—is a recipe for dysfunction at scale. By treating these elements as architectural concerns that require intentional design, we can build organizations that remain human and humane even as they grow beyond the limits of our cognitive capacity to maintain personal relationships with everyone involved.