When Everyone Has a Different Version
Get clarity by sticking to what’s observable.
Have you ever needed to respond to an issue that landed on your desk, but the whole thing felt murky? Everyone has a different version, and you can’t tell what’s actually happening. You just know it’s starting to affect the work.
Conflict brings a lot of information at once. We fill in gaps and reach for familiar stories so it feels more manageable.
That’s normal. It’s also one of the easiest ways to accidentally make a conflict worse.
A steadier move is to stick to what’s observable: the behavior, its impact, and the existence of a pattern, rather than stories, labels, or personality explanations. One way to do that is to separate the person from the presenting problem.
What happens in conflict: We start framing without realizing
When tension rises, our brains start sorting:
Would I have done something similar?
Does this seem reasonable?
Who feels most like the victim?
Who seems like the bad actor?
These questions can feel useful. Sometimes they offer empathy or context. But they can also pull us into quick conclusions about the person or situation, before we’ve even clarified what the actual problem is.
Separate the person from the problem
Here’s a simple fork in the road. When we’re under stress, it’s easy to collapse the person and the problem into one.
That sounds like:
“They’re the problem.”
“They’re not cut out for this.”
“They don’t care.”
“They’re just like this.”
Those statements may reflect real frustration, but they do something predictable. They turn the conflict into an identity verdict. And once the person is the problem, things get polarizing fast. People choose sides. Motives get assumed. Solutions shrink.
A more workable move is to keep the problem separate from the person.
That sounds like:
“This behavior isn’t working.”
“This skill needs strengthening.”
“There’s a blind spot that needs awareness.”
“There’s a gap between intent and impact.”
Same situation. Different framing. And this framing leaves room for clarity, coaching, boundaries, and repair.
Focus on behavior, impact, pattern
If you want a practical way to gather information and assess what’s actually happening, use three anchors. They help you stay out of labels and stories, and they keep the conversation grounded in what you can act on.
Behavior
What specifically happened? What did they do or not do?
A good test is this: what would show up if it was recorded?
Behavior usually starts with a verb.
Impact
What effect is this having on people, relationships, goals, or trust?
Impact helps you name why it matters, and it’s often what others are reacting to.
Pattern
What’s the trajectory? Frequency, duration, and common threads.
How long has this been happening?
Is it increasing or decreasing?
What happens when feedback or limits are introduced?
When you focus on behavior, impact, and pattern, next steps become more obvious and more proportional.
A quick example: labels vs. observable data
Labels
“Rude.” “Dismissive.” “Condescending.”
Observable data
Behavior: Emails and conversations from a supervisor open with statements like:
“If you were listening in the training…”
“Like we outlined in the checklist…”
“This should be obvious…”
Impact: Staff feel embarrassed asking questions. They begin routing questions through other people to avoid these interactions.
Pattern: It happens by email and in person. It has increased since the supervisor became aware that staff were going elsewhere for help.
Notice what happens here: we didn’t need to diagnose the person. We clarified the problem. The goal isn’t to litigate tone. It is to name what’s happening clearly enough to respond proportionally.
A better filter than “good or bad”
In conflict, “Is this good or bad?” often generates more debate than clarity.
A more useful question is: Is this behavior effective?
Sometimes the issue isn’t that something is prohibited. It’s that it isn’t working. Not every problematic behavior violates a policy, rule, or law, but it can still create real costs for the team.
Effective for results.
Effective for the work.
Effective for the team.
Effective over time.
That question tends to lower defensiveness and increase effective problem-solving.
Go-to questions you can use immediately
If you’re helping someone sort through a conflict, or trying to sort through one yourself, these are simple and powerful:
Behavior: “Could you give me a couple of specific examples of what they said or did?”
Impact: “What impact do you think this is having on the people involved and on the broader team?”
Pattern: “How long has this been going on, and has it changed over time?”
Bottom Line
Once you can name what’s happening in observable terms, you can begin choosing an approach for responding.
Having a clear understanding of what behavior isn’t working gives you a strong starting point for how issues actually begin to resolve: an actionable feedback conversation, a clear limit or boundary on a specific behavior, or more clarity through explicit team norms and expectations around communication and coordination.