Wisdom Gap Diagnostics Series
The Competency Framework Blueprint
Designing for actual performance.
What's Inside
- Seven design principles that separate a competency framework that gets used from one that just gets referenced
- Why most frameworks quietly become documents within a year of launch, and what actually prevents it
- A side-by-side comparison: the old launch-and-file playbook versus what actually keeps a framework alive
- A five-step diagnostic you can run this quarter, starting with three recent promotion decisions
- The deeper question every competency framework is quietly answering, whether anyone intended it to or not
Ready to see if yours is a system or just a document?
Takes about 3 minutes. Your free blueprint is emailed to you instantly.
Get the GuideWhat You'll Get
Seven Design Principles
From building for what's next to rewarding audacity alongside disciplined execution.
Old Playbook vs. Next Practice
What most framework launches get wrong, and what actually keeps a framework in active use.
A Five-Step Starting Diagnostic
Concrete questions to ask this quarter, starting with three real promotion decisions.
A Document, Not a System
Somewhere in most organizations sits a competency framework, carefully designed several years ago, listing traits like strategic thinking, collaboration, and results orientation. It’s referenced in the performance review template. Almost nobody outside HR can recall the last time it genuinely changed a hiring, promotion, or development decision.
This isn’t a rare failure. It’s closer to the default outcome. The gap between a competency framework and a competency system is simple to state and easy to miss in practice: a framework exists, a system gets used. Most organizations have the former and believe they have the latter, because the document is well written, formally launched, and occasionally cited. What actually determines whether it’s a system is whether it shapes real decisions when nobody is required to reference it.
The Maturity Gap, in Numbers
Recent industry research suggests most organizations are still building the basic infrastructure this requires, let alone the discipline to keep it alive. Mercer’s 2025/2026 Skills Snapshot Survey found that only 38% of organizations maintain a single, enterprise-wide skills library, up from 30% two years earlier, and just 55% map skills directly to jobs, up from 47% over the same period. Even among organizations actively working on this, the mean share of jobs with skills mapped sits at around 72%, meaning roughly a quarter of roles in even relatively mature organizations still sit outside any structured framework at all.
The direction of travel is positive. The absolute level of maturity, for most organizations, is not yet where the ambition suggests it should be.
Want a personalized score alongside this blueprint? Free, ten-question assessment.
Take the Assessment →The Business Case Is No Longer Really in Question
What’s changed in recent years isn’t whether competency and skills-based approaches work, that case is now well established, but how large the gap has become between organizations that have operationalized them and those still working from a static document. Research from Deloitte found that organizations with mature skills-based practices are 107% more likely to place talent effectively, 98% more likely to retain high performers, and 52% more likely to innovate than those without.
The shift is also showing up directly in hiring. LinkedIn’s Global Talent Trends research found that 85% of employers now use skills-based approaches in hiring decisions, up sharply from 56% just a few years earlier. Credentials alone are steadily losing ground as the primary signal organizations rely on, replaced by more specific, behaviorally grounded evidence of actual capability, exactly the shift this blueprint’s second design principle is built around.
How AI-Ready Is Your Organization, Really?
Take our free 4-minute assessment and get a personalized report on your leadership fluency, governance, and workforce readiness.
Take the Free AI Readiness Assessment →Seven Design Principles That Actually Drive Performance
The full blueprint walks through each of these in depth. In brief:
- Build for the next three to five years, not the last three — a framework built entirely on historical success patterns will always validate the past rather than prepare for what’s coming.
- Make every competency behaviorally specific — abstract traits can’t be assessed consistently by different people; specific behaviors can.
- Assess through multi-source evidence, not manager impression alone — a single manager’s judgment is shaped by proximity, recency, and personal bias.
- Separate current performance from future potential, explicitly — conflating the two is one of the most common and costly errors in talent systems.
- Calibrate consistently across levels and functions — a framework interpreted differently by different teams effectively becomes several different frameworks.
- Review the framework itself on a deliberate, regular cadence — competencies that predicted success five years ago aren’t automatically the ones that predict it now.
- Reward exploration and audacity alongside disciplined execution — a framework that only values executing the known playbook selects, often invisibly, against the capability a volatile environment actually needs.
See how we help frameworks actually get used.
Built around the seven principles in this blueprint.
Explore Capability Building Programs →Why the Standard Fix Falls Short
The standard approach commissions a well-designed framework, launches it formally with a briefing deck, embeds it in the performance review template, and treats the design work as complete. Design work, though, is maybe a third of what actually makes a framework drive performance. The remaining two-thirds is the ongoing discipline of keeping it used, current, and consistently applied, work that has no natural launch moment and is easy to quietly deprioritize once the initial rollout energy fades.
What to Do About It This Quarter
Start by testing whether your current framework is actually a system or a document. Pick three recent promotion decisions and ask honestly whether the framework was genuinely referenced, with specific evidence against specific competencies, or cited afterward to justify a decision made on other grounds.
From there, rewrite your three most abstract competencies as specific, observable behaviors at each level, examine how potential gets distinguished from performance in your promotion process, confirm who actually owns the framework at a senior level, and consider adding one principle most frameworks currently lack entirely: an explicit, assessed competency around comfort with ambiguity and well-reasoned risk-taking.
The Deeper Pattern
Every competency framework is, underneath its language of skills and behaviors, a statement about what an organization believes leadership actually is. A framework built entirely around disciplined execution of the known quietly teaches an organization that leadership means mastering what already exists. A framework that also values exploration and audacity teaches something different: that leadership means being genuinely capable of navigating toward what doesn’t yet exist.
Most organizations don’t choose this distinction deliberately. It emerges by default from whichever competencies happened to get written down first, often years ago, under very different conditions.
Want to meet the team?
Start with a 30-min conversation. No commitment needed.
Frequently Asked Questions
What’s the difference between a competency framework and a competency system?
A framework is a document, competencies listed, defined, and formally launched. A system is that same content actively shaping real hiring, promotion, and development decisions on an ongoing basis. Most organizations have the former and assume they have the latter.
How mature are most organizations’ competency frameworks, really?
Recent research suggests meaningful gaps remain even among organizations actively investing in this. Only around a third of organizations maintain a single enterprise-wide skills library, and even relatively mature organizations typically still have a quarter or more of roles sitting outside any structured framework.
Why do competency frameworks stop being used after launch?
Design work is only part of what makes a framework effective. The larger, ongoing task, keeping it current, consistently applied, and genuinely referenced in real decisions, has no natural launch moment and is easy to deprioritize once initial rollout energy fades.
What’s the business case for investing in a mature competency framework?
Organizations with mature skills-based practices are significantly more likely to place talent effectively, retain high performers, and innovate, according to recent research, and skills-based hiring approaches have become the norm rather than the exception across employers globally.
How often should a competency framework actually be reviewed?
On a deliberate, regular cadence, not treated as a permanent document. The competencies that predicted success several years ago aren’t automatically the ones that predict it now, and a framework nobody revisits quietly drifts out of relevance while still being trusted simply because it exists.
Curious About Other Areas of Your Organization?
Explore our free assessments and get a fuller picture of where you stand.
View All Assessments