For years, organizations could afford to treat competency frameworks as relatively stable infrastructure. A role was defined, competencies were mapped to it, proficiency levels were described, and the framework was used for hiring, development and performance conversations.
That assumption is becoming harder to sustain. AI, automation, digital tools, new operating models and changing customer expectations are altering how work gets done. The World Economic Forum reported in its Future of Jobs Report 2025 that 39% of workers' core skills are expected to change by 2030, while the skills gap is already cited by employers as a major barrier to transformation. (World Economic Forum, 2025).
The implication for HR is larger than adding a few AI competencies to an existing dictionary. The real question is whether the organization can continuously understand how work is changing, translate that change into capabilities, and turn those capabilities into practical talent-development decisions.
The future of competency management is not "build the perfect competency dictionary once." It is "build the organizational capability to keep competencies relevant."
Why AI creates a competency problem, not only a technology problem
When a technology changes, organizations often focus first on tools, processes and technical training. But the deeper change happens in the work itself. Tasks are redistributed between people and technology. Decision-making can move closer to the frontline. Roles can become broader. Collaboration patterns can change. Some technical skills become less differentiating while human judgement becomes more important.
The WEF expects technology-related skills such as AI, big data and cybersecurity to grow rapidly, while creative thinking, resilience, flexibility, agility and leadership remain important human capabilities. This combination means future performance is likely to depend on both technical fluency and distinctly human capabilities. (World Economic Forum, 2025).
The limits of a static competency framework
A traditional framework tends to assume that the organization already knows what each role requires. This works reasonably well when roles are stable. It becomes less useful when work changes faster than the review cycle.
- Competencies may describe yesterday's work rather than tomorrow's work.
- Role-based competency lists can become too narrow when work becomes cross-functional.
- Annual updates can lag behind technology and business-model changes.
- Development plans may focus on course completion instead of capability for real work.
- Talent decisions can remain tied to hierarchy and job history rather than demonstrable skills and adjacent potential.
What should replace the static model?
The answer is not to abandon competencies. It is to make competency architecture more dynamic and more closely connected to business strategy. A useful architecture should distinguish between what is enduring and what is changing.
1. Enduring capabilities
These are capabilities that remain strategically important across cycles: judgement, customer orientation, collaboration, leadership, problem solving, learning agility and ethical decision-making.
2. Emerging capabilities
These are capabilities whose importance is rising because of technology, strategy or market shifts: AI fluency, data interpretation, digital product thinking, human-AI collaboration, cybersecurity awareness or ecosystem leadership.
3. Role-specific skills
These are the technical or domain capabilities needed for particular work. They should be detailed enough to guide development but flexible enough to evolve as tools and processes change.
From competency dictionary to competency sensing system
This is where competency architecture needs a different operating model. Instead of asking HR to refresh the framework once every few years, the organization can establish a recurring process for sensing changes in strategy, technology and work.
- Identify strategic shifts and major changes in work.
- Translate those changes into future tasks and capabilities.
- Map the capabilities to roles, skills, projects and talent pools.
- Assess current proficiency and evidence of application.
- Prioritize development based on business importance and individual gaps.
- Review the architecture periodically and retire or refresh outdated elements.
This turns competency architecture into a living management system rather than a static HR document.
Why this matters for talent development
Once competencies are dynamic, learning and development can become more targeted. Instead of asking, "Which courses should we offer?", the organization can ask, "Which capabilities will constrain our strategy, and how will people build them through work?"
That shift matters because skills are developed through a combination of learning, experience, practice, feedback and exposure. Formal learning remains useful, but it is only one mechanism.
The HR shift: from competency maintenance to capability orchestration
HR's role is increasingly to connect business strategy, workforce skills, talent data, learning, internal mobility and leadership decisions. Competency architecture can become the common language that connects those systems.
The goal is not more competency labels. The goal is better decisions: where to build, where to buy, where to redeploy, who is ready, who needs experience, and which capabilities the organization must develop before they become constraints.
What organizations should do now
- Start with the capabilities most critical to the next 2–3 years of strategy.
- Separate enduring competencies from fast-changing skills.
- Map skills and capabilities across functions instead of only within job descriptions.
- Use evidence from projects and work outcomes to assess proficiency.
- Connect competency gaps to development experiences, not only training courses.
- Create a regular review cadence so the framework changes with the business.
The bigger shift
AI is making one assumption increasingly difficult to defend: that the organization can define work once and manage talent against that definition for years. Work is becoming more fluid. Skills are changing. Consequently, competency systems must become more agile.
The organizations that benefit most will not necessarily be those with the longest competency dictionaries. They will be those that can continuously translate changing business needs into capabilities, then turn those capabilities into action.
At HDI, we see competency architecture as an organizational capability: a practical bridge between business strategy, changing work, skills, talent development and organizational performance.
Frequently Asked Questions
What is the impact of AI on competency frameworks?
AI can change the tasks, decision patterns and skills required within existing roles. Competency frameworks therefore need to identify emerging technical and human capabilities and be reviewed more frequently.
Should organizations replace competencies with skills?
Not necessarily. Competencies and skills serve different purposes. A practical architecture can combine enduring behavioral or leadership capabilities with specific, observable skills and proficiency expectations.
How often should a competency framework be updated?
There is no universal interval. The review cadence should be linked to the pace of strategic, technological and operating-model change. Fast-changing skill areas may need much more frequent review than enduring leadership capabilities.
Sources and Further Reading
- World Economic Forum, Future of Jobs Report 2025 — https://www.weforum.org/publications/the-future-of-jobs-report-2025/
- World Economic Forum, Skills Outlook 2025 — https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/3-skills-outlook/
- Google Search Central, Optimizing for generative AI features in Search (2026) — https://developers.google.com/search/blog/2026/05/a-new-resource-for-optimizing
