There's one hire I made years ago that I still think about almost every week.
He was good on paper. Right industry, right experience, right energy in the interview. I needed someone to take a department off my plate and he walked in like he could do it. Six weeks in, I knew it was wrong. Not because of anything obvious. He showed up. He worked. He didn't break anything visible. He just slowly drained the room.
The customers noticed first. They didn't complain. They just stopped engaging the way they used to. Then the team noticed. My direct reports stopped bringing me ideas because every meeting got hijacked. Output went down across three departments adjacent to his, and nobody could tell me why.
I held on for nine months. I didn't want to admit I'd made a bad call. By the time I let him go, three of my best people had already left, and we were down a quarter on revenue we should have grown.
A bad hire doesn't just hurt the seat they occupy. They damage the seats around them, and the damage compounds the longer you wait.
The rule I follow now is simple. If I'm wondering at the six week mark whether someone is right for the role, the answer is already no. That's not a productivity test. It's a gut test. The high performers feel obviously right at six weeks. The ones who are going to work out fit. The ones I'm wondering about are the ones I will be removing in twelve months, and by then the damage is already done.
Three questions to ask at the six week mark.
Has anyone on the team independently mentioned this person to me without being asked? Good hires generate unprompted positive mentions. People come up to you and say, that new hire is great. Marginal hires generate silence. Bad hires generate carefully worded concerns from your most senior people, who don't want to look like they're complaining but feel obligated to flag something.
Am I avoiding any conversations because I think they'll create friction? If yes, the person is the friction, not the conversation. The conversations that matter happen in any healthy team. If you can't have a clear conversation with this person because you suspect they'll take it badly, you've hired someone whose presence is shrinking the space everyone else has to operate in.
If I had to start the search again today, would I hire this person for this role? If you hesitate, the answer is no. Don't argue yourself out of the hesitation. The hesitation is the answer.
The objection I hear from founders all the time is that they can't afford to lose someone six weeks in. They've sunk recruiting time into it. They've onboarded them. They've told the team this is the new person. Letting them go feels like admitting failure.
Here's the maths. A wrong hire at month two costs you the recruiting time and one month of salary. A wrong hire at month nine costs you the recruiting time, nine months of salary, three other employees who quit because of them, the customers they irritated, the strategic projects they slow walked, and the time it takes to find their replacement. The early call is several orders of magnitude cheaper than the late call.
I'd rather make a fast decision I'm only 80% sure of than slow walk a hire who's killing the room. Speed is the cost. Damage to the team is the alternative cost. Pick the cheaper one.
The other thing nobody talks about is what happens to your judgement when you're carrying a bad hire. You start questioning your other hires. You start second guessing your read on people generally. You spend energy managing around the person instead of building the business. The cost of keeping them is not just the salary. It's the bandwidth they take up in your head every day they're still there.
If you're reading this and there's a name in your head right now, that's the answer. The rest is just admin.
If your business is past the idea stage and you're ready to scale with capital and mentorship, applications for Founder Finds Future open soon.