Knowledge Base › Relationships

Relationships

The unspoken expectation: being angry at someone for something you never asked for

11 min readUpdated: 7 September 2026
The unspoken expectation: being angry at someone for something you never asked for

There is someone you have been slightly angry with for weeks. Nothing dramatic happened, and you could not say precisely what is wrong — it is just somehow harder with them. If you were asked what they should have done differently, you would get stuck. This article is about the fact that in such cases it is almost always the same situation: you had an expectation you never said out loud — and could not have put into words yourself until it was broken.

Why you cannot see what is bothering you

The unspoken expectation is unspoken because most of it is not even conscious. You are not withholding it — you simply do not know it is there, right up until someone breaks it.

These typically come from the family pattern, from earlier relationships, or from an unspoken sense of “that is how it is done”: that you call on a birthday, that someone coming home late lets you know, that you check on a sick person the next day. To you this is not a rule but the default state of reality — which is why it never occurs to you that it would have to be asked for.

The other person, though, came from a different default. And this is where the typical double bind comes from: you feel betrayed, they feel unjustly accused — and you are both right inside your own system.

Two offset neon grids overlapping only partly — two different defaults
No rule was broken. Two different defaults met, and neither had been spoken.

Expectation and request — the difference that decides everything

It sounds simple, and yet it is the heart of this article. The two are not degrees of politeness but two different mechanisms.

  1. An expectation cannot be heard. The other person does not know about it, so they cannot meet it. When they fail to, that was not a choice on their part — yet you experience it as a choice, and that is why it hurts so much.
  2. A request can be refused. This is what makes it hard: a spoken request is a risk. While it stays an expectation it is fulfilled in your imagination; the moment it becomes a request, it may turn out you will not get it.
  3. That is why it stays unspoken. Not out of forgetfulness: the unspoken expectation PROTECTS you from refusal. In exchange it guarantees disappointment — because what you did not ask for you can only receive by accident.

From this follows the uncomfortable realisation too: if someone “doesn’t get it” for months, then there is a fair chance they really do not — not because they are not paying attention, but because it was never said.

A quick test

Take your most recent irritation and ask: if I had asked for this in so many words beforehand, could they have done it? If yes — then it was an expectation, not a broken rule. If you cannot decide, what you were expecting is not concrete enough yet.

How to work it back

Resentment can be worked back into an expectation, and the operation is surprisingly quick — it only works in writing, not in your head, because in your head the endpoint is always the other person’s fault.

  1. Write down what happened — at camera level. Not “I didn’t matter” but “on Thursday they didn’t call back”. That is the only fact in the story.
  2. Write down what you expected instead — in the present tense, as a concrete behaviour. “I expect them to call back that day.” This sentence is the expectation itself, and for most people this is where it lands that they never said it.
  3. Write down what it meant to you that it did not happen. “It meant I am not important.” That is the meaning — and that is the part that actually hurts, not the phone call.
  4. Look at the distance between the two. Between a missed call-back and “I am not important” there is a leap. Not necessarily a wrong one — but not a proven one either, and it is that leap you have been angry about.
Neon staircase with three steps and a gap before the last — the distance between fact, expectation and meaning
Between the fact and the meaning there is a leap. That is what you have been angry about — not what happened.

In short

  • Behind lasting resentment there is usually an unspoken expectation, not a broken rule.
  • Most expectations are not conscious until they are broken — you are not withholding it, you do not know about it.
  • An expectation cannot be heard; a request can be refused — which is why it stays unspoken.
  • Working it back happens in writing: fact → what I expected → what it meant.
  • From there three ways lead out: say it / let it go / renegotiate — and all three are fine.

The three ways

Once you have the expectation in one sentence, three honest continuations exist. The trouble usually comes not from which one you pick but from picking none — and staying in resentful waiting.

  1. Say it. Turn it into a request: “It would help if you called back that day when you can’t talk.” Concrete, future-tense, doable. It is not about the past — this does not resolve the old grievance, it only prevents the next fifty.
  2. Let it go. Some things, thought through, you do not even want to ask for: because they are small, because they are not owed by this person, or because you can give them to yourself. Letting go is real only if you stop keeping score — what you have “let go” but still collect, you have not let go.
  3. Renegotiate. Some things are not one request but a whole arrangement: how you split the work, how much separate time fits in. That is no longer one sentence but a difficult conversation — and its first sentence can be written in advance.
Neon three-way fork with three equal, finished branches
Say it, let it go, or renegotiate. The trouble comes from picking none of the three.

What not to do

Three reflexes come on their own, and all three prolong the anger.

A faint, unreadable pattern of neon signal lights — the request wrapped in hints
A sigh and a silence are not a request. At most it gets across that something is wrong — not what.

The measurement: one week, one line

If this is not about one specific situation but a general tension, a week will bring it out. The method is deliberately minimal, because nobody keeps a journal while irritated.

Next to every irritation, a single line: “what I expected”. Not analysis, not abuse of the other person — one sentence, present tense, as a concrete behaviour. If you cannot phrase it, that is an answer too: write “I don’t know”.

A week later, read it through. Two things tend to emerge, and both are useful. One is that five of the seven irritations trace back to the same single expectation — in which case you do not need seven conversations but one. The other is that you were not even angry at the person you thought.

Neon threads that start apart but converge on a single point
Five of seven irritations trace back to the same expectation. Then you do not need seven conversations.

Where the line is

Two things this method does not promise, and being dishonest here would backfire.

The first: saying it is no guarantee. Having phrased it and asked for it, you can still be refused — indeed, sometimes it is only after saying it that it becomes sharply clear that what you need you will not get in this relationship. That is painful, but it is not the method failing: that was the situation all along, you just did not know it.

The second: not every expectation is reasonable — and conversely, not every “excessive” expectation is excessive. Some things really are too much to ask of a colleague but entirely normal with a partner. That cannot be settled from a list. What can be settled is whether you said it at all.

And one line that is not about this: if, in a relationship, saying your expectations is regularly followed by being explained that you did not want what you said you wanted, that is not an expectation question. Our article on gaslighting is about that.

Where a system helps

The difficulty here is that the irritations are individually trivial — which is exactly why you say none of them — and only side by side does it show that the same single expectation sits behind all seven. A week later you no longer remember them, only the bad feeling.

That is why in Mirrify the daily entry carries a date and a mood: one line that day is enough, and at the end of the week you can look through them on one screen. The AI mentor works from the same material: it shows recurring patterns in your own words — for example that the same sentence came back five times, always in the same situation.

What it does not do: it does not decide whether your expectation is reasonable, and it does not tell you which of the three ways to take. You have to write the one line yourself — the system only helps you have something to put side by side on the seventh day.

The one sentence worth taking with you

If you take one thing from all of this, let it be this: what you did not ask for you can only receive by accident — and the disappointment you feel is not the other person’s fault but the price of an unspoken sentence.

And if you can only do one thing now: take your most recent irritation and write down, in one present-tense sentence, what you expected instead. Often that alone makes it smaller.

Frequently asked questions

What is an unspoken expectation?

A need the other person does not know about because it was never said — and one you often do not know about either until it is broken. It typically comes from the family pattern or an unspoken sense of “that is how it is done”, which is why it feels not like a rule but like the default state of reality. The other person, though, came from a different default.

Why am I angry at someone if I never asked them for anything?

Because you experience an unspoken expectation as a choice: it feels as if they could have known and still did not do it. In fact they did not choose, because they did not know. Hence the typical double bind: you feel betrayed, they feel unjustly accused — and you are both right inside your own system.

What is the difference between an expectation and a request?

An expectation cannot be heard, so it cannot be met. A request, on the other hand, can be refused — and that is exactly why it is hard to say: while it stays an expectation, it is fulfilled in your imagination. The unspoken expectation protects you from refusal, but in exchange it guarantees disappointment.

How do I work out what is actually bothering me?

In writing, in four steps. Write down what happened at camera level (“on Thursday they didn’t call back”); what you expected instead, in the present tense as a concrete behaviour (“I expect them to call back that day”); what it meant to you that it did not happen (“that I am not important”); and finally look at the leap between fact and meaning. That is what you have been angry about.

What should I do once I have the expectation?

There are three honest ways. Say it as a request — concrete, future-tense, doable. Let it go, if on reflection you do not even want to ask for it (but letting go is real only if you stop keeping score). Or renegotiate, if it is not one request but a whole arrangement — that is a difficult conversation. The trouble usually comes from picking none of the three.

What should I NOT do?

Don’t test the other person (“let’s see whether it occurs to them”) — someone who does not know about the exam is going to fail it. Don’t wrap it in signals: a sigh and a silence are not a request but a punishment. And don’t hold them to it retroactively: the expectation applies from now on, not backwards.

What if I say it and still don’t get it?

It happens, and it is not the method failing. Sometimes it is only after saying it that it becomes sharply clear that what you need you will not get in this relationship — but that was true all along, you just did not know it. Nor is every expectation reasonable: what is too much to ask of a colleague may be entirely normal with a partner. What can be settled is not the reasonableness but whether you said it at all.

Turn reading into practice

Mirrify brings your journal, habits, goals and an AI mentor that works from your own data into one place.

Try it free → 14-day free trial · cancel anytime