Zenger Folkman studied 51,896 executives and sorted them by one habit: how often they asked for feedback. The leaders in the bottom 10 percent for seeking feedback landed at the 15th percentile for overall leadership effectiveness. The leaders in the top 10 percent for seeking it landed at the 86th percentile. Same companies, same rating scale, a 71-point gap that tracks almost perfectly with whether someone went looking for the truth about themselves.
That finding should worry any product manager who is good at the job. Because the better you get, the quieter the room gets about your weaknesses. The feedback that shaped your first few years, the direct manager who told you your PRDs buried the decision, the engineer who said your standups ran long, that stream thins out exactly as your decisions start to matter more. Nobody schedules a meeting to tell a respected senior PM that their roadmap reviews have turned into monologues. The growth input disappears right when the stakes climb.
Why the correcting stops
Early in your career, correcting you is cheap for the person doing it. You are junior, the power gap runs in their favor, and pointing out a gap in your work reads as mentoring. There is social credit in it. As you rise, that math inverts. Now the person who notices your blind spot is often below you on the org chart, and telling you costs them something real: political risk, the chance you take it personally, the worry that the feedback lands on their next review.
Researchers have a name for the acute version of this. They call it CEO disease, the condition where the most senior person receives the least accurate information about the most consequential calls. It does not require a C-suite title. A principal PM three levels down the stack catches a milder strain of the same illness. Fast Company summarized the pattern bluntly: the more senior you are, the less feedback you get, and the people around you soften the hard parts because silence feels safer than candor.
The part that makes this dangerous is that the silence does not feel like silence. It feels like competence. You stopped hearing criticism, so you conclude you stopped earning it. That is almost never what happened.
Your read on yourself gets worse, not better
The intuitive assumption is that experience sharpens self-knowledge. The evidence points the other way. Organizational psychologist Tasha Eurich ran a research program across roughly 5,000 people and found that about 95 percent believe they are self-aware, while only 10 to 15 percent actually are. More striking for anyone climbing a ladder: her work found an inverse relationship between power and self-awareness. Senior leaders, as a group, were less accurate about how they came across than the frontline managers below them.
Put the two findings together and you get the trap in full. The honest external signal fades as you get more senior, and your internal read of yourself drifts in the wrong direction at the same time. You are flying on instruments that are quietly going out of calibration, and the one gauge that could recalibrate them, other people telling you the truth, is the gauge that stops reporting.
Eurich draws a useful distinction between internal self-awareness, knowing your own values and reactions, and external self-awareness, knowing how others experience you. PMs tend to overinvest in the first and assume it covers the second. It does not. You can have a crisp sense of your intentions in a prioritization meeting and no idea that the room reads you as dismissive of engineering’s estimates. Only external input closes that gap, and external input is the thing drying up.
What the vacuum looked like for me
I ran into this hard during a fractional COO engagement a few years back, advising a mid-sized operations team through a systems migration. I came in senior, with decades of IT operations behind me, and for the first two months the working sessions felt smooth. People nodded. My recommendations went in largely unchallenged. I read that as alignment. I was wrong.
What was actually happening was that my seniority and the consultant label had priced honest pushback out of the room. The team had real reservations about the migration sequence I had proposed, and I heard none of them, because disagreeing with the expensive outside expert carried a cost none of them wanted to pay. I only found out when one engineer, the most junior person on the project, stayed late and told me the rollback plan I was confident in had a dependency the team had flagged twice in Slack. I had never seen the Slack thread. Nobody had routed it to me, because routing bad news upward to the person who designed the plan felt like a bad career move.
That one conversation changed the sequence and probably saved the migration a painful weekend. It also taught me something I have never unlearned: the absence of pushback is not evidence of a good plan. It is usually evidence that the room has decided telling me is not worth it. Earlier in my career, running network operations at a large telecom, I had plenty of people above and beside me willing to tell me I was wrong. The higher I climbed, the more I had to go hunt for that signal myself. It did not come find me anymore.
“My door is always open” is how you guarantee silence
The most common thing senior people say about feedback is the most counterproductive. “My door is always open.” “Just tell me if you see something.” These are passive invitations, and passive invitations fail for a precise reason: they put the entire cost of the interaction on the other person. They have to decide the thing is important enough to raise, pick a moment, walk through your open door, and risk your reaction. At every step the safe choice is to not bother. A survey cited across the leadership literature found roughly 90 percent of senior leaders say they want more constructive feedback from their teams, while most hesitate to actually ask for it. Wanting it and engineering it are different acts.
The open door also asks the wrong question. “Any feedback for me?” invites a social reflex, and the reflex is “no, you’re doing great.” It is the same reason “how was everything?” from a waiter gets “fine” even when the steak was cold. Broad, low-stakes, face-threatening questions get reassuring non-answers. If you want real information, you have to lower the cost of giving it and narrow the target enough that a specific answer is easy.
Engineering the signal yourself
The Zenger Folkman data is not really about feedback as a nicety. It is about feedback as the input that separates the 86th percentile from the 15th. At senior levels that input will not arrive on its own. You have to build the system that produces it. A few things that have worked, for me and for the PMs I have coached through it.
Ask about one thing, not everything. Replace “any feedback?” with a question so specific it is almost answerable in one sentence. “In that roadmap review, did I shut down the mobile team’s pushback too early?” “When I disagree in writing, does it read as thinking out loud or as a decision already made?” A narrow question signals you can handle a real answer and makes the honest response the easy one.
Go down the org chart, not up. Your manager sees a fraction of your actual work. The people who see the most unfiltered version of you are the engineers, designers, and analysts you work with daily, and they are precisely the group least likely to volunteer a critique. So ask them directly, one on one, and then do the hardest part: when they tell you something uncomfortable, thank them and change something visibly. The first time you act on a junior person’s hard feedback, you buy more candor than any open-door speech ever will. The first time you get defensive, you close the channel for a year.
Separate the ask from the review cycle. Feedback bolted onto performance ratings is corrupted by stakes; nobody tells the truth when a number is attached. Ask in the quiet weeks, when nothing is riding on the answer. The self-assessment you write at review time should be the downstream product of signal you gathered all quarter, not your first attempt to find out how you are landing.
Keep a written record of what you hear. I keep a running note of every piece of hard feedback I get, who gave it, and what I did about it. Patterns show up in writing that you will rationalize away in the moment. If three different people over six months describe you as hard to interrupt, that is not three opinions, that is a finding. A simple running impact-and-feedback log turns scattered comments into something you can actually act on.
The uncomfortable truth underneath all of this is that the plateau most senior PMs hit is not a skills plateau. It is a feedback plateau. The skills would keep developing if the signal kept coming. Eurich’s research even reached the product discipline directly: one podcast built an entire episode on the premise that the successful product manager is the self-aware product manager, because the job is fundamentally about judgment, and judgment without an accurate self-model drifts.
You can feel the room getting quieter as you get better. Most people read that quiet as a verdict in their favor. The ones who keep growing read it as the alarm it actually is, and go rebuild the signal by hand.