โ† Knowledge base
๐ŸŽš๏ธ

Casual, exclusive, and the bit in between

What each label actually specifies, why the middle is so uncomfortable, and how to have the conversation without an ultimatum.

Relationship science

Casual means dating without commitment or an expectation of exclusivity. Exclusive means neither of you is seeing anyone else. Between them sits a large, poorly-named territory where most modern dating actually happens โ€” the situationship โ€” and where almost all of the distress is.

Worth noticing what neither label specifies. Casual does not tell you whether feelings are permitted, how often you will see each other, or whether either of you is dating others in practice. Exclusive does not tell you whether you are in a relationship, whether it is serious, or what happens next. Both words feel like definitions and settle less than people expect.

Why the middle is so uncomfortable

Not because it is undefined. Because it is asymmetrically undefined โ€” one person usually knows what they want, and asking risks getting an answer.

Scott Stanley's sliding versus deciding applies here as much as it does to moving in together. Relationships accumulate the features of commitment โ€” frequency, routine, meeting friends, keeping a toothbrush there โ€” without anyone deciding anything. Then inertia does the rest: leaving gets more expensive before either person has decided to stay.

The specific cost of the middle is that one person is usually running a continuous background calculation โ€” what is this, where is it going, is asking going to end it โ€” and that calculation is expensive. Which is why "just keeping it casual" is only genuinely casual when both people mean it, and is otherwise one person waiting.

What genuinely casual requires

Casual relationships work. They work under conditions that are more specific than the word implies:

  • Both people actually want casual, rather than one accepting it as the available version of something else
  • It is stated, not inferred from the absence of a conversation
  • Exclusivity is addressed explicitly, because casual and non-exclusive are not the same thing and people assume opposite defaults
  • The terms get revisited, because what someone wanted in month one is not binding in month six
  • Either person can end it without it being a betrayal โ€” which is the actual content of "no strings"

The failure mode is not casualness. It is one person being casual and the other performing it.

The exclusivity conversation

There is no correct timing, and the search volume for one suggests people want a number. What the data supports is weaker and more useful: relationships where commitment was decided rather than slid into do better, whenever the deciding happened.

Three things make the conversation go better:

Ask about the present, not the future. "Are we seeing other people?" is answerable. "Where is this going?" asks someone to predict, which invites a hedge.

Say your own position first. "I'd like to stop seeing other people โ€” is that where you are?" gives them something to respond to. Asking them to declare first, with your answer contingent on theirs, is a negotiation rather than a conversation.

Accept that it can end it, and ask anyway. The reason people avoid this is that the answer might be no. A relationship that cannot survive the question was already going to end; the question only changes when you find out.

And separately: exclusivity and commitment are different steps that arrive bundled. Agreeing not to see other people is not the same as agreeing to a future together, and couples regularly discover months later that they agreed to different things in the same conversation.

sources

  • ยท Stanley, S. M., Rhoades, G. K., Markman, H. J. (2006). Sliding versus deciding. Family Relations.
  • ยท Clark, M. S., Mills, J. (1993). The difference between communal and exchange relationships. PSPB.
  • ยท Rhoades, G. K., Stanley, S. M. (2014). Before 'I Do': What Do Premarital Experiences Have to Do With Marital Quality? National Marriage Project.

More from the knowledge base