Competencies are how HR turns fuzzy concepts like "strategic thinker" into something measurable. A good competency framework gives managers a shared language for what strong performance looks like in each role, turns subjective judgments into observable behaviors, and creates a backbone for hiring, development, and promotion decisions. The worst frameworks have 40+ competencies, overlap each other, and nobody uses. The best ones have 8 to 12, each with clear behavioral anchors, and every manager can apply them without a translator.
The Three Types of Competencies Core or organizational competencies apply to everyone in the company. These are the behaviors that reflect company values and culture: things like "customer obsession," "ownership," or "bias for action." Amazon's 16 Leadership Principles are the best-known example.
Leadership competencies apply to people who manage others or operate at a senior IC level. These cover influencing, coaching, decision-making under ambiguity, and building high-performing teams. They often expand as someone moves from manager to director to VP.
Functional or technical competencies apply to specific roles: a software engineer's technical competencies differ from a salesperson's. These get granular and usually show up in career ladders or role-specific development plans.
What a Usable Competency Framework Includes A well-built competency has four parts: a clear name (not jargon), a brief definition of what it means, behavioral anchors at different proficiency levels (novice, proficient, expert), and examples of what it looks like in practice. Without behavioral anchors, the framework is aspirational at best.
The best frameworks also link each competency to outcomes. "Strong analytical thinking" might include behaviors like identifying the right data source, running appropriate analysis, and drawing defensible conclusions. Tie each level to specific work products and the framework becomes useful for real decisions.
How Often Should Competency Frameworks Be Updated? Every 3 to 5 years is typical. Sooner if the business strategy shifts significantly. The biggest risk is a framework that reflects the company's past rather than its future. If you're building AI-first products but your competencies don't mention learning agility or comfort with ambiguity, the framework is already stale.
Where Competency Frameworks Show Up in HR Programs Hiring: interview questions map to specific competencies, and interviewers score candidates on each one. Structured interviewing using competency-based questions is one of the few hiring practices with solid validity research behind it.
Performance: performance review ratings anchor to observed behaviors on each competency. This moves reviews away from general impressions toward specific evidence.
Development: each employee's development plan names the one or two competencies they're working to build, along with specific learning activities and stretch assignments. Mentoring pairs often get built around complementary competency strengths and gaps.
Building a Competency Model That Teams Actually Use The practical build: start with a workshop of senior leaders identifying behaviors that differentiate top performers from average, reduce the initial list to 8 to 12 competencies, define behavioral anchors for each at the levels that exist in your company, test the framework with one function before rolling it out broadly, and integrate it into at least two HR processes (hiring and performance) from the start. A competency framework that lives only in a document nobody opens has zero impact.
For research on competency modeling methodology, the Society for Industrial and Organizational Psychology publishes practice guidelines at siop.org . The U.S. Office of Personnel Management maintains the federal multipurpose competency framework at opm.gov/policy-data-oversight/assessment-and-selection/competencies , which is a useful free reference for employers building or benchmarking their own competency model against a mature public-sector example.
.svg)
.svg)
