- A bad hire costs one to two years of salary once rework, management time, and the re-hire are counted.
- Speed pressure produces the specific failure it is trying to avoid: an unfilled seat, six months later.
- Slowing down by two weeks is cheaper than being wrong by six months.
An open seat feels like an emergency. Work is piling up, the team is stretched, and every week the role stays unfilled reads as a week of lost output. So the process accelerates: fewer interviews, softer references, a candidate who is "good enough given the timeline." Eighteen months later the seat is open again, and the team is worse off than if it had stayed empty.
The arithmetic nobody does under pressure
The cost of a wrong hire is not the salary. It is the salary plus the recruiting cost paid twice, the three-to-six months of below-par output, the manager hours spent coaching and documenting, the work redone by teammates, and the morale tax on the people who carried the load. Sum it honestly and a mis-hire in a mid-level role costs one to two years of salary. Against that number, an extra two weeks of process is not slow. It is the cheapest insurance available.
Why the damage exceeds one seat
Strong performers calibrate against their weakest colleague. When a rushed hire underperforms and stays, because firing quickly is exactly as uncomfortable as hiring slowly, the team learns what the real bar is. The best people quietly recalibrate their effort or their tenure. A manager who cannot bring themselves to say no to a marginal candidate is making the same trade as the manager who cannot say no to anything: comfort now, paid for by the team later.
Fast process, slow decision
The useful distinction is between administrative speed and decision speed. Compress the scheduling, the feedback loops, the offer paperwork; candidates deserve a process that respects their time. Do not compress the evidence: a real work sample, an interview panel that includes the people who will work beside the hire, and reference calls where someone actually listens for hesitation. Teams that separate the two get both a fast candidate experience and a sound decision. Teams that conflate them get neither.
Frequently asked questions
How long should hiring for a key role take?
Long enough to see real evidence: a work sample, multiple structured conversations, and
honest references. For most roles that is four to six weeks of calendar time, most of
which can run in parallel.
What is the strongest predictor of a good hire?
A relevant work sample evaluated blind, followed by structured interviews with
consistent questions. Unstructured conversation is the weakest signal and the most
commonly used one.