I was facilitating a board meeting in Hong Kong, helping a tech company work through their expansion strategy. We were on the 42nd floor overlooking Victoria Harbour, and the twelve executives around the table were debating whether to expand into three new markets simultaneously. The voices kept getting louder and people kept interrupting each other. Charts kept appearing on the screen showing projected revenue doubling, tripling.

One woman sat at the far end of the table, her hands folded quietly in her lap. Her name was Lin, and she was the head of operations – the person who actually had to make all these ambitious plans work. While everyone else leaned forward, gesturing with pens, she stayed perfectly still, her eyes moving from person to person.

Then, about two hours in, she leaned forward and placed both palms flat on the table.

“I need to say something,” she said. Her voice was steady but quiet enough that the room had to fall completely silent to hear her. “We’ve been talking about growth and expansion for the past two hours – new cities, new teams, new revenue targets. But nobody has mentioned what this will cost the people who’ve been with us from the beginning. The team in Shanghai who built this company when we had twelve employees and no investors. The original developers who’ve been working seventy-hour weeks for three years. I’m looking at this expansion plan, and I see us hiring two hundred new people while laying off thirty of our core team to fund it. I’m worried we’re about to sacrifice the relationships that got us here for revenue numbers that might not even materialize.”

The executives who had been so animated moments before went very quiet. One of them, the CFO, put down his pen and leaned back in his chair, his face suddenly pale.

The conversation shifted completely after that. Instead of debating which three markets to enter, they started asking different questions. Could they phase the expansion differently? Could they protect the core team while still growing? What would happen to company culture if they let go of the people who’d built it?

By the end of that afternoon, they’d created a completely different plan – slower growth, but with the Shanghai team leading the expansion instead of being replaced by it.

Later, over tea in the quiet break room overlooking the harbor, I asked her what made her speak up in that particular moment. She wrapped both hands around her teacup and stared out at the water for a few seconds before answering.

“I tried to let it go,” she told me, her voice softer now than it had been in the boardroom. “I kept thinking someone else would bring it up – maybe David, our CTO who’s been here from the start, maybe someone from the original team. But the tightness in my chest kept getting worse with each slide. I could feel my heart pounding. My hands were actually shaking under the table.” She gave a small, embarrassed laugh. “And then I saw Marcus pull up that slide showing headcount reductions – thirty names, people I’ve worked with for years – to fund hiring two hundred strangers in markets we don’t understand yet. That’s when I realized – if I stayed silent, I’d be complicit in a decision I knew was wrong. I’d have to look those thirty people in the eye when we let them go, knowing I could have said something and didn’t.”

The honest answer is that your body tells you, if you’re willing to listen.

There’s a difference between the tightness in your chest that says “run away” and the energy that says “this matters.” The first comes from fear of conflict. The second comes from knowing that staying silent would damage something you care about.

I’ve watched this distinction play out countless times. A CEO sits through a strategic planning session feeling increasingly uncomfortable, then suddenly speaks up with an observation that shifts the entire conversation. A parent listens to their teenager for days before finally addressing a concerning pattern. A team member watches something unfold for weeks before finding the courage to name it.

When I ask people later what made them finally speak up, they rarely say “I decided it was time.” They say things like “I just knew I had to” or “I couldn’t not say something” or “It felt wrong to stay quiet.”

In my work exploring how people create collaboration where others see division, I’ve noticed a pattern. The conflicts worth engaging are the ones where staying silent would damage something you care about – a relationship, your integrity, someone’s safety, a shared purpose.

The conflicts worth letting go are the ones about being right, winning, or proving someone else wrong.

My mentor once said, “Mediocrity is a result of a tough conversation that never happened.” Lost intimacy is another result. Every conversation you don’t have is a connection you’ve already lost.

Last week, someone cut me off in traffic on my way to a workshop, nearly clipping my front bumper. I felt irritated, my hands tightening on the steering wheel. But I let it go because engaging that conflict serves nothing – we’d never see each other again. The same day, I noticed a dynamic in one of my workshops where one person kept interrupting another mid-sentence. I addressed it gently because letting that pattern continue would have damaged the safety we were trying to create together.

You can ask your question: In the comments here. Or send me a direct message

If you want your question to stay anonymous, just tell me. I’ll keep it confidential.