Most organizations that invest in competencies stop at the framework itself: a defined list of skills and behaviors. But a competency framework only creates value once it’s built into how the business actually runs, position by position, wired into hiring, promotion, performance management, and training. Without that infrastructure, a well-built framework becomes a document nobody uses. Recent research backs this up directly: most organizations pursuing skills-based talent decisions are struggling to see returns, not because their frameworks are wrong, but because they skip the infrastructure work underneath them.

Many organizations that invest in competencies get as far as the framework and stop there. They define what good leadership or strong performance looks like, publish it, and consider the work done. But a competency framework only creates value once it is built into how the business actually runs.

A Framework Isn’t the Same as Infrastructure

This is not a job description exercise. Understanding a role’s competencies means understanding how those competencies actually show up in the work: what the levers are, where the growth areas sit, and what the next level of that competency looks like as someone advances. That level of specificity has to happen position by position, which means it requires HR and the business working closely together, not HR handing down a framework from above.

Once that groundwork exists, everything else can connect to it. Feedback systems can be built around it. Performance management can reference it. Training, hiring, and promotion decisions can all draw from the same standard instead of operating on separate, inconsistent logic. Without that connective tissue, a framework sits on its own, disconnected from the decisions it was meant to inform.

A competency framework that isn’t built into how decisions get made is a document, not infrastructure.

What the Research Shows

This isn’t just an internal observation. Deloitte’s research team analyzed 87 organizations implementing more than 28 different skills strategies across skills demand identification, skills supply data, skills activation and governance, and skills-based talent management, and found that many organizations are struggling to realize tangible value from their skills-based approaches. That struggle is widespread: only 2% of HR leaders polled by Gartner say their organizations have successfully adopted skills-based approaches across all their processes.

What separates the organizations that do see results isn’t a better framework. Deloitte found that regardless of what outcome an organization was pursuing, the ones creating value consistently built the same foundational infrastructure first: a clear and simplified job architecture, a skills list or library, identification of the critical skills that matter most, and effective change management. And perhaps most tellingly, these strategies don’t often fail on design or technology. They are more likely to fail due to adoption, trust, and behavior change.

That last point matters. The problem organizations run into is rarely that the competency model itself is flawed. It’s that nothing was built underneath it to make the model usable.

Where to Start

Building this kind of infrastructure is not a weekend project. It is closer to a multi-month or multi-year undertaking, depending on the size and complexity of the organization, and it cannot be done all at once. The right entry point is a survey of where competency gaps are already showing up, often at the point where someone steps into a new level of responsibility and doesn’t have what the role requires. From there, you go deep on a specific level or component, build it out, and expand from that foundation.

This is deliberately narrow at the start. That is not a limitation, it is the point. Infrastructure that is built carefully in one place can be extended; infrastructure that is rushed across the whole organization at once usually cannot.

This is the same logic behind the OGC Leadership Competency Wheel: competencies aren’t a flat list that applies the same way to everyone. They function as a developmental progression, and building the infrastructure to support that progression, position by position and level by level, is what makes the framework usable rather than aspirational.

The AI Example

This pattern is playing out right now with AI. Many organizations are responding to AI’s arrival the same way they might respond to any new skill demand: announce that everyone needs AI training and send people to a generic course. That’s not a strategic response, it’s a reaction, and it happens precisely because the underlying infrastructure isn’t there to handle it any other way.

Organizations that already have their competency infrastructure in place are in a fundamentally different position. When a new competency need emerges, whether it’s AI fluency or something else entirely, they can plug it into a process that already exists rather than building a response from scratch under pressure.

Most competency initiatives don’t fail because the framework is wrong. They fail because organizations treat the framework as the finish line instead of the starting infrastructure, then expect consistency across hiring, promotion, feedback, and training to emerge on its own. It doesn’t. A firm selling a fast competency rollout, or a template you can implement without the underlying work, is selling you the part that matters least.

Wondering how to build the infrastructure behind a competency framework?  Let’s talk through where you should start.

Have a specific question about how this applies to your organization? Our FAQ page covers common questions on talent systems, leadership development, and engagement data.