There is a sentence couples therapists sometimes say to a couple struggling to communicate: you have to learn to listen to each other, but it does not mean you have to agree. The sentence has to be said because the people in front of them believe the opposite. They believe that listening is a kind of conceding, that to give a real hearing to what their partner is saying is to risk losing ground in an argument neither of them is willing to lose. So they do not listen. They perform listening, while preparing the next position, and the cycle continues until someone hands them a sentence that tells them they have been doing it wrong.
It is a useful sentence in therapy. It is also one of the more accurate descriptions of professional life I have encountered. The conflation between listening and agreeing is not a private problem. It is a defining feature of how people who have to work together fail to do so.
The conflation does its most quiet damage in places where it is least examined: in meetings, in leadership teams, in working groups, in any setting where people are convened on the premise that they are going to think together. These are the settings where listening should be most consequential. They are also the settings where the conflation between listening and agreeing is most powerful, because the cost of agreement, perceived or actual, can be felt in real currency. Status. Position. Whose framing wins. Whose work gets prioritized. People show up to such meetings already calibrated to defend, and they defend by not listening.
What looks like disagreement in those settings is often not. What looks like dialogue is often two or more people speaking past each other from different sides of an observation they share. The cost of this, mostly invisible to the people in the room, is enormous. Not because the meeting goes badly, though it does. Because the actual problem in front of them never gets named.
*What follows is a composite, drawn from a pattern I have seen across multiple meetings in more than one organization.
In senior-level technology governance meetings of the kind held at large regulated institutions, each line of business is allotted time to present compliance metrics, challenges, and project deliverable updates. Several directors, each a senior voice for their line of business and accountable to their own CIO, would spend their allotted time presenting their PowerPoints, sharing metrics, and firing off their frustrations past each other. One would argue that the framework imposed a uniformity that did not account for the operational resilience realities of their line of business. Others would argue similar points, sometimes conveying that their peers had been treating the same business continuity framework as a compliance exercise rather than a discipline rooted in real resiliency. At one such meeting, one of the directors said, "the artifacts we produce no longer correspond to or represent what our teams are actually doing." Another director agreed. "Exactly," he said. "Which is why we need everyone to take the artifact requirements more seriously." They were diagnosing the same gap from opposite sides: the framework, as administered, was not producing what it claimed to produce. Neither of them heard the other for what they were really saying. They could not, because the meeting had lost its original purpose to surface concerns and had become theatre in front of a governing body that everyone in the room knew was structurally unable to act on, improve, or even stress test their inputs. Under those conditions the only thing left to do was to be on record as having said something defensible. Nothing meaningful was decided. Everyone retrenched to their corner, kept checking their box, and defended their territory, even as they kept misunderstanding the alignment hidden in their own disagreement.
What is striking in that exchange is not that the second director failed to hear his colleague. He heard him. He registered what was said. He nodded. He even used the word exactly. And then he responded to a different sentence than the one that had been spoken. The words landed. The meaning could not be permitted to land. To let the actual claim through, that the framework was not producing what it claimed, would require him to revise something he was responsible for defending. So he heard the words and then, in the same breath, neutralized them by translating them into a familiar framing in which he was not implicated.
Carl Rogers, writing with Richard Farson in 1957, described this exact dynamic. Active listening, as he understood it, required a willingness to enter the other person's frame of reference closely enough that one's own frame of reference might shift. We have, Rogers observed, a natural tendency to judge, to evaluate, to approve or disapprove, and that tendency operates faster than our willingness to be persuaded. The Australian writer Hugh Mackay later called this the courage to listen, which is the right name for it. Listening is not difficult because it requires concentration. It is difficult because it requires a willingness to be moved.
The thing we call listening, in most professional settings, is something else. The systems theorist Otto Scharmer has a name for it: downloading. It is the lowest of the four levels of listening he identifies, and it is the level at which most workplace conversations operate. In downloading, we are not processing what is being said. We are confirming what we already believe, filtering incoming information through the framework we brought into the room, and waiting for evidence that either validates or contradicts our position. The conversation is theatre to us. We are not there to learn. We are there to hold ground.
Edgar Schein, working in the same intellectual neighborhood, named the cultural condition that produces this. Organizations, he observed, are built around telling rather than asking. Leadership is rewarded for advocacy, for clarity, for the confident assertion of positions. It is not rewarded for inquiry, for genuine questions to which the asker does not already have answers. Schein called the alternative humble inquiry, and the descriptor mattered. Inquiry requires humility because real questions involve real uncertainty about the answer, which means the asker might learn something that revises their view. Workplaces built around telling produce people who have not practiced asking. They have not practiced listening either, because the two practices are joined. You cannot do one without the other.
What we encounter in meetings, then, is not a failure of attention. It is the visible surface of a missing discipline. Listening as a practice has not been developed in most of the people doing it, because the institutions that employ them have never asked them to develop it. They have been asked to perform it. That is a different thing.
*The cost of this is not bad meetings. Bad meetings are the symptom we notice because they are tedious. The actual cost is harder to see. We lose the capacity to recognize alignment when it exists. We lose the ability to solve problems collaboratively, because collaboration depends on being able to hear what is actually being said by the people we are working with. We lose dialogue itself, in the older and more demanding sense of the word. David Bohm, who took the term seriously, distinguished between dialogue and discussion. Discussion shares a root with percussion, the breaking apart of an issue into competing fragments. Dialogue, in Bohm's reading, is something different. The Greek dia means "through," not "two," and logos is "meaning." The image he reached for was of a stream of meaning flowing among and through and between the people in the room. Most of what we call dialogue in organizational life is not that. It is discussion, and most of what we call discussion is parallel monologue.
The therapy sentence is correct. You do have to learn to listen to each other, and it does not mean you have to agree. The harder part of that sentence, the part the therapist does not have to say because the couple in front of her can feel it, is the first half. You have to learn. Listening is a learned discipline. It is not a personality trait, not a sign of empathy, not a competence we are born with. It is a practice. We have not practiced it. That is the work in front of us, individually and collectively, and it is not work most of our organizations are structured to reward. Which means most of the practicing will have to be done in spite of those structures, not because of them.