Competency Framework

Without a shared definition of "what good looks like," hiring interviews, performance reviews, and promotion decisions are inconsistent across managers. Competency frameworks are the organizational intervention against that inconsistency. Done well, they produce shared vocabulary and calibrated standards; done badly, they sit on a page in the HR portal that nobody references. The difference is whether the framework is operationalized in the processes that actually make decisions — or just documented.

Take a 3,500-person retail company's competency framework. Six core competencies apply to everyone (customer focus, teamwork, ownership, learning, communication, integrity); twenty functional competencies vary by function; eight leadership competencies apply to managers. Each competency has four proficiency levels with specific behavioral examples. Hiring interview guides map questions to competencies. Performance reviews rate on the competencies. Development planning identifies competency gaps and matches learning content. Promotion decisions reference the leadership competencies explicitly. Calibration meetings use the framework to pressure-test consistency.

Most competency frameworks were built 5-10 years ago by a consulting firm, approved by an executive team, and slowly abandoned as the business changed. The behavioral examples feel dated; the competencies don't map to current roles; the wording sounds like HR-speak nobody uses. Mature frameworks have an owner, a review cadence (every 2-3 years at a minimum), and a discipline of tying framework updates to business strategy changes. The ones that work are surprisingly short — 8-12 core competencies, not 40 — because managers can actually remember them.

In tech, competency frameworks are often engineering-specific and evolve with the craft. Functional frameworks for software engineering, product management, and design are more developed than for other functions.

In financial services and consulting, competency frameworks are deeply embedded in promotion processes and often publicly documented (Big 4 consulting firms have well-known frameworks).

In healthcare, clinical competency frameworks are defined by professional bodies and interact with employer frameworks.

In manufacturing, competency frameworks often integrate with skill-certification systems, where each competency has associated certifications.

In the public sector and education, competency frameworks are often defined by unions and regulators, producing rigid but well-known structures.

AI uses competency frameworks as ground truth for assessment in 2026. Manager-drafted feedback is mapped to the framework automatically. Performance review summaries highlight competency strengths and gaps with evidence pulled from the year's work. Development recommendations are competency-targeted. The framework itself becomes a living artifact that updates from the patterns agents see across the workforce — what competencies are actually driving outcomes versus which ones were defined aspirationally.

• Framework sprawl. 40 competencies nobody can remember. Smaller and well-known beats larger and ignored.
• Generic wording. "Demonstrates ownership" at all levels without behavioral specifics produces inconsistent interpretation.
• Disconnected from processes. Framework exists in a document; hiring and reviews happen without reference to it. The framework has no influence.
• Never updated. Competencies defined a decade ago that don't match current roles. Treat as living.
• Executive language. Competencies that sound good on a board slide but don't translate to daily work. Write for the line manager.