Make requests specific, present-tense, and doable
A genuine request names exactly what you’d like done, by when, in observable terms.
Key takeaways
- What it is: A genuine request names exactly what you’d like done, by when, in observable terms.
- Why it works: Vague requests put the burden of interpretation on the other person and create the conditions for disappointed expectations. "I need you to be more supportive" is a need statement, not a request — the other person cannot verify whether they’ve met it. "Would you be willing to put your phone away during dinner this week?" is specific, observable, and time-bounded. The precision matters because it allows for clear agreement or negotiation, and it makes it possible to check whether the request was met.
- Evidence: Established clinical or therapeutic practice.
- Avoid: Stating the need instead of the request — "I need connection" is true and important, but it’s not yet a request. The request is the specific thing you’d like to happen that would meet that need. Without it, the other person is left guessing.
Why it works
Vague requests put the burden of interpretation on the other person and create the conditions for disappointed expectations. "I need you to be more supportive" is a need statement, not a request — the other person cannot verify whether they’ve met it. "Would you be willing to put your phone away during dinner this week?" is specific, observable, and time-bounded. The precision matters because it allows for clear agreement or negotiation, and it makes it possible to check whether the request was met.
How to do it
- 1Name the specific action: not "be present" but "look up from your phone when I’m talking."
- 2Name the timeframe: "this evening" rather than "more often."
- 3Make it observable: if you couldn’t video-verify whether the request was met, it’s probably too vague.
- 4Ask for one thing at a time — multiple embedded requests reduce the chance any of them get a genuine yes.
What the evidence says
Clinical practiceSpecificity in behavioral requests is a core principle in behavioral activation and couples communication training. Vague expectations are a well-documented source of relationship conflict; clear behavioral targets allow mutual checking and repair.
Honest caveat: Specificity principle is well supported across behavior change and communication research; NVC-specific outcome research is limited and methodologically variable.
- — Rosenberg, M. B. (2015). Nonviolent Communication: A Language of Life (3rd ed.). PuddleDancer Press.
Common mistake
Stating the need instead of the request — "I need connection" is true and important, but it’s not yet a request. The request is the specific thing you’d like to happen that would meet that need. Without it, the other person is left guessing.
IX Coach helps you move from a stated need ("I need to feel heard") to a specific, doable request ("Would you be willing to reflect back what I said before responding?"), making the ask concrete enough for a genuine yes or no.
Practice this with IX Coach →