Hire Slowly, Fire Quickly Is Right. Almost Everyone Reads It Wrong.

“Hire slowly, fire quickly” might be the most repeated piece of startup advice that nobody actually follows correctly.

People hear “hire slowly” and build a process that drags for months. They hear “fire quickly” and assume it means cutting people who underperform on a spreadsheet.

Both readings miss the point, and getting them wrong has cost me real money and real teams.

Let me unpack what the cliche actually means after thirty years of building companies.

“Hire slowly” does not mean a slow process.

It means a rigorous one, run at speed. These two things get confused constantly. When I identify a candidate worth pursuing, I move fast, because their time is finite and good people are always being courted by someone else. A slow calendar is not discipline. It is just disorganization wearing a serious face.

My rule is simple. Once a candidate is in the pipeline, we close the interview loop within two weeks and reach a decision within six to eight. That matters even more in a startup, where so many hires are high-profile by nature. On a small team, one person can move the entire trajectory of the company, for better or worse.

The rigor lives inside that timeline, not outside it.

For twenty years, I have put candidates through a personality assessment called the Wonderlic. I do not use it to disqualify anyone. I use it as a data point I bring into the first real conversation. If the test flags a potential friction point for the role or the team, I raise it directly and give the person a chance to address it.

Sometimes the test is wrong, and a few minutes of honest discussion proves it. A lot of the time, the test is pointing at something real, and the times I have ignored those signals are the times I have regretted it most.

For candidates who clear the early screen, we pay them to complete a case study.

People are surprised by that. But compensating someone for serious preparation costs a rounding error compared to the cost of a bad hire and the cleanup that follows.

The case study tells me more about how someone actually thinks and works than any number of conversations across a table.

Now the other half. “Fire quickly” is the part people get squeamish about, and it is the part that has mattered most in every company I have built.

Here is the reframe.

1. The hires you need to move on from fastest are rarely the incompetent ones.

2. They are the ones everyone agrees are talented, but who are toxic inside a team.

I have seen people universally described as highly competent who were completely nonfunctional in a real business environment.

That combination is the most dangerous hire there is, because their competence buys them patience they should never get, and while you extend that patience, your genuinely productive people are paying the bill.

Personality and behavior have been the bigger problem in my career, by far, more than raw skill.

• The unproductive hire is easy to see and easy to address.

• The talented one who poisons the room is the one that quietly does the damage.

I have lived this in every business I have run. Recently at PerkyPet, with a small and young team, I terminate someone for genuinely bad behavior. The moment they were gone, the team’s productivity shot up. The people who had been absorbing the friction could finally do their jobs.

I learned it the hardest way at AlertBoot.

Early on, I had a leadership and sales hire who turned out to be bad for the team. I waited longer than I should have, but I needed time to be 100% sure. Once we finally made the change, we grew the company more than 100x from that point, with a team that was suddenly far more productive.

That growth did not happen despite the termination. It became possible because of it.

So yes, hire slowly and fire quickly. But hire slowly means rigorously, not sluggishly. And fire quickly means protecting your best people from the talented person who is quietly making everyone worse.

Being a leader is so much more than evaluating technical competence. The sooner you internalize that, the sooner your real players get to win.

Over the past weeks, I’ve been sharing lessons from three decades of building technology companies.

Four weeks ago, we unpacked the lessons that 30 years of building companies can teach about leadership, growth, and resilience.

Three weeks ago, we explored why trust isn't built during a crisis — it's built long before one arrives.

Two weeks ago, we questioned a popular startup practice and discussed what meaningful customer collaboration actually looks like.

And last week, we took a closer look at market assumptions and why founders should be skeptical of numbers that look too good on a slide.

Next week, I’ll share another lesson from the realities of building technology businesses, products, and teams that last.

Subscribe to get the next post the moment it goes live.