A text notification from his wife lights up his phone.
She is eleven weeks pregnant.
Still early enough that they have not told many people. Still early enough that hope feels fragile. Still early enough that every strange feeling in her body can become a question neither of them wants to ask out loud.
They’ve been trying for a couple of years. This is her first pregnancy.
But they are not in the “any day now” stage. There is no hospital bag by the door. No standing rule that he must be reachable every minute. No obvious reason to believe this particular text is any kind of emergency.
He’s just about to reach for it when he feels a tap on the shoulder from behind.
The department head needs him for just a few minutes to answer some questions about a major project he’s working on. There’s a real-time meeting happening with the company CEO and other C-suite leaders, so he grabs a pen and notepad, leaves his phone on his desk, and follows his department head to the conference room.
His answers spark more follow-up questions from the company’s top brass, some of whom are only hearing about this for the first time. He answers questions, explains why they’ve approached the project this way, and highlights what they’re aiming for as an end goal. This big, great thing that’s going to improve customer experience, and likely increase sales.
What was supposed to only take a few minutes has turned into an hour and a half unexpectedly.
He gets back to his desk.
His phone shows several texts and missed calls from his wife.
“omg where are you?”
“Please call me.”
“I’m scared.”
“Ben. Please.”
Then he sees the one that makes his stomach drop.
“I’m bleeding. I don’t know what to do.”
Then he calls her.
No answer.
He calls again.
No answer.
Then another text comes in.
“I’m at the hospital.”
He grabs his keys and runs.
The entire drive there, his mind is racing. He is terrified for her. Terrified about the baby. Terrified because he knows he missed something important.
And he also knows, in the most honest part of himself, that he didn’t do anything wrong. He didn’t ignore her. He didn’t choose work over her. He didn’t see the messages and decide they could wait.
He got pulled into a meeting by his boss. The CEO was there. Other senior leaders were asking him direct questions about a project that mattered to his job, his team, his future, and their family’s financial stability.
He had a perfectly good explanation. It was incredibly unlucky timing.
And by the time he walks into the hospital room and sees her face, that explanation is already sitting on the tip of his tongue.
“I’m so sorry. I didn’t have my phone. I got pulled into this thing with the CEO, and I thought it would only take five minutes, but then everyone kept asking questions, and I had no idea you were calling.”
All of that is true. Every word of it. And none of it is what she needs first.
Because she is lying in a hospital bed, scared and alone, after spending the past hour and a half discovering that when she reached for him during one of the scariest moments of her life, he wasn’t there.
Not because he didn’t care. Not because he did anything malicious. Not because he is secretly a bad husband.
But because, in the moment she needed him, the outcome felt exactly the same as if he hadn’t cared. That is the hard part. That is the part we hate.
Because when we know our intentions were good, and the circumstances were unfair, and the accusation feels inaccurate, every instinct in our body tells us to defend ourselves.
To explain. To correct the record. To make sure they understand that we are not the kind of person they seem to be accusing us of being.
But if his first move is to defend his innocence, then she has to spend the next few minutes taking care of his reputation while she is still lying there bleeding and afraid.
And that is not repair.
That is abandonment. Even if it’s dressed up as a reasonable explanation.
(article continues below)
I’ve spent years talking with people about their relationships.
One thing I’ve learned is that many people can describe the pain they’re experiencing with remarkable accuracy.
They know they feel alone. They know they don’t feel considered. They know they can’t talk about certain things without defensiveness, conflict, or withdrawal in response.
What people often struggle to identify are the trust dynamics underneath those experiences.
So I built something.
The Relationship Trust Assessment is a free tool designed to help identify the trust injuries creating the most strain in your relationship, along with the strengths you can build upon moving forward.
The assessment takes about 5-7 minutes to complete. Afterward, I’ll personally review your responses and send your results by email.
Take Free Relationship Assessment
A quick note: This is Version 1. The mobile experience works, but isn’t quite as polished as the desktop experience.
I’d love to hear what you think. - MF
It almost always goes the same way.
Someone seems mad or disappointed in us. Often, that person is our relationship partner—the person we talk to most, share the most with, and rely on in the most meaningful ways.
We love them. We don’t want to hurt them. So it feels brutal when they seem to imply that we don’t love them, don’t care about them, or can’t be counted on.
We were in the middle of something else.
Work. School. House chores. Solving a problem. A home project. A trip. One of the kids needed something.
The specifics change. The feeling does not.
It feels like an unfair accusation. A misunderstanding.
If they knew what was happening on my end, they wouldn’t be so upset. Let me explain.
But explaining yourself, justifying your choices, and defending your intentions almost never makes the situation feel better to either of you.
Because while we are busy defending ourselves, we are not doing the work of repair.
We are not trying to understand what happened to the other person.
We are not communicating that we care that something painful happened to them.
We are not helping them believe this is less likely to happen again.
We are making the moment about our innocence instead of their injury.
And that distinction matters.
When we defend (no matter how justified or “correct” one might feel), we are demonstrating care and protective instincts around ourselves.
Not around them.
We are saying, often without meaning to say it: I need you to understand why I’m not guilty before I can care about what happened to you.
That is a devastating message to send inside a partnership.
Your first move should almost never be self-defense.
Not when your partner is telling you they were hurt. Not when you believe they are missing important information. Not when your explanation is reasonable. Not even when your explanation is true.
There will probably be a time to clarify what happened and explain the circumstances. There may even be a time to say, “That isn’t what happened, and I need us to talk about that.”
But the first move, if you care about trust, is not protecting your innocence.
The first move is caring about their pain.
Defensiveness is trust erosion. Every time.
This is not a universal rule for every human interaction. You may need to defend yourself in court, at work, with unsafe people, or inside relationships where someone is acting in bad faith.
But in a committed partnership where both people are trying to preserve trust, self-defense as the first move is almost always corrosive.
Because by definition, partnership is not just you.
It’s the two of you. It’s a unit made of two people. And when you make the other person an adversary—when you communicate that you’re on your own side instead of theirs—you consistently signal that you are someone who prioritizes self-protection over connection.
You may not intend to signal or communicate that. But you will communicate it anyway.
“But Matt! She’s so critical of me and unfair to me! She accuses me of things I’m not doing!”
I understand.
There’s a chance she’s 100% wrong every time she suggests you did something she doesn’t like. It’s theoretically possible.
I’m not asking you to optimize for Correctness.
I’m asking you to optimize for Trust.
Correctness does not create a healthy, connected partnership that can survive many years of real life.
Trust might. And trust is built in exactly these moments.
So the next time your partner suggests you’ve done something that was bad for them, consider trying this before you explain anything:
“I’m really sorry. I hate that something I did, or failed to do, left you feeling hurt and alone. You and I both agree that you should never be hurt because of something I’ve done. I want to understand what happened for you before I explain what happened for me.”
Don’t say it if you don’t mean it.
But if that idea is consistent with your values, then start addressing outcomes. Start addressing impact.
Stop leading with your intentions.
Every accidental injury in the history of the world happened unintentionally. Accidental injuries are still injuries.
And in our relationships, we must become people who exercise care around injuries, even the ones we did not intend to cause.
Matthew Fray is the author of “This Is How Your Marriage Ends: A Hopeful Approach to Saving Relationships,” a relationship coach, and formerly the blogger at Must Be This Tall To Ride.
I spend most of my time helping people navigate conflict, communication breakdowns, repair, trust, and long-term relationship pain.
My book, This Is How Your Marriage Ends (1,000+ Amazon reviews, 4.6 stars)
The new evening-hours Relationship Repair Workshop (seats are limited to 15 per group). This is a small-group coaching experience for people serious about making lasting changes.
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.