Competency
framework

What a framework contains

For each role or role family: the competencies that matter (technical skills, knowledge domains, behaviours), each defined at observable proficiency levels, foundation through expert, with descriptors concrete enough that two assessors would rate the same person the same way. The descriptor quality is the whole game: "communicates effectively, level 3" is decoration, while "briefs senior stakeholders unaided and handles challenge" is a standard someone can be assessed against.

Why organisations bother

One spine, many uses. The same framework writes job requirements, structures interviews, locates skills gaps, shapes development plans, and makes progression criteria transparent instead of political. In regulated and safety-critical environments it goes further: the framework plus assessment evidence is how an organisation *proves* its people are competent, to a regulator, a court or a client, which is where competency management stops being an HR preference and becomes an operating licence.

Keeping it alive

Frameworks die of two diseases: over-engineering (forty competencies per role that nobody can hold in mind) and neglect (a beautiful document, last updated two restructures ago). The working versions keep it lean, under a dozen competencies per role, review it as roles genuinely change, and wire it into the systems people already use for hiring, learning and review, so the framework is the path of least resistance rather than an extra form.