Directory · E
Not sure this is the right entry? Run the check · New here? Start with the premise
Expectations
1 min read · 312 words
Your mind builds a predicted version of everything coming up, then runs it as though it were a confirmed itinerary rather than a guess. Most disappointment is the gap between that model and what actually arrived.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Expectations are the mind’s pre-built models of what will happen, running as though they were confirmed itinerary.
The software builds these automatically. Every upcoming event, interaction, and experience gets a predicted version generated in advance. The mind models the meeting, the conversation, the vacation, the outcome — and then treats the model as a preview rather than a guess. What arrives in the control room is not this might happen. It is this is what’s going to happen.
The Disappointment entry covers what occurs when reality doesn’t match the model. The Anticipation entry covers the chemistry the model produces before the event. This entry covers the model itself and why it distorts experience.
The fundamental problem: expectations set the reference point against which actual experience is measured. An event that would have been experienced as good, measured against neutral, is experienced as disappointing when measured against an expectation that was better. The same event, measured against an expectation that was worse, is experienced as a pleasant surprise. The experience hasn’t changed. The reference point has.
This means the mind’s modeling process is actively shaping the emotional response to events before the events occur. The system that builds elaborate, optimistic models produces more disappointment — not because reality is worse, but because the model set the bar above what reality could deliver.
To work with expectations: notice them forming and hold them as guesses rather than previews. The model is the mind’s projection, built from available data, filtered through the same biases and patterns described in the Beliefs entry. What arrives will differ. Holding the model lightly — this is what the simulator is producing, not what the future has confirmed — reduces the gap between the model and the arrival and allows the actual experience to register on its own terms.
Modelled as a preview, not as a guess
Every upcoming event, interaction and experience gets a predicted version generated in advance. The meeting, the conversation, the holiday, the outcome — each modelled automatically. The problem is the labelling: what arrives isn't this might happen, it's this is what's going to happen.
So the model gets treated as a preview, and reality gets measured against it. Something can go genuinely well and register as a disappointment simply because it went differently from the rendering — which is a comparison against something that never existed.
The expectations that cause most trouble are the ones you don't know you have. An unexamined model still runs, still sets the comparison, and only becomes visible at the moment it's violated — at which point it presents as the other person having failed rather than as your prediction having been specific.
It also distorts the experience while it's happening. Attention goes to checking the event against the model rather than to the event, which is why anticipated occasions so often feel oddly unattended — you were present and busy auditing.
Make the model visible before the event
An expectation you can see is one you can hold loosely. An invisible one just becomes a disappointment.
Real questions
Should I just lower my expectations?
That's the usual advice and it's slightly wrong. The issue isn't that the predictions are too high — it's that they're being held as confirmed rather than as guesses, and that they're frequently invisible. A specific accurate expectation held loosely causes no trouble. A vague one held as a requirement causes a great deal, regardless of how modest it was.
Why was I disappointed by something that went well?
Because you were measuring against a rendering rather than against nothing. The event can be objectively good and still differ from the model, and the comparison is what produces the flatness. It's why anticipated occasions so reliably underperform — the more detailed the prediction, the more ways reality has to diverge from it.
How do expectations affect the experience itself?
They redirect attention. Instead of attending to what's happening, a portion of you is auditing it against the model — which is why a long-anticipated event can feel oddly unattended even while it's going fine. You were present and busy checking. Dropping the audit is most of what people mean by being present at something.
Why do I only notice an expectation when it's broken?
Because an unviolated model runs invisibly — it does its work without ever needing to surface. Which means the first time you learn what you were expecting is the moment it fails, and at that point it presents as the other person having let you down rather than as your prediction having been unusually specific.
What's the difference between an expectation and a standard?
A standard is something you've decided and can state, and it's usually about behaviour you'd be willing to ask for. An expectation is a prediction that got promoted to a requirement without being examined or communicated. The practical test: have you ever said it out loud? If not, holding someone to it is holding them to something they had no access to.
Is it wrong to expect things from people?
Not at all — relationships require it, and expecting nothing isn't maturity. What causes damage is expecting things that were never stated, which produces a situation where someone fails a test they didn't know existed. The fix is usually conversion rather than reduction: turn the unspoken expectation into a stated request and the whole thing becomes answerable.