Listening: The Forgotten Half

The King Who Asked and Then Did Not Listen

Lesson 6.5 ended by asking what you are carrying that you have never written down. Now the harder question, the one that ends careers and administrations: what is true inside your organization right now that nobody has told you?

First Kings 12 records one of the fastest institutional collapses in Scripture, and it is a listening failure with a paper trail. Rehoboam succeeds Solomon. The northern tribes come to him with a grievance about the burden his father had placed on them and a straightforward proposal: lighten the load and we will serve you. Rehoboam does something that looks exactly like good process. He asks for three days. He consults the elders who had stood before his father Solomon, men with decades of governing experience. Their counsel, in verse 7, NASB 1995: 'If you will be a servant to this people today, and will serve them and grant them their petition, and speak good words to them, then they will be your servants forever.'

Then verse 8: 'But he forsook the counsel of the elders which they had given him, and consulted with the young men who grew up with him and served him.' Read that phrase carefully — the young men who grew up with him and served him. He did not stop consulting. He kept consulting until he found a room that agreed with him. And the room he found gave him the line he wanted: tell them your little finger is thicker than your father's loins, that your father disciplined them with whips and you will discipline them with scorpions. He said it. Ten tribes walked out. The kingdom never reassembled.

Understand what actually failed there, because leaders misdiagnose this constantly. Rehoboam did not lack information; he had the elders' analysis in hand. He did not lack process; he took three days and held two consultations. What he lacked was any willingness to be changed by what he heard. He was running a search, not an inquiry — and a search has a target. This is why 'I have an open door' and 'I always ask for input' are not evidence of anything. Rehoboam had both.

So let me draw the line this lesson runs along. Lesson 5.5 taught listening as influence craft — Voss, labeling, mirroring, the ladder that ends when the other person says that's right. That material is real and I am not retracting a word of it. But it is listening aimed at moving someone. This lesson is about something upstream and less glamorous: listening as the information system a leader governs by. The purpose is not to persuade the person in front of you. The purpose is to find out what is true when the entire apparatus around you is gently, sincerely, and often unconsciously arranged to prevent that.

Because here is the hard part, and it is the reason this discipline cannot be delegated to a survey. Nobody in your organization is going to walk in and say 'I have decided to hide the problem from you.' They will decide to wait for a better moment. They will decide the boss has enough on his plate. They will soften the number because the raw version sounds alarmist, and they will be genuinely trying to help you when they do it. The distortion is not a conspiracy. It is a set of small, well-intentioned decisions repeated at every layer, and the sum of those decisions is that the chief executive is the last person in the building to learn anything.

The Silence Tax

Every organization charges a price for telling the leader something he does not want to hear. Call it the Silence Tax. The leader almost never knows he set the rate, and he always did. Bad news has to clear four gates to reach him, and each one takes a cut.

The first gate is distance. Information about a problem starts with the person closest to it, who is usually the person with the least standing to raise it. Between that person and you sit layers, and each layer is a decision point about whether the thing is worth passing along. Nothing malicious has to happen for a signal to die at gate one. It simply has to be judged not big enough yet, four times in a row, by four reasonable people.

The second gate is translation. What survives the layers gets rewritten at each one. This is the best-documented failure in the set. Research on upward communication in hierarchies going back to Read's work in the early nineteen-sixties found that accuracy of upward reporting is degraded by subordinates' ambitions and by low trust — people with something to gain from the boss's good opinion transmit a version optimized for that opinion. The classic laboratory finding is Rosen and Tesser's MUM effect: people are reluctant to transmit unpleasant news even when they have no stake at all in the outcome. Read that twice, because it is the crucial point. The reluctance shows up in strangers with nothing to lose. In your organization it is layered on top of real career stakes.

The third gate is incentive. Somebody in the chain is measured on the number that would look bad. A commissioner whose performance dashboard is the thing in question does not have to lie; he only has to choose the framing, the time window, and the comparison that is technically accurate and directionally reassuring. Morrison and Milliken's work on organizational silence describes the systemic version: shared beliefs that speaking up is futile or dangerous, reinforced by management practices, producing a climate where withholding becomes collective and normal rather than individual and guilty.

The fourth gate is temperament, and it is yours. This is where the rate actually gets set. Your organization has watched what happens to people who bring you problems. Not what you said about it in an all-hands — what happened. Whether the meeting got cold. Whether the person got quieter afterward, or moved off the project, or stopped being copied. Amy Edmondson's psychological safety research, which Modules 2 and 5 have already used, establishes that teams surface more problems when interpersonal risk is low; the extension this lesson adds is about a specific person. In a hierarchy the leader's involuntary reaction is the single largest input to that risk, and everyone downstream is a highly motivated reader of it. You do not get to declare the tax rate. You publish it, continuously, with your face.

Now do the arithmetic, because it is worse than most leaders assume. Suppose each of four gates passes only three-quarters of the bad news it receives — which is generous. Roughly a third of what was known at the bottom arrives at the top, and the third that arrives is the third that was safest to send. That is not an information system. That is a filter tuned to produce comfort, and its output looks exactly like good news.

So the diagnostic question is not do people trust me. It is this: when was the last time somebody told you something that genuinely ruined your afternoon, and what visibly happened to them afterward? If you cannot recall an instance, you do not have a quiet organization. You have an expensive one.

Answering Before You Hear

Scripture treats this as a moral failure and not merely an operational one, which is the right diagnosis. Proverbs 18:13, NASB 1995: 'He who gives an answer before he hears, it is folly and shame to him.' Note the edition, because the NASB 2020 revises the wording of this verse; I am quoting the 1995 throughout, as the academy standard.

The Hebrew repays attention here. The clause is meshiv davar b'terem yishma — literally, one who returns a word before he hears. The verb shama' is broader than the English 'hear.' It runs from perceiving sound through paying attention to heeding and obeying; it is the same verb that opens the Shema. So the proverb is not condemning a man who interrupts. It is condemning a man who produces a verdict before the input has done any work on him. And the verdict on that behavior is two words: folly and shame. Not inefficiency. Not a development area. Folly, which in Proverbs is a moral category, and shame, which is a public one — because answering before hearing eventually becomes visible to everyone.

James 1:19, NASB 1995, is the companion text, and Lesson 5.5 has already worked the Greek on its first two clauses — quick to hear, tachys eis to akousai, against slow to speak, bradys eis to lalēsai. I want the third clause here, because it is the one that governs organizations: 'slow to anger.' The word is orgē, settled anger rather than a flash of temper. Ask why James attaches anger to a listening instruction at all, and the answer is the whole lesson. A leader's anger is the mechanism by which the price of telling him the truth gets set. Every person who has ever seen you angry about a problem has learned something about the cost of bringing you the next one. James is not offering a temperament preference. He is telling you that speed of speech and speed of anger are the same failure, and that both of them close the intake valve.

Now the philosophical version, because Hans-Georg Gadamer named the distinction better than anyone. In Truth and Method he argues that genuine conversation is not two people trading prepared positions but a process in which both are exposed to the subject matter and neither controls where it goes. His famous phrase is the fusion of horizons: understanding happens when my horizon — everything I can see from where I stand, with all the prejudices that standing gives me — is enlarged by contact with another. Gadamer insists that openness means something specific and costly: being willing to have my own position put at risk. He gives priority to the question over the answer, because a real question is one whose answer is not yet settled.

Put that against Rehoboam and you have the whole diagnosis in one line. He conducted two consultations and never once asked a real question, because the answer was settled before the elders opened their mouths. He was listening to reply. Gadamer's standard is listening to be changed — and the practical test is embarrassingly simple. When was the last time a conversation altered a position you walked in with? If the honest answer is that you cannot name one this year, then what you have been calling listening is a data-collection exercise with a predetermined output, and everyone around you already knows it.

Apply it to yourself before the next section. Think of the last meeting where you asked for input. Were you prepared to leave with a different conclusion than the one you carried in? Were the people in the room the ones most likely to disagree, or the ones who grew up with you and served you?

The Bubble Around a Chief Executive

Everything above intensifies with the size of the office, and the mayoralty of New York is close to the limit case: roughly three hundred thousand employees, more than forty agencies, and a City Hall with a genuine tendency to become an information bubble. The larger the enterprise, the more layers between the street and the desk, and the more attractive it becomes for every layer to arrive with a solution rather than a problem.

Crown Heights in August 1991 is the case I want you to study, and I want it handled factually. On August 19, a vehicle in a motorcade struck two children on a Brooklyn sidewalk, killing seven-year-old Gavin Cato. Hours later, Yankel Rosenbaum, a visiting Australian scholar, was stabbed nearby and died. Three days of unrest followed in a neighborhood where two communities lived on the same blocks with long-standing tension between them. Mayor David Dinkins went to the neighborhood, met with residents and families, and at one point tried to address a crowd and was shouted down.

The state review commissioned afterward, directed by Richard Girgenti and released in 1993, is the document worth reading, because its findings are precisely about the information system. It concluded that the police response in the first days was not effective, faulted the department's command and coordination, and found that senior officials — including the mayor — did not receive a timely and accurate picture of what was actually happening on the ground. It did not find that police had been ordered to hold back, a claim that circulated widely at the time. Whatever else you conclude about that period, hold the operative lesson: a mayor was physically present in the neighborhood and still did not have the information. Presence is not an information system. The reporting chain is, and his had failed above the street and below his office.

There is a slower New York version of the same disease. Through the late nineteen-sixties and early nineteen-seventies the city financed operating deficits with short-term debt and accounting practices that pushed the reckoning forward, while the warnings that existed were treated as pessimism rather than data. In 1975 the market simply declined to buy the paper, and by that autumn the city was operating under an Emergency Financial Control Board and a state-created financing entity. Nobody woke up one morning and invented a fiscal crisis. It was ten years of accumulated unheard warnings arriving at once, and the price was the city's independence over its own budget.

Both cases carry the same executive moral, and it is not about any individual's character. It is that the bubble is the default state of an executive office, and it forms fastest around leaders who are competent and confident. Competence makes you the person others expect to have the answer. Confidence makes you fast. And speed plus expectation equals a staff that stops bringing you the ambiguous thing because they can predict how you will receive it. This is not a criticism of decisiveness. It is a warning that decisiveness has a maintenance cost, and the cost is paid by deliberately building channels that route around your own gravity.

One more note, and it belongs in a mayoral curriculum specifically. Some of what you most need to hear will come from people who do not work for you and cannot be managed: community boards, block associations, clergy, tenant leaders, small business owners, and reporters you find irritating. They are outside your incentive structure, which is exactly what makes their information valuable and exactly why it is uncomfortable. A leader who only hears from people whose careers he controls has built an information system with a single point of failure, and it is him.

Building a Listening Infrastructure

Good intentions do not lower the Silence Tax. Structures do. Here are the ones that work, and the honest caveats about each.

Start with skip-levels, the simplest and most underused. You meet regularly with people two levels below you, without their manager in the room, on a schedule rather than in a crisis. The schedule matters more than the content: a recurring meeting makes speaking normal, and normal is what removes the risk. The caveats are real. Skip-levels can be used to undermine managers, and they will be perceived that way unless you are explicit about the rules — you are gathering information, not adjudicating disputes, and you will not act on a single account without telling the manager. Get that wrong and you will have built a channel that punishes the very people who use it.

Next, the red team. Assign a named person or group the explicit job of arguing against your preferred course, with the time and the standing to do it properly. The naming is the mechanism. Objecting to the boss's plan is expensive when it is a personal choice and free when it is your assignment, and this is the cheapest way to convert a career risk into a job description. Module 3 taught the pre-mortem — imagining the failure has already occurred and writing the story of how — and a red team is that same discipline given a permanent owner instead of an occasional meeting.

Third, a designated channel for the objection. Andrew Grove described looking for what he called helpful Cassandras — the people at the periphery of an organization who see the change coming before headquarters does, usually because they are close to customers or to the street. In a city government the equivalents are the borough offices, the 311 pattern data nobody has escalated, and the frontline supervisor who has watched a procedure fail forty times. Find them, meet them directly, and protect them visibly. What protects them is not policy language; it is what everyone observes happening to them afterward.

Fourth, and this one costs nothing: change what you ask for. Stop asking whether there are any concerns, which is a question with a socially correct answer and everyone in the room knows it. Ask instead what is the strongest argument against what I just said, or what will we wish we had known in six months, or who in this building thinks this is a mistake and what is their best point. Then make the person least likely to agree with you speak first, before the senior people have signaled which way the wind blows. Anchoring is not a theoretical risk in a room with a hierarchy in it; the first confident sentence sets the range for everything after it.

And fifth, the one that determines whether any of the other four work: what visibly happens to the first person who tells you something bad. Everyone is watching that. If you thank the person publicly, act on the information, and make sure their standing is intact or improved a month later, you have cut the tax rate for the whole organization more than any policy could. If you go cold, or defend yourself, or explain why they misunderstood the situation, you have raised it — and you will not be told the next thing. Ed Koch made how am I doing his public signature, and there is something genuinely right in it: inviting the complaint is stronger than defending against it. But a catchphrase is a posture, not a system. The posture without the structure produces a leader who feels approachable and is not.

Do not miss what this costs, because it is not free and I am not going to pretend otherwise. Real listening will slow you down, surface problems you would rather not own, and occasionally require you to change a position you had already announced. My own failure has been the opposite temptation — trying to keep everyone happy, hearing agreement and calling it consensus, and finding out later what it actually cost. Sometimes you cannot bring everybody along, and hearing them properly does not obligate you to obey them. It obligates you to decide with your eyes open. Lesson 6.7 takes up what happens next: how you carry hard truth back to a person once you have actually heard them.