There is a version of "hire slow, fire fast" that is used as a justification for keeping people on for too long and then firing them too abruptly. That is not the mantra. That is the worst of both worlds.
The actual principle is simpler and more demanding: be rigorous in hiring because a bad hire costs far more than a vacancy, and once you know someone is wrong for the role, act quickly because delay multiplies the cost.
The real cost of a bad hire
Most founders calculate the cost of a bad hire in salary. That is the smallest part of it.
A person who is wrong for a role — either wrong for the specific job, wrong for the stage of the company, or wrong for the culture — affects the output of everyone around them. If they are a manager, they affect the output of their entire team. They occupy a slot that cannot be filled by someone better as long as they are there. They absorb founder time in performance conversations, expectations-setting, and the emotional energy of managing a difficult situation. They create risk: the longer they stay, the more embedded they become in processes and relationships, and the harder the eventual separation is.
A rule of thumb used by operators with experience: the true cost of a bad hire, over a year, is two to three times their annual compensation when you account for the productivity drag on their team, the opportunity cost of the slot, and the disruption of the eventual exit.
Knowing that, most founders still keep underperforming people longer than they should. The reasons are understandable: hope that things will improve, discomfort with the difficult conversation, guilt about the impact on the person, uncertainty about whether the problem is the person or the context.
How to hire slowly in a way that works
Slow hiring does not mean long hiring. It means rigorous hiring.
The rigor is in the definition of the role before the search begins. What does success in this role look like at 30, 60, and 90 days? What specific outcomes does this person need to produce? What are the three to five things they need to be genuinely excellent at, as opposed to merely good at, for this role to succeed?
With that definition in hand, the interview process should be designed to test for those specific things. Not general intelligence, not culture fit in the abstract, not impressive career history. The question at every stage is: does the evidence suggest this person can produce the specific outcomes this role requires?
References are not optional. Not the ones the candidate provides — those will be uniformly positive — but the ones you find yourself by asking people you know who have worked with the candidate, or by going one degree of separation beyond the provided references.
How to fire fast without making it brutal
Fast firing does not mean impulsive firing. It means that once you have a clear and honest assessment that someone is wrong for the role — not a bad week or a difficult project, but a consistent pattern over a meaningful period — you act on that assessment rather than hoping it changes.
The conversation should be direct, specific, and respectful. Here is what was expected. Here is what happened. Here is why this is not working. Here is what comes next.
Most difficult firing conversations are made worse by vagueness. Managers try to soften the message to the point where the person being fired is not sure what is happening. This is not kindness — it is discomfort avoidance dressed as kindness. The person on the other side deserves clarity.
The practical question of timing: act before a natural inflection point in the business cycle — before a fundraise, before a key project launch, before a critical hiring period — rather than during it. The disruption of a departure is real, but it is almost always less than the disruption of keeping the wrong person through a critical period.
The culture of performance is the product
A startup's performance culture is visible in one number: the time between when a founder recognizes that someone is wrong for a role and when they act on that recognition.
Short lag times signal that standards are real and consequential. Long lag times signal that standards are aspirational and that underperformance is tolerated. Both signals are received clearly by the rest of the team, even when nothing is said explicitly.
Building a team of genuinely high performers requires maintaining standards consistently. That means both rigorous hiring and decisions on underperformance that are made promptly and handled respectfully.