Articles about organizational intelligence, measurement, and human systems.
An assessment can identify ten gaps without producing a single priority. When every gap becomes an action, the development plan stops providing direction: it spreads attention, combines different degrees of urgency, and makes progress nearly impossible to recognize.
An organization may spend months searching for a capability that already exists within it but is associated with another title, another industry, or a problem described by a different name.
If reasonable assessors cannot explain which evidence separates two adjacent levels, the architecture contains a nominal distinction—not a usable progression.
Closing a gap in a person's current role and preparing for the next level may involve similar actions, but they answer to different commitments. Combining them changes both the priority and the meaning of the assessment.
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.