You know what you need. A plant that runs smoothly. Operations that are efficient. A team that adapts when things change.
What you don't know is what skills that requires.
So you do what every company does. You write a job description. Five years operations experience. ERP proficiency. Leadership background. Lean manufacturing familiarity. It reads like a specification. It feels concrete.
It's a guess.
The Problem Isn't Hiring. It's That Skills Are Moving Targets.
Bad hires in mid-level operations roles cost $100,000 to $200,000. That's recruitment, onboarding, lost productivity (18% of salary annually), overtime, quality issues, the ripple through your best people. But the cost isn't the problem. It's the symptom.
The real problem is that you're hiring for skills that won't matter in eighteen months.
A plant manager hired someone three years ago to manage an ERP system. That person spent months learning the software, becoming proficient, building company knowledge around workflows and configurations. Today, the company is evaluating a new ERP system. Why? Competitive pressure changed. The platform evolved. The business priorities shifted.
The skill that person developed is now a liability. They have to unlearn what they became expert in.
This is not exceptional. This is the baseline now.
Here's why: the world is changing faster than it ever has. The Agricultural Revolution took 10,000 years to mature. The Industrial Revolution took 200 years. The Information Revolution took 50 years. The mobile revolution took 15 years. AI went from research to ubiquitous tool in under five years. Multimodal AI capabilities are advancing monthly.
Within AI itself, the compression is even sharper. Expert systems took 40 years. Machine learning matured over 20 years. Deep learning took a decade. Large language models went from research to consumer products in three years.
Your company operates in an environment changing 40 times faster than the Industrial Revolution. But your hiring process assumes skills are stable.
They're not. They haven't been for years. You just hired like they were.
Why Job Descriptions Lie
You need someone to run the plant. That's the outcome. It's clear. It's the right thing to hire for.
But running the plant in 2026 is different than running it in 2023. The tools change. The processes evolve. The competitive landscape shifts. The vendor you relied on gets acquired. The supply chain you optimized around breaks.
Someone who mastered the 2023 version of the job is not prepared for the 2026 version. They might be actively unprepared — muscle memory from the old system becomes a liability in the new one.
So what do you hire for? You default to what you know. The last person who ran the plant successfully had ERP experience and lean background. So you list those as requirements. You're describing yesterday's success as if it predicts tomorrow's performance.
It doesn't.
The recruiter feels this problem. They can't find someone who perfectly matches the description because the description was never accurate. It was always an approximation of "someone who can figure things out." But recruiting doesn't work that way. Recruiting requires certainty. So recruiters bend the narrative, candidates oversell fit, and everyone pretends the job description means something.
It doesn't. Trust collapses. 43% of job seekers ignore recruiter outreach entirely. Hiring managers catch candidates gaming AI systems. Candidates are using AI to bypass screening because they know the screening is for jobs that are already changing.
Everyone knows something is wrong. Nobody admits the job description is the problem.
Why the Timeline Breaks
You post the role, screen, interview, negotiate, onboard. If you're efficient, that's 60-90 days. A referral is faster, maybe 30 days. But onboarding is still 90 days before someone is productive.
That's 120-180 days.
In that window, the manufacturing landscape has shifted. The skills your hiring manager said were critical three months ago no longer matter. The tool your operations person was hired to manage has been replaced or integrated.
You're optimizing for a hire that's already half obsolete before they start.
Referral hires are fundamentally better. They convert at 20% versus 1.2% for traditional applicants. But the timeline hasn't changed. The source quality improved, not the underlying problem.
Because the underlying problem isn't finding someone with the right experience. It's that the right experience doesn't exist yet.
What Actually Matters
You're not really hiring for five years of ERP experience. You're hiring for someone who can run a plant when the tools and processes are changing constantly.
Someone who learns fast. Someone who sees a broken process and fixes it without waiting for documentation. Someone who can adapt when the platform they mastered becomes obsolete.
Someone who can survive ambiguity.
But you can't write that in a job description. It doesn't feel concrete enough. It doesn't pass HR screening. It doesn't feel like you're being rigorous.
So you list the skills instead. And you hire for yesterday. And you're surprised when yesterday's expertise doesn't solve today's problems.
Sometimes hiring is the right call. Sometimes it's not. Sometimes what looks like a hiring problem is a process problem that a hire will make worse. Sometimes the role is so dependent on upcoming changes that hiring for the current state is wasting a hire.
But none of that gets asked. The industry is built around hiring as the universal solution.
The conversation worth having is different:
Not "what skills should we hire for" but "how do we hire for someone who can figure out skills we can't predict."
That changes everything.