How to become a Skills-Based Organization: Start with the decisions you already make

TL;DR

A skills-based organization uses skills, not job titles or tenure, as the basis for decisions about hiring, staffing, promotion and development. Most companies already make these decisions every day; they just make them with poor visibility. Becoming skills-based means activating the skills data you already own, giving it a shared structure, and pointing it at one concrete decision first.

"You already make skills decisions. What's stopping you becoming a skills-based organization?" That was the premise of a recent session led by Loïc Michel, co-founder and CEO of 365Talents at Docebo Inspire City Series. It is a useful question because it removes the excuse that skills-based work is a future project. Every promotion, every staffing call and every nomination to a development program is already a skills decision. The question is how much you can see when you make it.

This article walks through Loïc's four answers to that question, with the research that supports them.

What counts as a skills decision?

A skills decision is any people decision that depends on what someone can do: who gets promoted, who is staffed on a project, who joins a leadership program, and who is redeployed when a role disappears. Most organizations make hundreds of them a year. The issue is rarely the quality of judgment. It is the quality of the information behind it.

That gap is measurable. In Deloitte's skills-based organization survey, 30% of respondents said their organization is ineffective at matching the right talent to work, and 75% of executives said deciding on skills rather than tenure, job history or network would widen access to opportunity. Full transformation remains rare: in its 2024 report How to Adopt a Skills-Based Approach for Talent Management, Gartner found that only 2% of the 80 HR leaders it polled had adopted skills-based approaches across all their processes (cited by Deloitte).

Loïc's point is that this 2% figure should not discourage anyone. Most teams are already making good skills decisions. They are just making them with less visibility than they would like, which is why "what can our workforce actually do?" is still such a frustrating question to answer.

Why is it so hard to see what your workforce can do?

Because most skills sit below the waterline. Loïc estimates that only about 20% of what people can do is visible in a profile, a job title or a learning history. The other 80% is project experience and know-how picked up on the job that nobody ever wrote down.

The research points the same way. Deloitte's Human Capital Trends work found that 71% of workers say they do work outside the scope of their job description. A job title describes the role someone was hired into, not the person doing it today.

The hidden part does not show up while you design a competency framework. It shows up at the moment of decision, when a manager has to pick someone in a week and the only proxies on hand are job title, tenure and who they happen to know. That is when good people get overlooked, and when a decision that should be about skills quietly becomes a decision about networks.

Do you need a skills survey to build a skills inventory?

Usually not. Most organizations have already paid to capture the bulk of the skills data they need: CVs, job histories, training records, certifications, project assignments. It sits in systems they own. The work is activating that data, not asking employees to declare everything again from scratch.

The reflex is still to launch a survey. It feels rigorous, but it asks people to repeat work they have already done, and the result is out of date as soon as it is filed. Loïc's framing turns the logic around: you are not asking employees to build something new, you are declining to ignore what they already gave you. Activate, don't collect.

This does not mean self-declaration has no place. Deloitte's 2026 analysis of 87 organizations notes that self-reported skills backed by manager input are often enough when the goal is growth and mobility rather than pay decisions. The point is sequence. Start from the evidence you hold, then ask people to confirm and complete it, instead of handing them a blank form.

Why does a skills-based organization need a shared skills language?

Because data without structure cannot answer forward-looking questions. Ten thousand employees describing themselves in ten thousand vocabularies gives you coverage, not insight. A shared language for skills and roles, often called a skills taxonomy or ontology, is what turns that pile into something you can plan with.

With a common structure in place, three questions become answerable:

• Which skills are growing or declining across the organization?
• What will a job family need in 18 months, and where is the gap today?
• Which two roles sit one step apart, so you can show someone a path instead of a vacancy?

The pressure to answer them is rising. The World Economic Forum's Future of Jobs Report 2025 found that employers expect 39% of workers' core skills to change by 2030. Deloitte's 2026 research lists a simplified job architecture and a skills library among the foundational moves shared by organizations that get value from skills, and stresses prioritizing a short list of critical skills rather than tracking thousands.

Is training completion a good measure of skills development?

No. A completion rate measures activity, not whether anyone became more capable. It tells you a course was finished, not that a gap was closed or that the person is now staffed on work that uses the new skill. Treating completion as a proxy for capability is how learning budgets grow while skills gaps stay where they were.

Part of the problem is organizational. Seeing a skills gap and closing it are two different jobs, usually owned by different teams: talent or workforce planning on one side, learning and development on the other. Loïc's argument is that the value sits in the connection between the two, when the gap identified in planning drives what learning offers and the skill gained in learning shows up in the next staffing decision.

Deloitte makes a similar case for skills-based learning tied to specific gaps rather than generic role-based programs, which it links to less wasted training spend and better use of existing talent.

Where should you start becoming a skills-based organization?

Start with one decision, not with the framework. Pick a decision you already make often and care about, such as filling critical roles internally or choosing who joins a leadership program, and point your existing skills data at it. The framework, the taxonomy and the reporting can grow from there.

This matches what Deloitte observed in organizations that get results: they start with the outcomes they want, not with skills, and the same research finds skills programs fail more often on adoption and trust than on design or technology. A first decision gives people a reason to trust the data, because they see it change an outcome.

Most organizations are further along than they think. The pieces are usually there already, in the systems they own and in the work their people do every day. What tends to be missing is not more data or a better framework. It is a clear first decision to point it all at.