Chloé for Unsplash+
Knowing when to say the thing and when not to say the thing is harder than it sounds. I learned the second half the hard way.
Most of us don’t struggle to see issues, we love pointing them out (especially when they aren’t about us). The harder part is deciding whether what we see is actually worth airtime. Early on, it’s very easy to confuse urgency with importance, especially when the thing in front of you feels big and loud.
I’ve learned that just because a thought is loud doesn’t mean it’s vital. Sometimes it’s loud because it’s emotional. Sometimes it’s loud because the person telling it is right next to you. Loudness has a way of masquerading as importance, but important things tend to be quieter. They show up in outcomes, secondarily. The best tell is seeing what happens after the conversation everyone is focused on.
When speed becomes sabotage
The hardest part of waiting isn’t fear… it’s the itch. I used to equate usefulness with immediacy. If I saw the issue, I felt responsible for saying it right then. Speed became proof. Observation, obligation.
I remember one time I was watching my team wrestle with a design problem. I could see the larger structural issue three steps ahead that would eventually make their current work unnecessary. My instinct was to run in and proclaim the bigger truth. I wanted to save them time and show my importance.
But by pointing at the horizon I’d only help them trip over their own feet.
If I chimed in at that moment, they’d lose the flow of the problem they actually had to solve. They would stop thinking about the design and think about project management, which was mine to hold, not theirs. I was trying to offload my vision so I didn’t have to carry the discomfort of watching them think.
I call this the “Hot Potato” instinct. It’s a behavior that’s relief-seeking disguised as leadership. You aren't giving the team a vision, you’re handing them a problem you’re tired of holding so you can clear your own plate. When you toss that big picture issue over the fence before they’ve finished the task at hand, you haven't solved anything. You’ve just diluted their focus and traded their momentum for your own peace of mind.
Upgrading the standards
Saying the thing is often about ego, not courage.
Teams often need better signal, not more information. Every unnecessary input, no matter how accurate, taxes attention. I’ve started holding myself to a simple standard. I only say the thing if I believe it serves the business, not my comfort. If even one percent of the reason I want to say the thing is to prove I’m perceptive or to offload a thought I’m tired of carrying, I wait.
Restraint takes discipline because you have to live with the discomfort of not speaking, knowing you could. But when you prioritize impact over noise, your words gain weight. Over time, people learn that when you finally do speak, it’s because it matters. And they listen.
Knowing when not to say the thing is judgment.
Knowing when to say the thing… comes next week.
The Editor’s Note: If today’s brief felt 🥴 I want to know why. Hit reply and tell me because I only want to write newsletters that reduce operational drag, not add to it!
Affiliate Link Disclaimer: Some of the links in this email are affiliate links, which means I may earn a small commission if you buy through them, at no extra cost to you.