The Seven Conversations: A Practical Guide for Engineers

If you read the Hold Me Tight review, you know the theory: most relationship fights aren't about the thing you're fighting about. They're about unspoken emotional needs hitting a communication protocol mismatch.

This article is the practical side. How to actually use Sue Johnson's seven conversations, adapted for people who think in systems and feel awkward talking about feelings.

Before you start: what engineers need to know

If you're an analytical person, two things will trip you up.

First: these conversations are not problem-solving sessions. Your instinct will be to identify the issue and fix it. That instinct is exactly what makes you great at engineering and terrible at emotional conversations. The goal is not to solve anything. It's to make the other person feel understood. Those are very different operations.

Second: you might feel nothing when you try to access your emotions. That doesn't mean you don't have them. It means the connection between your analytical mind and your emotional signals has gotten weak from underuse. If Martha Beck's Body Compass exercise left you blank, start there first. Build the ability to notice your own internal state before trying to communicate it to someone else.

The seven conversations (engineer's version)

1. Recognize the spiral (Relationships, Boundaries)

Before anything else, both people need to see the pattern. Not who's right or wrong. Just the pattern itself. “When I criticize, you withdraw. When you withdraw, I criticize louder.” That's the spiral. Name it together.

Engineer-specific: You might be the withdrawer. Engineers often go quiet during conflict because they need processing time. Your partner reads that as “you don't care.” Naming the pattern means you can say: “I'm going quiet because I'm processing, not because I'm checking out. Give me ten minutes and I'll come back.” That one sentence can stop the spiral before it starts.

2. Find the raw spots (Body Connection)

Each person has specific triggers that set off a disproportionate reaction. Johnson calls them raw spots. A comment that sounds neutral to you might hit your partner's deep fear of not being good enough. And vice versa.

Engineer-specific: Your raw spots might be around competence and being seen as capable. If your partner questions a decision in a way that feels like they're doubting your judgment, the emotional response may be far bigger than the situation warrants. Knowing your own raw spots helps you separate “they asked a reasonable question” from “they think I'm incompetent.”

3. Reach for the other (Relationships)

This is where vulnerability comes in. Instead of sending the encoded version (“You never help with anything”), you send the raw data (“I feel overwhelmed and I need you to notice”).

Engineer-specific: Try framing it as a status report instead of a complaint. “Current state: I'm at capacity. Request: I need support with X. Priority: high.” Sounds robotic written down. In practice, even an approximation of this clarity is miles better than the accusation version. Your partner would much rather hear a clear request than decode an angry hint.

4. Revisit a rocky moment (Boundaries)

Go back to a specific fight that went badly. Not to rehash it, but to understand it. What was each person actually feeling underneath? What need was unmet? This is post-flight analysis, not a retry of the mission.

Engineer-specific: You're probably good at this one, actually. Post-mortems are familiar territory. The trick is doing it without assigning blame. In engineering post-mortems, the goal is to fix the system, not punish the person. Apply that same principle here.

5. Forgive past injuries (Relationships)

Old wounds that never got properly acknowledged keep replaying. This conversation is about naming a specific hurt, having the other person really hear it, and beginning to let it go. Not pretending it didn't happen. Acknowledging it and choosing to move forward anyway.

6. Bond through sex and touch (Body Connection)

Johnson addresses physical intimacy directly. Emotional safety and physical connection feed each other. When the emotional protocol breaks down, the physical connection usually follows. And repairing one often helps repair the other.

7. Keep the connection alive (Work, Relationships)

Relationships don't stay fixed once you fix them. They need ongoing maintenance. This conversation is about building rituals, check-ins, and shared direction that keep the protocol running even when life gets busy.

Engineer-specific: Think of it like operational monitoring. You don't launch a system and walk away. You set up health checks, define thresholds, and have a process for when things drift. Relationships need the same.

This week's challenge

Pick conversation #1. Just the spiral recognition. Sit down with your partner (or think about a professional relationship where tension keeps recurring). Try to name the pattern together without assigning blame. “When X happens, I tend to do Y. When I do Y, you tend to do Z. When you do Z, I do more Y.”

That's it. Don't try to fix it. Just map it. Like drawing a system diagram before writing any code.

How to test if it's working: After two weeks of practicing spiral recognition, retake the Relationships dimension of the Essential Self Diagnostic. If the score shifted, even slightly, the awareness is landing. If it didn't, you might need a different entry point. That's fine. Try the Body Compass first to build internal awareness before attempting external communication.

Who this framework is for

Both people need to be willing. If only one partner is open to this, start with your own internal work first (diagnostic, Body Compass, awareness practices from the Healthy Minds Program).

These conversations assume a fundamentally safe relationship with communication problems. If vulnerability gets weaponized, or if there's abuse, this framework is not the right tool. Professional help should come first.

The bottom line

Seven conversations. Each one addresses a specific gap in the emotional communication protocol. Start with #1 (recognizing the spiral) because everything else builds on it. Don't try all seven at once. One conversation, practiced over a few weeks, will teach you more than reading about all seven in an afternoon.

The goal isn't to become a perfect communicator. It's to build a shared language for the stuff that's hardest to say. That shared language is worth more than any fix.