Facts, Feelings, and Assumptions: How to Break Down an Argument
Updated: 1 September 2026
You said one thing. They heard another. Ten minutes later you're not even arguing about the original problem anymore — you're arguing about who said what, who meant what, and who started it.
Almost every stuck argument has the same hidden cause: the two of you are mixing together three completely different things and treating all of them as if they were facts. Separate them, and most fights become solvable.
The three layers of any argument
Every conflict is built from three layers stacked on top of each other. They feel like one thing in the heat of the moment, but they behave very differently.
1. Events — what actually happened. Observable, recordable. "You came home at 9. I asked about dinner. You didn't answer and went to your room." A camera would agree with all of it.
2. Feelings — what you experienced. "I felt ignored. I was anxious all evening." Nobody can tell you these are wrong. They're yours.
3. Assumptions — the meaning you added. "You don't care. You did it on purpose. You always do this." This is the layer that causes the damage — because it feels exactly like a fact, but it isn't one.
The problem is layer three wearing the costume of layer one.
Why assumptions are so dangerous
"He was being spiteful" sounds like a report of something that happened. But it isn't. What happened was an action — he left the room. "Spiteful" is a conclusion you drew about his intentions, and you can't actually see intentions. You inferred them.
When you state an assumption as a fact, two things go wrong at once:
- The other person hears an accusation about their character, not a description of an event — so they defend themselves instead of listening.
- The real event never gets discussed, because you've both moved on to fighting about the interpretation.
This is why "you always" and "you never" escalate so fast. They aren't facts. They're assumptions dressed up as evidence.
Try it: break down your last argument
Take a fight you had recently and sort it into the three layers. Write it out — literally three columns.
- Events. Only what a camera would have caught. No "why," no "because." Just actions and words.
- Feelings. What you felt, in the first person. "I felt…" — not "you made me feel," which is already an assumption about cause.
- Assumptions. Everything left over: the motives, the "always," the "on purpose," the story you told yourself about what it meant.
Two things usually happen. First, the Events column turns out to be short and surprisingly uncontroversial — you both actually agree on most of it. Second, almost everything that hurt is sitting in the Assumptions column, unverified.
That's the whole game. The Assumptions column is a list of things you guessed — and most of them you can simply ask about instead.
What you can dispute — and what you can't
Once the layers are separated, a clean rule falls out:
- Events can be disputed. "That's not what happened — I did answer, I said 'in a minute.'" Good. Compare memories, agree on the record.
- Assumptions can be disputed. "I wasn't ignoring you — I had a migraine and couldn't talk." Even better. This is where most fights quietly dissolve.
- Feelings cannot be disputed. "I felt hurt" is not a claim about the world; it's a report about a person. There is nothing to argue. The only valid response is to hear it.
Most couples do this exactly backwards. They argue endlessly about feelings ("you shouldn't feel that way") and treat their assumptions as settled fact ("I know why you did it"). Flip it, and the temperature drops immediately.
From "he was angry" to "I thought he was angry"
The single most useful move is to rewrite your assumptions as what they actually are — your own perception.
- "He did it to hurt me" → "I thought he was trying to hurt me."
- "She doesn't respect my time" → "When she was late, I felt like my time didn't matter."
- "You were ignoring me" → "You didn't answer, and I assumed you were ignoring me."
Nothing is lost. You still get to say the hard thing. But now it's owned — it's your experience and your guess, offered for checking, instead of a verdict handed down as fact. That one shift is the difference between a conversation and a fight.
Where Humen fits
Sorting an argument into layers is simple to understand and genuinely hard to do in the moment — especially when you're upset and the other person is right there.
That's the mechanic Humen is built around. Each of you describes your side separately, and the app pulls it apart into layers automatically: it flags when a sentence is really an assumption about the other person ("he was angry") and nudges you to ground it as your own perception ("I thought he was angry"). Only the events get negotiated into one shared record — your feelings are never up for debate, and neither of you argues the other out of what they felt.
The result isn't a winner. It's a version of the fight you can both recognize — which is the only place resolution ever starts.
Humen is not a substitute for professional help. If conflict in your relationship feels unsafe, reach out to a qualified professional.
Frequently asked
How do I tell a fact from an interpretation?+
A fact is something a camera would have recorded — an action or a word that was actually said. An interpretation is the meaning you added on top: why they did it, what it says about them, how they feel. If the statement is about someone's inner state ('he was being spiteful'), it's an interpretation, not a fact.
Can you argue about feelings?+
No — and you don't need to. A feeling is never wrong; it's simply what someone experienced. You can question a fact ('that's not what I said') and you can question an assumption ('I wasn't ignoring you on purpose'), but 'I felt hurt' is not up for debate. Trying to argue someone out of a feeling is what turns a conversation back into a fight.
Why do we remember the same argument differently?+
Because you each stored a different mix of facts, feelings, and assumptions. Memory keeps the emotional headline and quietly fills the gaps with interpretation. That's normal — it's why writing down just the observable events, separately, before you compare, resolves so many 'that's not what happened' deadlocks.