Reviewed: 9 October 2026
A useful conflict resolution technique makes a disagreement easier to describe, investigate and decide. It does not require you to guess another person's motives or promise that every conversation will end in agreement. For a routine work disagreement, start with the task, identify the different interpretations, and establish who can decide the next step.
This guide works through an original fictional disagreement about a document. It covers preparation, listening, options, a decision and follow-up. The conversation is a teaching example, not a verified employee outcome or an employer policy. The method concerns ordinary task coordination; it does not replace an organisation's procedures for serious misconduct or safety concerns.
Separate the observation from the interpretation
An observation describes something you can check: a message, document version, agreed deadline or specific action. An interpretation explains what you think it means. Confusing the two can turn a manageable document problem into a debate about someone's character.
Consider these statements:
- Observation: “The brief says ‘a short comparison of both options.’ The draft I received describes only Option A.”
- Interpretation: “You ignored the brief because you do not respect my work.”
The observation identifies an issue to resolve. The interpretation adds a motive for which the speaker has no evidence. You can explain a practical effect without adding that motive: “I cannot complete the comparison section until we agree whether Option B belongs in this version.”
Before a conversation, note what you know, what you need to ask and what decision is yours to make. If you only review a document, do not assume you can change its scope or its deadline. Keeping those boundaries clear can prevent a second disagreement about authority.
The complete document disagreement
Fictional facts: Priya is preparing a two-page comparison of two packaging options for an internal review. Dev is reviewing the draft. Their task owner, Leela, wrote: “Prepare a short comparison of both options, with a recommendation. Send the review version on Friday.” No word limit or required comparison fields were specified.
Priya's draft contains a detailed description of Option A and a recommendation for A. It names Option B but does not compare its delivery time or minimum order. Dev returns a comment: “This is incomplete. Please rewrite before I review.” Priya replies: “I followed the request for a short document.” Neither message settles what the comparison must contain.
The problem is not yet proof that either person is unwilling to cooperate. Priya interpreted “short” as permission to concentrate on the recommended option. Dev interpreted “comparison” as requiring the same fields for both. They need to clarify that requirement and discuss a workable revision.
Prepare before speaking
Dev collects the original brief and the current draft. He identifies the two missing comparison fields and writes a limited request: agree on the fields needed for a reviewable comparison. He also recognises that his first comment named no specific gap.
Priya notes that the existing draft already fits two pages. Her concern is that adding more material may push it beyond the length she understood. She can propose a shorter table, but she cannot unilaterally remove the recommendation or move Friday's submission.
Neither person prepares a list of the other's past faults. That would broaden the conversation beyond the document they need to finish.
Open with a specific issue and acknowledge your part
Dev: “My comment said ‘incomplete’ without explaining the gap. That was too vague. I was looking for delivery time and minimum order for both options. The draft has those details for A but not B. Can we compare how we understood the brief?”
Priya: “I read ‘short’ as keeping the detail around the option I recommended. I was worried that a full description of both would exceed two pages.”
Dev: “So your concern is the length, and you expected the recommendation to drive the detail. Is that right?”
Priya: “Yes. I can add B's details, but I would need to shorten the A description.”
The paraphrase checks Dev's understanding. It is not a declaration that Priya's interpretation is the final requirement. Priya's confirmation also does not approve a revised deadline. They have clarified the disagreement, which is progress, but a decision remains.
Offer options with their consequences
They identify two possible revisions:
| Option | What changes | What remains uncertain |
|---|---|---|
| A | A compact table compares delivery time and minimum order for both; the recommendation follows it | Whether Leela accepts a table instead of two narrative descriptions |
| B | Two shorter narrative descriptions cover those same fields, followed by the recommendation | Whether the shortened descriptions provide enough detail within two pages |
Both options preserve a comparison and a recommendation. Neither silently removes part of the brief. Priya prefers the table because she can keep the two-page format. Dev can review either structure once the same fields are present for both options.
They ask Leela: “We interpreted the level of comparison differently. Would a table of delivery time and minimum order for both options, followed by the recommendation, meet the brief? We propose keeping the two-page review version and Friday submission.”
This request states the proposed scope and existing deadline. It does not present the team's preference as an already approved instruction.
Record an explicit decision
In this fictional case, Leela replies: “Use the table. Include both fields for both options and keep the recommendation. Friday remains the review deadline.” Priya revises the draft accordingly. Dev checks that each option now has delivery time and minimum order, then sends his review comments.
A follow-up message can be short: “The revised draft now has the agreed comparison table and recommendation. Dev's review comments are attached. Friday's review deadline is unchanged.” This records a completed revision and review. It does not claim that the document has been approved for purchasing or that a supplier has been selected.
What if the decision owner does not reply?
Change one case fact: Leela is unavailable and has not delegated the scope decision. Priya and Dev may prepare the proposed table if that fits their normal authority, but they should label it as a proposal. They cannot describe the disputed scope as approved merely because they prefer it.
A useful status message is: “We have a proposed table covering both fields for both options. Scope confirmation is pending from Leela. The draft is ready for that decision; Friday remains the recorded review deadline.” If the unresolved decision threatens the deadline, communicate that dependency through the team's normal process. Do not promise a new date on someone else's behalf.
This variation matters because listening and agreement are different states. People can understand one another and still need a decision from someone else.
Choose the technique that fits the problem
For an unclear requirement, ask a precise question and show the competing interpretations. For an error in your own message, acknowledge it and replace it with specific information. For competing constraints, set out options with their trade-offs. For a decision outside your authority, identify the owner and record what remains pending.
A pause can help when you cannot discuss the task usefully at that moment. Explain when and how you propose returning to it, rather than treating a pause as resolution. An apology for a vague comment can improve the opening, but it does not fill the missing comparison fields. A compromise that drops a required field may create a worse document even if it ends the argument quickly.
Practise without memorising the dialogue
Rewrite Dev's opening for a different routine problem: a spreadsheet contains the requested totals, but the units are missing. Your opening should identify the missing information, describe why it prevents review and ask how the other person understood the requirement. Avoid “always,” “never” and a claim about their intentions.
Then write two feasible options. Check whether each preserves the actual task. Name who can approve a changed requirement. Finally, draft a follow-up for both an approved option and a pending decision. If those messages read identically, you have probably hidden the unresolved part.
Questions people ask
Should I agree just to end the disagreement?
Check whether the proposed agreement meets the requirement and lies within your authority. Ending a conversation does not justify recording a decision that nobody authorised. You can state a point of agreement while clearly recording the remaining issue.
What if I made the first mistake?
Acknowledge the specific mistake and its effect. In this case, Dev's vague feedback is his responsibility even though the document still needs clarification. Owning that mistake does not require him to pretend the missing comparison is complete.
Does this guarantee a better working relationship?
No. It creates a clearer record of the issue, the options and the next action. Another person may disagree, new facts may emerge, or the task may need a formal decision. Evaluate whether the work and its status are clearer rather than assuming a guaranteed relationship outcome.
Sources and related practice
The UN Ombudsman guidance on difficult conversations discusses preparing for a conversation, listening and exploring the other person's perspective. Its institutional setting does not establish a universal workplace policy. The document example and dialogue above are original teaching material.
For interview practice, connect a truthful example to behavioural interview answers. For a broader introduction, use tell me about yourself sample answers. Describe what you actually did and whether the disagreement was resolved; do not turn a pending decision into a successful outcome.