Why conflict resolution comes down to five moments
Every guide to conflict resolution skills gives you the same six nouns: active listening, empathy, emotional regulation, problem-solving, compromise, patience. They are all true and none of them tells you what to do on Tuesday at two o'clock when the design lead walks into your office already angry.
So here is Tuesday. You run the engineering team. Jonas runs the design team, and the two of you report to the same product director. A release shipped a week late. Your engineers say design delivered the final screens late. Jonas says your engineers changed the spec twice and never told him the date was fixed. The product director wants to know by Friday whose fault it was, and the next release, which you and Jonas have to build together, starts Monday.
Sit in on enough of these conversations, feedback to a report, pushing back on your boss, a dispute with a supplier, an angry customer, bad news to a client, and a pattern shows up. Different rooms, different stakes, and the same five moments in the same order, each with its own skill and its own way of going wrong. Styles frameworks like Thomas-Kilmann describe which way you lean under pressure. The five moments describe what you actually do, and that is the part you can change.
Moment 1: Prepare before you speak
Going wrong. You walk in with the grievance. "Design was a week late, again, and I'm the one explaining it to the director." You have not decided what you need from this conversation, what you would accept, or what you would do if Jonas simply refuses. So whatever he says, you react to it.
Going right. Before the meeting you write three lines.
- What you need. A handoff date for the next release that both teams have agreed to.
- What you would accept. A date with conditions attached, if the conditions are real.
- What you know, against what you assume. You know the screens arrived on the 17th. You assume Jonas knew the 10th was the date, and you have never actually checked.
Then the oldest advice in the field, from Fisher and Ury's Getting to Yes, whose four principles Harvard's Program on Negotiation still teaches in the same order: separate the people from the problem. The problem is that two teams shipped against a date neither had agreed to. The problem is not Jonas. That sentence, held in your head, is what keeps the next twenty minutes from becoming a trial.
Two things in that preparation do most of the work:
- The walk-away. What you will do if this conversation produces nothing. Without one, you will accept whatever ends the discomfort fastest.
- The record. The dates and facts you can point to. A claim with a date in it is a problem to solve. A claim without one is a grievance to argue about.
Preparation is the skill nobody lists, because it happens before anyone is watching.
Moment 2: State the problem in the first minute
Going wrong. "Thanks for making time. I know the last few weeks have been hectic for everyone, and I really do value how the two teams work together, so I wanted to just, you know, check in on how the release felt from your side." Five minutes later Jonas still does not know why he is in the room, and when the point finally arrives it arrives as an accusation, because you have spent the preamble getting more nervous.
Going right. "We shipped a week late, and I think the cause is that we never agreed a handoff date. I'd like to fix that before Monday." Behaviour and impact, in two sentences, with the purpose attached. No character judgment, no softening, and the door is open.
The other person decides in the first minute whether this is an attack, and the preamble is what tells them it is one. People read a long run-up as a sign that something bad is coming, so by the time the message lands they are already defending. Two habits fix it:
- Say what happened and what it caused, not what kind of person they are. "The screens arrived on the 17th and we slipped a week" rather than "design is always late."
- Say why you are raising it, in the same breath, so the message arrives with a purpose attached instead of hanging in the air as a complaint.
It is the same whether the person across the table is your report, your boss, or a client waiting for bad news. The first minute is for the message, not for your comfort.
Moment 3: Stay calm when it gets heated
Jonas, thirty seconds in: "Your team changed the spec twice. Nobody told me the tenth was fixed. Don't put this on design."
Going wrong, two ways.
- You match it: "Twice, because the first screens were unusable." Now it is a trial after all.
- You retreat: "You're right, sorry, forget I raised it." Now the problem is still there, and you have taught him that heat makes you fold.
Going right. Acknowledge what is true without conceding the point. "That's fair. We changed it twice, and that cost you time. The thing I still want to solve is the date, because neither of us had one." You gave him the thing that was true, and you returned to the message.
Composure here is not a calm face. It is three specific things you do not do:
- Match the volume. Louder does not make you more right, and it tells him the message was personal after all.
- Over-explain to fill the silence. The more reasons you stack up, the more it sounds like a defence.
- Follow them into the side argument. Jonas has just offered you one, the spec changes. It is a real subject, but it is not today's subject. Acknowledge it in one sentence and go back to the date.
If the heat comes from a customer rather than a colleague, the same move applies with one addition: name the specific thing that went wrong for them before you explain anything, because an explanation offered before the acknowledgement sounds like an excuse.
Notice that conceding the true thing is not the failure. Admitting the spec changed twice gives away nothing and drops the temperature faster than any technique. The failure is conceding the point, which was the date, because the heat made you want the conversation to end.
This is the moment worth rehearsing, because nobody knows how they react to heat until they are in it. Run the feedback or the pushback scenario in a live roleplay and the counterpart deflects, blames, and raises the temperature on you. Afterwards you see whether you matched it, folded, or returned to the message, with your own lines quoted. The first minutes are free, no card required.
Moment 4: Move from positions to options
Here is where most conflicts stall. Two positions are on the table:
- Yours. Design must deliver by the tenth.
- His. Engineering must stop changing the spec.
Each is a demand the other person can only accept or refuse, and both of you have already refused.
Going wrong. You haggle the position. "Could you do the twelfth?" "Could you freeze the spec by the first?" Someone gives up, and you both leave with a date one of you does not believe in.
Going right. You ask the question that gets underneath the position. "What would you need from us to be able to commit to a date?" Jonas's answer is the interest behind his demand: he cannot design against a target that moves, so he needs the spec frozen a week before he delivers. Yours is predictability: you need a date you can plan the sprint around. Now there are options instead of positions:
| Option | What design gets | What engineering gets |
|---|---|---|
| Spec freeze on the 3rd, handoff on the 10th | A target that stops moving | The date |
| Two-stage handoff: rough screens on the 6th, final on the 10th | Room to iterate after the freeze | Something to build against earlier |
| Shared review on the 5th where either side can call a slip | A way to flag trouble without blame | No surprises on the 10th |
You trade: the freeze for the date.
This is the second half of Getting to Yes: focus on interests rather than positions, and invent options for mutual gain. In practice it comes down to three habits:
- Ask what they need before you argue with what they want. The demand is usually a clumsy translation of something more reasonable.
- Put more than one option on the table. A single proposal can only be accepted or refused. Two or three invite a choice.
- Trade, do not donate. When you give something, get something for it. A series of one-way concessions teaches the other person that pressure works.
Moment 5: Agree the outcome and write it down
Going wrong. "Okay. Let's both try to do better on this one and keep talking." Everyone nods. Nothing has changed, and in six weeks you will have this conversation again with more history behind it.
Going right. "So: spec freeze on the third, handoff on the tenth, and if either one slips, the other person hears the same day. I'll put that in the release doc this afternoon and you tell me if I've got it wrong." Agreed, not announced. Specific. On paper by the end of the day.
This is the moment most conflicts fail, and they fail for a human reason: the hard part feels over, both of you are relieved, and nobody wants to risk the mood by pinning anything down. So the agreement stays vague, and vague agreements renegotiate themselves the moment they are tested. A close that holds has four parts:
- The terms, with numbers and dates in them.
- Agreement, meaning you asked and they said yes, rather than you announced and they did not object.
- A check-in, a date when you both look at whether it worked.
- A record, written the same day, in a place you both already read.
If you could not fully agree, write that down too: what you are committing to anyway and which concern stays on the table. Anything less is resolution theatre, and in six weeks you will be back in the room.

That is the whole skill set, and notice what is not on it: nothing about being calm by temperament or empathetic by nature. The six adjectives from the top of this post are all in there, but each one turns out to be a specific thing you do at a specific moment.
| The adjective | Where it actually happens | What it looks like |
|---|---|---|
| Patience | Moment 1 | Preparing before you speak instead of reacting |
| Emotional regulation | Moment 3 | Not matching the heat, not folding, back to the point |
| Active listening | Moment 3 | Repeating back the true thing he said before you move on |
| Empathy | Moment 4 | Asking what he needs, and using the answer |
| Problem-solving | Moment 4 | Three options on the table instead of one demand |
| Compromise | Moment 5 | A trade both of you can repeat back, written down |
Behaviours with a time and a place can be practised. Temperaments cannot.
How to answer the interview question about conflict
A large share of the people searching this phrase are preparing for the question "tell me about a time you had a conflict with a colleague," and the standard advice is to answer in STAR: situation, task, action, result. STAR produces a competent answer and an invisible one, because "action" becomes a list of the six adjectives. "I listened actively, stayed calm, and found a compromise."
Tell it in the five moments instead. Each beat shows a skill rather than naming one, and the interviewer hears a person who knows what they did.

Three things make this version land:
- Pick a conflict where you conceded something true. The heat beat is where interviewers learn the most, and it is the one most candidates skip.
- End on the written outcome and what happened after it, not on the feeling in the room.
- Avoid the story where the other person was simply wrong. It has no turn in it, and a conflict without a turn is a complaint.
If you want to hear how it sounds under questioning, the interview practice scenarios will ask the follow-ups a real interviewer asks, starting with "what would you do differently."
How to practise conflict resolution skills
The difficulty with conflict is that you cannot rehearse it with the person it is with. By the time you are in the room with Jonas, the first minute is happening. The roleplays Closemind runs are built for exactly that gap: a counterpart who deflects when you give feedback, pushes back when you push back, and raises their voice on the dispute call, so you meet all five moments before the real one. Afterwards you get feedback on each, with your own lines quoted at the moment they worked and the moment they did not.
Pick the conflict you have coming, the feedback, the pushback, the dispute, the angry customer, and run it before Tuesday at two.








