Setup Considerations: proficiency scales

What this achieves

A proficiency scale defines the levels a skill or competency can be rated at. Every assessment, endorsement, and job-profile requirement is expressed on it, so changing the scale later changes what existing ratings appear to mean.

Decision 1: how many levels

Levels have to be distinguishable by the people using them. A manager who cannot articulate the difference between two adjacent levels will not apply them consistently, and their team’s ratings become noise.

Option	Description
Fewer levels	Applied more consistently. Less able to distinguish a capable practitioner from an expert, which matters when staffing or promoting.
More levels	Finer distinctions, and more disagreement about where the boundaries fall.

A five-level scale is the common default because it gives a clear middle and two steps either side. What matters more than the number is whether each level is described in terms someone can check.

Decision 2: describe levels by what someone does

The default descriptions in Humavera are written as observable behaviour rather than adjectives — aware of a skill but with limited applied experience, applies independently in standard situations, handles complex problems and coaches others, sets direction as the go-to authority.

Follow that pattern in your own scale. “Advanced” means nothing on its own; “handles complex problems and coaches others” can be judged against what someone actually did.

Example: Olivia Bennett rating one of her engineers at HC Corp UK Ltd can point at the complex work they handled and who they coached. She cannot point at “advanced”.

Decision 3: one scale or several

You can define more than one scale and set one as the default. Several scales let a technical ladder differ from a leadership one; they also mean two ratings in your organization are not comparable.

Start with one. Add a second only when a genuinely different progression exists and somebody has asked for it.

Decision 4: the scale is the contract with job profiles

Job profiles state the level a role requires, and gap analysis compares a person’s level against that requirement. The scale is what both sides are expressed in.

That is why the scale is worth settling before the library is built: a change to the scale changes every requirement and every held level at once.

Decision 5: deleting a scale is destructive

Deleting a proficiency scale makes every competency using it lose its proficiency level configuration. That is not a tidy-up, it is a data change across everything attached to the scale.

Retire a scale by moving what uses it onto another scale first, and delete only once nothing references it.

What is expensive to change later

Decision	Cost of changing later
Deleting a scale in use	Highest. Competencies using it lose their level configuration.
Changing the number of levels	High. Existing ratings sit on the old levels, and job-profile requirements move with them.
Rewriting level descriptions	Medium. Ratings already given were made against the old wording.
Which scale is the default	Low. It affects what is pre-selected next.
Adding a second scale	Low, but it costs comparability.

What happens next

Create the scale, then build the skill library and competency framework on top of it. Once people are assessed, the scale is what their levels, their endorsements, and every gap calculation are expressed in.