Culture Starts With Permission, Not Policies
The Week Your Team Went Silent
Giulia Scalaberni asked her new onboarding group a straightforward question: "Any questions?"
Nothing. Complete silence for an entire week.
No clarifications. No pushback. No one saying the process was unclear or the tooling needed adjustment. Just acceptance and quiet compliance. In a remote team spread across Europe and India, that silence was its own kind of answer—and it was telling her something was wrong.
The team wasn't confused enough to ask. They were uncomfortable enough not to.
That's the gap most leaders don't see. We assume silence means understanding. We assume compliance means agreement. We assume if something's genuinely broken, someone will speak up. But what Giulia discovered—and what her low-effort fix revealed—is that permission and psychological safety are not the same as an open door.
Why "Any Questions?" Doesn't Work
An open-door policy sounds good. It tests well in company values statements. It requires nothing from the leader except availability.
But availability isn't permission. And in cultures where hierarchy, formality, or directness norms run strong, asking "any questions?" in a room full of people is asking for silence.
Giulia's solution was small and deliberate: a three-question workshop, zero work talk allowed. The questions were personal and bounded. They had nothing to do with job performance or the platform or onboarding logistics. They were just three prompts designed to let people speak as humans first.
That's when the conversation opened.
The silence broke not because she held more office hours or invited people to drop by Slack. It broke because she created a specific, low-stakes context where speaking up felt safe. She didn't remove the barrier—she built a door next to it and walked through first.
Permission Is Structural, Not Rhetorical
The difference between a manager who asks "any questions?" and a leader who builds permission into the system is the difference between inviting people to solve a problem and removing the problem itself.
Real permission is structural. It's not about tone. It's not about being approachable. It's about designing moments, questions, and spaces where staying silent actually costs more than speaking.
Giulia's three-question exercise worked because it:
- Created a bounded context (not the whole meeting, just three questions)
- Removed work hierarchy (nothing about job performance or status)
- Went first (she modeled what vulnerable sharing looked like)
- Required participation (silence wasn't an option; everyone answered)
That's not an open door. That's a redesigned space.
The same principle applies everywhere else in leadership. If you want your team to bring problems to you early, you can't just say "my door is always open." You have to create a regular cadence where not bringing the problem is the exception. If you want people to challenge bad decisions, you can't wait for them to volunteer. You have to ask them specifically, by name, what they disagree with.
Culture doesn't change because leaders become nicer. It changes because leaders change the structure that makes silence rewarding.
What Happens When Permission Becomes Real
Once Giulia's team learned that questions were actually welcome—that asking for clarity was expected, not a sign of weakness—the whole dynamic shifted. People started surfacing problems earlier. They flagged unclear processes. They pushed back on decisions that didn't make sense.
The team didn't become more talkative because Giulia became more approachable. They became more engaged because she'd made it structurally easier to engage than to stay quiet.
This matters especially in technical teams and high-stakes environments. In defense, aerospace, nuclear, and manufacturing, hierarchies are often steeper. Formality runs high. The cost of speaking up feels real because the consequences of mistakes feel real. Silence doesn't signal happiness—it signals risk management.
The antidote isn't a culture of extreme informality. It's precision about when and how people speak. It's designing permission into the work itself, not hoping it leaks out of your personality.
If you're leading a team that's been trained to stay quiet—whether by organizational structure, industry norms, or past experience—asking them to suddenly voice concerns won't work. You have to build the structure that makes voicing them easier than not. That might be a standing question in one-on-ones. It might be a specific ritual where disagreement is required. It might be Giulia's three-question format, borrowed and adapted.
The mechanism matters less than the principle: permission that changes behavior is always structural, never just rhetorical.
Building teams that actually speak up requires structural design, not just good intentions. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, emotional intelligence, and organizational performance. Subscribe here.