12 | Lean In or Let Go

https://video.wixstatic.com/video/ff341d_8967d7e54de64bfcaf52cda40ca18844/480p/mp4/file.mp4

Read the lesson.

I want to start with something that might surprise you. Leaving someone guessing — about what you need, what you value, what matters to you — is actually a form of dishonor. Not on purpose. Not maliciously. But when the people closest to you can't honor you because you haven't told them what honoring you even looks like — that's a problem. And it's the problem we're solving today. Because here's the thing: healthy conflict only works if you know what you actually need. And most of us skip that step entirely.

Let's start by rewriting what conflict even means. When I say conflict, I don't mean a fight. I don't mean drama. I don't mean opening a can of worms. Here's how I define it: conflict is reconnecting — or establishing connection — when connection has been lost. That's it. Picture a line. On one side: your expectations. On the other side: reality. When those two things don't match, there's a gap. And that gap is where offense lives. That gap is where trust quietly starts to erode. Healthy conflict is simply the conversation that closes the gap. And it can take two minutes. It doesn't have to be a production.

So when do you lean into conflict? Simple rule: If you live with them, work with them, or do life with them — it is always worth clearing the air. Nothing is too big or too small. And when do you let it go? When it's someone you're not in relationship with. Someone you're not going to build trust with over time. The driver who cuts you off — let it go. The rude interaction at the coffee shop from someone you'll never see again — let it go. Not because it didn't matter. But because conflict is about rebuilding connection, and you're not in a connection with that person. The people you are in connection with? Those are the people worth fighting for.

Before you have the conversation, run through this checklist. Question one: are you clear? Can you specifically name what happened? Not a feeling. Not a vague frustration. A specific moment. If you can't get specific, you're not ready. Because vague offenses lead to vague conversations — and vague conversations lead to more disconnection, not less.

Question two: where are your emotions? Think of a scale, one to ten. Ten is through the roof. One is completely numb. You're looking for a five to seven. If you're at an eight, nine, ten — your thoughts are probably about blame. You're not thinking about understanding, you're thinking about being right. That's not the energy that rebuilds trust. Go work out. Vent to someone you trust. Sleep on it. Bring your emotions down before you bring the conversation up. If you're at a one, two, three — the opposite problem. You've processed so much that the feeling is almost gone. And the temptation is to just let it go. It wasn't that big of a deal. I'm over it. Don't do that. That "I'm over it" feeling is a signal that you've waited too long — not a signal that everything is fine.

I want to tell you about my friend. We lived together for about a year. We worked together. We shared mission together. We had genuine camaraderie. Or at least — I thought we did. A few years after she moved away, I went to visit her in Hawaii. One night we were sitting on her porch, sharing sliced mango and pineapple, and she opened up about a season of her life where she had been hurt by me. And I felt my own emotions spike — because this season she was describing was two or three years prior. And I had no idea. I let her talk. And then I asked her: why didn't you come directly to me? And she said what so many of us say. She didn't want to make it a big deal. She thought it was probably just her. She didn't want to add to my plate. And I told her: that's the entire point. The only way I can honor who you are is if you share who you are with me. I was over here wanting to honor you. I wanted to. But I couldn't — because I didn't know. She never told me. Here's what I've learned since that conversation: most of us — especially those of us who are wired for introspection, who take ownership seriously, who care deeply about other people's feelings — we internalize everything. We keep it inside. We convince ourselves it's broken in us, something to figure out alone. And that's actually a beautiful impulse. But taken too far, it robs the people who love you from actually knowing you. Leaving someone guessing what makes you happy — what honors you, what hurts you — that's not protecting them. That's keeping them at arm's length. I told her: you would have honored me by coming to me. I would have felt trusted. I could have learned something about your heart. Instead, I had a blind spot for three years, and she carried something she didn't have to carry.

So we've talked about when to lean in. Now let's talk about the other side — when you genuinely let something go. My lean, always, is toward clearing the air. With your family, your friends, your teammates, your colleagues — anyone you're in relationship with or working alongside — there is no thing too small. I mean that. The tiny stuff is worth a two-minute conversation. Because tiny stuff, left unaddressed, becomes the distance that people can't explain. For the people you're not in relationship with — the stranger who was rude, the person in traffic — that's actually where you get to practice the art of truly letting something go. Not stuffing it. Not swallowing it. Actually releasing it, because there's no connection to protect there. Now, that's the general rule. There are edge cases, absolutely. But if we can practice two things at the same time — genuinely letting go of what doesn't require a conversation, and leaning into daily healthy conflict with the people we're actually in relationship with — we are setting ourselves up to become culture of honor builders. Here's where it gets nuanced though. With your closest relationships — your spouse, your roommate, anyone you live with — if you chose to clear the air on every single missed expectation, you would be sitting around clearing the air all day. So this is where you choose your battles wisely. For my husband — he probably needs to let go of the way I sneeze. It's just how I sneeze. That's not worth a conversation. But if I get sassy when I'm tired and shift the entire energy of the house — that's worth clearing the air about. That's something we can actually address together. The difference is: one is just who I am, and the other is a behavior that's affecting our connection. Now here's the critical piece — and this might be the most important thing I say today. When you choose to let something go, you have to actually let it go. The worst, most ineffective conflict conversations happen when someone brings in a pile of things they supposedly already let go of — using them as evidence to defend a point. That's not letting go. That's stockpiling. And clear the air conversations are about one action. One specific moment. Not a pattern. Ask yourself: have you ever had a successful conversation with someone you love that started with "you always" or "you never"? I'm guessing no. Because that's a losing argument every single time. Nobody can course correct a pattern all at once. What they can do is address one action, one decision — and if that changes, and changes again, and changes again, over time, a pattern shifts. But you can't hand someone a highlight reel of their worst moments and expect that to build anything. One thing. Specific. That's what a clear the air is built for.

So here's the takeaway. If you're someone who tends to let things go — who stuffs it, processes alone, and convinces yourself it wasn't worth bringing up — I want to challenge you. The connection you're protecting by staying quiet? You might actually be undermining it. The people around you can only honor who you are if you show them who you are. That means when something doesn't sit right, you bring it up. Specifically. Calmly. With curiosity leading the way. Because conflict — real, healthy conflict — isn't the enemy of connection. It's how connection gets built.