Most competency models list thirty behaviors, get printed on a poster, and change nothing. Research on 2 million assessments shows that a small number of competencies do nearly all the differentiating — and that a usable framework looks very different from a complete one.
▸Definition
A leadership competency framework is a defined set of behaviors an organization expects from its leaders, used to align assessment, development, promotion and succession around the same language. An effective one is short, evidence-based, and validated against actual performance outcomes.
The terms are used interchangeably in practice. Where a distinction is drawn, a model describes the competencies themselves and a framework adds the structure around them: how they’re measured, how they differ by level, and how they connect to development. What matters more than the vocabulary is whether it’s built from evidence or assembled from a library.
The failure mode is nearly universal and worth naming plainly: most competency models are built for completeness rather than usefulness.
A committee assembles every desirable leadership behavior, arrives at 25–30 competencies, and produces something technically comprehensive and practically inert. Nobody can hold 30 behaviors in mind, so in practice the model gets used for annual ratings and ignored the rest of the year.
Our research points the other way — a small number of competencies carry most of the predictive weight.
Committee-built frameworks grow until they become comprehensive but unusable. Evidence—not more discussion—is needed to identify what matters most.
Off-the-shelf models describe leadership in general, not what drives success in your organization. Differentiating competencies vary by context.
A framework becomes meaningful only when high scores correlate with better performance. Without outcome-based validation, it’s a values statement—not a framework.
The finding that should govern how you build a framework:
Extraordinary leaders are defined by a handful of profound strengths, not by the absence of weakness.
A 30-competency framework implicitly asks leaders to be adequate everywhere, which our data says produces competent, unremarkable leadership. A short framework asks them to be exceptional at a few things, which is what actually differentiates.
Consider these further inputs worth having before you design:
Define what the organization needs leaders to produce over the next three years before naming any competency. A framework built without that anchor describes the leaders you currently have.
The question isn't "which competencies matter?" Everything matters somewhat. It's "which competencies distinguish your high performers from your average ones?" That's an empirical question, and answering it is what turns discussion into decision.
"Strategic thinking" is a label. "Anticipates market shifts and reallocates resources before they're forced to" is observable, ratable, and coachable. Labels produce inconsistent ratings; behaviors don't.
The same competency looks different for a front-line manager and an executive. Resist maintaining separate frameworks per level. Vary the behavioral indicators instead, so the language stays common across the organization.
Assess leaders against the framework and check whether high scorers actually perform better. If they don't, the framework is wrong and it's better to know early.
A framework that lives only in the annual review is decoration. It should drive the assessments, the development plans, the promotion conversations and the succession slate — using the same words in all four.
Adopt a validated framework when you need to move quickly, you want external benchmarking, and your leadership challenges look like most organizations’ — which is more often the case than internal politics tends to admit. You get research validation and comparison data you can’t generate yourself.
Build custom when you have genuine context-specific requirements (a distinctive operating model, a regulated environment, a differentiated strategy) and the assessment data to validate against. Custom without validation is the worst of both: bespoke and unproven.
Start from a research-validated core, then add the small number of competencies that are genuinely specific to you. You keep benchmarking on the core and get relevance at the edges.
One caution from our data either way: a competency framework is only as good as the instrument measuring it. If the assessment is weak, the framework’s quality is irrelevant — see 12 Components of the Best 360 Assessments.
Let our research become your solutions. Whether you are looking for a partner to help create a leadership competency model for your organization or need expert help to build a reliable, valid assessment to measure an existing model, we offer the secure foundation of empirical research. Our expertise in combining statistical analysis with actionable application is the answer your organization is looking for, and we can’t wait to partner with you on solutions that will make an impact.
For organizations with genuinely specific requirements and the intent to validate them.
They’re used interchangeably. Where a distinction is drawn, the model is the set of competencies and the framework is the surrounding structure; measurement, level differentiation, and the link to development. Evidence matters more than the vocabulary.
There’s no universal list, which is the point. The competencies that differentiate high performers vary by organization and context. Our research had identified a core list of capabilities most predictive of business outcomes as a validated starting point.
Adopt a validated framework unless you have genuinely context-specific requirements and the assessment data to validate a custom one. A hybrid — validated core plus a few specific additions — is usually the best trade-off.
Assess leaders against it and test whether high scorers actually perform better on outcomes you care about. Without that check, a framework is a values statement rather than a predictive tool.
When strategy changes materially, not on a fixed cycle. Frequent revision destroys the common language that makes a framework valuable; never revising leaves you describing the leaders you needed five years ago.
A short conversation is enough for us to point you in the right direction.
