Competency Framework Design

Theory & origin

Competency modeling traces back to David McClelland's 1973 argument that demonstrated competencies predict performance better than aptitude tests or credentials do. A framework turns that into practice: core, functional and leadership competencies, each described at observable proficiency levels, giving hiring, development and promotion one shared language. The hard part is behavioral anchoring. Competencies written as adjectives, like 'strategic' or 'collaborative,' are useless. Written as observable behaviors, they become something you can actually assess.

Key components

The parts of the model and what each one means, in plain terms.

Core competencies

Behaviors expected of everyone, derived from strategy and values, like customer orientation or collaboration. Usually 4 to 6, no more.

Functional / technical competencies

Role-family specific skills and knowledge, like financial modeling for finance or sourcing for procurement. Owned by the function, maintained centrally.

Leadership competencies

What is expected of people leaders at each level, from leading yourself to leading the enterprise. The basis of leadership assessment and succession.

Proficiency levels

Each competency described at 3 to 5 levels with observable behavioral anchors. The anchors are what make assessment defensible.

Applications

Where the framework earns its keep: interview guides, development plans, promotion criteria, job architecture mapping. A framework nobody uses is decoration.

How a consultant runs it

1. 01 Derive core competencies from strategy and values, and keep it to four to six that everyone is genuinely held to.
2. 02 Build functional sets per job family with the functions that own them, plus a leadership set per level.
3. 03 Write three to five proficiency levels per competency with behavioral anchors, so assessment is defensible.
4. 04 Embed the framework into hiring scorecards, development plans and promotion criteria. A framework nobody uses is decoration.
5. 05 Assign an owner and a refresh schedule. A stale framework is worse than no framework at all.

Worked example

Common pitfalls

1. 01 Writing aspirational adjectives instead of observable behaviors
2. 02 Copying a competitor's framework instead of deriving it from your own strategy
3. 03 Launching without embedding it into hiring and promotion processes, which is instant shelfware

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.