The real cost of a poor hiring decision

Some hiring problems announce themselves quickly. Others become visible through work the team starts doing twice. A meeting needs another meeting to settle the same question. A decision is reopened a week later. A colleague checks a piece of work before it reaches the client, then gradually takes over finishing it.

These are reasons to investigate. They are not enough to conclude that the new person is the problem. The role may be unclear, training may be missing or two managers may be asking for incompatible results. What matters is that the work is not happening as intended and other people are absorbing the difference.

That difference can stay hidden because people are trying to help. The client receives an acceptable result, so the extra effort doesn't appear in the complaint log. A manager completes a task at night, so the missed deadline doesn't appear in the report. The apparent result can look better than the process producing it.

This is why the cost of a mis-hire needs a closer look than adding up salary and a recruitment fee. You need to understand what happened to the work, the people doing it and the decisions that followed. You also need to leave room for the possibility that the business failed to provide the conditions it promised.

People may start to distrust handovers when they repeatedly receive incomplete work. They may become reluctant to take a promise to a client because they no longer know whether it can be kept. Those effects matter even when you cannot price them reliably.

Extra work is another warning. Sometimes a colleague volunteers because they have spare capacity or want to help someone learn. Sometimes the help becomes a continuing second job. Ask what changed, how often it happens and what it displaces. Don't assume that a capable person will always absorb it without complaint, or that somebody who speaks up is less committed.

I have spoken with leaders who became less confident after a poor hire. A later decision feels harder because they can still explain why the earlier one seemed sensible. That uncertainty can be useful if it leads to better checking. It can also lead to avoiding a necessary hire or demanding impossible certainty from the next candidate.

For the person in the role, repeated failure can be discouraging and humiliating. They may be trying hard at a job that was described inaccurately, missing support they expected or discovering that a capability they thought would transfer needs further development. None of those possibilities is resolved by telling them to show more ownership.

You don't need to diagnose their mental health to take that seriously. Ask about the work, the expectations and the support. Let them choose what personal information to share. Record the employment issue you can act on rather than speculating about what is happening inside their head.

Keep an account of these effects in ordinary language alongside the cost estimate you make. Which commitments became less reliable? Who carried additional work? What has the employee said about the gap between the promised role and the actual one? You can then consider a response without pretending each consequence has a price tag.

Costs you can record

Start with spending you can identify. An additional recruitment fee, paid temporary cover, repeated training or a client credit may be directly attributable to the problem. Keep the invoice or record and note why you have included it. Money already spent on productive work should not automatically become a loss because the employment later ended.

Then examine time. How much work had to be repeated? Who repeated it? How much additional management time did the problem require? An estimate can be useful if its basis is visible. The point is to understand the scale of the problem, not produce a falsely exact total.

Next, look at delayed or lost work. A postponed project may have delayed revenue, reduced margin or simply moved delivery to a later date. Those are different consequences. A client leaving may have several causes. Write down what is known, what is estimated and what cannot fairly be attributed to this hire.

The iceberg image is useful here as a reminder to look beyond the invoice. You still have to establish what the first count missed, how large those costs are and which can reasonably be expressed in money.

An estimate that doesn't count the same loss twice

The following example is invented to show how to calculate, not a typical cost of a bad hire. A business has paid $2,000 for temporary cover. It also records 20 hours of colleague rework and 10 hours of additional management time, valued for this exercise at an internal cost of $50 an hour. The recorded spending and estimated time cost total $3,500.

The time figures are not additional cash paid unless they created extra paid hours. They describe capacity used on this problem instead of something else. Label that distinction so the estimate cannot later be quoted as $3,500 of new expenditure.

Suppose the same rework delayed another project. You could estimate the margin lost through that delay instead of valuing the displaced hours. Do not automatically add both estimates. If they describe the same lost capacity, doing so counts the loss twice. If there is a separate, documented consequence, such as a contractual client credit, show it separately and explain the relationship.

Nor should you add the person's entire salary as a loss while ignoring useful work they completed. Salary, rework and lost output can overlap. Ask which cost arose because the intended result was not achieved, compared with a realistic alternative. That alternative might be a different hire, temporary cover, a redesigned role or leaving the position open for a while.

You don't need a complicated model. Use four columns: item, basis, amount and confidence. Separate cash spending from estimated time or lost margin. Add a note about possible overlap. Where you cannot make a defensible estimate, describe the consequence instead of inventing a number.

This estimate is a management aid, not proof that one person caused every problem around them. Review it with someone who understands the work and will challenge your assumptions. If you are using it to compare options, use the same rules for each option.

Urgency can make the next decision worse

When a role is not working, the backlog grows. The manager becomes more desperate for relief and the next search starts under greater pressure. That pressure can encourage the same shortcuts that contributed to the original problem.

That is the risk I call the Hiring Death Spiral: urgency can reduce investigation, weak investigation can leave requirements untested, and a poor decision can create more urgency.

There are several places to interrupt it. You can reduce or delay lower-priority work. You can arrange temporary cover for a specific task. You can give the team a clear account of what will not be delivered while the vacancy remains open. Those choices have costs, but they may buy the attention needed to make a considered decision.

Use any time you gain to improve the evidence. Extra weeks spent waiting for approvals or repeating interviews may add nothing useful. What matters is whether the process gives you the evidence this role requires at a reasonable cost to everyone involved.

Before starting again, write down what you learned from the previous attempt. If the issue was unclear authority, decide how authority will work. If a skill was missing, specify how the next process will assess it. If the work itself changed, revise the role. Otherwise a new person inherits the same unresolved problem.

The risk follows the responsibility

Small businesses can be particularly exposed when one person holds a large share of a critical capability or relationship. There may be no spare manager to supervise closely and no second team to take over the work. A founder can end up trying to run the business while quietly covering the role that was meant to free their time.

But headcount alone does not measure that risk. One person in a team of five is a fifth of its people, not necessarily a fifth of its output. A senior hire in a large organisation can affect many teams. A specialist responsible for a crucial system may create a risk that cannot be averaged across the payroll.

Ask where the work depends on one person, how quickly a problem would become visible and what the business could do in response. You may need a better handover, clearer checks or a deputy as well as a better selection process. Hiring carefully does not remove the need to design work that can tolerate mistakes and absence.

A people or operations leader may see this cost before anyone agrees to spend money on changing the process. You do not need an alarming estimate to make the case. Show which work is being repeated, who is carrying it and what it prevents them from doing. Keep that separate from costs the business would have incurred anyway. The person deciding the budget then has a specific problem to weigh against the cost of investigating it.

There is a smaller starting point. Define the result and conditions, agree the essential requirements, collect relevant evidence from a manageable shortlist and record the trade-off behind the decision. Chapter 9 shows the sequence, and the toolkit gives you teaching forms to use. The depth should reflect the role's consequences, not a fixed number of meetings or a claim that every vacancy needs the same programme.

A poor result has more than one explanation

It is tempting to decide that the person was a bad hire in some permanent sense. It can be equally tempting to insist that every failure is a capable person in the wrong setting. Both explanations are too easy if you have not examined the work.

A capability gap is one possibility. The person may not yet be able to do an essential part of the job. A mismatch between expectations and actual duties is another. The business may have provided inadequate support or changed the role after hiring. Personal circumstances can change too. Misconduct requires its own response and should not be disguised as a problem of fit.

Consider a hypothetical operations manager moving from an established company into a small agency. They may know how to improve an existing process but have less experience creating one while managing daily delivery. The agency may also expect them to decide priorities that the founder is unwilling to delegate. Training could address the first gap. It cannot, by itself, resolve the second.

If you call both problems a lack of initiative, the employee receives feedback they cannot use and the founder avoids a decision about authority. If you assume context explains everything, you might ignore a genuine capability requirement. A useful diagnosis distinguishes the problems and tests what could change them.

Use the cost to choose a response

Once you have an account of the problem, compare realistic next steps. Clarifying responsibility may be enough in one case. Another may need training, a change in duties or an honest decision that the role is not workable for the person. Waiting is also a decision, with consequences for the employee and the team.

State what you expect each proposed change to achieve and when you will look again. If the problem is repeated rework, define which errors should reduce and who will provide support. If approvals are blocking delivery, identify who can change the approval route. A general promise to improve communication is too easy for everyone to agree to and too vague to assess later.

Be careful with the comparison to leaving the role empty. A vacancy has costs, but a person who contributes useful work while learning should not be treated as equivalent to nobody. Compare actual alternatives. You are trying to choose a responsible response, not assemble a case for the conclusion you already prefer.