It's Not Your Expectations. It's Their Capacity.

I don't usually write content like this. Most of what I put out is self-focused — meant to help people examine their own relational capacities and grow them into the kind of relationships they actually want. But since a lot of my writing comes from social media posts I encounter and from my own life, there's something I want to address that has irked me for a while.

There's a phrase that gets weaponized in relationships — personal and professional — that I want us to look at more carefully:

"Your expectations are too much."

On the surface, it sounds reasonable. Maybe even wise. Like someone gently helping you recalibrate. But most of the time — whether I'm hearing it in mediation or in my own life — something else is happening underneath. The person saying it isn't naming a problem with your standards. They're avoiding a reckoning with their own capacity.

And that distinction matters.

Capability Is Not Capacity

Let's separate two things that often get collapsed. Capability is about what someone *can* do — the skills, the knowledge, the relational tools they possess. Capacity is about what someone is able or willing to bring to the table right now — given their bandwidth, their emotional availability, their priorities.

When someone has the capability to meet you but not the capacity, something honest needs to happen. They need to say: *I see what you're asking. I understand it. And I can't do that right now.* That's vulnerable. It costs something to admit.

But instead, what often happens is a redirect. Rather than naming the gap in their own capacity, they reframe the conversation around your expectations. Suddenly the issue isn't that they can't show up — it's that you shouldn't have asked them to.

The Real Move: Pathologizing the Ask

This is where the damage lives. When someone says "your expectations are too much," they're not just declining a request. They're reclassifying it. They're turning a reasonable need into evidence of a character flaw — you're too intense, too demanding, too needy.

And it works precisely because it's hard to argue against. Once your expectations are framed as the problem, defending them feels like proving their point. You push back, and now you're "doing it again." You're being too much — again.

This is a conflict pattern I see constantly. It functions as a kind of emotional sleight of hand. The person who can't meet the moment doesn't have to reckon with their limitation. Instead, they export the discomfort onto you. You end up managing their capacity gap *and* feeling bad for noticing it.

The Deeper Cut: Having Expectations at All

Sometimes it's not even "your expectations are too high." It's that having expectations *at all* is treated as the imposition.

This is the sharper version of the same dynamic. The ask itself — not the scale of it — becomes the problem. And this framing does something particularly corrosive: it teaches people that wanting something from someone is inherently unreasonable. That the safest relational posture is to need nothing, expect nothing, and be grateful for whatever shows up.

That's not a relationship. That's a hostage negotiation with your own needs.

And for people who've had to fight to be seen — in workplaces, in families, in institutions that weren't built with them in mind — this lands differently. When you've spent your life advocating for yourself because the alternative was being overlooked, being told your expectations are "too much" can feel like punishment for the very thing that kept you whole.

The Cousin: "Let's Just See Where It Goes"

There's a close relative of this phrase that I want to name, because it operates on the same logic but shows up wearing different clothes.

"Let's not put expectations on this. Let's just see where it goes."

You hear it early in relationships — romantic, professional, sometimes even familial. It sounds generous. Open-hearted. Like someone saying, *I'm not trying to box this in. I just want to be present.* But what it often means in practice is: *I want the benefits of this relationship without agreeing to any terms.*

This is the preemptive version of the same move. "Your expectations are too much" happens *after* you've asked for something. "Let's not have expectations" happens *before* — it sets the rules of engagement so that you can never reasonably ask for anything at all. It's a preemptive pardon for every future letdown, drafted and signed before anything has gone wrong.

And notice who this framing always benefits. It's never the person already showing up consistently who asks for no expectations. It's the person who wants connection without the cost of it. Access without obligation. Presence without reliability. The warmth of being chosen without the weight of choosing back.

I need to be personal here, because this one has irked me for years. I am someone who shows up with capacity. I do the work. I hold space. I follow through. And I've heard both versions — "let's not have expectations" and "your expectations are too much" — in some of the most important relationships in my life, including with my own parents.

When the person who was supposed to set the template for what showing up looks like — the person who gave you your first understanding of what love requires — is the same person telling you not to expect things, it doesn't just frustrate you. It disorients you. It makes you question whether your instinct to expect anything from anyone was flawed from the start. And then you carry that disorientation into every relationship after, second-guessing yourself every time you want to ask for something that should be simple.

Here's what I've learned, both personally and through this work:

"let's not have expectations" *is* an expectation.

It's asking you to expect nothing — which is the most demanding expectation of all. It requires you to override your own instincts, suppress your own needs, and perform a kind of emotional amnesia every time someone falls short.

You don't owe anyone that. Not a partner. Not a colleague. Not a parent.

What Honesty Actually Sounds Like

The alternative isn't complicated. It's just harder.

Honesty about capacity sounds like:

I hear you. What you're asking for makes sense. I don't have the bandwidth to give you that right now, and I want to be straight with you about it.

That's a statement about *them* — their limits, their reality. It doesn't require you to shrink, but it does require them to be vulnerable.

Contrast that with: *You expect too much.* That's a statement about *you*. It asks you to question whether what you needed was legitimate in the first place.

One invites repair. The other forecloses it.

In conflict work, I call this the difference between *owning your no* and *exporting your no.* When someone owns their no, they hold the weight of it. When they export it, you carry it — and you carry the shame of having asked.

A Framework for the Next Time It Happens

If you find yourself on the receiving end of "your expectations are too much," here are some questions worth sitting with:

Is the person responding to the substance of what I asked, or are they responding to the fact that I asked at all? Are they naming their own limitation, or are they making my need the problem? If I removed emotion from this and looked at the ask on paper — is it unreasonable, or is it just inconvenient for them?

And here's the most important one:

Am I willing to let someone else's discomfort with their own capacity redefine what I'm allowed to want?

You don't have to answer that out loud. But you should answer it for yourself.

The Invitation

This isn't about holding people to impossible standards. People genuinely run out of capacity. Life is hard, bandwidth is finite, and grace is real. But grace works both ways. If I can extend grace for your limitations, you can extend grace for my needs — without making them a diagnosis.

The next time someone tells you your expectations are too much, consider the possibility that your expectations are fine. The gap isn't in what you asked for. It's in what they're able to offer. And the only honest path forward is naming that — without making you the problem for noticing.