The Feedback Teams Are Afraid to Give Their Managers
There's a conversation that almost never happens in organizations. Not because no one thinks about it. Because no one knows how to have it safely.
It's the conversation where a team member tells their manager what they actually experience — not what they think is acceptable to say.
What Teams Think and Don't Say
Team members have a very precise opinion of their manager. What works, what doesn't, what they'd like to see change. That opinion builds week after week, in meetings, in 1:1s, in informal exchanges.
It rarely stays in a drawer for long. It circulates — between colleagues, in hallway conversations, sometimes in anonymous surveys. But it almost never reaches the manager it concerns directly.
Not out of malice. Out of risk calculation.
Why This Feedback Never Surfaces
Giving upward feedback — toward your manager — is one of the riskiest gestures in an organization. Even in cultures that call themselves open. Even when the manager explicitly says they want it.
The team member makes a simple, often unconscious calculation: is the benefit of saying worth the risk of having said? In most cases, the answer is no. Not because the manager would overreact or shut down. Because the power asymmetry is real, and teams know it.
So they hold it. They observe. They adapt. And the manager keeps leading without the information that would help them most.
What This Feedback Actually Contains
What teams hold back isn't always negative. It's often far more nuanced than that.
They hold specific observations: "When they come to a meeting without reading the docs, we all lose an hour." "They give positive feedback but never in public — it doesn't land the same way." "They delegate, then take the wheel back the moment anything gets complicated. We can't tell anymore if we actually own it."
This is information of enormous value for a manager who wants to grow. It's precise, contextual, grounded in reality. Infinitely more useful than a standardized annual review.
And in most cases, it remains completely invisible.
What Changes When This Feedback Becomes Visible
When a manager gains access to these observations — in a safe, structured, non-judgmental setting — something shifts.
First for them: they finally see what their team sees. Not a softened version, not an HR summary. The reality of what they produce as an effect on the people they work with every week. Uncomfortable. Also extraordinarily useful.
Then for the team: the simple fact that this feedback is taken seriously — and followed by visible change — alters the relationship. Trust grows. Not because the manager has become perfect. Because they showed they could hear it.
The Role of a Structured Program
It's not the manager's job to single-handedly create the conditions for this feedback to surface. It's too hard. Power asymmetry doesn't disappear because you want it to.
What allows this feedback to exist is an external structure that makes it legitimate and safe. A framework where team observations have somewhere to go. Where the manager can receive them without it becoming a confrontation. Where both sides understand the goal is growth, not evaluation.
That's precisely where the difference lies between a leadership program that leaves a mark and one that gets forgotten.
In the next article: why the ROI of a leadership program remains so hard to measure — and how to finally make it visible for those who fund it.