How to Handle Trusts and Psychological Safety When Scaling Organizations

Host A: Welcome back to DevTools Radio, I'm here with my co-host, and today we're diving into something that every engineering leader hits a wall on sooner or later — how do you actually maintain trust and psychological safety as your organization scales?

Host B: And this is such a real pain point. Like, things feel great when you've got a tight team of ten or twelve people, and then suddenly you're at fifty, a hundred, five hundred — and something just... breaks down.

Host A: Exactly, and that's almost word for word what Charlotte de Jong Schouwenburg said at Dev Summit Munich. She put it really bluntly — you can communicate well with twelve people, you know each other. That doesn't just happen with five hundred. Humans have cognitive limits; you can't scale people like you scale systems.

Host B: Which is such an important reframe, right? Engineers especially are used to thinking about scalability in terms of infrastructure. But the human layer doesn't follow the same rules at all.

Host A: And one of the biggest misconceptions she called out is this idea that trust is copy-pasteable. Just because you've built a high-trust team doesn't mean the next team you spin up inherits any of that. Each team has to grow its own trust from scratch.

Host B: That's kind of humbling when you think about it. So what's the distinction she draws between trust and psychological safety? Because I feel like people use those terms almost interchangeably.

Host A: Great question, and she's really precise about this. Trust is personal and directional — it's your belief about a specific person. Psychological safety is collective and environmental — it's the group's shared belief that it's okay to speak up, ask questions, admit mistakes, without fear of humiliation.

Host B: So trust supports individuals, and psychological safety supports the whole team's ability to learn and innovate. One is about relationships, the other is almost like... the climate of the room.

Host A: Perfectly put. And here's the practical upshot — you can't scale personal trust quickly, but you actually can scale psychological safety. You do it through explicit norms, things like "we critique ideas, not people" or "mistakes are data, not failures."

Host B: I love that — "mistakes are data." That's the kind of phrase that sounds simple but completely changes how a post-mortem feels. So how do organizations actually build these structures deliberately rather than just hoping it happens?

Host A: She calls it architectural — building trust and psychological safety at scale is intentional design, not a happy accident. Practically that means things like retrospectives, virtual coffees, global all-hands with shared storytelling, rotating meeting facilitators, even cross-site pair programming.

Host B: And I think the rotating facilitators piece is underrated. It distributes ownership of the culture rather than letting it live only at the leadership level, which is where a lot of companies go wrong.

Host A: She also emphasized monitoring what she calls human metrics — how long decisions take, how often people speak openly in retros, how much cultural drift is creeping in between teams or regions. That stuff is measurable if you're paying attention.

Host B: Which means leaders actually have to be paying attention to the social system, not just the delivery metrics. Especially when stress hits — that's when those cracks either hold or they don't.

Host A: That's the real test. Alright, if you're leading a scaling team, the takeaway is pretty clear — don't assume trust travels with your org chart. Design for it, set the norms early, and reward transparency over heroics.

Host B: Such a good one today. Thanks for tuning in to DevTools Radio — we'll be back next time with more conversations at the intersection of tech and the humans building it. See you then.