What Is a Culture Casualty in Hiring?

“He can say he’s not corporate, but that’s corporate”

A client was working through a senior hire who had checked every box. Experienced, credentialed, said all the right things about moving fast and rolling up his sleeves. Then the day-to-day started telling a different story. He cared about title. He was very by-the-book, very hierarchical. He wanted process where the company needed speed.

Here’s the line that named it: he can say he’s not corporate, but that’s corporate. The behavior is the truth. The interview answers were the marketing.

Nobody set out to hire a misfit. That’s why I call them casualties, not villains. The hire is often genuinely talented and genuinely trying. But their operating preferences, the ones nobody surfaced in the interview, collide with how your company actually runs. And because they’re mission-critical, everyone works around them instead of naming the problem.

Why one casualty is expensive

You didn’t hire a bad person. You hired someone whose defaults fight your company’s defaults. That fight has a daily cost:

• Decisions that used to take a conversation now take a meeting, a deck, and a follow-up.
• Your fastest people start routing around the new hire, which means the org chart and the real workflow no longer match.
• Junior employees watch the misfit’s behavior and learn that title and process are what actually get rewarded here.
• You spend leadership energy managing friction instead of building.

In a high-speed company, speed is the culture. Anyone who quietly re-installs bureaucracy is diluting the thing that makes you win, even while hitting their functional targets.

How to spot one early

• The interview answers were fluent, but the first ninety days keep producing small surprises about how they like to work.
• They ask about title, reporting lines, and approval authority more than about the mission or the customer.
• They add a step to processes that used to be one step.
• Peers stop bringing them into fast-moving decisions, and nobody can quite say why.
• You hear yourself explaining or defending their behavior to the rest of the team.

What to do about it

First, name it fast. A culture casualty compounds; the longer they operate, the more the team reorganizes around their preferences. Have the direct conversation about what the behavior is saying, not what the interview said.

Second, decide honestly whether it’s coachable. Some people genuinely didn’t know how the company runs and adjust once expectations become explicit. That’s a fixable gap between unspoken expectations, and the fix is to make the invisible visible. Others reveal that title and control are what they actually want. That’s DNA, and DNA doesn’t change on your timeline.

Third, fix your intake. Culture casualties get through because interviews test what people say, not how they operate. Probe for how they made decisions, what they did without permission, what process they killed rather than created. Ask for stories where speed beat polish. The pattern in the stories is the real resume.

Where it connects

The unspoken expectations that let a casualty through the interview are Invisible Collisions™: nobody said what they expected, and now everyone’s surprised. The habits and standards a casualty erodes are part of your company’s Invisible Operating System. And a casualty on the leadership bench is one common answer to why your leadership team isn’t leading.