Work Analysis, Competencies and Skills Architecture

Introduction and Context

Human resource planning begins with a deceptively difficult question: what work must the organization be able to perform, both now and in the future? Headcount alone cannot answer this question. Two organizations may employ the same number of people while differing substantially in productivity, capability, technology readiness, regulatory compliance, and capacity to innovate.

Work analysis provides the foundation for answering the question. It examines what work is performed, why it is performed, how it is performed, and what capabilities are required. Traditional job analysis focuses on jobs and their tasks. Contemporary organizations also need to understand projects, processes, teams, platforms, customer journeys, and changing skill requirements. Competency models and skills architectures extend job analysis by connecting work requirements to observable behaviours, knowledge, technical skills, and developmental pathways.

For human resource planners, the purpose is not merely to produce job descriptions. The purpose is to create a reliable map between organizational strategy and workforce capability. This map supports workforce forecasting, recruitment, selection, learning, career development, succession planning, performance management, job evaluation, redeployment, and the identification of critical roles.

Learning Objectives

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

1. Explain the purpose, scope, and methods of job and work analysis.
2. Distinguish tasks, duties, responsibilities, jobs, roles, competencies, and skills.
3. Apply major approaches to work design and competency modelling.
4. Construct a basic skills taxonomy and job-family architecture.
5. Identify critical roles using business impact, scarcity, and risk considerations.
6. Evaluate the reliability, validity, ethical implications, and limitations of work-analysis data.
7. Use work-analysis outputs to support current and future workforce planning.

1. From Job Analysis to Work Analysis

Job analysis

Job analysis is the systematic process of collecting and evaluating information about a job’s tasks, responsibilities, context, outputs, and requirements. A job is a relatively stable bundle of related work activities performed by an individual or position. A job description normally records purpose, duties, reporting relationships, working conditions, and accountabilities. A job specification identifies the qualifications, knowledge, skills, abilities, and other characteristics needed for effective performance.

Work analysis

Work analysis is broader. It examines work wherever it occurs, including formal jobs, team processes, temporary assignments, projects, customer interactions, and technology-supported activities. This broader perspective is important because digital transformation, agile structures, remote work, contingent labour, and automation may change how work is organized without immediately changing job titles.

A useful hierarchy is:

The hierarchy is not absolute. A “role” may be a formal job in one organization and a temporary responsibility in another. The analyst must therefore define terms clearly before collecting data.

Why analysis is important for HR planning

Work analysis supports four planning questions:

• Demand: What work and capabilities will be required?
• Supply: What capabilities are currently available?
• Gap: Which capabilities are insufficient, excessive, obsolete, or poorly distributed?
• Action: Should the organization hire, develop, redeploy, redesign, outsource, automate, or partner?

Without accurate analysis, workforce plans may forecast numbers without understanding capability. For example, a forecast of ten additional employees in information security is incomplete unless it specifies whether the organization needs incident responders, cloud-security engineers, privacy specialists, governance professionals, or security-awareness trainers.

2. Conducting a Rigorous Work Analysis

A defensible work analysis normally follows a sequence, although practical projects may iterate between stages.

Stage 1: Define the purpose and scope

The purpose determines the evidence required. A selection-oriented analysis emphasizes essential performance requirements and assessment methods. A training analysis emphasizes knowledge and skill gaps. A workforce-planning analysis examines future changes, critical dependencies, and capability supply. Analysts should identify the population, stakeholders, time horizon, and decisions that the results will support.

Stage 2: Collect information

Common methods include:

• Document review: job descriptions, operating procedures, performance standards, risk registers, process maps, and strategic plans.
• Interviews: discussions with jobholders, supervisors, subject-matter experts, customers, and internal partners.
• Observation: direct examination of physical, administrative, service, or operational work.
• Questionnaires: structured inventories such as task checklists or competency ratings.
• Work diaries and sampling: recording activities over a defined period to reveal frequency and variability.
• Critical incidents: descriptions of unusually effective or ineffective performance and the behaviours that produced it.
• Workshops: facilitated sessions used to validate tasks, future changes, and capability priorities.
• Digital process evidence: workflow logs, ticket data, quality records, and system-use information, interpreted cautiously and with appropriate privacy safeguards.

No single method is universally superior. Interviews provide context but may be affected by memory and self-presentation. Observation captures actual behaviour but may miss infrequent activities. Questionnaires are efficient but can oversimplify complex work. Triangulation—comparing several sources—is therefore a central quality practice.

Stage 3: Describe work outputs and conditions

A task statement should identify an action, object, and purpose or standard. “Prepares monthly compliance reports for regulatory submission” is more useful than “handles compliance.” The analysis should identify:

• outputs and customers;
• frequency, duration, and variability;
• decision authority and escalation points;
• tools, systems, and information used;
• physical, social, and environmental conditions;
• quality, safety, legal, and ethical standards;
• relationships with other roles;
• consequences of error or delay.

Stage 4: Identify requirements

Requirements may include technical knowledge, procedural skill, reasoning, communication, physical capacity, digital literacy, interpersonal behaviour, and professional credentials. Requirements should be classified as essential, important, or desirable. Analysts must distinguish genuine job requirements from historical preferences or unnecessarily restrictive qualifications.

Stage 5: Validate and document

Jobholders and supervisors should review the findings. Where selection or promotion decisions are involved, relevant subject-matter experts should evaluate the importance and frequency of tasks and the relationship between requirements and effective performance. Documentation should record the methods used, participants, definitions, assumptions, review date, and evidence supporting each requirement.

3. Work Design and the Nature of Performance

Work design concerns how tasks, responsibilities, authority, technology, and relationships are arranged. Job analysis describes work; work design asks whether the arrangement produces effective, sustainable, and meaningful performance.

Classical and contemporary perspectives

Scientific management emphasized task specialization, standardization, and efficiency. These principles remain useful where consistency and safety are critical, but excessive fragmentation can reduce motivation and learning. The job characteristics model proposes that skill variety, task identity, task significance, autonomy, and feedback influence experienced meaningfulness, responsibility, knowledge of results, and work outcomes.

Socio-technical approaches emphasize joint optimization of social and technical systems. A new digital system may improve speed while reducing discretion, increasing surveillance, or creating new coordination burdens. Contemporary work design therefore considers employee experience, resilience, inclusion, health, collaboration, and the distribution of decision rights.

Useful design options include job enlargement, job enrichment, rotation, team-based work, flexible scheduling, remote work, standard operating procedures, cross-training, and automation. Each option involves trade-offs. Rotation may increase learning but reduce short-term efficiency; automation may remove routine tasks but increase the need for exception handling and judgement.

Work analysis in changing environments

A job description is not a prediction. It should be reviewed when strategy, technology, regulation, structure, or customer needs change. Planners should ask:

• Which tasks are increasing, declining, or becoming automated?
• Which decisions are moving from people to systems, or from systems to people?
• Which new risks require human judgement?
• Which capabilities are becoming transferable across job families?
• Which work is becoming more collaborative or project-based?

This future-oriented analysis prevents the organization from planning only for yesterday’s jobs.

4. Competencies and Competency Models

A competency is a cluster of related knowledge, skills, abilities, motives, and behaviours that contributes to effective performance in a particular context. A competency is broader than a single skill. For example, “customer-centred problem solving” may involve customer knowledge, analysis, listening, judgement, communication, and follow-through.

A competency model is an organized description of competencies required across an organization, function, job family, or level. Common categories include:

• Core competencies: expected of most employees, such as ethical conduct or collaboration.
• Functional competencies: associated with a discipline, such as financial analysis or recruitment practice.
• Leadership competencies: associated with directing people, resources, and change.
• Technical competencies: specialized knowledge and methods, such as database administration.
• Behavioural competencies: observable patterns such as influencing, learning agility, or conflict management.

Competencies should be expressed in observable terms. “Strategic mindset” is too vague unless defined through behaviours such as interpreting external trends, evaluating long-term consequences, and linking decisions to organizational priorities.

Proficiency levels

A competency model often uses progressive levels. A five-level scale might describe foundational, working, proficient, advanced, and expert performance. Levels should describe complexity, independence, scope, and judgement—not merely years of experience. A person may have many years of experience without demonstrating advanced performance.

Example:

Competency models can support recruitment criteria, learning pathways, career conversations, performance expectations, and succession planning. Their weakness is that they can become generic lists detached from actual work. They should therefore be anchored in evidence and reviewed with practitioners.

5. Skills Taxonomies and Skills Architecture

A skills taxonomy is a structured classification of skills. A skills architecture is the broader system that connects skills to jobs, job families, proficiency levels, learning resources, credentials, projects, and career pathways.

A taxonomy may classify skills by domain, for example:

1. Business and organizational skills
2. Professional and functional skills
3. Digital and data skills
4. Interpersonal and communication skills
5. Leadership and management skills
6. Compliance, safety, and risk skills
7. Emerging or strategic skills

The architecture should distinguish related concepts:

• Skill: an acquired capacity to perform an activity.
• Knowledge: information and understanding relevant to performance.
• Ability: a more general capacity to perform or learn activities.
• Competency: an integrated pattern of knowledge, skills, abilities, and behaviours.
• Proficiency: the demonstrated level of capability.
• Credential: evidence of education, assessment, licence, or certification; it is not automatically proof of current competence.

Building a skills architecture

A practical process is:

1. Establish design principles and governance ownership.
2. Define a common vocabulary and remove duplicate terms.
3. Group skills into domains and subdomains.
4. Define proficiency indicators using observable evidence.
5. Link skills to jobs, projects, processes, and strategic capabilities.
6. Validate with experts and employees.
7. Connect the architecture to recruitment, learning, talent marketplaces, and workforce analytics.
8. Establish review cycles because skills change over time.

A skills architecture should not imply that every employee must possess every skill. It should show which skills are required, adjacent, developing, scarce, or strategically important.

Skills gap analysis

For an individual or workforce, the gap may be described conceptually as the difference between required and available proficiency. A simple planning table can distinguish immediate gaps from future gaps:

Numerical scores are useful only when rating definitions are clear and evidence-based. A score of “3” has no meaning unless the organization defines what performance at level 3 looks like.

6. Job Families and Career Architecture

A job family groups jobs that share a broad purpose, knowledge base, work processes, or career pathway. Examples include finance, human resources, information technology, sales, operations, and research. Subfamilies may distinguish payroll from talent management or software development from infrastructure.

A career architecture commonly links:

• job families and subfamilies;
• career levels or grades;
• role scope and decision authority;
• required competencies and skills;
• typical experience and development pathways;
• compensation or job-evaluation structures, where applicable.

Job families improve workforce planning by allowing demand and supply to be analyzed at a meaningful level. They also support internal mobility. A skills-based architecture may reveal that a business analyst, process-improvement specialist, and product owner share adjacent skills, even if their titles differ.

Care is required. Job families should not become rigid silos or assumptions about career progression. Employees may move across families through transferable skills, learning, and demonstrated performance. Career architecture must also be reviewed for gender, racial, disability, age, and other forms of structural bias.

7. Identifying Critical Roles

Not every role is equally critical, and criticality is not the same as seniority. A critical role is one whose vacancy, failure, or capability shortage could materially threaten strategic objectives, safety, legal compliance, customer continuity, or organizational resilience.

Useful criteria include:

• impact on strategic outcomes;
• difficulty and time required to replace capability;
• scarcity of external and internal talent;
• dependence of other processes on the role;
• consequences of error;
• regulatory, safety, or ethical significance;
• exposure to operational disruption;
• uniqueness of institutional knowledge.

A critical-role assessment should examine the work, not merely the incumbent. Otherwise, organizations may confuse a highly visible employee with a genuinely critical role. A role can be critical even when several people perform it, and a senior role may be replaceable if its capabilities are widely available.

A simple qualitative matrix can classify roles as high, medium, or low criticality across impact and replaceability. More formal scoring may be used, but false precision should be avoided. The assessment should lead to action: succession depth, cross-training, documentation, retention attention, external partnerships, automation, or redesign.

8. Application to Workforce Planning

The outputs of work analysis become inputs to workforce planning in several ways.

Forecasting demand

Strategic plans can be translated into capabilities and work volumes. A plan to expand digital services may create demand for product management, cybersecurity, user research, data engineering, and change management—not simply “more employees.” Scenario planning is useful because future demand is uncertain. Planners may construct baseline, growth, and disruption scenarios and identify capabilities common to all scenarios.

Assessing supply

Supply analysis considers employee skills, proficiency, experience, location, availability, retirement risk, turnover, mobility, contractors, partners, and learning capacity. Self-reported skill data should be supplemented with work samples, qualifications, manager evidence, project outcomes, and assessments where appropriate.

Choosing interventions

Capability gaps can be addressed through:

• build: learning, coaching, apprenticeships, and stretch assignments;
• buy: recruitment or acquisition of specialized talent;
• borrow: contractors, consultants, alliances, or managed services;
• bind: retention, knowledge transfer, and career opportunities;
• redesign: process improvement, team restructuring, or automation;
• redeploy: movement of existing employees into higher-value work.

The best intervention depends on urgency, cost, scarcity, risk, and the organization’s ability to develop capability.

9. Technology, AI, and Data Governance

Human resource information systems and talent platforms can connect jobs, skills, learning, projects, and workforce data. Natural-language processing may help extract skill terms from documents, while AI systems can suggest related skills or identify emerging requirements. These tools can increase scale, but automated suggestions are not automatically accurate.

Important safeguards include:

• human review of inferred skills and job requirements;
• transparency about data sources and decision logic;
• data minimization and access controls;
• validation for disparate impact and discriminatory patterns;
• correction mechanisms for employees;
• separation of development data from unnecessary surveillance;
• regular review of obsolete or duplicated skills.

AI-generated job descriptions may reproduce historical bias or encode inflated requirements. Automated proficiency scores may mistake system activity for competence. Technology should support professional judgement, not replace accountability.

10. Ethical, Legal, and Professional Considerations

Work analysis affects access to employment, development, promotion, pay, and redundancy. It must therefore be fair and evidence-based. Requirements should be job-related, necessary, and proportionate. Analysts should avoid proxy criteria that exclude groups without improving performance prediction.

Privacy is relevant when collecting diaries, productivity data, location data, communications, or system logs. Employees should know the purpose, scope, retention period, and access arrangements. Consultation is particularly important where analysis may change jobs, workloads, monitoring, or employment status.

Accessibility should be considered in both work design and assessment. A requirement should not be treated as essential if reasonable accommodation or assistive technology can enable effective performance. Professional practice also requires respect for employee expertise: jobholders are sources of knowledge, not merely objects of measurement.

11. Illustrative Case: Northstar Health Services

Background

Northstar Health Services, a fictional regional provider, planned to introduce a shared digital patient-record system across hospitals and clinics. Its workforce plan initially requested 40 additional “IT employees.” Leaders soon realized that the project involved clinical workflow redesign, data governance, cybersecurity, user training, and ongoing support.

Problem

Existing job descriptions were outdated and used inconsistent titles. The organization could not determine which capabilities were available internally, which roles were critical during implementation, or whether recruitment was more appropriate than development.

Analysis

A cross-functional team reviewed process documents, interviewed clinicians and administrators, observed registration and discharge workflows, and analyzed service-desk records. It identified five job families: clinical informatics, data governance, cybersecurity, application support, and organizational change. It also identified transferable skills among nurses, business analysts, records staff, and IT employees.

Critical roles were assessed using service impact, regulatory exposure, scarcity, and time to replace. The implementation lead, privacy specialist, clinical workflow analyst, and cybersecurity incident lead were classified as highly critical. A generic “IT specialist” category was rejected because it concealed materially different requirements.

Approach and solution

Northstar created a skills taxonomy with proficiency indicators and mapped roles to current and future requirements. It developed a six-month training pathway for internal candidates in workflow analysis and data governance, recruited two cybersecurity specialists, used a temporary implementation partner during peak demand, and established cross-training for application support. Job descriptions were rewritten around outcomes, decision rights, and essential capabilities.

Outcome

The organization reduced unnecessary external recruitment, improved internal mobility, and created clearer succession coverage for critical roles. It also discovered that some employees had high capability that was invisible under the old job titles. The project team retained a quarterly review process because system functionality and regulatory expectations continued to change.

Learning points

The case illustrates that workforce planning is a capability problem before it is a headcount problem. It also demonstrates the value of triangulated evidence, job-family architecture, critical-role analysis, and a blended build-buy-borrow strategy.

Challenges and Limitations

Work analysis is affected by changing work, incomplete observation, political interests, inconsistent terminology, and the difficulty of measuring knowledge work. Experts may disagree, employees may exaggerate or minimize tasks, and managers may describe ideal rather than actual performance. Competency models can become lengthy, subjective, and disconnected from decisions. Skills taxonomies can create an illusion of precision while missing tacit knowledge, relationships, creativity, and context.

These limitations do not make analysis unnecessary. They require transparent methods, multiple evidence sources, periodic review, practitioner participation, and modest claims. A good architecture is useful because it improves decisions; it is not valuable merely because it contains many categories.

Best-Practice Principles

1. Begin with strategic and operational decisions, not with a catalogue of terms.
2. Analyze outputs, context, dependencies, and future change—not only tasks.
3. Use multiple evidence sources and document assumptions.
4. Define competencies through observable behaviour and performance evidence.
5. Separate essential requirements from historical preferences.
6. Treat proficiency as demonstrated capability, not simply tenure or credentials.
7. Link skills to jobs, projects, learning, mobility, and critical roles.
8. Review architectures regularly as technology and strategy change.
9. Involve employees, managers, subject experts, legal advisers, and inclusion specialists.
10. Use analytics and AI as decision support subject to human accountability.

Chapter Summary

Work analysis establishes what work an organization performs and what capabilities that work requires. Job analysis remains important, but contemporary workforce planning must also examine processes, teams, projects, technology, and future changes. Reliable analysis uses clear objectives, multiple methods, observable outputs, validated requirements, and documented evidence.

Work design determines how tasks, authority, technology, and relationships are arranged. Competency models organize integrated knowledge, skills, abilities, and behaviours, while skills taxonomies classify specific capabilities. A skills architecture connects those capabilities to proficiency levels, jobs, job families, learning, career movement, and strategic priorities. Job families create a useful structure for workforce planning, but they should remain permeable enough to support mobility.

Critical-role identification focuses on the consequences of vacancy or capability failure rather than status alone. Workforce planners use these outputs to forecast demand, assess supply, and select build, buy, borrow, bind, redesign, or redeployment interventions. Technology and AI can improve scale, but privacy, fairness, transparency, validation, and human accountability are essential. The central principle is that workforce planning should connect organizational purpose to demonstrable capability rather than relying on job titles or headcount alone.

Key Terms

Job analysis: Systematic study of a job’s tasks, responsibilities, context, and requirements.

Work analysis: Broader examination of work across jobs, teams, processes, projects, and technologies.

Task: A distinct activity with an identifiable action and output.

Duty: A group of related tasks.

Job: A relatively stable bundle of related work assigned to a position.

Role: An expected contribution within a work system.

Work design: The arrangement of tasks, authority, technology, and relationships.

Competency: An integrated cluster of knowledge, skills, abilities, and behaviours contributing to performance.

Competency model: An organized description of competencies required in a defined context.

Skill: An acquired capacity to perform an activity.

Proficiency: The demonstrated level of capability.

Skills taxonomy: A structured classification of skills.

Skills architecture: A system linking skills to jobs, levels, learning, projects, and career pathways.

Job family: A group of jobs sharing a broad purpose, knowledge base, or career pathway.

Career architecture: A framework connecting job families, levels, competencies, and progression.

Critical role: A role whose vacancy or capability failure could materially threaten organizational outcomes.

Triangulation: Comparison of evidence from multiple sources or methods.

Redeployment: Movement of existing employees into different or higher-value work.

Human capital risk: The possibility that workforce capability, availability, or behaviour will harm organizational performance.

Review Questions

Short Answer Questions

1. What is the difference between job analysis and work analysis?
2. Distinguish a task, duty, job, and role.
3. Why should competency descriptions use observable behaviours?
4. What is the purpose of a skills taxonomy?
5. Why is a critical role not necessarily a senior role?

Long Answer Questions

1. Explain the stages of a rigorous work-analysis process and discuss the strengths and limitations of at least three data-collection methods.
2. Compare competencies, skills, proficiency levels, and credentials, explaining how each contributes to workforce planning.
3. Describe how job families and career architecture can support internal mobility and succession planning.
4. Evaluate the benefits and risks of using AI to construct or maintain a skills architecture.
5. Explain how work design theories inform decisions about specialization, autonomy, teamwork, and automation.

Analytical / Application Questions

1. A university plans to introduce an AI-supported student-advising service. Identify the work activities, job families, competencies, and critical roles that should be analyzed before implementation.
2. An organization reports a shortage of “digital skills.” Design a method for determining whether the real problem is recruitment, development, redeployment, work redesign, or inaccurate terminology.
3. Using the Northstar Health Services case, recommend a balanced build-buy-borrow-bind strategy and justify the criteria you would use to evaluate its success.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes work analysis from traditional job analysis?

A. Work analysis examines only senior management positions.

B. Work analysis includes jobs, processes, teams, projects, and technology-supported work.

C. Work analysis eliminates the need to study tasks.

D. Work analysis is limited to calculating employee numbers.

Correct Answer: B. Work analysis includes jobs, processes, teams, projects, and technology-supported work.

Question 2

Which data-collection method is most directly useful for observing actual behaviour in context?

A. Direct observation

B. A compensation survey

C. A corporate mission statement

D. An annual budget

Correct Answer: A. Direct observation

Question 3

Which description is the best task statement?

A. Handles compliance

B. Is responsible for quality

C. Prepares monthly compliance reports for regulatory submission

D. Works professionally

Correct Answer: C. Prepares monthly compliance reports for regulatory submission

Question 4

What is a competency?

A. A job title used for payroll purposes

B. An integrated cluster of knowledge, skills, abilities, and behaviours

C. A certificate that automatically proves performance

D. A list of employee benefits

Correct Answer: B. An integrated cluster of knowledge, skills, abilities, and behaviours

Question 5

What is the main purpose of a skills taxonomy?

A. To classify and organize skills using a common structure

B. To replace all performance assessments

C. To rank employees by popularity

D. To determine annual leave entitlement

Correct Answer: A. To classify and organize skills using a common structure

Question 6

Which feature makes proficiency levels more useful?

A. They are based only on years of service.

B. They describe observable differences in complexity, independence, scope, and judgement.

C. They use identical descriptions for every level.

D. They are assigned solely by job title.

Correct Answer: B. They describe observable differences in complexity, independence, scope, and judgement.

Question 7

Which statement about critical roles is most accurate?

A. Every senior role is automatically critical.

B. A critical role is identified by the consequences of vacancy or capability failure.

C. Critical roles are determined only by salary level.

D. A role is critical only if it has one incumbent.

Correct Answer: B. A critical role is identified by the consequences of vacancy or capability failure.

Question 8

Which intervention involves moving existing employees into different or higher-value work?

A. Redeployment

B. Outsourcing

C. External recruitment

D. Job evaluation

Correct Answer: A. Redeployment

Question 9

Why is triangulation valuable in work analysis?

A. It guarantees that all employees receive promotions.

B. It compares evidence from multiple sources and methods.

C. It removes the need for validation.

D. It reduces all jobs to numerical scores.

Correct Answer: B. It compares evidence from multiple sources and methods.

Question 10

Which safeguard is most appropriate when AI suggests employee skills from workforce data?

A. Accepting all suggestions without review

B. Publishing private data publicly

C. Human review, transparency, privacy controls, and bias validation

D. Using system activity as automatic proof of competence

Correct Answer: C. Human review, transparency, privacy controls, and bias validation