Something in the business is breaking. Sales are inconsistent. Jobs are falling behind. The floor keeps calling you with questions nobody else can answer. So you do what feels like the responsible move. You hire someone whose title matches the pain.
Six months later the pain is still there. Sometimes it's worse, because now there's a salary attached to it.
I see this pattern often enough to give it a name. It isn't a hiring problem. It's a sequencing problem. You hired a person to fill a job that was never really a job. It was a set of decisions that only ever existed in your head, and no title fixes that on its own. Before the next one, six questions worth answering honestly.
- If this person started tomorrow with zero access to you for two weeks, could they still do the job?
- Is there a written answer for how the last five hard calls in this role got made, or does that answer only live in your head?
- Are you hiring to remove a decision from your plate, or to take on work that's already been made repeatable?
- Could you grade this person's first month against a written standard, or only against your own gut?
- If they lasted six months and then walked, would the next person start from zero too?
- Is this actually a capacity problem, or a knowledge problem wearing a job posting?
If more than two of those answers only live in your head, the rest of this piece is what that costs the person you hire.
What actually happens
The new hire shows up ready to work, and the first thing they run into isn't a task list. It's a wall of context they can't see. How a job actually gets priced here. Which vendor gets the call when the usual one falls through. What a client really means when they say it's urgent. None of it is written down anywhere, so the only way to learn it is to ask you, over and over. The hire was supposed to take questions off your plate. Instead it added a new person asking them.
The risk just moves
A talented hire finds a way through this anyway. They shadow you, take their own notes, and slowly build a private version of the knowledge you never wrote down. Once they have it, something shifts. You're no longer the single point of failure. They are. The risk doesn't disappear. It just moves to someone with a resignation letter.
The wrong conclusion
A less fortunate hire doesn't find a way through it. They struggle, get quietly written off as not a fit, and leave within the year. You conclude that good people are hard to find right now. The real conclusion is narrower and less comfortable. The hire isn't the problem. The timing is.
The pattern has numbers behind it. Roughly three in ten new hires are gone inside ninety days, and the most common reason they give is that the day-to-day role was not what they expected. The role in their head never matched the one that existed, because the one that existed was never written down.
The job has to exist first
A hire should be stepping into a role. If they're reconstructing that role out of your head while they're supposed to be doing the job, the job description was never the missing piece. The documentation was. The order of operations behind this, documenting judgement before handing out authority, is the argument of The Owner Is The Ceiling, and this is what it looks like on the payroll.
The fix has numbers too. Organizations with a strong onboarding process improve new hire retention by 82 percent and productivity by over 70 percent, per Brandon Hall Group research. Strong onboarding is mostly documentation with a start date.
None of this is an argument against hiring. It is an argument about order. Write the role down first, then hire into it, and the salary you were already going to spend starts buying what you thought it was buying.