“Culture fit” is not a problem statement

Hiring discussions drift into vague language fast. One phrase does most of the damage: “culture fit.”

You hear it after the interview. Someone on the panel says, “I’m not sure they’re a culture fit.” Everyone nods. The candidate gets passed over. The team moves on to the next resume.

The problem is that culture fit is not a problem statement. It is a compressed conclusion sitting on top of an undefined concern. When you hear it after the interview, that is a signal. Not about the candidate, but about the process. The problem you started with was never complete.

The hire starts before the interview

Most hiring processes begin the same way. Someone leaves, gets moved, or gets managed out. The team says: “We need to replace Person X.” Then everyone jumps straight into scheduling interviews.

That jump is where things go wrong.

We were hiring a production manager. The panel was a mix of HR, supervisors, and department managers. We had interviewed three candidates. When we got to the debrief on the second one, a supervisor said he just didn’t see them working out. I asked what that meant. He said he wasn’t sure the floor would respect them. I asked what in the interview gave him that read. He circled back to the same place. He just didn’t see it.

Nobody else in the room pushed back. A few heads nodded. We moved on.

What that supervisor had was a model of what a successful production manager looked like in that plant. It wasn’t wrong. He had watched enough people succeed and fail in that role to know something real. The problem was that model had never been named before we started interviewing. It lived in his head and in the heads of everyone else at the table. We had interviewed three people against criteria nobody had written down, and when the debrief came, each person in the room was scoring against a different version of the job.

“They just don’t have it” was the only language available when the real language had never been established.

The lesson from that situation was not complicated: you cannot solve a problem you have not described.

Replace or change. Pick one.

When you decide to hire, you are making one of two choices, even if you have not said it out loud.

You are either trying to replicate what the last person did, because it worked and you want more of it, or you are trying to hire someone different because what the last person did was not working. Those are not the same problem. They require different criteria, different interview questions, and different definitions of success.

Most teams skip this conversation entirely. They post the old job description, assume everyone has the same candidate in mind, and start interviewing. The panel members each carry a different mental model of what they are looking for. Nobody reconciles them before the first interview starts.

Then they sit in a debrief and disagree. The word “culture fit” fills the gap where shared criteria should have been.

Most situations have elements of both. That is why you have to name them separately before the interviews begin.

The criteria you evaluate against should be decided before the first interview.

Define the problem before you define the candidate

The better move is to slow down before anyone walks into the room. This is the hiring manager’s conversation to call.

Start with the last person in the role. What worked? What did not? What gap exists on this team right now? If you are trying to replicate, say that. If you are trying to change something, name what you are changing and why.

Then move to the team’s actual concerns. If the panel is worried about ambiguity tolerance, accountability, cross-functional collaboration, or the ability to challenge assumptions respectfully, those concerns belong on paper before the process starts. Not as personality traits to hope for. As defined criteria with observable behaviors.

Now you have something to interview against. The conversation shifts from evaluating people to evaluating evidence against a defined problem.

The interview becomes evidence gathering

When the criteria are defined before the interview, the interview changes. Questions become more deliberate. Evaluators know what they are listening for. The debrief has a structure.

After the interview, three questions do most of the work:

• Can they do the work?

• Do we want to work with them?

• Can they become more than they are today?

If the answer to any one of them is no, you have a discussion point. If the answer to all three is yes, you have a candidate you could hire.

The first question is about capability. The second is about how this person operates and whether the panel can point to specific observations that support that read, not a feeling about vibes. The third is about what the interview itself revealed. How did they handle not knowing something? How did they respond to being pushed? The question is not about potential in the abstract. It is a bet on direction based on what you actually observed.

When the panel has done the problem definition work upfront, these questions are answerable. When they have not, the debrief collapses into impressions and the word “culture fit” does the work that criteria should have done.

Describe the problem first

This is not a framework problem. Most hiring managers have seen enough process documentation. The issue is that the problem was never clearly described before the process started.

“Culture fit” said after an interview is not a verdict on the candidate. It is a receipt. It tells you what did not happen before the interview began. When fit is defined upfront as observable criteria, it is a legitimate disqualifier. When it is not, it is a gap in the process, not a verdict on the candidate.

Describe the problem first. Define what you are replacing or changing and why. Name the concerns before they become conclusions. Then solve the problem.