Most competency models I am shown started life as a job analysis that never got translated. Someone ran interviews, built a task inventory, wrote up the knowledge and skills required, called the output a competency model and stopped. What they produced is a job analysis with a new label. The two are related, but they are different exercises, and treating them as one is why so many competency models read like duty statements instead of describing what effective performance looks like.
This article is about method. It covers where job analysis sits in building a competency model, what evidence it supplies, and where the translation from tasks to behaviours has to happen.
What Is Competency Model Job Analysis?
Competency model job analysis is the systematic study of a role, using job analysis methods, as the evidence base for a role-level competency model. It borrows the data-gathering discipline of traditional job analysis, covering tasks, duties, working conditions and input from incumbents and supervisors, and uses that evidence to identify, define and validate the competencies a role needs. I call the result a competency profile: the competencies and required levels for one role.
Traditional job analysis is task-oriented. It documents what a job holder does, in what conditions and to what standard, and it serves classification, pay grading and defensible selection criteria. Competency modelling is behaviour-oriented. It asks what a person needs to demonstrate, across changing tasks, to perform effectively now and as the role evolves. The competency model job analysis is the bridge between the two.
Job analysis supplies the evidence. The competency profile is what is built from it.
A note on terminology. A competency framework is also called a competency model, especially in the United States. I use competency profile for the competencies and required levels for one role, and competency matrix for the grid of required against current proficiency. Usage varies by region, and I explain the differences in this competency model definition.
Why Job Analysis Belongs in the Process
A competency profile built without evidence is a guess presented as strategy. HR teams under time pressure often lift competencies from a generic library, apply the organisation's branding and move on. It looks credible in a leadership meeting. It falls apart when a manager asks why strategic thinking appears in a frontline supervisor role, because nobody checked what the role requires.
Job analysis answers that question with evidence rather than opinion. People who do the work can tell the difference between a competency derived from watching the work and one copied from a template. The first gets used. The second gets filed. The broader build steps sit in my guide to competency model development.
The Five Steps
1. Identify subject matter experts
High-performing incumbents and their supervisors are the primary data source. A panel of four to eight per role is typical: large enough to compare views, small enough to manage.
2. Gather the evidence
Use established job analysis techniques: structured interviews, the critical incident technique, behavioural event interviews, task inventories and, where the role allows, direct observation. The aim is a documented set of tasks, critical incidents and the knowledge, skills, abilities and other characteristics associated with strong rather than average performance.
3. Translate tasks into behaviours
This is the step that separates the two exercises. A task describes what is done. A competency describes how effective performance looks, stated as observable behaviour. The task of preparing monthly budget variance reports becomes the competency of financial analysis and judgement, defined by what separates a strong report from a mediocre one.
A task inventory stops at the first row. A competency profile goes through all four.
4. Check against the framework
Group the translated behaviours into clusters and check them against the organisation's competency framework, so the profile reuses shared definitions rather than inventing parallel language for the same thing.
5. Set levels and confirm with the experts
Level each competency against observable indicators, then return to the panel for a validation pass. If the panel does not recognise the result as a description of their work, the analysis was incomplete.
Named Approaches Worth Knowing
McClelland's 1973 paper, Testing for Competence Rather Than Intelligence, argued for studying what top performers actually do rather than relying on aptitude tests. Behavioural event interviewing grew out of that tradition and works from critical incidents given by top and average performers to isolate the behaviours that separate them.
The O*NET Content Model, maintained for the US Department of Labor, holds job-oriented data such as tasks and work activities alongside worker-oriented data such as skills, abilities and knowledge in one taxonomy. It is a clear public illustration of how task-level evidence maps onto competency-style constructs at scale. The Department's competency model publications show the same layering, with foundational competencies beneath industry and occupation-specific ones.
In government, the US Office of Personnel Management builds its governmentwide competency models from structured occupational studies with incumbents and supervisors. It is a large-scale, standardised version of the same expert-driven process a single organisation runs on a smaller scale.
What Competency Model Job Analysis Is Not
- It is not traditional job analysis alone. That stops at tasks and duties and does not, by itself, produce levelled behavioural competencies.
- It is not a competency framework. The framework is the organisation-wide system. This method produces the evidence for one role-level profile that draws on, and feeds back into, the framework.
- It is not a job description. A job description records responsibilities and reporting lines. It rarely says what level of proficiency is required.
- It is not a shortcut. Borrowing competencies from a library is a fair starting point when speed matters. Once the evidence step is removed, it is labelling, not analysis.
Matching the Depth to the Stakes
Select the depth by what the profile will be used to decide.
Full analysis takes weeks, not days, and the cost is only justified when the profile will carry real weight: selection decisions, regulated occupations, high-volume roles or anything likely to face legal scrutiny. Where the stakes are lower, adapting framework competencies with a short expert sense-check is defensible. The judgement is matching depth to use, not applying maximum rigour everywhere or skipping it everywhere to save time. For use in assessment, see the competency assessment framework guide.
Common Failure Modes
- Stopping at step two. The task inventory is presented as the profile. It reads like a job description with a proficiency scale added, and nobody can say what level three looks like.
- Skipping the analysis. A purchased library produces polished competencies that do not describe the role. Line managers notice and quietly stop using them.
- Under-sampling. One or two interviews reflect those individuals, not the role.
- Skipping validation. A profile not checked back with the panel is a hypothesis, and it is usually treated as one the first time it informs a real decision.
FAQ
Is job analysis the same as competency modelling?
No. Job analysis documents tasks, duties and conditions. Competency modelling translates that evidence into behavioural competencies with proficiency levels. Job analysis is an input and the competency profile is the output.
Do you always need job analysis to build a competency model?
No. Adapting framework competencies suits low-stakes or fast-turnaround needs. Full job analysis is warranted when the profile will drive selection, regulated roles or other high-stakes decisions.
Who should be involved in the job analysis?
High-performing incumbents and their direct supervisors, typically four to eight per role.
What is the difference between a task and a competency?
A task describes what gets done. A competency describes the behaviour, skill and judgement that separates strong performance from average performance in doing it.
How many experts are enough?
There is no fixed number, but one incumbent reflects that person, not the role. Most practitioners compare four or more before treating the output as representative.
Does job analysis replace the competency framework?
No. It produces the evidence for one role-level profile. That profile should draw on and stay consistent with the framework's definitions and levels.
