Job Analysis, Competencies and Performance Standards

Introduction and Context

Performance management begins before an objective is written or an appraisal form is completed. It begins with a defensible understanding of the work itself. Job analysis identifies what a role exists to accomplish, the activities through which it creates value, the resources and constraints surrounding it, and the knowledge, skills, abilities and other characteristics required for effective performance. Role profiles translate this understanding into an accessible managerial document. Competency frameworks describe the capabilities and behaviours that enable performance across roles or occupational groups. Performance standards specify the level, quality, timeliness, reliability and behavioural manner expected in a given role.

These elements form an architecture for performance management. If the architecture is weak, performance objectives may be irrelevant, appraisal criteria may be inconsistent, recruitment may select unsuitable candidates, and development activity may address symptoms rather than causes. If the architecture is sound, employees can understand what they are accountable for, managers can evaluate performance more fairly, and the organisation can align individual contribution with strategy.

The challenge is greater in contemporary organisations. Traditional jobs often have relatively stable duties and reporting relationships. Agile roles may involve changing priorities, cross-functional teams and shared accountability. Evolving roles—such as data product manager, sustainability analyst or AI governance specialist—may not have established occupational boundaries. Consequently, job analysis must be rigorous without becoming rigid.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the purpose, scope and methods of job analysis.
2. Distinguish job descriptions, role profiles, competencies, behavioural indicators and performance standards.
3. Construct accountabilities and performance criteria that are relevant, observable and strategically aligned.
4. Apply competency frameworks to traditional, agile and evolving roles.
5. Evaluate the reliability, validity, fairness and practical usefulness of performance standards.
6. Design a role architecture that supports performance management, development and workforce decisions.

1. The Architecture of Work and Performance

A job is a bundle of relatively enduring responsibilities performed in exchange for employment. A role is broader and more relational: it describes the contribution expected from a person within a particular organisational system. One employee may occupy several roles, and a role may be distributed across a team rather than assigned to one individual.

The following distinctions are central:

A useful performance architecture connects these elements:

Organisational strategy → role purpose → accountabilities → objectives and standards → competencies and behaviours → evidence and feedback

The sequence is not entirely linear. Evidence from performance reviews, changing technology, customer needs and employee experience should periodically inform a revision of role profiles and standards.

Job purpose and accountabilities

A job purpose is a concise statement of the role’s fundamental contribution. It should explain why the role exists, whom it serves and the value it creates. For example:

“To convert customer and operational data into reliable insights that improve service decisions and business performance.”

Accountabilities are enduring areas of ownership for which the role-holder is answerable. They are not simply lists of activities. “Prepare monthly reports” describes an activity; “provide accurate and timely management information for operational decisions” describes an accountability. Accountabilities should normally be few enough to prioritise—often four to eight—and broad enough to remain meaningful as methods change.

Outputs, outcomes and inputs

Outputs are immediate products or services, such as a report, design, completed transaction or trained employee. Outcomes are the consequences or value produced by those outputs, such as improved decision quality, reduced processing time or increased capability. Inputs include resources, information and authority required to perform the work. High-quality role profiles distinguish these concepts so that employees are not evaluated solely on activity volume when the organisation actually needs valuable outcomes.

2. Job Analysis: Purpose, Scope and Methods

Job analysis is a systematic process of collecting, validating and interpreting information about work. It can support recruitment, workforce planning, job evaluation, learning design, succession planning, reasonable adjustments and performance management. It should be conducted for the purpose at hand because the level of detail required for legal classification differs from that required for agile team design.

What should be analysed?

A comprehensive analysis may examine:

• major responsibilities and recurring activities;
• expected outputs and outcomes;
• stakeholders, customers and service relationships;
• decision rights, authority and escalation routes;
• technology, equipment and information used;
• working conditions and constraints;
• interdependencies with other roles;
• knowledge, skills, abilities and other characteristics;
• risks, compliance obligations and ethical responsibilities;
• indicators of effective and ineffective performance; and
• foreseeable changes in the work.

Main methods

Interviews with role-holders, supervisors, customers and subject-matter experts provide rich contextual information. Structured interview guides improve comparability, while critical-incident questions—“Describe a time when excellent performance made a difference”—often reveal important behaviours.

Observation is valuable where work is visible and frequent, such as manufacturing, customer service or clinical processes. It is less suitable for infrequent managerial decisions, confidential work or cognitively complex activity that cannot easily be observed.

Questionnaires and inventories enable information to be collected from many employees. Standardised instruments improve efficiency but may encourage respondents to overstate the importance of their own tasks.

Work diaries and activity logs capture variation over time and can reveal interruptions, coordination demands and hidden work. They must be interpreted carefully because recorded frequency does not necessarily equal strategic importance.

Document and data analysis uses procedures, service-level agreements, risk registers, customer feedback, workflow records and performance data. Data should inform, not automatically determine, the role profile; digital traces may be incomplete or biased.

Workshops and focus groups are useful for mapping interfaces and distinguishing individual from team accountability. Skilled facilitation is needed to prevent senior voices from dominating.

No single method is universally superior. Triangulation—comparing information from multiple sources—improves credibility. The analyst should record the source, date, context and degree of agreement for major conclusions.

A practical job-analysis process

1. Clarify the purpose and scope. Identify whether the analysis supports performance, recruitment, redesign, compliance or several purposes.
2. Identify knowledgeable sources. Include incumbents, managers, internal customers, technical experts and, where appropriate, employee representatives.
3. Collect work evidence. Combine interviews, observation, documents, workflow data and critical incidents.
4. Separate work from person. First identify what the role requires; only then specify the capabilities needed to perform it.
5. Map accountabilities and interfaces. Clarify ownership, collaboration, consultation and escalation.
6. Draft the role profile and standards. Use outcome-oriented language and distinguish minimum requirements from preferred capabilities.
7. Validate. Review the draft with stakeholders and test whether it represents actual and future work.
8. Govern and review. Assign ownership, version control and a review cycle triggered by material changes.

3. Role Profiles for Different Types of Work

A role profile is more adaptable than a traditional duty-based job description. It normally includes:

• role title, level and reporting relationships;
• purpose and contribution;
• key accountabilities;
• decision authority and boundaries;
• major stakeholders and interfaces;
• expected outputs and outcomes;
• technical and behavioural competencies;
• performance standards and evidence sources;
• essential qualifications or experience, where justified; and
• likely developments in the role.

Traditional, agile and evolving roles

For agile roles, the role profile should state enduring accountabilities while leaving methods and task sequences adaptable. A product owner, for example, may remain accountable for product value and prioritisation even when the backlog, tools and team structure change. Performance standards should not reward the mere completion of ceremonies; they should examine value delivered, decision quality, stakeholder alignment and learning.

For evolving roles, profiles can include “near-term accountabilities,” “capabilities under development” and “conditions for responsible experimentation.” This avoids pretending that uncertain work can be described with false precision.

4. Competencies and Behavioural Indicators

A competency is an integrated set of knowledge, skills, motives, attributes and behaviours associated with effective performance in a work context. Competencies are not personality labels. They should be expressed in job-relevant terms and supported by evidence.

Competencies may be classified as:

• core competencies, expected across the organisation, such as ethical conduct or collaboration;
• functional competencies, specific to a discipline, such as financial modelling or employment-law interpretation;
• leadership competencies, relevant to influence, direction and stewardship; and
• technical or digital competencies, relating to tools, methods, systems and professional standards.

A competency framework should answer three questions:

1. Which capabilities matter for the organisation’s strategy?
2. How do they differ across levels or contexts?
3. What observable behaviour demonstrates effective use of the capability?

Behavioural indicators

Behavioural indicators translate an abstract competency into observable evidence. Consider the competency evidence-based decision-making:

• Developing: identifies relevant information and distinguishes evidence from assumption when prompted.
• Proficient: evaluates the quality of evidence, explains trade-offs and makes proportionate decisions.
• Advanced: integrates uncertain evidence, tests assumptions and enables others to make sound decisions.

Indicators should describe behaviour, not labels such as “excellent communicator” or “strategic thinker.” They should avoid unnecessary cultural or personality assumptions. “Invites relevant dissent before finalising a high-risk decision” is more assessable than “has a positive attitude.”

Proficiency levels

A four-level scale can be useful when its meaning is defined:

1. Foundational: performs structured aspects with guidance.
2. Working: performs independently in familiar situations.
3. Advanced: handles complexity, coaches others and adapts methods.
4. Expert or strategic: shapes practice, resolves novel problems and influences across boundaries.

Levels should not be treated as universal rankings of human worth. A role may require expert technical skill but only working-level people leadership. Competency level must therefore be matched to role context.

5. Designing Performance Standards

A performance standard describes the expected level of performance against an accountability or objective. Strong standards combine clarity with judgement. They may address:

• quantity: volume, capacity or coverage;
• quality: accuracy, completeness, reliability or customer value;
• time: deadlines, cycle time or responsiveness;
• cost or resources: budget adherence and efficient use of resources;
• risk and compliance: controls, safety, confidentiality and lawful conduct;
• service or relationship: stakeholder experience and responsiveness; and
• behavioural contribution: collaboration, inclusion, learning and responsible challenge.

A standard should be relevant, observable, sufficiently controllable by the role-holder and proportionate to the role. It should identify evidence sources and distinguish absolute requirements from desirable performance.

Standards, targets and measures

A measure is an indicator used to assess performance. A target is a specified desired value or condition for a defined period. A standard is the broader expectation, which may include qualitative judgement, professional requirements and contextual constraints. Not every important standard can be reduced to a single number.

For example, a contact-centre standard might require timely resolution, accurate information, respectful interaction and appropriate escalation. A narrow target based only on call duration could encourage employees to rush customers or avoid complex cases.

Quality criteria for standards

A useful test is the CLEAR principle:

• Connected: linked to strategy and the role purpose;
• Legitimate: within the role’s reasonable influence;
• Evidence-based: supported by credible information;
• Adaptable: capable of revision when conditions materially change; and
• Reviewable: discussed regularly with documented rationale.

The familiar SMART approach—specific, measurable, achievable, relevant and time-bound—can help with objectives, but it is insufficient by itself. “Measurable” should not be interpreted as “numerical at all costs,” and “achievable” should not legitimise low expectations or ignore resource constraints.

Individual and team standards

Modern work often requires both individual and collective standards. Individual standards may cover professional expertise, reliability and ownership. Team standards may cover coordination, knowledge sharing, collective delivery and system improvement. Managers should clarify how contribution will be recognised when outcomes depend on many people. Otherwise, employees may compete for credit or avoid necessary assistance.

6. Alignment, Validity and Fairness

Performance criteria should demonstrate content validity: they cover important aspects of the work and do not overemphasise trivial or easily measured activities. They should also show construct validity: the criterion should represent the capability or contribution it claims to assess. A sales employee’s revenue may reflect territory quality, pricing and market conditions as well as individual skill; interpretation must therefore consider context.

The principle of controllability is equally important. Employees should not be held solely accountable for outcomes substantially determined by factors outside their influence. This does not eliminate accountability for preparation, escalation or risk management, but it requires careful attribution.

Fairness involves more than applying the same form to everyone. It requires equivalent opportunity to understand expectations, access to resources, consistent evidence rules, reasonable adjustments where required, and a process for reviewing disputed judgements. Standards should be examined for adverse impact and unnecessary barriers related to disability, gender, race, age, culture, caring responsibilities or other protected characteristics, in accordance with applicable law.

Managers should distinguish performance gaps caused by capability, motivation, role ambiguity, workload, system failure or conflicting goals. A disciplinary response to a poorly designed role is neither fair nor effective.

7. Technology and AI in Job Analysis and Performance Management

Digital tools can support job analysis by clustering task data, identifying workflow bottlenecks, summarising interviews and detecting changing skill demands. Natural-language systems can help draft role profiles, but generated text must be validated by knowledgeable humans. Automated systems may reproduce historical bias, infer sensitive characteristics, confuse activity with contribution or create surveillance pressures.

Governance should include:

• a documented purpose and lawful basis for data use;
• data minimisation and access controls;
• transparency about what is collected and how it informs decisions;
• human review and a route to challenge or correct records;
• testing for disparate impact and measurement error;
• retention and deletion rules; and
• clear separation between developmental analytics and disciplinary surveillance.

AI should assist professional judgement rather than replace it. In particular, an algorithm should not be allowed to convert proxies—such as keyboard activity, online presence or message volume—into presumed effort or value without strong evidence of relevance.

8. Applied Case: Redesigning Performance Standards at Northstar Services

The following is an illustrative fictional case.

Background

Northstar Services, a regional business-to-business support provider, employed 120 service specialists. Its annual appraisal system assessed employees mainly on number of tickets closed and average handling time. Leaders observed that complaints were increasing, complex cases were being transferred repeatedly, and experienced employees were reluctant to coach colleagues because coaching reduced their individual productivity statistics.

Problem

The existing measures were easy to calculate but poorly represented the organisation’s purpose: resolving customer problems accurately and maintaining long-term client trust. The standards also ignored team interdependence and encouraged undesirable behaviour.

Analysis

An HR project team analysed customer interviews, quality audits, ticket histories, employee diaries and manager interviews. It found four major accountabilities:

1. resolve customer issues accurately and appropriately;
2. communicate clearly and maintain professional relationships;
3. identify recurring causes and contribute to service improvement; and
4. support team capability and continuity.

The team also identified constraints: issue complexity varied substantially, some resolutions depended on engineering teams, and customer satisfaction was influenced by product defects outside a specialist’s control.

Approach and solution

Northstar replaced the single productivity emphasis with a balanced role profile. Standards included:

Ticket volume remained a diagnostic measure rather than a stand-alone rating. Managers reviewed cases in context, including complexity, system constraints and customer need. Monthly conversations replaced a single annual judgement. Employees could challenge inaccurate records and explain relevant contextual factors.

Outcome

After two review cycles, Northstar reported fewer repeat contacts, increased use of knowledge articles and improved employee perceptions of fairness. The organisation did not treat these changes as proof that every improvement was caused by the new system; it continued monitoring customer outcomes, workload and unintended effects.

Learning points

The case demonstrates that performance standards should represent value, not merely activity. It also shows the importance of triangulating evidence, recognising team contribution and preserving managerial judgement. A measure becomes harmful when it is easier to count than the actual work is to understand.

9. Implementation and Review

Implementation requires more than publishing a new template. HR should provide managers with guidance on writing accountabilities, gathering evidence, giving feedback and handling disagreement. Employees should participate in validating role profiles because they possess knowledge of informal work, hidden dependencies and operational risks.

A governance process should specify:

• who owns each role profile;
• when profiles are reviewed;
• what constitutes a material change;
• how new technology or regulatory requirements are incorporated;
• how competency indicators are calibrated across managers; and
• how employee feedback and appeal data inform improvement.

Calibration should focus on evidence and standards, not forced ranking. Managers can compare interpretations of proficiency levels, examine inconsistent ratings and identify whether some roles face systematically different conditions. Documentation should be concise enough to be used and detailed enough to support accountability.

Challenges and Limitations

Job analysis is not neutral. Participants may protect status, exaggerate responsibilities or describe ideal rather than actual work. Analysts may privilege visible tasks and miss emotional labour, informal coordination or inclusion work. Role profiles can become obsolete when strategy, technology or regulation changes. Competency frameworks can become bureaucratic dictionaries disconnected from real decisions. Quantitative standards can create gaming, tunnel vision and unhealthy competition. Conversely, standards that are entirely vague can produce inconsistency and bias.

These limitations cannot be eliminated by a perfect form. They are managed through multiple evidence sources, periodic review, transparent reasoning, employee participation and a willingness to revise assumptions. The central design principle is disciplined adaptability: be specific about contribution and responsible behaviour, while remaining open about how work may be accomplished as circumstances change.

Chapter Summary

Job analysis provides the evidence base for understanding work. Role profiles convert that evidence into purpose, accountabilities, interfaces and expected contribution. Competency frameworks identify the knowledge, skills, attributes and behaviours that enable effective performance, while behavioural indicators make abstract capabilities observable. Performance standards define expected quality, quantity, timeliness, risk management and relational contribution.

Effective systems distinguish activities from outcomes, measures from standards, and individual from team accountability. They triangulate information, respect controllability, test validity and address fairness. Traditional roles may require relatively stable descriptions, whereas agile and evolving roles require enduring purposes, flexible methods and periodic renegotiation of accountabilities. Technology and AI can support analysis but must be governed for transparency, privacy, validity and human review. Ultimately, performance criteria should help people understand valuable work, improve it and contribute responsibly to organisational purpose.

Key Terms

Job analysis: Systematic collection and interpretation of information about work.

Job description: Formal statement of duties, requirements and employment conditions.

Role profile: Outcome-oriented description of a role’s purpose, accountabilities, interfaces and capabilities.

Job purpose: Concise statement of why a role exists and the value it creates.

Accountability: An enduring area of ownership for which a role-holder is answerable.

Output: Immediate product or service produced by work.

Outcome: Effect or value resulting from an output.

Competency: Integrated capability associated with effective performance in context.

Behavioural indicator: Observable behaviour demonstrating a competency.

Core competency: Capability expected across an organisation.

Functional competency: Capability specific to a professional or technical field.

Proficiency level: Defined degree of capability in a competency.

Performance standard: Expected level, quality, timing or manner of performance.

Measure: Indicator used to assess an aspect of performance.

Target: Desired value or condition for a defined period.

Content validity: Extent to which criteria cover important aspects of the work.

Controllability: Degree to which a role-holder can reasonably influence an outcome.

Triangulation: Comparison of evidence from multiple sources or methods.

Calibration: Process of improving consistency in managerial interpretation and rating.

Role ambiguity: Lack of clarity about responsibilities, authority or expected results.

Review Questions

Short Answer Questions

1. Distinguish a job description from a role profile.
2. What is the difference between an output and an outcome?
3. Identify four sources of evidence that may be used in job analysis.
4. What is a behavioural indicator, and why is it useful?
5. Explain the principle of controllability in performance standards.

Long Answer Questions

1. Explain the job-analysis process and evaluate the strengths and limitations of at least three job-analysis methods.
2. Discuss how competency frameworks can support performance management without becoming bureaucratic or disconnected from work.
3. Compare the design of role profiles for traditional, agile and evolving roles.
4. Analyse the relationship between performance standards, validity and fairness.
5. Explain how organisations can govern the use of AI and digital data in job analysis and performance assessment.

Analytical / Application Questions

1. A university assesses academic advisers primarily by the number of students seen per week. Design a more balanced set of accountabilities and performance standards, explaining how you would avoid rewarding rushed or low-quality advising.
2. A software team shares responsibility for product delivery, but its appraisal system rates individuals only on personal task completion. Analyse the likely behavioural consequences and propose an individual–team performance architecture.
3. Select an emerging role in your sector. Construct a concise role purpose, four accountabilities, three competencies with behavioural indicators, and a review mechanism for updating the profile as the role develops.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes an accountability from an activity?

A. An accountability describes an enduring area of ownership, whereas an activity describes something done.

B. An accountability is always numerical, whereas an activity is always qualitative.

C. An accountability applies only to managers, whereas an activity applies only to employees.

D. An accountability is a personal trait, whereas an activity is a competency.

Correct Answer: A. An accountability describes an enduring area of ownership, whereas an activity describes something done.

Question 2

Which method is especially useful for understanding infrequent but consequential decisions?

A. Counting routine transactions only

B. Critical-incident interviewing

C. Measuring online presence

D. Using a generic personality inventory

Correct Answer: B. Critical-incident interviewing

Question 3

What is the primary purpose of a behavioural indicator?

A. To replace all performance evidence with a rating

B. To describe an observable demonstration of a competency

C. To rank employees across unrelated jobs

D. To specify an employee’s salary range

Correct Answer: B. To describe an observable demonstration of a competency

Question 4

Why can ticket volume be a poor stand-alone performance standard for service specialists?

A. It is never possible to measure ticket volume.

B. It may reward speed while ignoring complexity, quality and customer value.

C. It measures outcomes rather than activities.

D. It automatically accounts for team contribution.

Correct Answer: B. It may reward speed while ignoring complexity, quality and customer value.

Question 5

Which principle requires that employees not be held solely responsible for outcomes largely outside their influence?

A. Controllability

B. Seniority

C. Centralisation

D. Standardisation

Correct Answer: A. Controllability

Question 6

In an agile role profile, which element should generally remain stable while methods may change?

A. Every daily task sequence

B. The role’s enduring purpose and accountabilities

C. The exact software tool used

D. The annual ranking distribution

Correct Answer: B. The role’s enduring purpose and accountabilities

Question 7

What does content validity mean in performance assessment?

A. The criterion is popular with employees.

B. The criterion covers important aspects of the work.

C. The criterion is entirely numerical.

D. The criterion produces identical ratings for everyone.

Correct Answer: B. The criterion covers important aspects of the work.

Question 8

Which practice best supports credible job analysis?

A. Relying exclusively on the job-holder’s opinion

B. Using only historical job descriptions

C. Triangulating interviews, observation, documents and performance evidence

D. Allowing an algorithm to infer all accountabilities

Correct Answer: C. Triangulating interviews, observation, documents and performance evidence

Question 9

Which is the most appropriate use of AI in role-profile design?

A. Automatically determining employee worth from keyboard activity

B. Drafting and clustering information subject to human validation and governance

C. Removing employees’ ability to challenge performance data

D. Replacing subject-matter experts entirely

Correct Answer: B. Drafting and clustering information subject to human validation and governance

Question 10

A competency described as “invites relevant dissent before finalising a high-risk decision” is primarily an example of what?

A. An observable behavioural indicator

B. A job title

C. A compensation formula

D. A work output

Correct Answer: A. An observable behavioural indicator