
Who should own a skills architecture
Who can change a skill, approve a level, or decide that the evidence is sufficient to use a result? These three decisions require different authorities.
PRYSMAP brings together perspectives on organizational intelligence, measurement, and human systems.
99 articles

Who can change a skill, approve a level, or decide that the evidence is sufficient to use a result? These three decisions require different authorities.

A scale reduces differences in interpretation when it requires assessors to recognize the same evidence—not when it replaces vague words with more elegant labels. Designing one means defining what will be observed, making the boundaries between levels explicit, and testing those boundaries with cases that reveal where disagreement begins.

A conversation about a gap does not require softening the evidence until it becomes unrecognizable. It requires separating the expectation, the observation, and the interpretation so that the person can understand and participate.

Creating a separate skills catalog for every role offers immediate precision: each position receives a tailored list. The cost comes later, when the same capabilities are duplicated under different names, levels, and criteria, and every change requires dozens of versions to be maintained.

A skill is a useful construct for organizing capabilities, but an assessment cannot access it directly. It accesses decisions, explanations, procedures, outcomes, and behaviors produced under specific conditions.

Identifying a gap does not justify prescribing training. First, we need to understand what is preventing performance and what kind of intervention might change it.

When two roles share the same skills, the meaningful distinction does not come from changing the catalog. It comes from specifying the level of contribution the organization expects from each role.

A skill is a useful construct for organizing capabilities, but it never appears as a complete object to the person assessing it. What we see are partial manifestations in specific tasks, decisions, and contexts.

Choosing who should assess a skill is not a search for the most reliable source. It is an exercise in identifying who had sufficient access to the behaviors, decisions, and outcomes relevant to the conclusion we need to draw.

Track, role, and level answer different questions. When an architecture treats them as synonyms, every change in title ends up altering skills, expectations, and mobility paths that should remain separate.

A skills assessment is sound when it can support both the interpretation of its results and the decisions made from them. Five conditions must work as a chain: object, evidence, levels, sources, and rules.

A gap describes the distance between performance and an expectation. Turning it into development requires interpreting its origin, setting its priority, addressing the likely cause, and then checking what changed in the work itself.