Blog
Latest
The gap between announcing a skills-based hiring initiative and actually running one isn’t a process problem. It’s a readiness problem. Here’s what has to be true before the rollout begins.
You’ve probably had this conversation. Maybe with your CHRO. Maybe with your board. Maybe in a leadership offsite where someone put up a slide with a McKinsey statistic on it and the room nodded.
“We’re moving to skills-based hiring.”
And then— you went and did it. You dropped degree requirements. You rewrote job descriptions. You may have purchased some new technology. You announced the initiative, trained the team, and told the business the approach was changing.
And six months later, if you’re being honest, your hires don’t look all that different from before.
You’re not alone. Research from the Burning Glass Institute and Harvard Business School found that 85% of employers now claim they practice skills-based hiring. The actual shift to non-traditional talent has materialized in fewer than 1 in 700 hires.
85% adoption. 0.14% actual change.
The organizations behind that gap aren’t being dishonest. Most of them genuinely believe they’re doing what they said they’d do. The problem is that what they did—drop requirements, rewrite descriptions, buy tools—is not the same thing as changing how hiring decisions actually get made.
What they changed was the signal. What they didn’t change was the system.
Skills-based hiring doesn’t fail at implementation. It fails at the decision that comes before implementation.
The Wrong Diagnosis
When a skills-based hiring initiative stalls, the instinct is to look at implementation. The tools weren’t right. The process wasn’t defined clearly enough. The vendor over-promised.
These are real problems. But in most cases, they’re symptoms.
The NACE Job Outlook 2026 survey asked employers what’s standing in the way of skills-based hiring.
The top two answers, tied at 46.3% each: buy-in from hiring managers, and cultural hurdles within the organization. Lack of assessment tools came in third at 36.8%.
Notably, lack of time and resources — the excuse leadership teams reach for most — ranked second-to-last, cited by just 12.6% of respondents. The barriers aren’t downstream of the launch. They’re upstream of it. They’re organizational.
Here’s what this means practically: if you’re solving for implementation, you’re solving for the wrong thing.
The organizations that actually make this work—not just announce it—do a different kind of work first. They answer five uncomfortable questions before they build a single rollout plan. And they’re honest about what they find.
Five Questions That Come Before the Roadmap
What follows isn’t a checklist. It’s a diagnostic. These are the questions that determine whether you’re actually ready to implement skills-based hiring—or whether you’re about to invest significant organizational energy in something that will stall six months in and leave your team with less credibility than when you started.
1. Do you have leadership alignment—or just a mandate?
A mandate says: “We’re doing this.” Alignment says: “We understand what this requires, we’ve made space for it, and we’re prepared to protect it when it gets hard.”
Here’s how you tell the difference.
Skills-based hiring, done properly, will produce shortlists that include candidates who don’t look like what your hiring managers have historically hired. That’s the entire point.
The first time a senior hiring manager sees one of those shortlists and says “these people don’t have the right background,” what happens next tells you everything about whether you have alignment or just a press release.
Real alignment means leadership has agreed, in advance, that non-traditional candidates on a shortlist are a feature—not a bug—and there’s a named executive who will hold that line when the pressure comes. Because it will come.
The question to ask yourself: Can you name the specific person who will defend a skills-based shortlist when a hiring manager pushes back? If the answer is “our CHRO is supportive of this direction,” that’s not alignment. That’s optimism.
2. Is your job architecture actually ready?
Skills-based hiring requires knowing what skills you’re hiring for. This sounds obvious. It’s, in practice, surprisingly rare.
Most organizations’ job architecture was built around credentials and years of experience, because those were the proxies that were easy to filter on when the systems were designed.
Replacing them with skills-based criteria requires doing work that most organizations genuinely haven’t done: defining, at the role level, what capabilities actually predict success in that specific context.
It’s also worth being clear about what “skills” means here—because it’s not a monolith. Technical skills are part of it.
Transferable skills are part of it. And then there are the behavioral and cognitive competencies—critical thinking, learning agility, the constellation of traits that research consistently shows predict performance across roles and industries—that are often the most important and the least measured.
The question to ask yourself: Pull up your three most frequently filled roles. Do the requirements describe what someone needs to be able to do—or what they need to have done before? If the answer is mostly the latter, your job architecture isn’t ready.
3. Have you actually thought through where to start?
The choice of where to pilot isn’t a logistical decision. It’s a strategic one. And it’s one of the most common places organizations get it wrong.
Start with the highest-visibility roles in your organization—the ones everyone is watching, the ones that report directly to a skeptical SVP—and you’re running your first experiment at maximum pressure, before you’ve worked out the operational friction. That’s how initiatives get declared failures before they’ve had a real chance.
Start with roles that are representative but lower-stakes—where you have a sympathetic hiring manager, enough volume to see patterns, and a reasonable timeframe to measure outcomes—and you build the evidence base that earns you the room to expand. You also build the muscle memory your team needs before the political stakes get higher.
The question to ask yourself: Is your pilot selection based on where skills-based hiring is most likely to succeed—or where the mandate is loudest? Those are often different roles.
4. What does success look like before you can prove ROI?
The outcome metrics everyone wants—quality of hire, 90-day performance, first-year retention—take months to materialize after the hire is made.
If your entire success framework is built on lagging indicators, you’ll spend six to twelve months not knowing whether your initiative is working. And in that vacuum, every squeaky wheel becomes evidence that it isn’t.
Organizations that sustain SBH initiatives define leading indicators too—process metrics you can track in real time that signal the machinery is functioning before the outcome data arrives.
Shortlist acceptance rate. Candidate pool composition at the screening stage. Time-to-fill on piloted roles versus your historical baseline. Hiring manager satisfaction after the intake meeting. None of these require waiting a year. All of them tell you whether something meaningful is changing.
This also matters politically. If you can only point to outcomes that take twelve months to measure, you’ll lose the internal argument before the data shows up. Leading indicators are how you keep the initiative alive long enough to prove what it’s worth.
The question to ask yourself: Can you name three leading indicators you’ll track in the first 90 days of your pilot? If the answer is no, you don’t have a measurement plan. You have a hope.
5. What breaks first—and have you planned for it?
Every skills-based hiring implementation hits friction. That’s not pessimism—it’s just true. The question is whether you’ve mapped the most likely failure points before they become crises.
The failure modes tend to cluster around four scenarios. A hiring manager rejects a skills-based shortlist and leadership doesn’t intervene—that’s an alignment failure, and it usually happens within the first 60 days.
A job description gets rewritten with skills-based language but the ATS is still filtering on keywords underneath—infrastructure failure.
Assessment data comes back and nobody was trained to have a conversation about it in the intake meeting—capability failure. A non-traditional hire makes an early mistake and someone uses it to relitigate the whole initiative—political failure.
None of these have to be catastrophic. All of them will feel like a crisis if you’re treating them as surprises.
The question to ask yourself: Can you walk through your most likely failure scenario and describe what your response will be? If it still feels hypothetical, it will feel like an emergency when it becomes real.
A premature SBH rollout doesn’t just fail. It vaccinates the organization against trying again.
What Readiness Actually Looks Like
Some organizations will read through those five questions and realize they’re not ready yet. That’s not a failure. It’s the most useful thing this piece can tell you.
A premature rollout doesn’t just stall. It vaccinates the organization against trying again. When the initiative fails because the conditions for success weren’t in place, the lesson people draw is that skills-based hiring doesn’t work.
The actual lesson—that it requires specific organizational conditions to work—rarely gets told. The result is a leadership team that has “already tried that” and a talent acquisition function that has lost credibility on the initiative that mattered most.
The organizations that are genuinely ready tend to share some common characteristics. They have an executive sponsor who understands not just what skills-based hiring is, but what it will ask of the organization politically and operationally.
They have at least a working answer to the job architecture question for their pilot roles. They’ve chosen that pilot deliberately—for likelihood of success, not visibility.
They’ve defined leading indicators they’ll track in the first 90 days. And they’ve had the honest conversation about what breaks first and what the response will be.
None of that is the rollout plan. It’s the work that makes the rollout plan executable.
One More Thing That Has to Be True
There’s a version of skills-based hiring that organizations attempt after doing all of this readiness work—and it still stalls. Usually because they dropped credential requirements without replacing them with something that actually works.
Removing “Bachelor’s degree required” from a job description and replacing it with nothing is not skills-based hiring. It’s a shorter job description.
The signal the credential was providing—however imperfectly—has been removed. Nothing has replaced it. Hiring managers are now making decisions with less information, not better information. And shortlist rejection rates climb.
This is where validated assessment becomes structural, not optional.
When you can actually measure the competencies that research shows predict performance across roles—critical thinking, learning agility, and the behavioral traits that develop through real-world experience—you’ve replaced a credential proxy with something that tells you what you actually need to know.
The Workday 2025 Workforce Study found that hiring for skills is five times more predictive of job performance than hiring for education, and twice as predictive as hiring for prior experience.
But that finding holds only when you’re measuring skills. Not when you’re just removing requirements.
The readiness question here is the same as the others: do your hiring managers understand what the assessment is measuring and why—before the first candidate result lands in their inbox?
If they don’t, the data will be ignored or misinterpreted. And the initiative will stall at a different point than it would have otherwise, but stall it will.
The Honest Starting Point
Skills-based hiring is not complicated as a concept. As an organizational change initiative, it’s genuinely difficult—and the difficulty is almost never where organizations look for it.
The 85% of organizations claiming adoption are not lying. They’re working with an incomplete definition of what adoption actually means. It’s not dropping requirements. It’s not announcing the initiative. It’s not buying a new tool.
Adoption is when the hiring decisions your organization actually makes—not the ones it talks about making—are different from what they were before. That change requires readiness. And readiness starts with five honest questions.
The failure rate for skills-based hiring is not a feature of the approach. It’s a feature of starting in the wrong place.
Ready to run the diagnostic? Download the SBH Readiness & Implementation Guide—a practical tool with the frameworks, questions, and templates to do this work before the rollout begins.