Read a sample: 1. What a Disagreement Is Really About
The meeting is nearly over when Maya says the team should release the revised customer guide on Friday. Daniel says it needs another review before anyone sends it out.
Maya hears resistance to a deadline the team has already discussed. Daniel hears a willingness to publish instructions that might confuse customers. They both repeat their positions, a little more firmly each time. By the end of the meeting, neither has changed their mind, and both leave with a less generous impression of the other.
What are they disagreeing about?
The obvious answer is the release date. But that answer alone leaves out useful information. Maya is responsible for getting the guide to a support team that has been asking for it. Daniel is responsible for checking whether the instructions match the product. They may have different information about how much work remains. They may also have different authority: perhaps neither can approve a delay without their manager.
If Maya decides that Daniel is simply obstructive, she is likely to argue about his attitude. If Daniel decides that Maya does not care about accuracy, he is likely to defend the importance of his work. Neither response tells them whether the guide can be reviewed in time, whether part of it could be released, or who can decide if the deadline must move.
A disagreement is not always a contest between personalities. Often, it is a situation in which people hold different views about what is true, what matters most, what should happen, or who gets to decide. Those differences can feel personal, especially when the consequences affect someone’s work, reputation, time, or sense of being respected. The feeling deserves attention. It does not, by itself, identify the issue that needs to be addressed.
This chapter gives you a way to slow down before you choose a response. You will learn to identify the issue, the people connected to it, and the decision or understanding needed next. The goal is not to make every disagreement tidy. It is to make it clear enough that the right conversation can begin.
Imagine that Maya describes the situation to a colleague in three different ways:
- “Daniel is difficult.”
- “Daniel and I disagree about releasing the guide on Friday.”
- “We need to decide whether the remaining review can be completed before Friday or whether the release plan needs to change.”
Each description points her toward a different conversation. The first invites a discussion about Daniel’s character. The second identifies a difference in position but leaves the practical question open. The third gives the disagreement a shape: there is work to assess and a release plan to decide.
The third description is not necessarily the whole story. Daniel may believe the review process itself is inadequate, even if the immediate deadline can be met. Maya may be concerned that repeated delays have damaged trust with the support team. Those concerns matter too. The point is not to choose the neatest description and stop thinking. It is to begin with a description that can be examined and corrected.
A useful working description usually does three things:
1. Names the subject without assigning a motive.
2. Identifies the difference that needs attention.
3. Points toward a decision, clarification, or next step.
For example:
> “We have different views about whether the guide is ready to release. We need to understand what remains to be checked and decide how to proceed.”
That statement does not require Maya to give up her preference for Friday. It also does not require her to accept Daniel’s assessment. It makes room for both people to explain what they know.
Contrast it with “Daniel always holds things up.” Even if Maya can recall other delays, the sentence turns a specific issue into a broad judgment. Daniel is likely to respond to the accusation rather than help examine the guide. A more useful conversation would allow Maya to raise a pattern with examples if the pattern is relevant, while still identifying what needs attention now.
A position is what someone says they want: “Release it Friday,” “Wait for another review,” “Use my proposal,” or “Do not change the schedule.” Positions are important because they tell you where people currently stand. They do not always explain why they stand there.
Behind a position, you may find:
- A concern: What could go wrong, or what might be lost?
- A priority: What is the person trying to protect or accomplish?
- A constraint: What limit affects the available choices?
- An uncertainty: What does the person need to know before moving forward?
Maya’s position is to release the guide Friday. Her priority may be getting useful material to the support team. A constraint may be that support staff have already planned training around the guide. Daniel’s position is to wait for another review. His concern may be that an incorrect instruction will create extra work for customers and staff. His uncertainty may be whether the latest product changes are reflected in the document.
These are possibilities, not conclusions Maya can make on Daniel’s behalf. She needs to ask him. The distinction matters because an assumption that sounds sympathetic can still be wrong. Perhaps Daniel has already finished his review and is waiting for input from someone else. Perhaps Maya’s main concern is not the support team but a commitment made to a customer. A…