Strategy & Job architecture

Competency management: from loose competencies to a working model

How to define competencies with behavioral indicators per level, measure them through assessments and feedback, and let them carry through into matching and development.

In short

  • Competency management is the systematic definition, measurement and development of competencies in the organization.
  • It starts with the job architecture. Which competencies does each role require, at what level, and with which behavioral indicators?
  • Competencies only become useful when they are reusable. Define once, use in multiple job profiles.
  • The value arises when competencies carry through into assessments, matching and development. Not as a loose list, but as a working model.

What is competency management?

Competency management is the systematic definition, measurement and development of the competencies your organization needs. It goes further than a list of competencies: it is a model that determines which competencies are relevant per role, at what level they are expected and how you measure and develop them.

In practice, that means defining competencies with behavioral indicators per level, assigning them to job profiles, measuring them through assessments and 360° feedback, and using the results for matching and development.

Competency management is not a goal in itself. It is the mechanism that ensures the job architecture, the assessments and the matching all work in the same language. Without a competency model you are comparing apples and oranges.

From loose competencies to a working model

Many organizations have competencies, but no competency model. The difference is structure and reusability.

  • Loose competencies: each manager defines their own competencies per vacancy. No consistency, no comparability, no basis for matching.

A competency model: competencies are defined centrally with behavioral indicators per level. They are reusable, so the same competency has the same definition everywhere. They are assigned to job profiles from a library.

  • Behavioral indicators per level: "communication" at junior level looks different from senior level. By recording behavioral indicators per level, the expectation becomes concrete and measurable.
  • Competency levels: a layered model (for example basic, advanced, expert) makes growth visible and development targeted. You know not only which competency someone needs, but also at what level.

Competencies in the job profile

Competencies are one of the building blocks of the job profile. They describe the talent profile that fits the role, meaning what someone needs to bring to be successful.

In the job profile, competencies sit alongside skills, responsibilities and KPIs. Together they form the complete standard.

The strength lies in reusability. If you define "customer focus" with behavioral indicators per level, you use the same definition in the profile of an account manager, a customer service employee and a project leader. The expected level differs, but the definition is consistent.

That makes comparison possible. You can match employees on the same competencies, regardless of their current role. That is the basis for internal mobility and career moves.

Measuring competencies: from definition to data

Defining competencies is step one. Measuring is step two. Without measurement, competencies remain a reality on paper only.

  • Assessments measure aptitude and behavior: an assessment tests how someone scores on the competencies the role requires. The difference between aptitude and demonstrated behavior is one of the most valuable insights.
  • E-assessments measure at scale: online questionnaires that measure aptitude and potential for the whole organization. Suitable as the basis for the talent profile.

360° feedback measures behavior in practice: colleagues and managers assess how competencies show up in day-to-day work. That is the mirror you cannot hold up yourself.

The combination of assessment (aptitude) and 360° feedback (behavior) gives the most complete picture.

From competencies to matching and development

Competency data only becomes valuable when it flows into matching and development.

  • Matching: the job profile defines which competencies a role requires. The talent profile (from assessments and feedback) shows how someone scores. Matching compares the two and shows where the fit is and where the development opportunities lie.
  • Development: differences between the job profile and the talent profile become concrete development goals. Not everything at once, but a focus on the competencies where the aptitude is there and the behavior can still grow.
  • Internal mobility: matching on competencies makes internal mobility well-founded. You see which employees fit which roles, including roles they are not in now.

In this way, competencies are not just a definition; they are also turned into concrete action and growth.

Common mistakes in competency management

Competency management can deliver a lot, but there are pitfalls.

  • Too many competencies: if every role has 15 competencies, the model loses its focus. Limit yourself to the five to eight competencies that are most relevant per role.
  • Generic definitions: "communication" without behavioral indicators per level is neither measurable nor comparable. Invest in concrete behavioral indicators.
  • No link with processes: competencies that do not come back in selection, assessments and development are a paper exercise. The value lies in the use.
  • One-off instead of living: competencies change as roles change. Build a model that moves along with the organization.
  • No reusability: if each manager defines their own competencies, inconsistency arises. Work from a central library with reusable definitions.

Frequently asked questions

How many competencies should a job profile have?

Five to eight competencies per job profile is a good guideline. Measuring more does not provide more insight, but makes the model less focused. Focus on the competencies that are most distinctive for the role.

What is the difference between competencies and skills?

Skills are specific, often technical abilities that you can learn, such as Excel, project management or Python. Competencies are broader and describe behavior in a work context, such as customer focus, analytical ability or leadership. Competencies have a stronger link with personality and aptitude.

Should I develop my own competency model?

Not necessarily. You can start with an existing framework and adapt it to your organization. The most important thing is that competencies are defined consistently, have behavioral indicators per level and are reusable in multiple job profiles.

How do I keep competencies up to date?

By linking competencies to the job architecture and having them come back in assessments, feedback and development. If a competency is no longer relevant for a role, that becomes apparent in use. That way the model stays alive.

Can AI help define competencies?

Yes, AI can generate behavioral indicators based on the role and the level. But the output must always be validated by the organization. AI speeds up the process; the organization safeguards the quality.

You decide on career progression based on more than gut feeling

For each job, Talensa defines what the role requires, measures where someone stands and follows the development plan until the next measurement point. That way, you have the facts on the table in every conversation about career progression.

ISO/IEC 27001 certified (27001 10112026.1) · Hosting in the EU · Data processing agreement