Competency Framework Design
The anatomy of a competency framework: core values-based competencies, functional/technical competencies, and leadership competencies, each defined at observable proficiency levels. Done well it powers hiring, development, and promotion with one shared language.
Explore
When to use
- Building or refreshing job architecture, career paths, or leveling guides
- Making promotion and hiring criteria explicit and defensible
- Diagnosing capability gaps against strategy
When not to use
- When the organization will not maintain it — a stale framework is worse than none
- As a 47-competency dictionary; beyond ~8 per role nobody can use it
- For fast-changing skills better tracked in a live skills taxonomy
Worked example
A scale-up with chaotic promotions builds a framework: 5 core competencies, functional sets for 6 job families, 4 proficiency levels with behavioral anchors. Promotion cases must now cite evidence against the anchors. Promotion complaints drop, and the same anchors become the interview scorecard — one language across the talent lifecycle.
Common pitfalls
- Writing aspirational adjectives instead of observable behaviors
- Copying a competitor's framework instead of deriving from your own strategy
- Launching without embedding into hiring/promotion processes — instant shelfware