Interpreting and Understanding: Meaning Before Judgment

Between receiving a message and deciding what to do about it, two things have to happen that most organizations skip entirely. The message has to be interpreted, read in its context, and understood, grasped along with the motivation that produced it. Skip these and you can run a technically complete listening process that acts, efficiently and confidently, on things nobody actually said.

These are the fourth and fifth canons, and I take them together because they fail together, usually inside the same summary document.

Interpreting: context is not decoration

Interpreting means making meaning of what was said, in context rather than in isolation. The isolation version is seductive because it scales: strip the comments out of the survey, sort them by theme, count the themes. Communication does not survive this processing, because the same sentence means different things from different places.

We need more planning time, written by a first-year teacher, most likely describes drowning. The identical sentence from a twenty-year veteran who has never once complained is a different message entirely, something upstream has changed, and a person with two decades of calibration is telling you the load stopped being carryable. A theme-counter logs them as two votes for planning time. An interpreter notices the second one is an alarm.

Context that changes meaning is usually cheap to attach: who said it, from what role, at what point in the year, whether they have said it before, what they said it alongside. For example, when I processed teacher submissions in my own listening research, every item kept its metadata, role, timing, and surrounding items, and that surrounding information changed the reading of the item more often than not. The words were the tip. Context was the iceberg.

The structural rule: whoever interprets input must either hold context about the work it came from or be required to go get it. Input from the loading dock interpreted only by people who have never stood on the loading dock is not interpretation. It is translation by someone who does not speak the language.

Understanding: the message has a why

Understanding goes one layer deeper: grasping both the message and the motivation behind it. Every piece of voice was sent by someone who chose to spend effort and, usually, some credibility. That choice has a reason, and the reason is part of the information.

What is this person trying to protect? What are they afraid is about to happen? What have they watched fail before? A complaint about a new procedure might be resistance to change. It might also be a veteran recognizing the exact shape of a mistake the organization made five years ago, phrased badly because they are angrier than they are articulate. The words are similar. The motivations are worlds apart, and so are the correct responses.

Kluger and Itzchakov's review of listening research points at why this matters beyond accuracy: being listened to in this fuller sense measurably changes speakers, less anxiety, less extremity, more willingness to examine their own view (Kluger & Itzchakov, 2022). People can tell the difference between an organization that processed their sentence and one that understood their situation. Only the second builds the relationship that makes future voice cheaper.

Keep the voices intact

One practice guards both canons at once: preserve people's actual words as far up the chain as possible.

In my dissertation research I quoted participants verbatim, disfluencies and all, it's like, ohh, I would not have thought that, because cleaned-up speech is subtly different speech. Organizations should hold a version of the same discipline. Every summary that moves input upward should carry representative quotations, unpolished, attributed at whatever level of anonymity the channel promised. When a leadership team reads the sentence a person actually wrote, interpretation and understanding at least have raw material. When they read staff expressed concerns regarding implementation timeline, the canons have already been strangled by the prose.

A simple test for your own pipeline: take a decision that was influenced by collected input, and ask the decision-makers to quote one actual sentence from that input. If nobody can, your organization is listening to its own paraphrase.

Interpreting and understanding are where listening becomes knowledge. They cost more attention than counting themes, which is exactly why they are rarer, and why the organizations that do them hold an advantage that never shows up on a dashboard: they are acting on what their people actually meant.