Tell a Hire Is Not Working: Act Early, Learn, Move On
How to tell a hire is not working: compare the work to the ninety-day document, act within weeks, learn from the miss and know when you need a manager.
To tell a hire is not working, compare what is happening with the ninety-day outcomes you agreed, and act quickly when the gap is clear, because delay is not kindness. You will usually know within a couple of months, and the instinct is to wait.
That instinct is understandable and it is expensive. This post covers how to recognise the situation, why acting early is better for everyone, how to use the experience to make the next hire stronger and how to notice the point at which the company needs a manager and not another individual contributor.
How to tell a hire is not working without waiting for certainty
Certainty rarely arrives. What does arrive is a growing sense that something is off, and without a written reference point that sense stays vague. This is the first reason the ninety-day document matters: it turns a feeling into a comparison.
Ask three plain questions. Is what was meant to exist beginning to exist? Is the company becoming different in the way you described? Does the person own the area and make the decisions that were agreed? If you struggle to answer yes to any of them after the early weeks, and small, specific feedback has not changed the picture, you have your answer, or most of it.
| Question | If the answer is no |
|---|---|
| Is what was meant to exist beginning to exist? | Say what you see, specifically, and what you expected |
| Is the company different in the way you described? | Check whether the document was accurate before you judge the person |
| Do they own the area as agreed? | Check whether you have actually let go of it |
| Has feedback been given and understood? | If not, give it now. If yes and nothing shifted, the picture is clear |
The second and third rows are a fair test of yourself. A hire can fail because the role was described wrongly, or because the founder kept every decision. Look at those possibilities first, so that you are honest about where the problem sits.
Why delay is not kindness
The instinct is to give it more time and to hope the situation resolves. It rarely does, and the cost of waiting is paid by everyone.
| Who | What waiting costs them |
|---|---|
| The person | They are failing in a role that does not suit them while their alternatives narrow |
| The team | They absorb the gap and watch to see whether you will address it |
| You | You spend your scarcest attention on it |
The first row is the one that most contradicts the feeling of being kind. Leaving someone in a role that is not working does not protect them. It delays an outcome that is coming anyway while their options shrink.
Check what you have already done
Before concluding that a hire is not working, look at the earlier steps. Did you give feedback early and specifically, as described in how to give feedback to early hires? Did the first two weeks give the person what they needed, as in how to onboard your first employees?
If the answers are no, part of the problem may be yours, and the right step is to correct it and watch for a short, defined period. If the answers are yes and the gap persists, the decision is clearer. The aim is not to avoid blame. It is to make sure you are acting on what actually happened.
Acting decisively and humanely
When the picture is clear, act. Do it clearly, with genuine support and without pretending it was a surprise. Because you gave feedback early and held a review against the agreed outcomes, it should not be one.
This is better for everyone than a slow deterioration. The person gets the truth while they still have choices, the team sees that standards are real and you recover your attention. Any decision to end the arrangement should be made quickly and handled humanely, and you should be honest about the reasons.
Build each hire on evidence from the last
A hire that did not work is expensive. It is wasteful to pay that price and learn nothing. After each of the first few hires, review what your process actually predicted and what it missed.
- Did the work sample surface what mattered?
- Did the reference calls tell you anything you did not know?
- Was the ninety-day document accurate?
Each question points at a step in the process. The work sample is covered in how to run a work sample test, the calls in how to do reference checks, and the document in how to write a ninety day role outcome. Adjust the weak step before the next role, instead of repeating an unexamined process ten times.
What the review can teach you
| If the review shows | Then change |
|---|---|
| The task did not reflect the real work | The design of the work sample |
| The references told you nothing new | Your questions, and who you call |
| The document was inaccurate | How you describe the role before you open it |
| A concern came up twice and was explained away | Your habit of following up repeated points |
Ten hires is enough to learn a great deal about your own hiring if you look, and almost nothing if you do not. The point of looking is that the next candidate benefits from the last one.
When the problem is that you need a manager
Sometimes the issue is not the individual. Somewhere in the first ten to fifteen people, the constraint stops being capacity and becomes coordination. You become the bottleneck on decisions, context is not reaching people and everything routes through you.
In that state, hires can seem to be failing when they are really being starved of direction. The instinctive response, hiring another doer, makes the coordination problem worse. The signal to watch for is how your week is spent. If you are spending most of your time relaying context and unblocking people, the next hire is a manager or a lead.
Delaying that decision is how the founder becomes the constraint on the company they built. Treat it with the same discipline you apply to any other role: name the constraint, then choose the hire that removes it.
Accepting the honest limit
You will get one of the first ten wrong. That is not a failure of character, and it does not mean your process is bad. It means the sample is small, the information is limited and the time pressure is real. The realistic aim is a decent hit rate and a fast, humane correction when it goes wrong.
Founders who treat a mis-hire as a personal failure tend to hold on too long, because ending it feels like admitting a mistake. Those who treat it as an expected event can act promptly, learn something and carry on.
Writing down what you see
Before you speak to the person, put your observations on paper in plain terms. Note what was agreed, what has happened and where the two differ. Doing this separates what you have evidence for from what you merely feel, and it makes the conversation more precise and less personal.
It also protects you against a quieter error, which is to judge against a standard that has drifted. If the real expectation has moved and the document has not, the person is being measured by something never stated. Amend the document openly, or hold to it, but do not let the two come apart.
A short check before the conversation
- I have compared the work with the ninety-day outcomes.
- I gave small, specific feedback early, and I can say what it was.
- I have looked at whether the role, the document or my own habits are part of the problem.
- If the decision is to end it, I will say so plainly and quickly.
- I will review what my process predicted and what it missed.
If you can tick all five and the picture is still clear, you are not acting hastily. You are acting at the right time. The cost of waiting longer is paid by the person, the team and you, and none of them is helped by a slower answer.
Common mistakes
- Waiting. Delay costs the person, the team and you.
- Pretending it is a surprise. If feedback was early, the conversation should be no shock.
- Skipping the review. A miss with no learning will repeat.
- Hiring another doer to fix a coordination problem. It deepens the bottleneck.
- Blaming without looking. Check the document, your feedback and your own habits first.
Frequently asked questions
How long should I wait before deciding?
You will usually know within a couple of months. Give early, specific feedback first, and compare the work with the ninety-day outcomes you agreed.
Is it unfair to act on one bad month?
The aim is not to act on one month but on a gap you have already named, discussed and seen persist. Early feedback is what makes the decision fair.
How do I know I need a manager?
Watch where your time goes. If you spend most of it relaying context and unblocking people, the constraint has become coordination, and the next hire is a manager or a lead.
What should I do after a hire fails?
Review what the process predicted and what it missed, then adjust before the next role.
The full method, with the checklists, is in The First Ten Hires Playbook, a free 33-page playbook.