Why Leaders Are Always the Last to Know
He was the CEO of a mid-sized manufacturing company, and he was the last person in the building to know that his leadership team was afraid of him. Not afraid in the sense that he was cruel. He had never raised his voice in a meeting. He had never berated anyone publicly. He was smart, competent, and demanding, and somewhere along the way, being demanding had become a kind of force field. His direct reports had learned that disagreeing with him meant a longer conversation, a deeper interrogation of their reasoning, and a subtle but unmistakable temperature drop in his demeanor. It was easier to agree and handle things quietly on the side. The CEO thought he had an aligned leadership team. What he actually had was a compliance machine that smiled at him and did whatever it wanted after the meeting ended.
The paradox at the heart of leadership is this: the person who most needs honest feedback is the one least likely to receive it. The higher you go, the quieter the room gets. Not because people stop having opinions, but because the cost of expressing them rises with every level of authority. The leader sees agreement and assumes alignment. The team sees a risk and chooses silence. The gap between what the leader thinks is happening and what is actually happening grows quietly, and by the time it is visible, the damage is already done. This is the trust-breaker pattern from Chapter 4 of the book, and I have seen it destroy more leaders than poor strategy, bad markets, or financial miscalculation ever could.
The tension is exposed in a single reality: bad news does not travel upward unless trust lives there. Most leaders believe bad news travels upward as a matter of organizational gravity. They assume that if something is wrong, someone will tell them. That assumption is the most dangerous thing a leader can carry. Bad news does not travel upward. It travels sideways, it travels downward, it travels into whispered conversations in the hallway, and it travels onto the resumes that people update while you are still running the all-hands meeting. The only direction it does not travel naturally is up, because upward communication requires trust, and trust is what the leader who needs the bad news has usually already broken.
Proverbs 15:22 (NLT) captures the principle with surgical precision: “Plans go wrong for lack of advice; many advisers bring success.” The verse does not say plans go wrong because the leader lacked information. It says they go wrong for lack of advice. Advice is different from information. Information is data. Advice is the interpretation of that data through the lens of someone who is willing to tell you what they actually think. A leader can have all the dashboards, reports, and metrics in the world and still have no idea what is really happening, because the people who understand the data are not willing to tell the leader what it means if the leader has not earned the right to hear it.
The same principle appears in Proverbs 12:15 (NLT): “Fools think their own way is right, but the wise listen to others.” The contrast is between thinking your own way is right and listening to others. The fool and the wise leader face the same situation. Both have access to the same information. Both have direct reports who could tell them what is happening. The difference is whether those direct reports believe their input will be received or punished. The fool does not just refuse to listen; the fool creates conditions where no one is willing to speak. The wise leader does the opposite. They build a feedback pipeline that operates when they are not in the room, not because they surveil the team but because the team trusts that honesty is safe.
This brings us to the framework for rebuilding the feedback pipeline. The leader who discovers they are the last to know faces a specific repair process, and it does not start with asking for more feedback. It starts with examining why the feedback stopped in the first place.
The first cause is defensive reactions. When a leader receives difficult feedback and immediately explains, justifies, or corrects the person who gave it, that person learns a lesson. They learn that feedback is not a gift; it is a trap. The leader may not mean to be defensive. They may genuinely believe they are providing context. The person on the other side hears something different, however. They hear that their observation was wrong, or that they missed something, or that the leader already had a reason. After a few rounds of this, the feedback pipeline dries up. The leader does not hear less because people agree more. They hear less because people have learned that speaking is not worth the effort.
The second cause is selective hearing. Most leaders have a mental list of whose opinion they value. The list is usually small: the trusted lieutenant, the longtime colleague, the person who has been with them since the beginning. The problem is that the people on that list are often the people who learned to navigate the leader’s defensive patterns long ago. They know what to say and how to say it. They are not necessarily the people with the most accurate view. They are the people who have figured out how to stay safe while appearing honest. The leader who only listens to their inner circle is not getting a representative sample of organizational reality. They are getting a polished version of what their inner circle thinks they can handle.
The third cause is positional loneliness. As a leader rises, the number of people who can speak to them honestly and without agenda shrinks. Peers become competitors. Direct reports become dependent on the leader’s approval. Board members have their own interests. The leader ends up surrounded by people who want something from them, and the feedback that comes through that filter is always shaped by what the sender wants the leader to do. Proverbs 18:2 (NLT) names the pattern: “Fools have no interest in understanding; they only want to air their own opinions.” The leader who does not actively resist this dynamic will end up hearing everyone’s agenda and no one’s truth.
Rebuilding the pipeline requires three specific moves, and they must be done in order.
First, acknowledge the gap publicly. The leader who discovers they are the last to know must name it. “I have realized that I am not hearing the full picture, and I know that is because of something I have done.” This is not a technique. It is a confession. Proverbs 28:13 (NLT) applies here: “People who conceal their sins will not prosper, but if they confess and turn from them, they will receive mercy.” The confession does not make the leader weak. It makes the conditions for honesty possible again, because the team sees that the leader knows what they have been doing and is taking responsibility for it.
Second, reward the feedback you receive. When someone brings you a hard truth, your first job is not to evaluate whether it is accurate. Your first job is to make sure the person who brought it feels safe. Thank them. Tell them what you will do with the information. Follow up. The leader who thanks someone for hard feedback and then acts on it has just invested in a feedback pipeline that will operate for years. The leader who argues with the feedback has just reinforced the message that honesty is not safe.
Third, create structural channels for anonymous input that you cannot ignore. A quarterly survey with honest questions. A third-party facilitator who gathers feedback from your team and presents it without attribution. A trusted advisor outside the organization who interviews your direct reports. The goal is not to bypass the relational work of building trust. It is to create a safety net for the years when that relational trust is being rebuilt, because the feedback you need does not stop while you are learning to receive it better.
Proverbs 10:17 (NLT) frames the whole challenge as a choice: “People who accept discipline are on the pathway to life, but those who ignore correction will go astray.” The leader who accepts correction is on a different path from the one who ignores it. The correction does not feel good in the moment. It exposes blind spots, challenges assumptions, and forces the kind of self-examination that most of us would rather avoid. The path of accepting it, however, is the path of life. The path of ignoring it is the path of going astray, and the saddest part is that the leader on the wrong path never realizes it until the consequences arrive.
Proverbs 29:1 (NLT) puts it even more starkly: “Whoever stubbornly refuses to accept criticism will suddenly be destroyed beyond recovery.” The word “suddenly” is the part that catches my attention. It does not feel sudden from the inside. It feels gradual. One meeting where you cut off a dissenting voice. One quarter where you dismissed a concern as negative thinking. One year where your inner circle learned to tell you what you wanted to hear. It feels gradual until the moment it is not, and then it feels like it happened overnight.
The leader who wants to avoid that outcome does not need a new strategy. They need a new relationship with feedback. They need to see criticism not as a threat to their authority but as the most valuable signal their team can send them. They need to stop asking, “Do they trust me?” and start asking, “Have I given them a reason to?” The answer to the second question determines the answer to the first, and the leader who is honest about that connection is the leader who will not be the last to know.
Leadership Challenge: Think about the last time someone on your team gave you difficult feedback that you did not want to hear. How did you respond? Did you thank them, or did you explain why they were wrong? That single response taught your team more about whether honesty is safe than every speech you have ever given about open communication. If you cannot remember the last time someone gave you hard feedback, ask yourself why, and start with the assumption that the answer is something you have done.
I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.