


Ask five HR leaders to explain the difference between a skill and a competency, and there’s a good chance you’ll hear five different answers. For years, that ambiguity didn’t create many practical problems. But AI has changed the stakes.
As roles and performance expectations shift, organizations can no longer afford to treat these terms as interchangeable because, when they do, the talent and rewards programs built on them become less useful.
The latest WTW Talent Intelligence Report points to a widening gap between workforce data and the work people are actually being asked to do. Three findings stand out.
Some changes are easy to see in the skills organizations are adding. Prompt design, data literacy, model evaluation and workflow automation are turning up in job postings and development plans, and not just in technical functions. These capabilities increasingly matter across roles and levels.
The less visible shift is in the competencies people need to use those skills well. Critical thinking, judgment about when to rely on AI output, responsible use, adaptability and learning agility are becoming increasingly important in almost every role. Knowing how to operate an AI tool is only the starting point. Employees also need to spot when the output is incomplete, inaccurate or simply inappropriate.
AI competencies for leaders
Leaders need the same core competencies everyone needs and have them expressed at the level of contribution expected of their role. As leaders’ scope and responsibilities grow, expectations grow too: from applying a competency in their own work to guiding others and, ultimately, setting the standard across the organization.
For example, consider AI critical thinking and judgment. The competency applies to every level; its expression changes in line with the individual’s contribution. Earlier in a career, that might mean checking whether an AI-generated answer seems right, verifying important information and knowing when to raise a concern. For a manager, it also means making sure the team knows how to check AI-generated work and when to escalate an issue. More senior leaders bring consistency across teams, while executives set the direction and accountability for responsible AI use across the organization.
Describing the same AI competency by level of contribution makes a broad expectation much more useful. Instead of leaving something like “use good judgment” open to interpretation, employees can see what it means in their role and how it builds from one level to the next, particularly as they grow in their careers and become leaders. One set of core AI competencies aligns the organization. Defining them by level turns that alignment into clear expectations for performance, growth and leadership.
Updating one without the other creates a gap. A skills-only approach can turn into a long inventory of tools and techniques that age quickly and say little about the context in which a skill should be used. Meanwhile, a competencies-only approach can be too broad to guide hiring, learning investment and/or redeployment. It also may not reveal whether the workforce can do what the business needs next.
Together, the two tell a fuller story. Skills add precision and can evolve quickly as work and technology change. Competencies supply continuity and context. Their maintenance cycles should reflect that difference.
Skills may need to be refreshed continuously or quarterly, while competencies usually warrant a more deliberate review every few years or after a major shift in strategy or technology. That said, these cycles shouldn’t run in isolation. Each review should ask how a change in one affects the other, so the two remain aligned.
The distinction between skills and competencies is more than a matter of terminology. It changes how core talent processes work in practice.
Jobs that involve similar work and skills are grouped into job families. Together, these families make up an organization’s job architecture. The work differs from one family to another, but the same standards for scope, impact and influence are used to define job levels across the organization.
Competencies show how people are expected to work at those levels, while skills describe what they need to know and be able to do to perform the job’s work. A job profile brings these elements together, giving employees one clear view of the job and what’s expected while also making it easier to price and keep the job current.
Skills and competencies help employees see where they can go next and what they need to develop to get there. Skills reveal transferable abilities and gaps for moves within or across job families, while competencies clarify how expectations change with greater scope and responsibility. Together, they give employees and managers a practical basis for career conversations, targeted learning and development experiences that prepare people for their next move.
Once there’s a clear picture of what jobs require, skills and competencies help organizations plan for what they need next. Skills data shows what the workforce can do today compared with what the organization will need. This helps leaders decide when to build, buy or borrow talent. Competencies indicate how readily the workforce can adapt to the change ahead, which helps leaders judge what is realistic to build internally.
Connect

Aligning your skills and competencies doesn’t require a full redesign on day one. There are four practical steps that will get you on your way:
AI will keep changing how work gets done. Organizations don’t need perfect definitions of skills and competencies, but they do need shared, current ones. That gives leaders a firmer basis for deciding what talent they need, where to invest in development and how roles should evolve next.