The 5 Biggest Hiring Mistakes

Hiring is the highest-leverage decision most small business owners make, and most of us treat it like the lowest.

I didn’t understand that early on. I thought hiring was something you did between the real work — the sales calls, the product decisions, the fires that needed putting out.

So I rushed it. I trusted my gut. And more than once, that decision came back to cost me money, momentum, and people I actually wanted to keep.

The numbers back up what I learned the hard way. One bad hire can drag down team productivity by 30% or more.

Meanwhile, businesses with a structured, intentional hiring process are 3.5 times more likely to end up with genuinely high-performing teams. That gap isn’t about who has access to better candidates. It’s about who has a better process.

That’s really what Scientific Hiring came out of — not a theory I read about, but a set of mistakes I made enough times to finally stop making. Here are the five that cost me the most, and what I do differently now.

I used to hire on gut feel. It felt right. It wasn’t.

For years, I hired the way most small business owners do — I met someone, liked them, and made a decision somewhere in the first fifteen minutes of the conversation.

It’s not a coincidence that this is also how 81% of managers, according to Harvard Business Review, end up admitting their gut-based instincts led them straight into a bad hire.

I get why we do it. Gut instinct feels efficient. It feels like confidence. But what it actually is, most of the time, is pattern-matching against people we already like — which has nothing to do with whether someone can do the job.

The fix wasn’t complicated, but it did require me to slow down. I started building a scorecard for every role before I ever posted the job — the specific technical skills, the cultural markers, the growth potential I was actually looking for.

I started asking behavioral questions tied directly to that scorecard instead of whatever came to mind in the room. And where I could, I gave candidates a real task instead of a real conversation — a coding problem for a developer, a short writing sample for a content role — because how someone performs on an actual piece of work tells you more than an hour of charm ever will.

Companies that use data-driven hiring processes are 36% more likely to end up with strong performers. That’s not a small edge. Hiring without that structure is like driving blindfolded — you might get where you’re going, but you’re relying on luck to get there, and luck runs out.

I hired for right now. I should have hired for where we were going.

This one’s subtle, and I didn’t see it clearly until I’d made the mistake a few times. When you’re moving fast and a role needs filling, it’s tempting to hire the person who can do the job today — and stop there. I did this more than once, and it always caught up with me.

SHRM’s research says only 35% of new hires are actually prepared for the roles their companies will need a year down the line. And McKinsey has found that high performers are up to 400% more productive than average ones — not incrementally better, but categorically different in the value they create. When you hire only to fill a gap, you’re optimizing for the wrong variable entirely.

What changed for me was the questions I started asking in interviews — not “can you do this job” but “how do you handle change, and what have you gone out and learned recently without anyone telling you to.”

Adaptability and hunger show up in the answers to those questions in ways that are hard to fake. I also started mapping out, before I even opened the role, where I wanted that position to be in six months and a year — so I was hiring against a target, not just a hole in the org chart.

I know what a good answer sounds like now, because I know what I’m listening for. That’s the part most people skip.

The most technically skilled person I ever hired was also one of my worst hires.

I mean that literally. Early on, I hired almost entirely on skill — technical ability was the whole scorecard, as far as I was concerned. And I learned, more than once, that a highly skilled person who doesn’t fit your culture doesn’t just fail to help. They actively make things worse.

Columbia’s research on this is stark: companies with strong cultures see a 13.9% turnover rate. Companies with weak ones see 48.4%. That’s not a marginal difference — that’s the difference between a team that compounds over time and one that’s constantly starting over. Deloitte found something similar: employees who are aligned with their company’s values are three times more likely to stay long-term.

If you’re not sure what your culture actually is — and I wasn’t, for longer than I’d like to admit — the fastest way to find out isn’t to write a values statement. It’s to ask your own people. They’ll tell you what the company actually stands for, not what you wish it stood for.

Once I understood that, I changed how I interviewed. I started asking about real moments of conflict — “tell me about a disagreement you had with a coworker and how you handled it” — because how someone answers that tells you more about fit than any list of values ever could.

I brought candidates in to meet the team, not just me, because how they show up in a group is different from how they show up across a desk. And I started building our mission into the actual language of job postings and interviews, not just the About page.

Skill gets someone in the door. Fit determines whether they stay, and whether the people around them stay too.

“Figure it out” is not an onboarding plan. I know because I used it.

For a long time, I didn’t write real job descriptions. I hired someone, pointed them in a general direction, and assumed they’d figure it out. I called it trusting people. It was really just avoiding the work of being clear.

That instinct is more common than it should be — Gallup found that only half of employees actually understand what’s expected of them at work. Glassdoor’s data shows that clear job roles reduce turnover by 27%. That’s a huge return on something as unglamorous as writing a good job description.

What I do now is build a 30-60-90-365 day plan for every role before the person even starts, with specific, measurable goals attached to each stage — not vague aspirations, but things like “increase engagement by 20% in the first 90 days.” I review it with them on day one, so there’s no ambiguity about what success looks like.

And I check in at real intervals — first week, 30 days, 60 days, 90 days — not because I don’t trust them, but because regular, structured feedback is what keeps people from quietly drifting off course.

The version of me that skipped this step wasn’t being efficient. He was just deferring a problem that always showed up later, bigger.

I used to think onboarding ended after the first week. It was actually where the real work started.

This is the mistake that’s easiest to make because it looks like a finish line instead of a starting point. You’ve hired someone, they’ve shown up, they seem capable — job done, right? I used to think so. What I was actually doing was what I’d now call the “tribal method” — letting new hires absorb the job by osmosis, picking things up from whoever happened to be nearby.

Only 12% of employees, according to Gallup, strongly agree that their company does a good job onboarding them. And the cost of that is real — SHRM found that employees who go through structured onboarding are 69% more likely to stay three years. That’s not a soft metric. That’s retention, at scale, driven by something almost every company treats as an afterthought.

Now I start onboarding before day one — a welcome packet, a clear picture of week one, access to the resources they’ll need before they need them. I build in real feedback sessions through the first ninety days, because continuous feedback increases engagement by 4.6 times, according to Gallup — and I make sure there’s a real path for ongoing learning, since employees who get that are 94% more likely to stick around, per LinkedIn’s research.

Onboarding was never the finish line. It was the first real test of whether everything I did before the hire actually worked.