A Relationship is a Relationship is a Relationship
I've said this for years. To teams, to individuals, to family and friends and to leaders navigating something that felt new and overwhelming. It's usually the thing that settles the room. Not because it's complicated. Because it's true, and somewhere along the way we stopped acting like it was.
The values that make a relationship work don't change much. Clarity. Authenticity. Respect. Accountability. These aren't professional skills or personal skills. They're relationship skills. And we carry them everywhere. Into the boardroom, into the kitchen, into the difficult conversation we've been putting off, into the one we didn't see coming.
We're reasonably good at this. Most of us, most of the time. We know how to read a room. We know when to push and when to wait. We know that the way we say something to a colleague at 8am on a Monday is not the way we say the same thing to our kid at dinner. Same values. Different delivery. We do this constantly, and mostly without thinking about it.
What I want to talk about is what happens when we forget that we know this. And we do forget.
Share this article with a colleague:
March 19, 2026 at 3:36:48 a.m.

Take the gap between what you meant and what was heard.
It happens in a practice area meeting when the scope of a file gets discussed but the roles don't. Everyone leaves the room with a different understanding of who is doing what by when. Nobody said the wrong thing. Nobody was careless. The communication just didn't close the loop it needed to close.
It happens in a partner meeting when associate development is on the table. Strategies get named. Concerns get raised. The meeting ends with a general sense that something will be done. But who is responsible for the conversation? By when? And what does progress look like? The gap between a decision made and a decision owned is where development goes quiet.
It happens at home when someone volunteers to handle the vacation planning and three weeks later the other person is frustrated because nothing has been booked. Not because anyone dropped the ball. Because "I'll handle it" and "I'll handle it by Tuesday" are not the same sentence, and nobody noticed the difference until it mattered.
And it happens when you RSVP'd to a dinner party a month ago and the date arrives and you don't go. Did you send your regrets, or did you just not show up? The host noticed. The relationship absorbed it. Neither of you will mention it directly, and it will sit there anyway.
Same gap. Same cause. Different setting.
The fix is identical in every one of these situations. Be specific about scope. Name the roles out loud. Confirm the timeline isn't just implied. Check in before you leave the room, the table, the conversation. This isn't a professional skill that occasionally transfers to personal life. It's a relationship skill that lives in all of these places simultaneously, whether we're treating it that way or not.
The people who are genuinely good at this, and you know who they are, because working with them feels different, are good at it everywhere. Not because they have a system. Because they've stopped separating the skill from the relationship.
This doesn't mean assigning roles and deadlines like a project manager who wandered into the wrong room. It means being mindful of who is in the room and what the relationship requires. It means creating space to really listen. Asking directly. Deciding together what accountability looks like.
In the vacation example, that might sound like: I've booked this hotel, these dates, this location. Before I move on, any concerns? It's not a presentation. It's a check-in. The difference is small and everything.
The same question asked in a partner meeting before everyone disperses does identical work. Not a debrief. Not a formal confirmation of roles. Just: before we leave this room, does everyone have what they need?
The people who ask that question in both places tend to have fewer blown timelines, fewer relationship repairs, and fewer conversations that start with "I thought you were handling that."
There is a particular kind of attention that changes the quality of everything that follows it.
Not active listening as a technique. Not the performance of nodding and maintaining eye contact and waiting for your turn to speak. The real version. The kind where you are genuinely trying to understand what the other person is communicating, not just what they are saying.
And it runs in both directions. Real listening includes the willingness to notice when you're not landing. When the room has gone quiet in a way that means something. When the answer came too fast. When the person across from you is agreeing in a register that doesn't quite sound like agreement. Adjusting isn't weakness. It's the relationship asking you to pay attention.
It looks different depending on where you are. In an executive meeting it might be noticing that the person who hasn't spoken yet is the one with the most at stake. Pausing. Asking directly. Not because the agenda requires it but because the relationship does. In that pause something often surfaces that would otherwise leave the room unspoken and do its damage quietly.
At the dinner table it looks like putting down the thing in your hand and turning toward the conversation. Not because what's being said is urgent. Because the person saying it is deciding, in real time, whether this is a table where they are heard. And they will remember the answer long after they've forgotten what was said.
Same skill. Same values. Completely different stakes, until suddenly they aren't.
The people who struggle most with this aren't careless. They're just not adjusting for the relationship in front of them. They're carrying the habits of one context into another and wondering why the results are different. The executive who is excellent at running a tight meeting and genuinely baffled by why their teenager has stopped talking to them. The parent who is warm and present at home and slightly terrifying to work for.
Same person. Different rooms. The skill didn't travel because they didn't bring it.
Most relationships don't end badly because people are unkind. They end badly because someone waited too long.
I have ended professional relationships deliberately. Before the frustration became permanent. Before the thing that was starting to erode trust had enough time to erode it completely. Not because the relationship had failed, but because I could see where it was going if I didn't act while we were still capable of an honest conversation.
This is not a comfortable thing to do. It requires you to name something that isn't fully broken yet. To say, clearly and without the permission of a catalyst, that this isn't working and here is why and here is what I think we should do about it. Most people wait. They wait for the blowup, the next missed deadline, the thing that finally makes the conversation unavoidable. And by then the relationship has absorbed damage it didn't need to absorb.
The same pattern runs through personal relationships so precisely it barely needs saying. The friendship that drifted and then ended in silence. The family relationship that finally broke over something small because the actual thing was never addressed. The partnership that ended in anger when it could have ended in respect, if someone had been willing to have the harder conversation six months earlier.
A relationship ended with care has a future. It might look different. It might be less frequent, more bounded, professionally cordial where it was once close. But the door stays open. A relationship ended in anger rarely does.
This is not a professional skill. It is not a personal skill. It is the same skill, and it requires the same thing in every context. The willingness to value the relationship enough to be honest with it before honesty becomes impossible.
Here is where I want to pause and name something that is getting lost in almost every conversation about AI right now.
The skills I have been describing are not going to help you work with AI. They already do. The conversation has just been framed as a skills gap. Something new to learn, a competency to acquire. And that framing is doing real damage. It makes available skills feel unavailable.
When you work with an AI partner, everything that makes a relationship function applies.
Clarity about what you need. Honesty about what isn't working. The willingness to adjust your communication without abandoning your values. The ability to create space, check in, and course correct without drama. These are not new competencies you need to develop for an unfamiliar technology. They are the same competencies you have been building your entire professional and personal life.
What changes is the audience. Not the values.
The managing partner who knows how to ask a precise question in a partner meeting already knows how to prompt well. The leader who checks in before leaving the room already knows how to iterate. The person who ended a professional relationship with care rather than waiting for the blow up already understands that the quality of the working relationship shapes the quality of the work.
You do not need to be a different person to work effectively with AI. You need to be the same person you are when you are at your best in any relationship. Attentive. Clear. Honest about what is and isn't landing. Willing to adjust delivery without losing yourself in the process.
The fear that surrounds AI is real and I don't dismiss it. But some of what reads as fear is really disorientation. The category feels new, so the skills feel unavailable. They aren't. They're the same skills. The same values. A different relationship to apply them in.
A relationship is a relationship is a relationship.
A few questions worth sitting with.
Where in your life are you clearest about scope and accountability?
The place where expectations rarely go sideways, where people know what they're responsible for and follow through. Are you bringing that same clarity everywhere else, or does it live in one room and stay there?
Think of the last relationship that ended badly or is ending badly right now. Was there a conversation that could have happened earlier? Not the conversation that finally happened. The one before that. What stopped it?
Who in your life communicates differently from you? At work, at home, in the communities you're part of. Are you adjusting for them, or are you waiting, perhaps without realising it, for them to adjust for you?
And the last one, which is the one this whole piece has been building toward:
Where have you decided that AI is a separate category? Something that requires different skills, a different version of yourself, a competency you haven't developed yet. What would change if you stopped?
You don't need to answer these out loud. They'll do their work quietly. But they tend to be most useful when you resist the urge to answer them quickly.
The only thing left to do is decide to bring what you already know into the room.
Not a new framework. Not a certification or a course or a carefully curated change management plan. Just the clarity you already practice, the listening you already know how to do, the honesty you've already proven you're capable of when the relationship matters enough.
It has always mattered enough. You just have one more relationship to apply it in now.
If this is sitting with you and you want to think it through in the context of your organisation, I'd welcome the conversation.