Read a sample: 1. What Listening Changes
Maya leaves a project meeting convinced she has been helpful. Her colleague Ben said the client presentation was “not ready,” so Maya offered to polish the slides before the next review. Ben thanked her, and the conversation moved on.
Later, Maya discovers that Ben was less concerned about the slides than about a missing decision. The team had not agreed on which recommendation to present. By the time she sent around an improved deck, people were still debating its central message.
Maya heard Ben’s words. She did not yet understand what he meant by them.
That distinction is at the heart of this book. Hearing gives you access to the words someone says. Listening is the work of finding out what those words mean in the situation you share. It includes noticing what the speaker identifies as important, what remains uncertain, and what kind of response would actually help.
In a busy workplace, that work can feel like an extra step. You have messages waiting, a meeting about to start, and a problem that appears to have an obvious solution. Moving quickly can be useful. But when you act on the wrong understanding, speed at the beginning may lead to more work later.
Better listening does not require you to become the quietest person in the room. It helps you choose a more useful response—whether that response is a decision, a question, a disagreement, or a simple acknowledgment.
Workplace conversations often rely on shorthand. A colleague says a plan is “almost done.” A supervisor asks for “a quick update.” A client says, “We need to revisit the scope.” Each statement carries information, but none tells you everything you need to know.
“Almost done” might mean the main work is complete and a small edit remains. It might also mean the draft exists but has not been reviewed. A “quick update” might be a short written note, or it might be a request to explain a delay before the next meeting. Revisiting the scope could mean removing one feature or reconsidering the entire project.
The listener’s challenge is not to guess which meaning is correct. It is to recognize when the distinction matters and ask.
Imagine a colleague says, “I’m worried about the launch.”
You might hear a request for reassurance and reply, “We’ve handled bigger projects than this.” You might hear a request for help and offer to take over a task. You might hear criticism and begin explaining why the schedule was reasonable.
Any of those responses could miss the point. The colleague might be worried that a supplier has not confirmed delivery, that the support team has not seen the final instructions, or that nobody has decided who will approve the release. The words signal concern; they do not identify its cause.
A more useful response could be, “What part of the launch are you most concerned about?”
That question does not require special knowledge or a long conversation. It simply leaves room for the speaker to explain before you decide what their concern means.
Listening this way is especially valuable when the same words carry different meanings for different people. “Ready,” “urgent,” “approved,” and “finished” can seem precise until a project depends on them. Two capable colleagues may use the same term while imagining different next steps. Neither person has to be careless for a misunderstanding to occur.
Consider Maya and Ben’s conversation more closely. Their exchange begins during a team check-in:
Ben: “I don’t think the presentation is ready for the client review.”
Maya: “I can clean up the slides this afternoon. The visuals are a little uneven.”
Ben: “That would help. Thanks.”
Nothing in this exchange is hostile or obviously unreasonable. Maya wants to contribute. Ben may genuinely appreciate the offer. Still, the conversation leaves a consequential question unanswered: What does “not ready” mean?
Now imagine a different version:
Ben: “I don’t think the presentation is ready for the client review.”
Maya: “What feels unfinished?”
Ben: “The slides need work, but the bigger issue is that we haven’t agreed on which option we’re recommending.”
Maya: “So the recommendation needs a decision before polishing the deck will be very useful. Is that right?”
Ben: “Exactly. I’m also not sure who has the authority to make that call.”
Maya: “Would it help if we asked Priya to clarify the decision and who owns it?”
Ben: “Yes. Once that’s settled, I can update the content, and your help with the slides would be great.”
The second conversation does more than reveal a problem. It changes the order of the work. Maya learns that the slide design matters, but it is not the first priority. She also learns that Ben is uncertain about decision authority. Her eventual offer is similar, yet it is better timed and connected to what the team needs.
Notice that Maya does not assume Ben’s concern is the only concern. She checks her understanding and suggests a next step. Ben remains free to correct her or propose something else.
This is what better listening changes: not just how a conversation feels, but what becomes possible after it. People can coordinate around a clearer problem, make their reasoning visible, and catch a mismatch before it hardens into a plan.
Listening does not guarantee that colleagues will agree or that every decision will be easy. Priya may have a different view of who owns the recommendation. The…