Afraid of the Reaction

A CEO I was coaching wanted to let their first engineering hire go. This person didn't take ownership, the CEO told me, couldn't be trusted with the harder calls, had become the kind of drag on the team everyone could feel but nobody named out loud. They had been in the room since the beginning, one of the first hires, and they had helped build the thing from nothing.

I asked about the file before I asked about the engineer. What had the CEO told the engineer, in writing, about what they expected, and when? There was nothing: no documented feedback, no clear standard, no record of a single conversation about what "better" would have looked like, nothing behind the CEO's certainty except the certainty itself.

I used to think this was an HR problem, and it partly is. In an at-will state, a company that fires someone with no documented history is exposed to a wrongful-termination claim, and it usually finds that out only once a lawyer is already involved. But I treated it as a compliance gap, and missed the part that mattered. The CEO hadn't skipped the file for lack of time. They'd chosen, every week for months, not to fill it in.

This CEO would tell you they were busy, or that they kept hoping the engineer would improve on their own, or that they didn't want to come across as a hard-ass. None of that was the real reason, and by the third conversation, they knew it too. They didn't want to sit in a room with someone they'd hired personally, in the earliest, hardest days of the company, and watch that person's face change when they heard the honest version of how things were going.

You can't have that conversation for real without absorbing another person's disappointment, or anger, or tears, in real time, with no script to hide behind. There's no template for that moment. You either sit in it, or you find a reason to leave the room before it starts. They were avoiding the fifteen minutes where someone else's face falls in front of you, on purpose, because of something you did.

The gap in the file wasn't a missing fact. This CEO hadn't built the steadiness it takes to set a standard out loud, in front of a real person who might react badly. Some people can sit in a room while someone else's face falls and stay clear about what needs to be said anyway. Most people can't, not without practice, and this CEO hadn't had the practice.

A few years ago I worked with a leadership team on a strategic plan. Three months later, they were running the company exactly the way they had before I started: the same frenetic, haphazard scramble from one urgent thing to the next, plan or no plan. I could see the culture was a direct reflection of the CEO's own style, and their own dysfunction, and another draft of the plan wasn't going to change how they ran the room.

I let it go. If I'd said it directly, I would have had to tell the client the real problem in the building was them, not strategy. They hadn't hired me to say that, so I didn't.

I've told myself different versions of why, over the years. I was protecting the relationship. It wasn't my place. The engagement was almost over anyway. All true, and all beside the point. I was avoiding what the CEO was avoiding: if I'd named it out loud, I would have had to watch someone's face change in real time, and I didn't want to be the one who caused that, even when it was true, even when they were paying me specifically to tell them true things.

A team feels the cost of one avoided conversation well beyond that single moment. It watches a low performer never get addressed, and draws the only reasonable conclusion available: the standard the rest of them are held to doesn't apply, or nobody enforces it, or it was never real to begin with. The people picking up the slack start to resent it. Nobody says anything about that either, for the same reason the original feedback never got said: nobody wants to be the one who starts that conversation.

A leader who avoids the hard conversation doesn't get rid of it. They just have it later, after it's grown, at a higher cost. What could have been fifteen uncomfortable minutes with one person becomes a team that's decided the leader can't be trusted to enforce anything. Or a resignation nobody saw coming. Or a wrongful-termination claim with a very good case. The leader was always going to have it. The only real choice was when, and at what size.

You can't fix this by telling someone to be braver. Whatever this CEO was avoiding, the pattern was so old and so automatic that no one could talk them out of it in a single conversation. You can't talk someone out of flinching before they've had a chance to notice they're doing it. The pattern formed early, for good reason at the time, and it kept running long after the reason stopped applying.

A pep talk didn't help. Practice at a smaller scale did: a minor correction with someone lower-stakes, a small disagreement held instead of smoothed over, none of it dramatic enough to justify avoiding. By the time we finally wrote the standard down together and rehearsed how to deliver it, the CEO had already survived several smaller versions of someone's face falling.

The CEO did eventually have the conversation with the engineer. Not easy, not comfortable, but fine. The engineer already half-knew. Everyone half-knows, before you ever say it.

I was never asking about the file, or about the engineer. It came down to whether the CEO could sit still while someone else's face changed because of something they'd said, on purpose, and not need to fix the feeling in the room before they could finish the sentence. That's the skill missing from most performance conversations that never happen, and it's not one you find out you have until the day you're forced to use it.