In this article
- Better listening separates four layers
- Clarify vague words with a concrete example
- Check the request hidden inside the explanation
- A hypothetical readiness discussion
- Reflect both the issue and the uncertainty
- Notice tone without treating it as evidence of intent
- Turn understanding into a usable next step
- Be careful when the message travels through others
Harvard Business Review encourages leaders to develop their listening practice. This article focuses on ambiguous workplace language rather than general advice to pay attention.
Better listening separates four layers
A workplace message can contain an observation, an interpretation, a request and an unresolved decision. The speaker may combine them in one sentence.
“We cannot launch this” might mean a required check failed, a resource is missing, a stakeholder is uncomfortable or the speaker wants someone to decide the acceptable risk.
Ask which part is being stated. “What specifically prevents launch?” is a useful first question.
Then distinguish what is known from what is expected. “The test failed” and “I think the test will fail” require different responses.
Do not treat this as a rigid interview format. Use the distinctions to clarify the message, not to make the speaker categorise every sentence.
Clarify vague words with a concrete example
Words such as urgent, difficult, unfair and ready can mean different things to different people. Ask for the event or requirement behind the word.
For “urgent,” ask what deadline or consequence makes it urgent. For “unfair,” ask which decision or allocation the person means. For “not ready,” ask what would need to be true to proceed.
Avoid asking in a tone that challenges the person’s right to raise the concern. Curiosity should be audible in both the words and the pace.
If the issue is sensitive, explain why you need detail and allow an appropriate alternative channel.
A specific example can reveal a real problem without requiring agreement with every broad label.
Check the request hidden inside the explanation
After hearing the context, ask what the colleague needs from you. They may want a decision, help with access, a second view or simply confirmation that you understand.
A manager who offers sympathy when approval is needed leaves the work stuck. A manager who makes a decision when the employee wants to think through options can remove useful ownership.
Try: “What would help you move this forward?” Then check whether the requested action is within your authority.
If the colleague does not know, help identify the next decision. You do not need a complete solution to make the immediate question clearer.
A hypothetical readiness discussion
Imagine a project lead says, “The team is not ready for the new process.” The manager initially hears resistance to change.
She asks what readiness would look like. The project lead identifies that two users cannot access the system and the escalation owner has not been named.
Those are specific gaps. The manager can assign the access issue and confirm who owns exceptions.
The project lead also says the team feels uneasy. That concern remains worth discussing, but it no longer obscures the practical requirements.
This hypothetical shows why a broad phrase should be explored before it becomes a judgement about motivation.
Reflect both the issue and the uncertainty
A good summary makes it easy for the speaker to correct you. “You have confirmed the access problem, and you are less certain whether the training covers exceptions. Is that accurate?”
Do not sharpen an uncertain concern into a definite accusation. If someone says a colleague may have missed a step, do not repeat it as a proven failure.
Likewise, do not soften a confirmed requirement into a preference. If a mandatory check is incomplete, call it a requirement.
Ask whether anything important is absent from your summary. The missing point may be the one the speaker was struggling to state.
Notice tone without treating it as evidence of intent
A hurried voice can reflect urgency, stress, limited time or communication style. It does not prove disrespect.
Use what you notice as a prompt for a question, not a conclusion: “This sounds time-sensitive. What needs attention first?”
Be careful with cultural and language differences. A short message may be efficient rather than hostile; a polite agreement may still leave uncertainty about the task.
Where helpful, confirm the next step in writing. Keep the note factual and concise, with the owner and timing visible.
Do not record sensitive personal detail unless it is necessary and appropriate for the process.
Turn understanding into a usable next step
End by checking the action, owner and unresolved question. “We agree that access is the immediate blocker; Maya will contact the system owner today, and we will review the training question tomorrow.”
If no decision is possible yet, state what evidence is needed and who will obtain it. Listening should make the uncertainty clearer, even when it cannot remove it immediately.
For related practice, read Peak Belt’s clear-communication guide and decisions-under-pressure guide, alongside TrueNorth.
Be careful when the message travels through others
A second-hand account may omit context or sharpen uncertainty into a confident claim. Where appropriate, check the issue with the person who observed it or review the relevant record. Avoid repeating a rumour as fact. If the concern needs formal reporting, use that route instead of conducting an informal chain of interviews. Good listening includes knowing the limits of the information you received.
In the next conversation containing a vague concern, ask for one concrete example and the decision needed. Check those two points before offering your answer.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.