WorkforgeSlow hiring is rarely caused by one broken step. It is usually the accumulation of small delays that nobody owns: a scheduling gap here, a late piece of feedback there, an approval waiting on someone who is travelling. Each delay looks reasonable in isolation, which is exactly why the total goes unexamined.
The cost is real but hard to see. You do not get an alert when a strong candidate accepts elsewhere. You simply never hear from them again, and the role stays open.
Here are five signals worth taking seriously.
1. Your strongest candidates withdraw before the final stage
Pay attention to who drops out, not just how many. If withdrawals cluster among your best-qualified applicants, speed is likely the cause. The most capable candidates usually have other processes running, and they tend to accept the offer that arrives first with reasonable terms.
When weaker candidates drop out, that is often self-selection working correctly. When strong ones do, you are losing races you did not know you were in.
2. Nobody can answer "where is this candidate right now?"
Ask three people involved in a live role what stage a specific candidate is at. If you get three different answers, or someone has to check their inbox to reconstruct it, the process has no shared state.
Without shared state, delays become invisible. A candidate can sit untouched for a week because each person assumes someone else has the next action. Nothing is escalated, because nobody knows there is anything to escalate.
3. Interview feedback arrives late, and in prose
Two problems usually travel together here. Feedback is slow, and when it arrives it is unstructured commentary rather than an assessment against the criteria you agreed on.
Late feedback stalls the next step directly. Unstructured feedback is worse in a subtle way: it forces a second round of discussion to work out what the interviewer actually meant, and it makes candidates hard to compare. You end up deciding on recall and impression rather than evidence.
4. The bar moves while the process is running
If the definition of a strong candidate shifts between the first and fourth interview, everyone before the shift was assessed against a standard that no longer applies.
This shows up as reopened debates, extra "just to be sure" conversations, and requests to see more candidates when the real problem is that the requirements were never settled. Time spent re-litigating the brief is time the candidate experiences as silence.
5. Scheduling consumes more calendar time than deciding
Track the difference between elapsed time and active time for a single hire. Active time is the hours actually spent interviewing, reviewing, and deliberating. Elapsed time is how long it took start to finish.
When elapsed time is many multiples of active time, your constraint is coordination, not judgement. Adding more interviews or more reviewers will make it worse.
Where to start
Resist the urge to redesign everything. Two steps usually surface the real problem:
- Measure elapsed versus active time on your last three hires. This tells you whether you have a decision problem or a coordination problem, and those need different fixes.
- Write down the stage definitions and the decision criteria before opening the next role, then do not change them mid-process. If they turn out to be wrong, finish the round and fix them for the next one.
Most teams discover their bottleneck is coordination rather than assessment. That is good news, because coordination problems are more tractable than judgement problems. They mostly require agreeing on who owns the next action, and making the current state visible to everyone who needs it.