Mark had a reputation in every meeting he sat in: he never lost an argument.
As VP of Product at a fast-growing logistics platform, he’d built that reputation the honest way — sharper prep than anyone else in the room, data ready before the objection even landed, and a calm, almost surgical way of dismantling a weak proposal without raising his voice. Colleagues joked that disagreeing with Mark was “a great way to learn something.” His director called him the most persuasive person on the leadership team.
So it made no sense that his department was quietly falling apart.
Two of his best engineers had requested transfers within the same month, both citing vague reasons on their exit paperwork — “wanted a change of scope” — that didn’t match what Mark knew about their career goals. His weekly leads meeting, once lively, had gone strangely flat: people agreed with him quickly now, sometimes suspiciously quickly, and initiatives that got unanimous nods in the room somehow stalled the moment everyone went back to their desks. And the same disagreement — a recurring standoff between his product team and the engineering lead, Priya, over release timelines — had now resurfaced for the fourth quarter in a row, despite Mark “winning” the argument, thoroughly and logically, every single time.
That was the part that genuinely puzzled him. He wasn’t losing these conflicts. He was winning them decisively, with better data and cleaner logic, every time they came up. So why did the exact same fight keep coming back, like the resolution had never actually happened at all?
By the time Mark reached out to a mentor at Acumentor, he wasn’t asking how to win more arguments. He’d started to suspect, uneasily, that winning was somehow the problem — he just couldn’t see how.
The Mistake Almost Everyone Makes About Conflict
Mark’s confusion is one of the most common blind spots in leadership, and it starts with a quiet, almost invisible assumption most people never examine: that conflict is something to be won.
Someone is right, someone is wrong. Someone prevails, someone concedes. The goal, when disagreement shows up, is to come out ahead — or at minimum, to not be the one who gets hurt by it.
That model isn’t just emotionally exhausting. It’s factually wrong about what most conflicts actually are. The majority of workplace and relationship disputes — over how a project should run, whose priorities matter more, how resources get allocated — aren’t fundamentally about right and wrong. They’re about competing needs, different values, and unspoken fears that haven’t yet been made explicit.
When a conflict is approached as something to win, the wrong problem gets solved. The question becomes how do I prevail here? when the far more useful question is what does each of us actually need, and is there a path that gets us both there?
That second question is the entire foundation of a win-win mindset — and it’s the piece Mark’s air-tight, logically unbeatable arguments had been skipping every single time.
Why “Winning” a Disagreement Rarely Ends It
Here’s what standard advice about conflict — listen more, stay calm, communicate clearly — tends to miss: most of it treats conflict as a communication problem, when it’s usually a needs problem wearing a communication problem’s clothes.
You can out-argue someone completely and still miss what they were actually upset about, because the words of a conflict are rarely its real cause. When Priya pushed back on release timelines for the fourth straight quarter, she wasn’t really contesting Mark’s math. She was defending something less discussable — her team’s sense that their capacity was never genuinely factored in, only argued around. Mark had been so focused on winning the position that he’d never once gotten near the interest underneath it.
This gap between what’s said and what’s meant is closely tied to a pattern worth naming honestly: a person can be entirely convinced they’re “just protective of high standards” while functioning, from everyone else’s seat, as someone whose conversations always somehow end up validating their own read of things — a dynamic explored in the quiet line between healthy self-assurance and self-centered leadership.
The Three Layers Beneath Every Disagreement
A genuine win-win outcome isn’t a compromise where both sides give something up — that model leaves everyone half-satisfied and the real tension fully intact. It’s a solution that addresses what both people actually need, even if it looks nothing like either person’s original proposal. Getting there means moving through layers most conflicts never reach.
Positions are what people say they want out loud — extend the deadline, hold the deadline, give my team the budget. Positions are easy to argue about and almost useless for understanding what’s actually going on. Two positions in direct opposition feel irreconcilable, because on the surface, they are.
Interests are what people actually need underneath the position — and interests are almost always more compatible than positions let on. The team wanting an extended deadline may need room to do quality work without burning out. The team defending the original date may need to protect a client relationship riding on it. Those aren’t opposed. They’re raw material for an actual solution — reachable only by asking what would that give you that you don’t have right now? instead of preparing the next rebuttal.
Fears sit deeper still — the worst-case scenario each person is quietly trying to avoid. A colleague who resists changing their process is often afraid that changing means admitting they’d been doing it wrong. A leader who pushes back hard on every proposal is sometimes protecting against being blamed for outcomes they don’t fully control. Reaching this layer takes real trust and a working level of emotional self-awareness — but in the conflicts that keep recurring, naming the fear underneath, even tentatively, can dissolve in minutes what logic alone never touched.
Mark, it turned out, had spent a year winning at Layer 1 while the real conflict was sitting untouched at Layer 2 — and every unanimous nod in his meetings was Layer 3 in disguise: people who’d learned that disagreeing with him cost more than it was worth.
How Leaders Actually Resolve Conflict at Each Layer
Knowing the three layers exist is the easy part. The skill that separates leaders who defuse recurring conflict from leaders who just keep winning the same argument is knowing what to do differently at each one.
At the position layer, the job is to stop arguing it and start translating it. A position is a demand, and demands invite counter-demands — which is exactly how Mark’s quarterly standoff with Priya kept looping. The move here isn’t to concede the position or to out-argue it more skillfully. It’s to treat it as a clue rather than a claim, and ask a genuine question before responding to it at all: “Help me understand what’s driving this ask.” A leader who responds to a position with a counter-position is negotiating. A leader who responds to a position with a question is actually resolving something.
At the interest layer, the job is to make both sets of interests visible in the same conversation — at the same time. This is where most well-intentioned leaders still fall short: they get curious enough to uncover the other person’s interest, but stop there instead of naming their own interest just as openly, which quietly turns “understanding” into one-sided interrogation. Resolution at this layer looks like a leader saying, plainly, “Here’s what I actually need, and here’s what I’m hearing you need — let’s see what solves for both,” and then genuinely building the solution from that shared starting point rather than defaulting back to whichever position sounded more reasonable. This is the layer where Mark and Priya’s phased release structure was actually built — not proposed by either of them beforehand, but assembled once both interests were finally on the table together.
At the fear layer, the job is to name it without weaponizing it. Fears are rarely spoken directly, and a leader who spots one has real power in that moment — power that can be used to reassure or, just as easily, to exploit. Resolving at this layer means naming the fear gently and as a hypothesis, not a diagnosis: “I wonder if part of this is a worry about how it’ll look if the timeline slips — is that fair to say?” — and then addressing it directly rather than letting it keep operating underground, disguised as a disagreement about something else entirely. A fear that’s been named accurately and met with reassurance rather than judgment tends to stop driving the conflict almost immediately, which is precisely what let Mark and Priya’s standoff finally stay resolved instead of resurfacing a fifth time.
The pattern across all three: resolution moves in the opposite direction of instinct. The instinct is to meet a position with a better position, meet an interest with your own case for why yours matters more, and leave a fear unspoken because naming it feels risky. Leaders who actually end recurring conflict do the reverse at every layer — question the position, share the interest, and name the fear out loud.
When It’s Personal: Conflict in Relationships
Relationship conflict — with a partner, a parent, a close friend — carries a different charge than workplace disagreement, because the stakes are never purely practical. An argument with someone you love is never just about the thing being argued. It’s also, always, about the safety and continuity of the relationship itself.
A few shifts change how these conflicts unfold. Naming the relationship as the real subject — I know this feels heated, and I want you to know I’m not going anywhere, I want us to actually solve this — often changes the emotional register before the substance is even addressed. Repair matters more than resolution: research consistently shows that couples who fight but reliably reconnect afterward are in far better shape than couples who avoid conflict by quietly suppressing it. And understanding has to come before problem-solving — the instinct to jump straight to solutions, however well-intentioned, is usually experienced as not being heard at all, which is part of what makes genuinely meaningful relationships so much harder to sustain than they look on paper.
When It’s Professional: Conflict at Work
Workplace conflict adds power differentials, organizational stakes, and a cultural norm in most companies that treats visible disagreement as a sign of dysfunction — which pushes it underground instead of resolving it. The result is familiar to almost anyone who’s worked on a team: polite surface agreement masking real disagreement, decisions made through side conversations instead of the actual room, and resentment that quietly accumulates until it surfaces as disengagement or turnover.
Separating the person from the position is the first discipline — the colleague whose proposal seems wrong will still be your colleague tomorrow. Making the real, often unspoken interests explicit and treating them as legitimate — it sounds like there’s a concern about how this affects your team’s workload; is that part of what we need to address? — is often the move that breaks a stuck professional conflict open, a skill that becomes essential for anyone trying to navigate office politics without losing themselves in the process. And establishing shared stakes — naming, out loud, that both people are actually invested in the same underlying outcome — creates a fundamentally different starting point than two competing proposals ever can.
The Emotional Skills Underneath the Strategy
None of the framework above works without a few underlying capacities.
Self-awareness under pressure is the baseline: noticing the defensiveness or fear you’re bringing into a conversation, before it quietly shapes everything you say. Feedback received without a defensive reflex depends on this same muscle — the ability to hear something uncomfortable as information rather than as a verdict on your worth. Emotional regulation matters just as much: staying activated enough to engage honestly, calm enough to think clearly, and knowing when to call a genuine pause rather than push a conversation past the point either person can actually process it. And underneath all of it is a harder requirement — real curiosity about the other person’s experience, and a genuine willingness to discover that your own position was partly, or even substantially, wrong.
That last one is the piece that unravels most “undefeated” arguers. Being right in the room and being effective in the relationship turned out, for Mark, to be two entirely different achievements.
What Actually Changed for Mark
The Acumentor mentor Mark worked with didn’t spend the first session talking about release schedules. She asked him to walk through his last four disagreements with Priya — not what was said, but what he’d been trying to protect each time he built his case.
It took him longer than he expected to answer honestly. He wasn’t defending the release date. He was defending a story about himself: that he was the person in the room who thought most clearly under pressure, and that losing an argument, even once, would mean he wasn’t.
The framework itself was almost simple once that was named. Before the next conflict came up, Mark got clear on his real interest — not “hold the deadline” but “protect the client relationship it was tied to.” Instead of opening with his case, he asked Priya to lay out hers first. He listened for what her position was actually protecting, and asked, plainly, what she was most worried about if the timeline didn’t move. It was the first time in four quarters either of them had asked that question out loud.
What came out of that conversation wasn’t a compromise where both sides lost a little. It was a phased release structure neither of them had proposed on their own — one that protected the client date on the pieces that mattered most and gave engineering real breathing room on the rest. Priya’s team hit the date. Nobody burned out doing it. And the standoff that had resurfaced every quarter for a year didn’t come back a fifth time.
The two engineers who’d requested transfers stayed, once they saw the shift ripple through how leads meetings actually ran. One of them said, months later, almost offhand, that meetings had started to feel like people were actually building something together instead of waiting to see who’d win.
Mark hadn’t lost his edge. He’d just stopped mistaking winning the argument for solving the problem — and discovered, a little late, that the second one was the only version anyone else in the room had ever wanted.
A Practical Starting Point
The shift starts small, and it starts before the next hard conversation, not during it: get honestly clear on your own interest, not just your position — ask yourself what it would actually cost you if the other person got everything they’re asking for, and let that answer show you what you’re really protecting. Then, in the conversation itself, ask before you argue. Every time the urge to prepare a rebuttal shows up, try asking instead: what does this tell me about what they actually need?
It is, in the end, a fairly small pivot — from how do I win this to what do we both actually need, and is there a path that gets us both there. But it’s the pivot that decides whether a disagreement resolves once, or keeps quietly coming back dressed as something new.
If a version of this pattern sounds familiar in your own leadership or relationships, Acumentor’s free Success Path Assessment maps where conflict, communication, and self-image are quietly working against each other — and builds a personalised path to change it