Why should different roles rate the same items?

Executives, HR, managers, and specialists see the same processes differently. The differences between roles, tensions such as executive blind spots or high variance, show where leadership's picture diverges from everyday reality and focus the discussion on the right things.

How many respondents does a measurement need?

Groups with fewer than three responses should not be analyzed, and a role average is meaningful only when a role has at least two respondents. These limits protect both result reliability and respondent anonymity.

FAQ

How do you measure competence management in practice?

Q: How do you measure competence management?

By rating the maturity of competence management processes regularly, from several roles, and with a sufficient number of respondents. Each sub-area is rated on three dimensions (operational, experiential, impact) on a 1-10 scale, and the measurement is repeated on an agreed rhythm to produce a trend.

Competence management is measured by rating process maturity regularly, from several roles, and with enough respondents. A single survey gives you a snapshot; only repeated measurement gives you a direction.

Three principles of measurement

1. The same framework every time. When the same sub-areas are rated on the same scale (1-10) and the same dimensions (operational, experiential, impact), results are comparable from one measurement round to the next. Without a fixed framework there is no trend.

2. Several roles, same questions. Leadership often rates processes higher than employees experience them. That gap is not a measurement error; it is the most valuable finding, showing where the management picture and everyday reality diverge. Role-based assessment makes these tensions systematically detectable.

3. Enough respondents. Do not compute statistics from small groups: a group with fewer than three responses gives neither a reliable picture nor anonymity protection. A role average is meaningful only when the role has at least two respondents.

From measurement to management

Measurement becomes management with three additional steps: results are reviewed by role (where are the tensions?), development initiatives are logged at measurement points (which initiative was running when maturity changed?), and next actions are prioritized by gaps (where is the current state furthest from the target?).

The practical setup is light: an assessment round starts with an invite link with no user management for assessors, and results, trends, and tensions update automatically. Start with a free trial.

A worked example

Situation

The same firm wants to know whether last year's mentoring programme changed how competence needs are identified. HR has a skills list from the spring. Leadership wants a number they can put in a quarterly review. Nobody can show a before-and-after of the practice itself.

What to measure

Do not treat the skills list as the measure of the process. Rate the identification practice on the same 1-10 framework, from leadership, HR, managers and specialists, and keep the same items for the next round. Invite enough people that a role result can be shown: at least two respondents in a role, and do not analyse groups smaller than three.

How to read the result

A first round might show leadership at 7 on the operational dimension and specialists at 4 on the experiential dimension for the same item. That gap is the finding. It does not prove the mentoring programme failed or succeeded. It shows whose picture of the practice you currently have, and where coverage is still missing.

A decision that follows

Record the mentoring programme against the identification area, agree one change you can make in how needs are collected this quarter, and set the next measurement date. At the next round, look at the same item and ask what else besides the programme could explain a move. A higher score alone is not proof of impact.