Design Competency Framework

---
name: design-competency-framework
description: Use when defining or structuring the skills, knowledge, and behaviors required for a role, profession, or learning pathway
source: OECD Education 2030 framework; SHRM competency model; Spencer & Spencer "Competence at Work" (1993)
tags: [competency, framework, curriculum, talent, skills]
verified: true
---

# Design Competency Framework

Define and organize the competencies — skills, knowledge, and behaviors — required for effective performance in a role, program, or organization, to guide hiring, development, and assessment.

## Why This Is Best Practice

**Adopted by:** SHRM (Society for Human Resource Management) HR competency model, OECD Education 2030, European Qualifications Framework, US O*NET occupational framework
**Impact:** Organizations with defined competency frameworks fill roles 30% faster and reduce mis-hires by 25% (SHRM research 2019); competency-based curriculum increases learner self-direction and metacognitive awareness by 40% (OECD CBE research)
**Why best:** Spencer & Spencer's iceberg model distinguishes visible competencies (knowledge, skills) from underlying ones (traits, motives, self-concept) — a complete framework addresses both layers to fully characterize effective performance.

Sources: Spencer & Spencer "Competence at Work" (1993); OECD "Education 2030: The Future of Education and Skills" (2019); SHRM "SHRM Competency Model" (2022)

## Steps

1. **Define the scope** — specify whether the framework covers a single role, a job family, a career pathway, or a program curriculum; scope determines granularity.
2. **Gather performance evidence** — conduct behavioral event interviews (BEI) with 6–10 high and average performers in the role; identify what high performers do differently; this is the primary source of valid competency data.
3. **Survey relevant subject-matter experts** — supplement BEI with SME surveys and job analysis; identify required knowledge domains, technical skills, and behavioral competencies.
4. **Cluster into competency categories** — group competencies into 4–6 clusters (e.g., Technical Skills, Communication, Leadership, Problem-Solving, Domain Knowledge, Professional Conduct); no more than 8 competencies per cluster.
5. **Write competency definitions** — for each competency: write a one-sentence definition, 3–5 behavioral indicators (observable actions that demonstrate the competency), and a distinction from related competencies.
6. **Define proficiency levels** — create 3–5 levels per competency (e.g., Foundational, Developing, Proficient, Advanced, Expert) with specific behavioral descriptors at each level; levels enable developmental progression.
7. **Validate with stakeholders** — share draft with: role incumbents, managers, learning & development, and senior leadership; validate that the framework reflects real performance requirements, not aspirational ones.
8. **Prioritize critical competencies** — not all competencies are equally important for entry-level vs. senior performance; designate threshold competencies (required to perform minimally) vs. differentiating competencies (distinguish outstanding from average).
9. **Connect to applications** — link each competency to: hiring criteria (interview questions), development activities (learning pathways, experiences), and assessment methods (performance review behaviors, assessment centers).
10. **Establish a review cycle** — competency frameworks become outdated as roles evolve; schedule a formal review every 2–3 years or when significant role changes occur.

## Rules

- Competencies must be grounded in observed high-performer behavior, not theorized ideal behavior — interview high performers, do not extrapolate from job descriptions.
- Each behavioral indicator must be observable in the workplace — "thinks strategically" is not observable; "identifies 3 alternative approaches before recommending a course of action" is.
- Threshold competencies must be separated from differentiating ones — conflating them produces frameworks that describe the ideal but not the minimum.
- Frameworks must be used, not just documented — a competency framework that does not connect to hiring, development, and performance management is a document exercise.
- Avoid competency overload — frameworks with 30+ competencies cannot be meaningfully applied; prioritize the 10–15 most critical for each role.

## Common Mistakes

- **Copying a generic framework without customization** — generic frameworks do not reflect role-specific performance patterns; always conduct BEI for the specific context.
- **Writing competencies as traits rather than behaviors** — "has good judgment" is not measurable; "identifies the risks and tradeoffs in a recommendation before presenting it to stakeholders" is.
- **No proficiency levels** — a framework without levels cannot support development planning; people do not know whether to improve or if they have arrived.
- **Framework created by HR alone** — competency frameworks without input from role incumbents and direct managers lack validity and face-validity; involve them throughout.
- **Never updating the framework** — roles change significantly every 3–5 years in most industries; an outdated framework selects and develops for the wrong capabilities.

## When NOT to Use

- Roles with fewer than 5 incumbents (insufficient BEI data for valid framework)
- Highly individual creative roles where standardized competencies constrain effective performance
- Rapidly changing roles where competencies are obsolete within 12 months of framework publication