Only 42% of U.S. employees report having a chance to formally provide feedback to their manager, according to Gallup’s 2024 workplace research. Fewer than one in four have ever formally rated their manager’s performance. Yet in my experience running IT operations teams for over two decades, nearly every manager I’ve worked with would describe themselves as “open to feedback.”

That gap between self-perception and reality is one of the most damaging blind spots in management. You can read every book on giving feedback, practice every framework, and still miss the most important skill: receiving it well when the feedback is about you.

The Power Problem Nobody Talks About

The moment you become someone’s manager, the feedback channel narrows. This isn’t a personality failure. It’s structural. Research published in Organization Science found that when leaders openly sought feedback and shared what they learned, team psychological safety increased measurably. But the study also revealed a catch: most leaders initiated this behavior once or twice and then stopped, often because early feedback felt threatening.

Your direct reports are doing a constant calculation every time they consider telling you something uncomfortable. They’re weighing the value of being honest against the risk of changing how you see them. And in most cases, silence wins. Not because your people are cowardly, but because the math genuinely favors keeping quiet. The person who controls their workload, their raise, and their career trajectory is the same person asking, “What could I do better?”

That power dynamic doesn’t disappear because you’re friendly. It doesn’t disappear because you have an open-door policy. It only starts to shift when you prove, through repeated behavior over time, that honest input from your team leads to better outcomes for everyone and worse outcomes for no one.

Three Signs Your Team Has Already Gone Quiet

In a fractional COO engagement through Ops Harmony, I worked with a director who insisted his team was “brutally honest” with him. Within two weeks of observing their meetings, three patterns were clear.

Agreement came too fast. When the director proposed a plan, heads nodded within seconds. No clarifying questions, no pushback, no alternative suggestions. In a psychologically safe environment, a new proposal generates questions. Immediate consensus usually means people have learned not to challenge.

Feedback only went one direction. The director gave plenty of feedback to his team: detailed, specific, constructive. But not once did a team member offer feedback upward. The relationship was teacher and student, not two professionals in conversation. Effective 1-on-1 meetings should include time for the manager to ask what they personally could do differently.

Problems surfaced late. Issues that should have been raised in week one of a project kept appearing in week six. Not because people didn’t see them early, but because raising a concern meant implicitly criticizing a decision the director had already made. The team had learned that flagging problems felt, to the director, like an attack on his judgment.

None of these patterns are rare. If you’re reading this list and thinking “that’s not my team,” consider the possibility that you simply haven’t seen what your people have decided not to show you.

Building a Feedback Pipeline That Runs Uphill

Zenger Folkman’s research across hundreds of thousands of 360-degree assessments found that leaders who ranked in the top 10% at asking for feedback were rated, on average, at the 86th percentile in overall leadership effectiveness. Leaders who ranked in the bottom 10% at seeking feedback were the least effective leaders in the dataset, full stop.

The correlation is striking, but the mechanism matters more than the number. Effective feedback seeking isn’t a once-a-year survey. It’s a series of small, low-stakes moments where you make it easy for people to tell you the truth.

Ask specific questions. “Do you have any feedback for me?” is almost useless. It puts the entire burden of framing, timing, and risk on the other person. Instead: “In that project kickoff yesterday, was there anything I said that made the scope less clear?” or “When I jumped into the conversation between you and the client, was that helpful or did it undermine you?” Specificity reduces the social cost of answering honestly.

Ask the right people at the right time. The best feedback comes from someone who just watched you do the thing. After you facilitate a meeting, ask one attendee (privately, not in front of the group) what you could have done differently. After you make a decision, ask the person most affected whether the process felt fair. Proximity to the event makes feedback concrete rather than abstract.

Respond with curiosity, not defense. This is where most managers fail. Sheila Heen, who studies feedback dynamics at Harvard Law School, has documented how recipients of critical feedback instinctively question the giver’s qualifications and the accuracy of the information. That instinct kicks in even when you explicitly asked for the feedback. The discipline is simple to describe and genuinely difficult to execute: when someone gives you feedback, your only job in that moment is to understand it. Not to agree, not to explain, not to contextualize. Just to understand.

Close the loop. If someone tells you that you tend to dominate brainstorming sessions, and you work on it, tell them you worked on it. Ask whether they’ve noticed a change. This does two things: it proves you actually listened, and it creates a precedent that giving you feedback leads to visible action. Gallup’s workplace research consistently shows that employees are more willing to provide upward feedback when they’ve seen previous feedback produce results.

What I Got Wrong (and What Changed When I Fixed It)

Early in my career leading IT operations teams, I thought asking for help and asking for feedback were essentially the same thing. They’re not. Asking for help is about a problem you already know exists. Asking for feedback is about problems you can’t see yet because you’re the one causing them.

The turning point came during a network infrastructure project in 2011 when a senior technician told me, after the project shipped successfully, that my habit of checking in twice daily had slowed his team’s progress by roughly 15%. He’d calculated it: fifteen minutes of context switching per check-in, two check-ins per day, across a four-person team. The project succeeded despite my oversight cadence, not because of it.

That conversation only happened because I had, over the previous six months, been explicitly asking that specific technician for one piece of feedback after each major milestone. Not a general “how am I doing?” but a targeted “what did I do on this milestone that you’d want me to change next time?” It took six months of consistent asking before he trusted the question enough to give me something real.

The Gallup data backs this up: only 36% of managers receive peer feedback through any formal process. The feedback channels most managers rely on (annual surveys, 360 reviews, open-door policies) are too infrequent, too formal, or too risky for the people using them. If you want honest feedback, you have to build informal channels and maintain them through consistent behavior over months, not days.

The Skill That Changes Everything Else

Building trust with your team, developing your active listening skills, becoming a better communicator: every one of these management competencies depends on accurate information about how you’re actually showing up. Without feedback flowing uphill, you’re navigating on outdated maps.

The managers who get this right share one trait that Zenger Folkman’s data confirms: they treat feedback seeking as a practice, not an event. They ask regularly, ask specifically, respond without defensiveness, and close the loop with action. It’s not complicated. But it requires something that no framework can give you: the willingness to hear that you’re part of the problem.