Culture Starts With Permission, Not Policies
The week the team went silent
Giulia Scalaberni asked her new onboarding group a simple question: "Any questions?"
Nothing. Silence for an entire week.
No clarifications. No pushback. Nobody said the process was unclear or the tooling needed work. Just quiet compliance. In a remote team spread across Europe and India, that silence was an answer of its own, and it told her something was wrong.
The team wasn't too confused to ask. They were too uncomfortable.
Most leaders miss this. They assume silence means understanding, compliance means agreement, and if something's broken, someone will say so. What Giulia found (and what her low-effort fix proved) is that an open door doesn't give anyone permission to walk through it. That gap gets wider on distributed teams, where trust across cultures takes deliberate work.
Why "any questions?" doesn't work
An open-door policy sounds good. It reads well in a values statement, and it asks nothing of the leader except availability.
Availability isn't permission. In cultures where hierarchy, formality, or indirectness run strong, asking "any questions?" in a full room gets you silence.
Giulia's fix was small and deliberate: a three-question exercise with zero work talk allowed. The questions were personal and bounded. None of them touched job performance, the platform, or onboarding logistics. They gave people a way to speak as humans first.
That's when the conversation opened.
She didn't add office hours or invite people to ping her on Slack. She created a specific, low-stakes setting where speaking up felt safe, and she answered first.
Permission is built into the structure
A manager who asks "any questions?" is inviting people to clear a barrier on their own. A leader who builds permission into the system removes the barrier.
That means designing moments, questions, and spaces where staying silent costs more than speaking. Tone and approachability help, but they don't do the job alone.
Giulia's exercise worked because the context was bounded (three questions, not a whole meeting), work hierarchy was off the table, she modeled the sharing herself, and everyone answered. Silence wasn't an option.
The same principle applies across the rest of leadership. If you want your team to bring problems to you early, "my door is always open" won't get you there. You need a regular cadence, like one-on-ones that actually work, where not raising the problem is the exception. If you want people to challenge bad decisions, ask them by name what they disagree with. Leaders who practice radical candor make that kind of direct question routine.
Culture changes when leaders change the structure that makes silence the safe choice. Being nicer won't do it.
What happens when permission becomes real
Once Giulia's team learned that questions were welcome and asking for clarity was expected, the dynamic shifted. People raised problems earlier. They flagged unclear processes. They pushed back on decisions that didn't make sense.
They engaged more because she had made engaging easier than staying quiet.
This matters most when the stakes are high. On teams where mistakes are expensive, hierarchies tend to be steeper and formality runs high. Speaking up feels risky because mistakes have real consequences. On those teams, silence usually means people are managing their own risk. It rarely means they're happy. Organizations that build just culture into safety reporting apply the same thinking.
The answer isn't extreme informality. It's precision about when and how people speak, with permission designed into the work instead of left to the leader's personality.
If your team has learned to stay quiet, whether from organizational structure, industry norms, or past experience, asking them to suddenly voice concerns won't work. Build the structure that makes speaking up easier. That might be a standing question in one-on-ones, a ritual where disagreement is required, anonymous feedback channels for the concerns people won't say in a room, or Giulia's three-question format, borrowed and adapted.
The mechanism matters less than the principle: permission that changes behavior is built into how the team works.
Teams that speak up are designed that way. Our virtual workshops are one way to start, and you can see how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.