There is a version of you that your team sees. And there is a version they show you.
These are not always the same thing.
This is not about dishonesty. Most people on your team are not liars. They are skilled readers of the room who have learned, through dozens of small interactions, exactly what you want to hear – and exactly how to package it before it reaches you.
That is the telephone game problem. And it lives in more tech teams than anyone is comfortable admitting.
Why Smart Teams Go Silent
Amy Edmondson, the Harvard Business School professor who coined the term psychological safety, has spent over two decades studying why brilliant people stay quiet. Her findings, laid out in The Fearless Organization, are uncomfortable reading for most leaders.
The short version: people do not speak up when they believe the risk of speaking outweighs the reward.
In tech teams, that calculation happens constantly. Someone notices a problem in the architecture three sprints before it becomes a crisis. Someone sees a deadline slipping two weeks before the status report goes out. Someone knows the estimate is unrealistic the moment it is given.
But they have also watched what happens when people flag these things. The leader gets tense. The meeting gets awkward. The messenger gets grilled. So next time, they stay quiet.
This is not a people problem. It is a communication culture problem. And it starts at the top.
Google’s Project Aristotle, one of the most cited studies on team performance, found that psychological safety was the single strongest predictor of team effectiveness, more than individual talent, role clarity, or structure. Teams that spoke up outperformed teams that did not. Every time.
Research from MIT Sloan Management Review puts a sharper point on it: leaders who create environments of honest dialogue consistently get better information, make faster decisions, and catch problems earlier. The data is not subtle.
The Three Patterns That Kill Honest Dialogue
In my work with tech leaders using the CQ Leadership Method and the Process Communication Model, I see three patterns that shut down real dialogue in otherwise high-performing teams.
Pattern 1: The Expert Trap.
You got promoted because you are good. Really good. And somewhere along the way, being the person with answers became part of your identity. The problem is that leaders who project constant competence teach their teams that questions are inconvenient and uncertainty is weakness. So people stop asking. And stop telling.
Pattern 2: Emotional Unpredictability.
You do not have to shout to create fear. A leader who gets visibly tense when plans change, who shuts down in difficult conversations, or who goes cold when someone challenges a decision sends a clear signal: emotional risk is real here. People calibrate accordingly. They test the waters once, maybe twice. Then they stop testing.
The Process Communication Model is useful here precisely because it helps you understand what your own stress behaviours look like to others, not to yourself. Most leaders are shocked by the gap.
Pattern 3: Rewarding the polished version.
When someone brings you a neat summary, you move on quickly. When someone brings you a messy problem with no solution yet, the meeting drags. Without meaning to, you signal which one is preferable. Your team is watching every reaction, every expression, every pause before you respond.
What Actually Rebuilds It?
Here is what I see working with leaders who have genuinely shifted the culture on their teams – not as a culture initiative, but as a practical communication habit.
Start with your listening, not your questions.
Most leaders think the fix is asking better questions. It is not. The fix is what you do after someone answers. Do you go curious or do you go defensive? Do you ask a follow-up or do you pivot to your own view? Real dialogue is built in those seconds after someone finishes speaking.
I wrote about this in depth here: Why So Many Tech Leaders Don’t Listen.
Name the silence, do not just hope it goes away.
If your 1:1s feel polished and frictionless, say that out loud. Try: “I notice our conversations lately tend to be pretty smooth. That could mean everything is genuinely fine, or it could mean we have not created enough space for the messier stuff. I want to hear both.”
This is a simple reframe. But it gives people explicit permission to bring you the unfiltered version. That permission matters more than you think.
Make safety visible through your reaction to bad news.
The moment someone brings you a real problem, a slipping deadline, an unhappy stakeholder, a mistake, you have about fifteen seconds to set a cultural precedent. If you thank them, get curious, and focus on the path forward, you have made it safer for the next person. If you look for blame or go quiet, you have made it more dangerous.
This is what I mean when I say culture is built one conversation at a time. Not in team retreats. Not in values workshops. In the small moments nobody is documenting.
One Question Worth Sitting With
Before your next team meeting or 1:1, ask yourself honestly:
When was the last time someone on my team told me something I did not want to hear?
If you struggle to remember a specific moment, that is your signal. Not that your team is doing fine. That your team has learned what to show you and what to keep to themselves.
The good news is that this is fixable. Not with a new process or a restructured stand-up, but with deliberate, consistent, communicating differently. Starting today. Starting with you.
PS. Do you want to save time from checking the new things on the blog or podcast? Sign in to the Leadership Pulse and have it in your inbox once a week with 0 effort!
