That is, the KSAOs are described in a manner that highlights their relationships
to the work or the objectives, or sometimes the KSAOs needed
to achieve each objective are identified and grouped together. In addition,
they are usually defined in terms of observable job behavior. Sometimes
this characteristic even affects how the competency model is developed. A
traditional job analysis is inductive (starting with job tasks and KSAOs to
arrive at conclusions about what is important to the job), whereas competency
modeling is more deductive (starting with the outcomes and backing
into the tasks and KSAOs).
Fifth, they are developed top down rather than bottom up like job
analysis. They not only start with gathering information from executives
rather than lower level job employees like job analysis, but they usually
start with defining the competencies for executive jobs and then work their
way down.
Sixth, competency models may consider future job requirements either
directly or indirectly (e.g., Parry, 1996; Rodriguez et al., 2002; Schippmann
et al., 2000). They do not document the status quo but attempt to
look into the future and sometimes try to even define that future.
Seventh, competency models are usually presented in a manner that
facilitates ease of use. Designing for ease of use often includes the utilization
of organization-specific language. Models may be in the form of