The definition of competencies as SKAO either singularly or in plural is a technical definition that we sometimes use internally. On the Overview page, we have:
Competencies can represent competencies, skills, knowledge, abilities, traits, learning objectives, learning outcomes, and other similar constructs that define performance, mastery, attainment, or capabilities.
There's another definition that flows more easily from the dictionary definition of "Competence" being "the ability to do something effectively or efficiently" -- that is, a competency is "the ability or capability to do a specific thing effectively or efficiently."
I found this trying to create the least presumptive definition of competency that I could, so that a conversation with six companies wouldn't devolve into arguing definition.
This latter definition created zero pushback across ~35 people I spoke with, and actually engendered a willingness to speak about competencies across organizations.
- Should we distinguish between a technical definition and a general definition?
- Which definitions should we use?
The definition of competencies as SKAO either singularly or in plural is a technical definition that we sometimes use internally. On the Overview page, we have:
There's another definition that flows more easily from the dictionary definition of "Competence" being "the ability to do something effectively or efficiently" -- that is, a competency is "the ability or capability to do a specific thing effectively or efficiently."
I found this trying to create the least presumptive definition of competency that I could, so that a conversation with six companies wouldn't devolve into arguing definition.
This latter definition created zero pushback across ~35 people I spoke with, and actually engendered a willingness to speak about competencies across organizations.