Relational Intelligence: Why "Good Communicator" Isn't the Skill You Think It Is

Most people rate themselves highly on relationship skills. "Great communicator." "Really empathic." Meanwhile their partner is three feet away, quietly checked out. That gap between self-perception and actual relational competence is the starting point for a framework called relational intelligence, developed by therapist Figs O'Sullivan, LMFT, and it's worth unpacking because it treats relationships less like a feelings problem and more like a systems-design problem.

The distinction matters: emotional intelligence is about understanding feelings, yours and your partner's. Relational intelligence is about understanding the dynamic between two people, the feedback loops, the way one person's defensive move triggers the other's survival response, and what to do about it in real time.

Here's the working example. Emotional intelligence is knowing you're angry. Relational intelligence is knowing your anger just activated your partner's abandonment wound, which will make them withdraw, which will make you angrier, and that unless you interrupt the loop in the next 45 seconds, you're both looking at a three-day cold war. That's a different skill set, and most couples never train it.

The data backs up how common this failure mode is. Across 58,221 completed relationship assessments from Empathi's research, in the 6,159 cases where both partners completed the assessment, 74.1% of couples were caught in a pursue-withdraw cycle, a pattern where one partner chases connection and the other retreats from it. Tellingly, both partners typically describe the other person as the one withdrawing. Nobody thinks they're running the loop. Everybody is.

There's a neurobiological reason this is hard to self-correct. Attachment science treats relational threat, rejection, criticism, emotional distance, with the same biological urgency as physical threat. Silent treatment fires the amygdala and floods the body with cortisol. That's why people say "I don't know what came over me." They're not wrong. It wasn't a conscious choice; it was a nervous system in survival mode, running code written decades before they met their partner.

The core claim here is blunt: you cannot apply a cognitive solution to a biological problem. Couples who've "talked it out" 400 times aren't failing because they lack vocabulary. The conversation was never the bottleneck. The dysregulated nervous system underneath it was.

The Five-Part Framework

O'Sullivan breaks relational intelligence into five learnable capacities, drawn from 17 years of clinical work. None of them are personality traits; all of them are skills that can be trained.

• Recognition and return. You will get triggered. That's not preventable, and claiming otherwise is either dishonest or a sign of dissociation. The actual skill is noticing fast when you've left your regulated self and shifted into survival mode, then shortening the time it takes to come back. Some couples take three days to recover from a fight. Relationally intelligent couples take three minutes. Same trigger, radically different recovery curve.
• Governing protector parts. Criticism, withdrawal, sarcasm, keeping score: these are protective strategies that developed for good reason, usually early in life. The fix isn't exiling them, it's acknowledging them without letting them drive. "I see you, I know you're trying to protect me, but I've got this" is a fundamentally different internal stance than either suppressing the urge or acting on it.
• Turning the flashlight inward. During conflict there's a pull toward narrating what your partner is doing wrong, what O'Sullivan calls the "Story of Other." It feels accurate and often is, but it's a dead end: nobody changes behavior because they were told what's wrong with them. The alternative is reporting your own internal experience, "when you went quiet, something in my chest tightened," rather than diagnosing theirs.
• Protecting the "Third Chair." Every relationship has three entities: you, your partner, and the relationship itself. O'Sullivan uses an empty chair in session to represent that third entity. Most conflict is "me versus you," where even the winner damages the thing that sustains both people. Reframing it as "us versus the loop that's trying to kill the connection" turns two combatants into one team solving a shared problem.
• Following the biological protocol. Repair has a sequence, and the steps aren't optional. Skipping ahead to resolution before the nervous system has actually settled just resets the loop for next time.

A simple operational test O'Sullivan teaches couples: before saying something in conflict, ask "is this going to feed the relationship or starve it?" That single question, applied honestly, reportedly redirects a large share of escalating conflicts before they go nuclear.

Key Takeaways

Relational intelligence isn't the same thing as emotional maturity, and conflating them causes a lot of wasted effort. Emotional maturity is an individual capacity, regulating yourself, taking responsibility, tolerating discomfort, and you can build it alone. Relational intelligence requires a second person; it's a systemic skill about reading the space between two people and adjusting in real time. You can be personally well-regulated and still be relationally unintelligent, which is a more common combination than people assume.

The practical upshot for anyone trying to apply this: stop optimizing for "never getting triggered" and start optimizing for faster recovery. Track your own early warning signals (chest tightness, a buzzing urge to "win," sudden sarcasm) and treat that signal as a small decision window rather than a point of no return. And when conflict escalates, resist the pull to diagnose the other person's behavior. Report your own internal state instead. It's a less satisfying move in the moment, but it's the one that actually changes the loop instead of feeding it.