Competency Framework
A competency framework is the shared structure, spanning every job family, that names the competencies each one requires, levels them on a shared proficiency scale, and states the required level for every role, so that assessment, gap analysis, and development all read from one definition of good.
By Samantha, SkillsDB|Published |Updated
What It Is
A competency framework is the reference architecture for how an organization describes capable work. It holds the competencies, grouped by job family and often by a small set shared across all roles; the proficiency scale and the behavioral anchors that give each level a meaning; and the required level of each competency for each role. The framework itself does not record what anyone can do. It records what the work demands, and it is the fixed side of every gap calculation. Assessments supply the moving side. A framework earns its keep when three things are true: practitioners recognize their own work in the definitions, an assessor can place a person at a level without guessing, and a change in the framework flows automatically into the gap reports and plans built on it. A framework that fails any of the three becomes a document rather than a system.
Key Facts
- The framework is the fixed side of a gap: it holds required levels, never assessed levels.
- One organization-wide proficiency scale, usually 0 (N/A) to 5, should run through every competency in the framework.
- Job families are the organizing unit; a mid-size organization typically has 8 to 20 families and 3 to 6 role levels within each.
- A small set of core competencies, usually 3 to 5, applies to every role and sits above the family-specific ones.
- Required levels per role are the part most often left blank, and without them the framework cannot produce a gap.
- Ownership splits: HR or L&D owns the structure and scale; each job family owns its competency definitions and anchors.
The Parts of a Framework
| Part | What it contains | Who owns it |
|---|---|---|
| Job families | Groups of roles that share a body of work, with role levels inside each | HR, with function leaders |
| Competencies | Named, outcome-shaped bundles per family plus a core set for all roles | Each job family, drafted by practitioners |
| Proficiency scale | The single scale every competency is leveled on | L&D or the framework owner |
| Behavioral anchors | One observable statement per level per competency | Subject-matter experts in the family |
| Required levels | The level each role must reach on each competency | Role owners, calibrated across the family |
| Evidence rules | What counts as proof at each level: test, observation, work product, certification | L&D with quality or compliance where regulated |
How SkillsDB Models It
In SkillsDB the framework is built in Library → Careers: each Career is a job role, its Sections group the Skills that role requires, every Skill carries a benchmark grade, and Levels give the same Skill a higher benchmark as seniority rises. A Software Engineer career might hold a Backend Development section with API Design benchmarked at 2 for Junior, 3 for Mid-Level, and 4 for Senior, plus a Leadership section with its own benchmarks set per level. Careers that share a shape sit together in a Job Family, and Career Types and Labels keep a large library filterable. When an administrator assigns an engineer to the career at Mid-Level, SkillsDB compares her current grades to the Mid-Level benchmarks at once: her Skills Profile shows the gaps in red, her manager sees the same cells in the Skills Matrix grouped by section, and editing a benchmark changes both views without a re-import. See Competency Frameworks and Job Architecture.
Related
Frameworks should run things, not decorate them.
See how SkillsDB connects a competency framework to assessment, gaps, and learning the day it is published.
Book Demo