Requests vs Expectations

Requests vs. Expectations: The Communication Habit Quietly Killing Your Sex Life

September 07, 20266 min read

I see this over and over in my coaching sessions with couples. Not once in a while. Constantly. Someone is sitting across from me, frustrated, hurt, sometimes furious, and when I ask what they actually said to their partner, the honest answer is nothing. They never said it out loud. They just expected the other person to know.

Unspoken expectations in relationships might be the single biggest killer of intimacy I've come across, and it's rarely dramatic. It's quiet. It's "he should have known to call me." It's "she should know I want more romance by now." It's "he should know how to make love to me this way," after years together, without either of you ever actually talking about what "this way" even means. And here's the hard truth I tell every couple I work with: if you didn't clearly ask for something, you don't get to punish someone for not giving it to you.

A request and an expectation are not the same thing

A request is spoken. It's clear. And it gives the other person a real, honest choice, a yes, a no, or a counter-offer. An expectation is unspoken, and then you feel hurt, or resentful, or quietly furious, when it doesn't get met.

Here's what an actual request sounds like: "I would like to have dinner with you Friday at 7pm, are you available?" That's specific. That's defined. Compare that to "hey, we should hang out sometime," which isn't a request at all, it's a vague suggestion nobody can actually say yes or no to.

Once you make a real request, the other person has three honest options. Yes, "I'll go to dinner with you Friday at 7." No, "I'm not available for that, but thank you." Or a counter-offer, "Friday doesn't work, but Saturday would, does that work for you?" That's how two grown adults actually build an agreement together. Compare that to an expectation, where nobody ever gets asked anything, and somebody just quietly waits to be disappointed.

Where this shows up hardest: in the bedroom

Unspoken expectations do the most damage in erotic and intimate spaces, more than almost anywhere else in a relationship. "He should know how to make love to me this way." "She should be turned on the way I want her to be turned on." "He doesn't have sex with me the way I want." Notice the judgment baked into every one of those sentences. Nobody handed anyone a manual. If you've never actually said what you want, out loud, specifically, your partner is not failing you. They're guessing, same as you would be in their position.

When couples first sit down with me, I ask a simple question: what do you actually want? And it goes silent. Completely silent. Or I get "I just want more passion," and I have to ask, what does passion actually look like to you? What does that mean, specifically? Or "I want more sex," and I ask, how much is more? Once a week? Twice? If you tell the universe you want more money and it hands you a penny, technically that's more money. It's not going to change your life. Vague desires get vague results. Specific requests get real answers.

More real examples, so you can hear the difference for yourself

"If they cared, they'd check in." That's an expectation. "Would you be open to checking in with me after I've had a hard day?" That's a request. Same underlying desire. Completely different odds of actually getting your needs met.

"They should stay connected after intimacy." Expectation. "I love closeness after sex, would you be open to staying connected like that?" Request.

"This should be progressing by now." Expectation. "I'm looking for something that grows into real commitment, how do you feel about that?" Request.

"They should just know I need reassurance." Expectation. "I feel more secure with verbal affirmation, would you be willing to offer that sometimes?" Request.

Notice the pattern. A request risks vulnerability, because you might hear no. An expectation avoids that risk entirely, and quietly builds resentment in its place instead. I'll say that one again because it's the whole point: a request risks vulnerability, an expectation avoids it and creates resentment.

A confession, because I catch myself doing this too

I'm not exempt from this, and I think it helps to say so. Not long ago I was talking to someone I was dating, texting back and forth, and then I didn't hear from him for two days. I got mad. Genuinely irritated. In my head I was thinking, why hasn't he texted me back, why hasn't he called, this is disrespectful. When he finally called, I basically came at him with it.

And he said something that stopped me, he said I just need to tell him directly if I'm not happy that he's not texting back, instead of expecting him to somehow already know. He was right. I had never actually made the request. I'd told him earlier, in general terms, that consistent communication mattered to me, but I hadn't made a clear, specific ask about response time or what "consistent" meant to me. I was sitting in the expectation seat, feeling hurt about something I'd never actually voiced. That's an easy trap to fall into even when you teach this stuff for a living.

Fun aside, because I geek out on this

I looked into the word technology once, outside of the phone-and-computer context we usually use it in. It traces back to Greek, techne, meaning art or craft, and logia, the study of. Technology, at its root, means the study of artistic expression. I think about requests the same way. Making a clear, specific request is a craft. It's a skill you build, not something you're born knowing how to do. Nobody's naturally fluent in asking directly for what they want, especially around sex and desire. You get better at it with practice, like any other art.

How to actually shift this, starting tonight

Pick one thing you've been silently expecting from your partner. Not five things. One. Turn it into an actual, spoken, specific request. Not "you should know I want more affection," but something like "I'd love it if you kissed me hello when you walk in the door, would you be open to that?" Then let them answer honestly, yes, no, or a counter-offer, and actually receive whatever they say instead of treating anything but an enthusiastic yes as a personal rejection.

Quick answers, since these come up constantly in my DMs

What's the real difference between a request and an expectation? A request is spoken out loud, specific, and gives the other person room to say yes, no, or offer an alternative. An expectation lives silently in your head, and you feel hurt or resentful when it isn't met, even though the other person was never actually asked.

Why do unspoken expectations hurt relationships so much, especially around sex? Because judgment hides inside them. "He should know how I like to be touched by now" sounds like a fact, but it's really a silent test your partner didn't know they were taking, and one they were bound to fail eventually.

How do I turn a resentment I already have into a request? Get specific about the exact behavior you want, not the vague feeling underneath it, then ask for it directly, in a sentence that could honestly be answered with yes, no, or let's find a middle ground.

If this is hitting home and you're realizing how much of your relationship has been running on expectations nobody ever actually voiced, that's exactly the work I do with couples in private coaching. Apply for a Clarity Session and let's get specific about what you actually want, together.

blog author avatar

Rose Heartsong

Rose Heartsong is a Sex, Love & Intimacy Coach based in Laguna Beach, California, and the host of Sex Ritual Radio. Her work blends conscious kink, Tantra, and nervous system science to help singles and couples move from managing their relationships to intentionally creating them. Trained under Psalm Isadora and certified in dominatrix practice, Rose helps people find the words for what they've never been able to say.

Back to Blog