Most so-called competency models are a category error. They are flat lists of traits treated as if they were a structure. The real thing is an architecture — and the difference matters far more than the language suggests.
Open almost any competency framework and the same pattern appears: a bulleted list. Strategic thinking. Executive presence. Business acumen. Change orientation. The list is long, the definitions are generous, and every item is defensible in isolation. The problem is not any single competency. The problem is that a list is not a model.
A model has structure. It says how the parts relate, what depends on what, and what changes when. A list says only that these things exist and are considered good. Two organizations can share every item on the list and still be talking about entirely different things — because the underlying architecture is where the meaning lives, and the list does not carry it.
The underlying architecture is layered. At the base is mode of thinking — how a person processes complexity and time. Above that sits capability — the applied judgment that mode enables in a specific kind of work. Higher still is fit — the match between capability and the actual demands of the role. Traits like 'strategic thinking' are outputs of that stack, not building blocks of it. Naming the output without naming the stack is the category error.
This is why lists proliferate without ever settling. Each generation of leaders adds their favorite terms; each vendor markets a new taxonomy. The list grows; the model does not exist. The way out is not a longer list. It is dropping the list altogether and describing the architecture — layer by layer — that produces the behaviors the list was trying to point at.