Competency management
From Competency Framework to Everyday Decisions
Most frameworks are commissioned once, delivered as a spreadsheet, and opened during appraisal season by the people who remember they exist. A competency model earns its keep when it is small enough to remember, specific enough to settle an argument, and wired into the decisions managers make every week.
Competency record
Client requirements workshop
- Owner
- Head of Delivery
- Levels defined
- 4 of 5, observably
- Evidence accepted
- Scenario, work product
- Roles using it
- 3
- Last reviewed
- 4 months ago
Illustrative interface. Not customer data.
What this actually means
A competency is not a bigger skill
The two words get used interchangeably and then a framework collapses under the confusion. They describe different things, they are measured differently, and a working model needs both.
A skill is a capability
Something a person can do: write a SQL query, run a payroll cycle, read a balance sheet. Narrow enough to assess directly, and it means the same thing in any organization.
A competency is behaviour in context
How a person applies skills, judgement and conduct to the work your organization actually does. It is yours, it is observable, and it usually needs more than one kind of evidence.
A role standard is the bar
Which competencies a job requires and at what level. This is the thing a person gets compared against, and the thing most organizations never write down.
What every competency record carries
- A definition you could argue with
- Written so two managers watching the same person would reach the same conclusion. If it cannot be disputed, it cannot be evidenced either.
- Levels that discriminate
- Each level describes different observable behaviour, not the same behaviour with adverbs attached. Three good levels beat five that blur into each other.
- The evidence it accepts
- Assessment, work product, structured scenario or manager validation. Declared up front, so nobody has to invent a standard of proof under time pressure.
- A named owner
- A person, not a function. Competencies owned by the business stay current; competencies owned by nobody become archaeology within two years.
- A review date
- Work changes and definitions rot quietly. A record that has passed its review date is flagged as stale rather than presented as current.
- The roles that use it
- Visible from the record itself, so the cost of changing a definition is obvious before somebody changes it.
What it is for
The decisions a framework is supposed to settle
A competency model is not an inventory exercise. It is shared vocabulary that lets several different decisions get made consistently by people who are not in the same room.
-
Two managers describe the same job the same way.
Role standards are defined from a shared library rather than rewritten in each job description, so the bar for a role does not move depending on who is hiring for it.
Shared role standards
-
Know what a promotion actually requires.
The difference between two levels is written down in observable terms, so the answer to what would get me promoted is a document rather than a manager's mood.
Transparent level criteria
-
Stop interviewing for the same thing five different ways.
Hiring panels work from the same competency definitions the role standard uses, which makes scorecards comparable and post-interview debriefs shorter.
Consistent evaluation
-
Find the internal candidate before posting externally.
When people are measured against a common set of competencies, matching a person to an open role is a query rather than a memory test.
Internal mobility
-
Aim development at a defined level, not a vague ambition.
A development plan built against level criteria has a finish line and a way to check whether it was crossed, which is the difference between a plan and an intention.
Development planning
-
Retire the definitions that no longer describe the work.
Usage is visible per competency, so the ones nothing references can be archived deliberately instead of accumulating until somebody commissions a replacement framework.
Framework hygiene
The hard part
Governance, not authoring
Writing the first version of a framework takes a quarter. Keeping it true takes forever, and that is the part no spreadsheet helps with. The platform treats a competency as a record with an owner and a lifecycle rather than a row in a document.
- Propose. Anyone can raise a competency the work needs. It arrives as a draft, not as policy.
- Define. The owner writes the levels and declares what evidence counts. Until both exist, it cannot be attached to a role.
- Pilot. Used on one team first. Definitions that two assessors read differently surface here, cheaply.
- Publish. It becomes available to role standards, assessments and development plans across the organization.
- Observe. Usage, assessment spread and disagreement between assessors are visible to the owner as evidence the definition is working.
- Revise or retire. Changes are versioned, so an assessment made last year still says which definition it was made against.
Four ways a framework dies
- It was too big to learn
- Several hundred competencies is a reference work. Managers use what they can hold in their head, which in practice is a handful per role.
- The wording could mean anything
- Advanced stakeholder management means whatever the reader wants. A definition that cannot be disputed cannot be evidenced either.
- Nobody owned it
- A framework owned by a project that ended is a framework that stopped tracking the work the day the project closed.
- It only touched appraisals
- Vocabulary used once a year is vocabulary nobody learns. It has to appear in hiring, development and staffing decisions to stay alive.
Questions
What HR leaders ask before rebuilding a framework
What is the difference between a skill and a competency here?
A skill is a discrete capability that can be assessed on its own and means roughly the same thing anywhere. A competency describes how skills, judgement and conduct combine in your organization's context, which makes it specific to you and usually harder to evidence. The platform models both, because role standards need skills for precision and competencies for the parts of a job that no test captures.
We already have a framework in a spreadsheet. Do we start over?
No, and starting over is usually the wrong instinct. Import what exists, then work through it by usage: the competencies actually referenced by roles get an owner, observable level definitions and a review date, and the rest sit in an archive until something claims them. Most organizations find that a third of the framework is doing all the work.
How many competencies should a role have?
Fewer than feels responsible. A role standard that lists twenty competencies will be read once and never used to make a decision. Somewhere between five and eight, each one genuinely load-bearing for the job, produces a standard managers can hold in their head and apply consistently, which is the only kind that changes anything.
Who should own a competency?
Someone in the business who does the work, not HR. HR owns the method, the levels scale and the governance cadence; the person who runs delivery owns what good delivery looks like. Frameworks owned entirely by a central function drift from the work because the people who notice the drift have no way to change the record.
Bring the framework you already have
Send us the spreadsheet. We will show you which competencies are actually referenced, what it would take to make them evidence-based, and what the first role standard would look like.
Keep reading
-
Skills
How skills, levels and evidence are modelled underneath.
-
Enterprise
The full workforce view for HR, L&D and leadership.
-
Employee skill assessment
Establishing a level against a definition, from evidence.
-
Skills gap analysis
What a role standard is for once people are measured against it.
-
Workforce analytics
What the framework lets you report once it is in use.
-
Reskilling
Using shared definitions to find the roles a person is closest to.