You can't say nothing

Next time you're triggered in a meeting, remember: the punch you think you're pulling still lands, and has even more weight than if you'd actually said something. Because the team learns two "unsaid" but blazingly real truths. 1) You're the type of leader that has minefields. 2) And you just showed where one of them is located.

Here's what you have to assume, always: your team feels what you don't say. When you pull back from a hard conversation, a truth still gets communicated, and your team learns to hide theirs from you.

You pull back for a reason that sounds responsible. You withdraw to avoid doing something rash in the heat of the moment. But the rash thing is the withdrawal. It signals eggshell territory, and it is detected anyway.

So what is the withdrawal protecting? Exposure. Your real state, maybe portrayed imperfectly. It is a form of nakedness, and no moment feels like a good moment for it, so the "not now, not like this" urge is overwhelming. What gets tried instead doesn't hold. Changing the way you feel. Trying to let it go. Trying not to be bothered.

The amount of tension you leave unnamed sets the amount of candor your team withholds. Decision quality plummets along with engagement, because less candor means worse information behind every decision. It is a breathtaking tax on the decision to "not make a mistake in the heat of the moment", and it is much costlier than the mistake.

You can either have a plan for how you will draw attention to something going on beneath the line, or you allow a culture to create itself, where the gorillas are never named, and therefore hold all of you hostage. It's a culture of tiptoeing, where the goal is no longer growth or challenge, but not triggering hidden tripwires.

What can you do instead?

The script. Design the general response in advance so the hot-state risk is removed. It can sound like this:

"Hey, team, can we pause for a moment? I just want to flag my perspective on what occurred. I heard something that I didn't like hearing, and I think I showed some irritation instead of speaking up. I know our best work depends on us being able to fearlessly exchange ideas, even at the risk of it not being easy to hear... If and when our openness stalls, let's stop and talk about it rather than let the unsaid hold the room hostage. So I held back just now. Here's what I want to do instead. I want to explore the ideas further. Can we circle back?"

The minimum. There's never a situation when you can afford to say nothing. When the moment really is wrong, the minimum you can get away with: "Hey, I think some tension just showed up. This doesn't seem like an ideal moment to deal with it. Let's talk about it at [specific date and time]."

Sets and Reps. The only answer is exposure. You have to get the "doing it badly" phase out of the way because it's not possible to get it right without first getting it wrong and then fixing it. The delay impulse is an infinite loop. You delay because you are not ready, but the only way to be ready is to choose a moment to stop delaying, make some mistakes, fix them, and move on to doing it well.

What could your script look like for what you'll say next time you're tempted to say nothing?

Best,

C

If there's a gorilla in your room right now, it can help to plan the naming with someone outside the room. 30 minutes, here: https://calendar.app.google/oggFtXP2xHFxDzZW9

Subscribe to The Work Beneath the Work

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe