A competency framework solves the consistency problem in talent management. Without one, every hiring manager uses different criteria to evaluate candidates, every performance conversation uses different standards to evaluate employees, and the organisation has no coherent picture of what 'good' looks like across different roles and levels.
A competency framework defines a set of core competencies — typically 8-15 — that apply across the organisation at various levels. Each competency has a definition (what it means in this organisation's context), behavioural indicators (observable actions that demonstrate the competency at different proficiency levels), and level descriptors (how the competency manifests differently for individual contributors versus managers versus senior leaders).
Common competency categories include: core organisational competencies that apply to everyone (communication, teamwork, integrity), leadership competencies that apply to people managers (developing others, strategic thinking, decision-making), and functional competencies specific to certain role types (technical skills, sales skills, financial acumen). The framework defines which competencies apply to which roles and at which levels.
The framework's value extends across the full talent lifecycle. In recruiting, it provides the evaluation criteria for structured interviews and scorecards. In onboarding, it communicates what success looks like to new employees. In performance management, it provides the behaviourally anchored standards for annual reviews. In development planning, it identifies the gap between current and required competency levels. In succession planning, it defines the criteria for readiness to move to higher-level roles.
Key Points: Competency Framework
- Behavioural anchors: Effective competencies are defined through observable behaviours, not abstract qualities — replacing 'good communicator' with specific behavioural examples.
- Level differentiation: Competencies look different at different seniority levels — the framework must articulate what excellence means for ICs versus managers versus executives.
- Lifecycle application: The same framework drives recruiting criteria, performance standards, development planning, and succession readiness assessment.
- Cultural expression: The choice of competencies reflects and reinforces organisational values — what the framework includes and excludes sends a strong cultural signal.
- Practical length: Frameworks with 20+ competencies become unwieldy — 8-12 core competencies with clear behavioural anchors is the practical sweet spot.
How Competency Framework Works in Treegarden
Competency Framework in Treegarden
Treegarden allows interview scorecard templates to be built around competency framework dimensions. When a job is created, the relevant competencies for that role and level are pulled into the interview scorecard, giving interviewers pre-defined questions and behavioural anchors to evaluate against. All interviewers across multiple rounds assess the same competencies with the same criteria, producing comparable scores that support structured hiring decisions rather than informal impressions.
See how Treegarden handles Competency Framework → Book a demo
Related HR Glossary Terms
Frequently Asked Questions About Competency Framework
Building a competency framework from scratch typically follows a four-phase process. First, define the strategic context: what behaviours will enable the organisation to execute its strategy? This involves conversations with senior leaders about what distinguishes high performers from average performers at each level. Second, benchmark externally: review established competency frameworks from SHRM, Lominger, and other sources to identify standard competency language you can adapt rather than inventing from scratch. Third, draft and validate: create a draft framework and validate it with employees at various levels — do the competency descriptions ring true as descriptions of what actually matters in this organisation? Fourth, calibrate: ensure the behavioural anchors and level descriptors are sufficiently specific that different assessors would reach consistent conclusions when evaluating the same behaviour. The calibration step is where most frameworks fail.
Skills frameworks and competency frameworks address different dimensions of capability. A skills framework catalogs specific technical and functional abilities: software proficiencies, domain knowledge, certifications, and measurable task capabilities. Skills are generally either held or not held, or held at a quantifiable level. A competency framework describes behavioural patterns and attributes: how a person approaches problems, collaborates with others, communicates, and leads. Competencies are inherently gradational — you can demonstrate leadership competency at a junior, intermediate, or senior level, but the behaviour manifests differently at each level. Many organisations use both: a skills framework to track specific technical capabilities and a competency framework to assess behavioural excellence.
Yes — using the competency framework in hiring is one of its highest-value applications. Structured interviews built around the competency framework ensure that all candidates for the same role are assessed against the same criteria, producing evaluation data that is both more reliable (consistent across interviewers) and more legally defensible (documented, criteria-based decisions) than unstructured interviews. Competency-based interview questions ask candidates to describe specific past situations that demonstrate the relevant competency — 'tell me about a time when you had to influence a decision without having direct authority' to assess influence and stakeholder management. The answers are scored against the framework's behavioural anchors, producing a numerical score that reflects how closely the candidate's demonstrated behaviour matches the standard for the role.
Competency frameworks become shelf-ware when they are developed with significant investment, communicated with fanfare, and then left to drift out of use as day-to-day operational pressures crowd out the sustained effort required to embed them. Prevention requires building the framework into unavoidable processes rather than expecting managers to voluntarily apply it. If the performance review form requires managers to assess employees against framework competencies, the framework gets used for every review. If interview scorecards are built around framework competencies, every structured interview uses the framework. If development plan templates reference framework competencies, every development conversation uses them. The framework should become the invisible infrastructure of talent decisions rather than an additional thing managers have to remember to do.