Arguing the case for a feeling

What this means

Of the three beliefs, the one about being understood came out strongest in your answers. You do not only expect a feeling to be inconvenient. You expect it to be misread, dismissed or argued with. So when you finally raise something, you bring a case: the background, the three earlier times, the reasons any reasonable person would feel the same. The feeling itself is one sentence. The defense of it takes ten minutes.

This makes sense from the inside. If you spent years with people who answered "I'm hurt" with "you're overreacting," you learn that a feeling needs a lawyer. The trouble is how it sounds from the other chair. A partner who hears a long, well-argued explanation does not hear "I'm hurt." They hear an accusation with exhibits, and they respond the way people respond to accusations, by defending themselves. Which you then read as proof that they do not understand.

The loop it creates

That is the mechanism worth seeing clearly. The expectation of not being understood produces a way of speaking that makes understanding harder. Your partner argues with the case, because the case is what you gave them. You repeat the point, because it has not landed. They get more defensive. The conversation ends with both of you feeling misread, and the schema has one more piece of evidence.

Check your answers. If the high ones were explaining at length, repeating the same point, or taking feelings to a friend because your partner would not get it, this is your pattern. The last one matters most. Going elsewhere meets the need for the evening and quietly removes your partner from the part of your life where they could prove the schema wrong.

What to do next

Lead with the feeling, alone. One sentence, then a pause. "I felt shut out last night." No history, no justification. If they ask why, answer. If they do not, let the silence do some work before you fill it.

Ask for the response you want. "I don't need you to agree, I need you to know" is a fair request, and many partners will meet it once they know that is the request. Without it, most people default to problem-solving or defending, which feels like not being understood even when they understood fine.

Count the times you were understood. It sounds trivial and is not. People with this pattern tend to file every time they were misread and forget the times they were not. A rough tally for a month gives the schema something new to update on.

If you want to rehearse the short version first, Lovon can help with that.