Updated 20 October 2026.
When a conversation becomes difficult, try describing a possible concern before defending your own solution. Keep the description tentative, let the other person correct it, and listen to the correction. The purpose is to understand the situation more accurately, not to announce what someone must be feeling.
Never Split the Difference by Chris Voss with Tahl Raz introduces negotiation techniques built around understanding the other party. The Black Swan Group's article describes labeling as attaching a tentative identifier to emotions, dynamics, or circumstances. Our practice sequence below applies that idea to an ordinary work disagreement.
Notice what was said before guessing why
Write down the other person's actual concern as closely as you can remember it. Then mark the explanation you are adding. “We cannot support another custom feature” is an observation about their words. “They do not care about this customer” is your inference.
The distinction matters because a label is an attempt to check an interpretation. If you already believe your guess is certainly correct, it is easy to turn a listening technique into an accusation with a polite introduction.
Choose a manageable conversation for practice. Do not use a memorized technique as a substitute for appropriate help in unsafe or coercive situations.
Offer a tentative description and leave space
Describe the possible constraint in plain language. For example, you might say that the additional maintenance appears to be the main concern. Use your normal voice and stop long enough to hear the reply.
Avoid stacking several guesses together. A long speech about someone's motives gives them more to dispute and less room to explain. Also avoid following the label immediately with a rebuttal that makes the listening feel staged.
If they correct you, accept the correction as information. You do not need to defend your original wording to make the exercise worthwhile.
A worked example: a disputed delivery date
Imagine a client asks for a report by Thursday. You propose Friday, and the client repeats that Thursday is essential. Your initial interpretation is that they are being inflexible.
An original practice response could be: “It sounds as though something important depends on having this ready on Thursday.” That sentence tests a possibility without claiming to know the client's emotional state.
The client might explain that a board meeting is scheduled for Friday morning. They might instead say that the real concern is a previous missed promise. These possible answers lead to different discussions. Neither response is assumed to occur.
You can then check the practical requirement: which sections are needed for that event, what quality checks remain, and what you can honestly deliver. Understanding a deadline does not require accepting an impossible commitment.
Turn understanding into a clear next step
Summarize what you now understand and ask whether you missed anything. Only then discuss options. Separate the other person's requirement from the particular solution they first requested.
If an agreement emerges, record the deliverable, owner, deadline, and unresolved risks. A conversation that feels calmer may still end with different expectations unless those details are explicit.
The negotiation learning path provides a broader reading sequence. This exercise stays with one listening move and the information it produces.
Review the accuracy of your interpretation
Afterward, note your original guess, the correction or confirmation, and what changed in the available options. Do not judge success solely by whether the other person accepted your preferred deal.
For recall, explain why a tentative label differs from telling someone how they feel. Then write one concern you need to understand in your next conversation. Prepare to be wrong about it; the correction may be the most useful part of the exchange.
Continue with ReadSprint
Open the related book summary to revisit the book's broader ideas. Use the free Book-to-Action Plan to organize your own takeaways into practice and review phases; the tool arranges the entries you supply rather than validating the method or predicting results.
Source checked 20 October 2026: The Black Swan Group on tentative labeling. The source supports the attributed book concept. The scenarios, questions, and practice steps in this article are original ReadSprint suggestions; example outcomes are hypothetical.
