A director we coached, Mark, ran a weekly planning meeting he genuinely loved. People nodded, agreed, said “sounds good,” and left. Then his lead engineer quit, and the exit conversation revealed that the team had known the roadmap was unrealistic for two months. Nobody had said a word in the room. They’d said plenty in DMs.
That gap, between what people say in the meeting and what they actually think, is the open communication problem. Most advice tells you to be transparent and keep your door open. Mark’s door was always open. His team still didn’t tell him the one thing that mattered.
In our coaching at Risely, the pattern we see most often has nothing to do with a team that won’t talk. It’s a manager who reads silence as agreement, when the silence is the symptom. This post covers what open communication actually requires, why people withhold the real objection, the scripts that change it, a self-check you can run today, and three companies that built it into the job.
What is open communication at work, really?
Open communication is when people tell you the inconvenient truth without first calculating whether it’s safe to. It’s not the volume of talking or the number of channels you have. It’s whether the honest answer reaches you before the decision gets made, not after it goes wrong.
That’s a higher bar than most open-door policies clear. A door that’s open in theory does nothing if walking through it has cost someone a project or a promotion before. Open communication lives in what people predict will happen when they speak up, and that prediction is built from your past reactions, not your stated values.
So the useful question isn’t “is my door open?” It’s “what does my team expect when they bring me bad news?” If the honest answer is “he’ll get defensive,” you don’t have open communication. You have a polite team protecting itself.
Why does open communication matter for productivity?
Open communication improves productivity because better information reaches the people making decisions while there’s still time to act on it. When problems surface early instead of getting worked around, you catch mistakes before they ship and choose with the full picture instead of a sanitized version of it.
The downstream effects are concrete:
- Faster problem-solving, because issues get named instead of routed around quietly.
- Better decisions, since the real risks reach the table before a choice locks in. Our guide on why communication is important in the workplace breaks this down further.
- Higher retention, because people who learn their input doesn’t matter eventually take it somewhere it does.
None of this requires a personality transplant on your team. It requires you to make speaking up the lower-risk option, which is a set of behaviors you can practice.
Why do people withhold the real objection?
People withhold the real objection because, in the moment, staying quiet is the safer bet. Smart people run constant cost-benefit math: what happens to me if I say this, versus if I let it slide? When the math favors silence, you get silence, and it has nothing to do with how shy they are.
Three forces tilt that math toward quiet.
The cost of being wrong feels public; the cost of staying silent feels invisible. If raising an off-base concern gets you a sigh and a correction in front of peers, but staying quiet costs nothing visible, the rational move is to wait and see. One defensive reaction can teach a whole team this lesson in a single meeting.
Then there’s the memory of past feedback that vanished. People have watched their input disappear into a void, or get used against someone later. That history doesn’t reset because you said “I want your honest take.” It resets when they see honesty change something. For the deeper version, see our guide on communication problems in the workplace.
The manager rewards agreement without knowing it. This is the one most managers miss in themselves. You nod faster at people who agree, move on the second someone says “sounds good,” or tense up when someone hesitates. The team reads all of it, and learns to give you the version you want.
A coaching observation worth sitting with: the managers who tell us they’re the most open often lead the teams that have gotten best at reading what they want to hear. Openness is measured by how often someone tells you something you didn’t want to hear, not by how open you happen to feel.
Does your team sound open or actually communicate openly?
The difference between a team that sounds open and one that actually is shows up in specific, observable signals. Use the table below as a quick diagnostic. Read down the right column honestly, and count how many describe your team.
| Situation | Sounds open | Actually open |
|---|---|---|
| You ask “any concerns?” | Silence, then “looks good” | Someone names the weakest part out loud |
| You make a call people doubt | They go along, grumble later | They push back to your face, then commit |
| A project is slipping | You find out at the deadline | You hear about it in week one |
| You react to bad news | People watch your face first | People lead with the bad news |
| Feedback you gave lands wrong | You never hear it didn’t | Someone tells you it stung |
| A junior person disagrees with a senior one | They defer | They say so, and it’s normal |
If most of your honest answers sit in the left column, that’s not a verdict on your character. It’s a signal that the incentives in your room reward agreement, and incentives are something you can change. The next section is how.
How do you promote open communication on your team?
You promote open communication by changing what gets rewarded in the room, not by adding more meetings or another values poster. The goal is to make the honest answer the easy answer. Three practices do most of the work.
Ask questions that assume a problem exists
“Any concerns?” almost always gets silence, because it asks people to volunteer dissent in front of the group. Swap it for questions that take a problem as given, so naming one looks like cooperation, not conflict.
- “What’s the weakest part of this plan?”
- “If this fails in three months, what broke?”
- “What would you change if this were yours to ship?”
- “Who here is least convinced, and why?”
These give people permission to be critical without looking difficult. That permission is most of the game. For more on speaking and inviting directness without aggression, our one-stop guide to assertive communication for managers goes deeper.
Close the loop, out loud, every time
Nothing kills open communication faster than input that goes nowhere. If someone raises a concern and never hears about it again, they learn one lesson: don’t bother. Closing the loop is the single most useful habit here, and it costs you about thirty seconds.
Try this, verbatim, in your next meeting: “Last week three of you flagged the timeline. We’ve moved the deadline two weeks, and here’s the new plan.” Say it even when the answer is no: “I heard the budget concern. We’re still going ahead, and this is why.” The “no” with a reason builds more trust than the silence ever could. Framing those moments as positive communication rather than verdicts keeps people coming back.
Reward the inconvenient point in public
When someone raises the awkward thing, especially when they’re right and it’s inconvenient, thank them where the team can see it. Do it more than once, until people believe you mean it. One visible “good catch, I’d missed that” teaches more than a quarter of culture talk.
The flip side matters too: never punish the messenger, even with a micro-reaction. The tightened jaw, the “well, actually,” the visible disappointment. People track those signals far more closely than your words, and they’ll adjust to avoid them.
How does open communication work on remote and async teams?
On remote and async teams, open communication takes deliberate design, because the casual signals that build trust in person don’t exist by default. Nobody catches you in the hallway, and someone who quietly stops contributing in threads is invisible until it’s a problem.
A few things hold it up. Write decisions and their reasoning in a shared, searchable place, so context doesn’t live only in the heads of people who were on the call. Make async dissent normal: a written “I disagree, here’s why” comment should read as routine, not escalation. And watch the silence, because in async work no reply is data, not consent.
One scenario we see often: a manager, call her Dana, asks for feedback in a public channel and gets a wall of thumbs-up emojis. The real reactions arrive in three separate DMs that night. Her fix was small. She started asking specific people by name in the open thread (“Raj, you’ve shipped this before, where would it break?”), which made considered pushback the expected response instead of the brave one. Strong active listening matters just as much in writing as in a room.
What are common ways open communication quietly fails?
Open communication usually fails not from neglect but from well-intentioned habits that backfire. These failure modes look like effort, which is what makes them hard to spot in yourself.
The most common is open-door theater: you announce the door is always open, then sigh, multitask, or look rushed when someone actually walks through it, and the behavior overrides the invitation. A close cousin is rewarding agreement, where you ask for input but visibly light up at the answers that match your view and deflate at the ones that don’t, so the team quietly optimizes for your face.
Then there’s feedback that vanishes. You collect input in a survey or a one-on-one, it’s never mentioned again, and people conclude the asking was a formality. The subtler trap is confusing nice with honest. A team where everyone is pleasant and nobody disagrees is conflict-avoidant, not open, because real openness includes friction. Treating disagreement as a constructive feedback problem rather than a relationship problem keeps it productive. The last one is skipping the why: you make a call and just announce it, and without the reasoning, people can’t engage with it, so they stop trying.
3 real examples of open communication done well
The companies known for open communication didn’t get there with slogans. They built specific, repeatable rituals that made transparency the default path, so being open required no courage. Here are three worth copying.
-
Google’s TGIF all-hands. For years Google ran a company-wide meeting where employees submitted and upvoted questions for leadership in advance, so the uncomfortable ones couldn’t quietly get skipped. The mechanism is the point: hard questions on the record, voted up by peers, are far harder to dodge than a vague “any questions?” at the end of a town hall.
-
Buffer’s radical transparency. Buffer made openness structural by publishing its salary formula and revenue numbers openly, internally and publicly. When the financials aren’t a secret, the conversations around them get more honest, because there’s nothing left to guess at. Their open salary calculator means a pay question becomes a math question, not a political one.
-
Bridgewater’s recorded meetings. Ray Dalio’s firm records most meetings and encourages “thoughtful disagreement,” where junior people are expected to challenge senior ones on the merits. You don’t have to adopt the whole intense system to steal the principle: when challenging up the chain is the explicit, expected norm, people stop saving their real opinion for the parking lot.
The common thread is structure, not culture. None of these relied on people simply choosing to be open. They built rituals that made openness the path of least resistance, which is the only kind that survives a stressful quarter.
Start with one behavior, not a culture overhaul
Open communication doesn’t change because you announce a new value. It changes when the manager makes the honest answer safer than the polite one, one conversation at a time. You don’t need a program. You need reps.
Pick a single practice from this post and run it for two weeks. Replace “any concerns?” with “what’s the weakest part of this plan?” Close the loop, out loud, on one thing your team flagged last week. Then watch what people start telling you once they believe it lands.
If you want a coach in the room for those reps, Merlin runs scenario practice on exactly these moments: the meeting where nobody pushes back, the feedback you keep avoiding, the news you don’t want to react badly to. Managers who practice with Merlin see an average 26% improvement in their target skills over 12 weeks. Try Merlin free and start with the conversation you’ve been putting off.
Frequently asked questions
How do you encourage open communication without forcing people to speak up?
Change what you ask and what you reward, not how loud the room is. Replace “any concerns?” with questions that assume a problem exists, like “what’s the weakest part of this plan?”, and visibly thank people who raise inconvenient points. People open up when speaking honestly becomes the lower-risk option.
Why do employees stay quiet even when they disagree?
Usually because the cost of being wrong feels higher than the cost of staying silent. One defensive reaction from a manager, or one piece of feedback that vanished into a void, can teach a whole team to nod and save the real objection for a hallway conversation later.
How do you know if your team actually communicates openly?
The real test is how often someone tells you something you didn’t want to hear, not how open you happen to feel. If nobody pushes back in your meetings, treat the silence as a symptom to investigate, not a sign of alignment.
What is an example of open communication at work?
A manager closing the loop is the clearest example: “Last week three of you flagged the timeline, so we’ve moved the deadline two weeks, and the new plan is below.” It shows the team that speaking up changes outcomes, which is what keeps them doing it.