How to Ask For What You Want: Wants vs. Requests

THE SHORT VERSION: If you've ever quietly hoped a partner would just know what you needed without you having to say it, you're not alone – and it isn't because you're bad at communicating. Most of us were never taught the difference between a want and a request, so we keep expecting the first to somehow deliver the second.

In this guide, you'll learn why unspoken wants so often curdle into resentment, why hinting rarely gets you what you actually need, and how to turn a want into a request specific enough for someone to actually say yes to.

Why this distinction gets missed

Here's a pattern worth noticing: you want something from your partner, but you never actually say it. Not because you're avoiding it on purpose – asking directly can feel exposed, and maybe nobody modeled it for you growing up. So the want just sits there, quiet, waiting to be noticed.

Except it doesn't stay quiet for long. Confusing an unspoken want with an unmade request is one of the most common causes of quiet resentment – you feel let down by someone who was never actually given anything they could respond to.

Confusing an unspoken want with an unmade request is one of the most common causes of quiet resentment.

Marshall Rosenberg, who developed Nonviolent Communication, put his finger on why this keeps happening: needs and feelings live inside you, and they're real and universal – but a request has to leave your head and become something concrete enough for another person to act on. Skip that translation step, and your partner isn't ignoring you. They're guessing.

How to turn a want into a request

So how do you actually make that translation? Start with the want, exactly as it feels, even if saying it out loud feels a little raw: "I want to feel prioritized."

That's honest, but it's not something anyone can act on yet – "prioritized" means something different in every head it lands in. So take it one step further: turn it into something specific enough to say yes or no to. "Can we have twenty minutes alone tonight, phones away?"

Notice what changed. The first sentence describes a feeling. The second one hands your partner something they can actually do. That's the whole shift – and it's smaller than it sounds once you've made it the first time.

Ask yourself this

• What is one thing I've silently wanted from a partner but never actually asked for?
• Why haven't I asked – fear of rejection, fear of seeming needy, or just not having the language?
• If I imagine saying the want out loud, what's the worst realistic response, and could I actually handle it?
• Is there a want I keep expecting someone to guess, instead of stating?
• What would a small, specific, answerable version of that want look like as a request?

Practice this today

Try this today: pick one want you've been quietly holding onto, and write down the raw, internal version first – no editing, no cleaning it up. Then rewrite it as a request specific enough that someone could say a clean yes or no.

Say both versions out loud, one after the other. Most people notice something surprising: the request feels far less exposed than the want did in your head. The anticipation is usually the hard part, not the actual asking.

A conversation starter for partners

Want to bring your partner into this instead of practicing solo? Try opening with the idea itself, before your specific list: "I read about the difference between a want and a request, and I realized I've been expecting you to guess some things instead of asking. Can I practice on you?"

Framed that way, it lands as something you're building together – not a complaint about what they've missed.

Where to take this next

You'll get the full version of this tool – with guided practice on real scenarios – inside Temple's Exploration course, alongside the other communication frameworks it's built to pair with.

// Andrea