Articles about organizational intelligence, measurement, and human systems.
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.
A catalog identifies which skills exist and how to find them. An architecture adds the relationships needed to interpret expectations, assess evidence, guide development, and identify paths between roles.
More measurement can broaden understanding while making a decision harder. The difference depends on whether each signal has an explicit function, a defined audience, and a recognizable use.
Two people can observe the same behavior and reach different conclusions. The usual response is to ask which one of them got it wrong.