Planning and Governing a Job Analysis

Introduction

Job analysis is the systematic process of collecting, evaluating, and documenting information about work. It identifies what work is performed, how it is performed, why it is performed, and the capabilities required for effective performance. Although job analysis is often associated with writing job descriptions, its strategic value is broader. It supports recruitment, selection, training, performance management, job evaluation, workforce planning, compensation, organizational redesign, occupational health and safety, and legal defensibility.

A technically sound analysis can still fail if it is poorly scoped, excludes important stakeholders, relies on unrepresentative employees, or is communicated as a hidden restructuring exercise. Planning and governance therefore determine the credibility and usefulness of the final product. Governance establishes who makes decisions, what evidence is acceptable, how disagreements are resolved, how records are controlled, and when the analysis will be reviewed.

This chapter presents an integrated approach to planning and governing job analysis. It emphasizes stakeholder identification, subject-matter-expert (SME) selection, sampling, communication, change management, documentation, quality assurance, and ethical practice.

Learning Objectives

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

1. Define the purpose, scope, boundaries, and outputs of a job-analysis project.
2. Identify stakeholders and select appropriate SMEs using defensible criteria.
3. Design representative samples of jobs, work sites, incumbents, supervisors, and work situations.
4. Develop a communication and change-management plan that builds trust and participation.
5. Establish project governance, decision rights, documentation controls, and quality standards.
6. Evaluate common threats to validity, reliability, fairness, and legal defensibility.
7. Apply these principles to a complex organizational job-analysis project.

1. The Planning Logic of Job Analysis

A job-analysis project should begin with a decision, not a questionnaire. The project team must first ask: What organizational decision will the analysis support? A project intended to redesign jobs requires different evidence from one intended to validate selection criteria. A compensation study may emphasize responsibility, complexity, and working conditions, while a training-needs analysis may emphasize task frequency, difficulty, and error consequences.

A useful planning chain is:

Business or workforce problem → decisions required → information needed → sources and methods → analysis products → implementation and review.

For example, if an organization is introducing automated customer-service tools, it may need to determine which tasks will disappear, which will change, and which new competencies will become important. The analysis should then examine work processes, technology interactions, exception handling, judgment, customer risk, and future capability requirements—not merely reproduce existing job descriptions.

1.1 Defining the unit of analysis

The unit of analysis is the object about which conclusions are made. Possible units include:

• a job or occupational role;
• a position held by one individual;
• a job family containing related roles;
• a task, duty, or work activity;
• a work process or workflow;
• a competency or capability;
• a team or collective work system.

Confusing these units creates serious errors. A position is an individual instance of work, whereas a job is a broader pattern of substantially similar duties. Two employees may hold the same job title but perform different work; conversely, different titles may conceal substantially similar work. Titles are therefore useful identifiers but weak evidence of job content.

1.2 Establishing scope

Scope should specify:

• the organizational units and locations included;
• the jobs, job families, grades, or occupations covered;
• the time horizon, including current work and planned changes;
• the employment groups included, such as permanent, temporary, contract, remote, or shift workers;
• the purposes for which findings may be used;
• the methods and evidence sources;
• the deliverables and approval points;
• explicit exclusions.

A scope statement might read: “This project will analyze customer-support roles in three regions to update job descriptions, identify future digital-service competencies, and review selection criteria. It will not determine individual performance ratings, make redundancy decisions, or set pay grades.” Such exclusions are not administrative details; they protect participants from misunderstood consequences and prevent the project from becoming an uncontrolled collection of unrelated requests.

1.3 Current work and future work

Traditional job analysis often assumes that jobs are stable. In dynamic environments, this assumption is unsafe. A robust project distinguishes among:

• current work: activities regularly performed now;
• emerging work: activities already appearing but not yet standardized;
• anticipated work: activities expected because of strategy, technology, regulation, or market change.

Future-oriented analysis should not present speculation as fact. Analysts should label evidence according to its status and identify the assumptions underlying forecasts. A job description may appropriately include a future competency, but it should distinguish a validated current requirement from a planned development priority.

2. Stakeholders, Sponsors, and Subject-Matter Experts

2.1 Stakeholder mapping

Stakeholders are individuals or groups who affect the project, are affected by it, provide evidence, approve outputs, or may challenge its legitimacy. Typical stakeholders include:

• executive sponsors and business-unit leaders;
• HR business partners and job-analysis specialists;
• line managers and supervisors;
• job incumbents;
• newly hired or experienced employees;
• employees working different shifts, locations, or arrangements;
• employee representatives, unions, or works councils;
• occupational health and safety specialists;
• legal, compliance, privacy, and information-security advisers;
• learning, talent, workforce-planning, and compensation professionals;
• customers or service users where work outcomes depend on them;
• technology, process-improvement, and analytics specialists.

Stakeholder influence and knowledge are not the same. A senior executive may authorize the project but have limited knowledge of daily work. An incumbent may possess detailed tacit knowledge but have no formal approval authority. A governance design should therefore give people influence appropriate to their responsibilities without treating hierarchy as a substitute for evidence.

A stakeholder matrix can classify each group by interest and influence:

The matrix is a planning aid, not a rigid formula. Stakeholders with low formal influence may be highly important ethically, especially if they bear the consequences of inaccurate analysis.

2.2 Selecting SMEs

An SME is a person whose knowledge is sufficiently relevant and detailed to contribute credible information about work. SMEs may be incumbents, supervisors, technical experts, customers, or other knowledgeable observers. No single SME is automatically representative of an entire job.

Selection should consider:

1. Job knowledge: familiarity with the tasks, decisions, tools, and conditions involved.
2. Performance experience: sufficient exposure to routine and non-routine work.
3. Breadth: experience across relevant products, clients, locations, or systems.
4. Recency: current knowledge of the job, while preserving historical insight where change is being studied.
5. Communication ability: capacity to describe work clearly without excessive jargon.
6. Perspective diversity: inclusion of high performers, typical performers, newer workers, different shifts, and workers requiring accommodations where relevant.
7. Independence: willingness to report actual work rather than simply repeat official documents.

SME selection must avoid convenience sampling. Managers may nominate only highly visible employees, and volunteers may be unusually engaged or dissatisfied. A defensible approach combines purposive selection with transparent criteria and, where feasible, stratified sampling across relevant work conditions.

2.3 Managing SME bias

SMEs can overstate rare tasks, omit routine work, describe ideal procedures rather than actual behavior, or interpret questions through concerns about pay and job security. These are not reasons to disregard SME evidence; they are reasons to triangulate it.

Useful safeguards include:

• asking separately about frequency, importance, difficulty, and consequences of error;
• requesting recent examples of typical and critical work;
• comparing incumbent, supervisor, observation, workflow, and performance-system evidence;
• using multiple SMEs independently before consensus discussion;
• recording disagreements rather than forcing artificial unanimity;
• asking participants to distinguish “must do,” “sometimes does,” and “may do.”

Consensus is useful for clarifying terminology, but agreement alone does not prove accuracy. A dominant participant can create apparent consensus, and a group may normalize unsafe or inefficient practices. The analyst remains responsible for evaluating evidence.

3. Sampling for Representativeness

Sampling is the process of selecting cases from the broader work population. In job analysis, the sample may include jobs, incumbents, locations, shifts, customers, tasks, incidents, or work products. The sampling strategy should reflect the intended generalization.

3.1 Job and incumbent sampling

If all positions in a small job are materially similar, a census may be feasible. In larger populations, sampling is required. Relevant strata may include:

• geographic region;
• business unit or product line;
• shift and schedule;
• tenure or experience level;
• work setting, such as remote, hybrid, or onsite;
• customer or case complexity;
• technology platform;
• employment arrangement;
• demographic or accessibility dimensions where work experience may differ.

Random sampling can reduce selection bias, but random selection from an inaccurate job list does not create a valid sample. The sampling frame—the list from which cases are selected—must be checked for missing, duplicate, outdated, or misclassified positions.

3.2 Task sampling

Task sampling is especially important where a job contains many activities. A task can be examined according to frequency, time, importance, difficulty, consequences of error, and required judgment. Rare tasks may deserve inclusion because they involve safety, legal, financial, or reputational risk. Conversely, frequently performed tasks may have low strategic importance but still consume substantial time.

Analysts should avoid reducing task importance to frequency alone. A low-frequency emergency response may be more consequential than a high-frequency administrative activity. The analysis should therefore preserve separate ratings rather than collapsing all dimensions into one unsupported score.

3.3 Sample adequacy

There is no universal sample size for job analysis. Adequacy depends on job heterogeneity, project purpose, available resources, and the precision required. A small, homogeneous job may be adequately represented by a carefully selected panel; a geographically dispersed and highly variable job may require substantially broader coverage.

The project plan should document:

• the population size and characteristics;
• the sampling frame;
• selection criteria;
• anticipated nonresponse;
• coverage of exceptional work conditions;
• the rationale for concluding that additional data are unlikely to change the findings.

That final judgment is a professional conclusion, not a magical numerical threshold. Analysts should test whether important themes recur across strata and whether unresolved differences could alter the intended decision.

4. Methods and Triangulation

No method captures every aspect of work. Interviews reveal reasoning and tacit knowledge but can be affected by memory and impression management. Observation captures behavior but may miss infrequent cognitive work. Questionnaires allow broad coverage but may produce superficial or inconsistent responses. Document review is efficient but may describe formal procedures rather than actual practice.

Common methods include:

• structured interviews;
• focus groups and SME workshops;
• questionnaires and task inventories;
• direct observation and work shadowing;
• work diaries or experience sampling;
• critical-incident interviews;
• review of standard operating procedures and workflow maps;
• analysis of systems, tickets, cases, quality records, and safety reports;
• customer or stakeholder interviews;
• expert review of emerging work.

Triangulation means comparing evidence from different sources, methods, or perspectives. It is not merely collecting more data. The analyst should specify what each method is expected to establish. For example, system logs may help estimate task occurrence, while interviews may explain judgment and exceptions. A discrepancy is a finding to investigate, not automatically an error.

A practical evidence record can contain the following fields:

5. Project Governance

Governance is the system through which authority, accountability, oversight, and quality control are exercised. It should be designed before data collection begins.

5.1 Governance roles

A typical structure includes:

• Executive sponsor: authorizes the project, allocates resources, and resolves strategic barriers.
• Project owner: is accountable for the business outcome and use of findings.
• Project manager: manages schedule, risks, communications, and dependencies.
• Lead analyst: controls methodology, evidence interpretation, and technical quality.
• SME or validation panel: reviews work content and identifies omissions or inaccuracies.
• Employee or labor-relations representative: advises on consultation, fairness, and workforce implications.
• Legal, privacy, or compliance reviewer: examines regulatory and data risks.
• Data or document custodian: maintains records, access permissions, and version control.

One person may perform multiple roles in a small project, but incompatible responsibilities should be separated. For example, the person whose preferred restructuring outcome depends on a finding should not be the sole validator of that finding.

A responsibility matrix clarifies participation. In a RACI matrix, Responsible means performing the work, Accountable means answerable for the outcome, Consulted means providing input, and Informed means receiving updates. Each major deliverable should have one clear accountable role, even if several people are responsible for producing it.

5.2 Stage gates

Stage gates prevent a project from moving forward on untested assumptions. Useful gates include:

1. Initiation gate: purpose, scope, risks, resources, and decision uses approved.
2. Design gate: unit of analysis, methods, sample, instruments, and ethics safeguards approved.
3. Data-quality gate: participation, coverage, contradictions, and evidence sufficiency reviewed.
4. Validation gate: draft findings checked by representative SMEs and relevant stakeholders.
5. Approval gate: final outputs accepted, limitations recorded, and implementation owner assigned.
6. Review gate: outputs monitored and scheduled for revision.

Stage gates should not become bureaucratic rituals. Each gate should specify evidence required, decision authority, and conditions for rework.

5.3 Change control

Scope changes are common. A new technology rollout, legal requirement, reorganization, or employee-representative concern may require additional analysis. Uncontrolled changes create schedule failure and make findings difficult to interpret.

A change request should document:

• the requested change and reason;
• affected jobs, methods, outputs, and stakeholders;
• resource and schedule implications;
• new risks or ethical concerns;
• decision authority;
• whether earlier findings require revalidation.

6. Communication and Change Management

Employees may interpret job analysis as a precursor to surveillance, redundancy, intensified work, pay reduction, or performance discipline. Silence allows rumors to fill the information gap. Communication should therefore begin before data collection and continue through implementation.

6.1 Communication principles

Effective communication is:

• purposeful: explains what decision the analysis supports;
• truthful: avoids promising outcomes that are not yet known;
• specific: describes who will participate, what data will be collected, and how it will be used;
• two-way: provides channels for questions, corrections, and complaints;
• inclusive: reaches different shifts, languages, locations, and accessibility needs;
• proportionate: shares enough information for informed participation without exposing confidential data.

A communication plan should identify the audience, message, sender, channel, timing, feedback mechanism, and escalation route. Supervisors need guidance so that they do not unintentionally pressure employees to produce favorable descriptions.

6.2 Participation and psychological safety

Participation is meaningful only when employees can provide information without unreasonable fear of reprisal. Analysts should explain confidentiality limits, distinguish project data from performance-management records, and avoid collecting unnecessary personal information. Where anonymity cannot be guaranteed—for example, in a small team—the limitation should be stated clearly.

Employees should be able to challenge factual errors. However, validation is not a veto over evidence. A participant may disagree because a finding has implications for workload or status. The project should record the disagreement, investigate it, and document the resolution.

6.3 Managing implementation change

Job-analysis outputs often alter job descriptions, selection criteria, training, workflows, or reporting relationships. Change management should therefore continue after the report. Managers should be prepared to explain what will change, what will not change, when changes take effect, and how employees can obtain support.

A useful distinction is between:

• descriptive change: correcting the record to reflect work already performed;
• developmental change: building capabilities for anticipated work;
• structural change: altering responsibilities, authority, staffing, or work design.

These categories may require different consultation, legal review, and implementation processes.

7. Documentation and Quality Standards

Documentation creates an audit trail from project purpose to final decision. At minimum, the project file should contain:

• approved charter and scope statement;
• stakeholder and SME-selection rationale;
• sampling frame and sample plan;
• instruments, protocols, and interviewer guidance;
• consent, privacy, and data-management procedures;
• raw and processed evidence, subject to access restrictions;
• coding rules and classification decisions;
• records of disagreements and resolutions;
• validation feedback;
• version history and approval records;
• limitations and recommendations for review.

7.1 Quality dimensions

Quality is multidimensional. Important standards include:

• Validity: findings represent the work or construct they claim to represent.
• Reliability: procedures produce reasonably consistent results under comparable conditions.
• Representativeness: relevant variation in work is covered.
• Traceability: conclusions can be linked to evidence and decisions.
• Transparency: assumptions, exclusions, uncertainty, and disagreements are visible.
• Usability: outputs are understandable and fit the intended HR process.
• Fairness: the process does not unjustifiably exclude groups or encode irrelevant barriers.
• Currency: findings remain accurate as work, technology, and regulation change.

Reliability does not guarantee validity. Several analysts may consistently code an outdated job description, producing high agreement about an inaccurate account. Conversely, disagreement may reveal genuine variation that requires a more nuanced job model.

7.2 Quality assurance questions

Before approval, reviewers should ask:

1. Does the evidence address the stated purpose?
2. Were relevant work settings and employee groups included?
3. Are tasks distinguished from competencies, outputs, and performance standards?
4. Are essential requirements supported by evidence rather than preference?
5. Have rare but consequential activities been considered?
6. Are current and future requirements clearly separated?
7. Can each major conclusion be traced to sources?
8. Have contradictory findings and limitations been documented?
9. Are the proposed uses consistent with what participants were told?
10. Is there an owner and review date for maintaining the output?

8. Ethical, Legal, and Regulatory Considerations

Job analysis can affect access to employment, pay, promotion, accommodation, and job security. Ethical practice therefore requires more than technical accuracy.

First, requirements should be job-related and necessary for the intended purpose. Analysts should distinguish essential functions from customary practices or preferences. A requirement that excludes a group must be examined for relevance and proportionality, with reasonable accommodation considered where applicable.

Second, personal data should be minimized. Analysts should collect only information needed for the project, restrict access, define retention periods, and protect sensitive responses. Applicable privacy, employment, accessibility, labor, health and safety, and recordkeeping laws vary by jurisdiction; legal review is necessary when outputs will affect regulated decisions.

Third, automated tools require scrutiny. Natural-language systems can summarize interviews, cluster tasks, or compare job descriptions, but they may reproduce historical bias, remove context, expose confidential information, or generate plausible but unsupported statements. AI-generated classifications must be treated as provisional. Human reviewers should verify sources, preserve an audit trail, test for disparate effects where relevant, and prevent the system from making unreviewed employment decisions.

9. An Illustrative Case: Northstar Health Services

The following is a fictional illustrative case.

Background

Northstar Health Services operates outpatient clinics in four regions. Its “patient access coordinator” role has expanded from appointment scheduling to digital registration, insurance verification, referral coordination, patient messaging, and escalation of safeguarding concerns. Job descriptions differ across clinics, and managers use inconsistent selection criteria.

Problem

The executive team wants a common job architecture and updated selection process. Employee representatives are concerned that the project will be used to increase workloads without additional staffing. Remote and evening-shift employees report that previous HR projects captured only daytime work.

Analysis and planning

The project charter defines three uses: updating job descriptions, identifying training needs, and reviewing selection criteria. It explicitly excludes individual performance ratings and immediate pay reductions. The unit of analysis is the job family, with clinic-specific variation documented separately.

The governance group includes the HR project owner, a lead job analyst, clinic managers, six incumbent SMEs from different regions and shifts, an employee representative, a privacy adviser, and a patient-experience specialist. The SME sample includes new and experienced employees, onsite and remote workers, and clinics with different patient populations.

The team uses document review, structured interviews, a task inventory, observation of selected workflows, system-log analysis, and a validation workshop. System logs show that insurance-verification tasks occur frequently, while safeguarding escalation is rare. Interviews establish that the latter requires high judgment and has serious consequences if mishandled. The final analysis therefore preserves both frequency and consequence rather than treating the rare task as unimportant.

Approach and solution

The communication plan explains that the project will document current work and future digital capabilities, not rank individual employees. Employees receive a channel for correction and questions. The team records differences among clinics instead of forcing one generic description.

The final outputs distinguish:

• common tasks performed across clinics;
• clinic-specific duties;
• essential competencies, such as privacy judgment and communication;
• trainable capabilities, such as use of a new registration platform;
• future requirements that depend on planned system implementation.

Each conclusion is linked to evidence, and unresolved differences are documented. The selection review removes a preference for “five years of clinic experience” because evidence shows that comparable customer-service and privacy experience can support effective performance. The revised criteria focus on demonstrable capabilities and provide a route for reasonable accommodation.

Outcome

Northstar adopts a common job family description with controlled local supplements. Training is developed for digital registration and escalation protocols. Managers receive guidance on the distinction between essential requirements and preferred experience. A six-month review is scheduled after the new platform is introduced.

Learning points

The case demonstrates that planning decisions shape analytical quality. Explicit scope reduced fear, diverse sampling improved representativeness, triangulation revealed the importance of rare tasks, and governance prevented one stakeholder group from controlling the findings. It also shows that job analysis is not a one-time document-writing exercise; it is a governed evidence process that must be revisited when work changes.

10. Best-Practice Checklist

Before launching a job-analysis project, the project team should be able to answer “yes” to the following questions:

• Is the decision purpose explicit?
• Is the unit of analysis defined?
• Are scope boundaries and exclusions written down?
• Are current, emerging, and anticipated work distinguished?
• Have affected and knowledgeable stakeholders been identified?
• Is SME selection based on transparent criteria?
• Does the sample cover meaningful work variation?
• Are multiple evidence sources planned?
• Are privacy, confidentiality, accessibility, and labor-relations issues addressed?
• Are governance roles and decision rights clear?
• Are stage gates, change control, and version management established?
• Do communication materials explain purpose, use, participation, and feedback?
• Are quality standards and validation procedures specified?
• Is there an owner and review date for the final output?

Chapter Summary

Planning and governing job analysis is foundational to the credibility of every later HR decision based on work information. Effective planning begins by defining the decision purpose, unit of analysis, scope, boundaries, and distinction between current and future work. Stakeholder mapping ensures that authority, expertise, workforce impact, and regulatory responsibilities are all recognized.

SMEs should be selected using transparent criteria that address job knowledge, experience, breadth, recency, communication, independence, and perspective diversity. Sampling must cover meaningful variation in jobs, incumbents, locations, shifts, technologies, and work situations. Because every method has limitations, interviews, observation, questionnaires, documents, system data, and critical incidents should be triangulated.

Governance establishes sponsors, analysts, validation panels, employee representatives, advisers, decision rights, stage gates, change control, and records management. Communication and change management are essential because employees may associate analysis with surveillance, restructuring, or loss. Trust depends on truthful explanations, meaningful participation, confidentiality safeguards, and opportunities to correct factual errors.

Quality requires validity, reliability, representativeness, traceability, transparency, usability, fairness, and currency. Ethical and legal practice requires job-related requirements, data minimization, accessibility, privacy protection, and careful human oversight of AI-supported analysis. Finally, job analysis should be maintained as work evolves rather than treated as a permanent description of a changing organization.

Key Terms

Job analysis: Systematic collection and evaluation of information about work and its requirements.

Unit of analysis: The object about which conclusions are made, such as a job, task, competency, or work process.

Scope statement: A document defining what a project includes, excludes, and intends to produce.

Stakeholder: A person or group that affects, contributes to, approves, or is affected by a project.

Subject-matter expert (SME): A person with relevant and sufficiently detailed knowledge of work.

Sampling frame: The population list from which cases, jobs, or participants are selected.

Purposive sampling: Selection based on specified relevance criteria rather than chance alone.

Stratified sampling: Sampling that deliberately represents defined subgroups or work conditions.

Task: A distinct work activity performed to produce an outcome.

Competency: An underlying capability involving knowledge, skill, judgment, or other attributes.

Triangulation: Comparison of evidence from multiple sources, methods, or perspectives.

Governance: Structures and processes for authority, accountability, oversight, and control.

Stage gate: A formal review point at which continuation, revision, or approval is decided.

Change control: A process for evaluating and authorizing modifications to an approved project.

Traceability: The ability to connect conclusions to their evidence and decision history.

Validity: The extent to which findings represent what they claim to represent.

Reliability: The consistency of a method or conclusion under comparable conditions.

Psychological safety: A climate in which people can provide information or raise concerns without unreasonable fear of reprisal.

Job-relatedness: The extent to which a requirement is connected to effective performance of the work.

Job currency: The continuing accuracy of job information as work changes over time.

Review Questions

Short Answer Questions

1. Why should a job-analysis project begin with a decision purpose rather than a questionnaire?
2. Distinguish a job from a position as units of analysis.
3. Identify four criteria for selecting subject-matter experts.
4. What is triangulation, and why is it useful in job analysis?
5. Name three quality dimensions that should be assessed before approving job-analysis findings.

Long Answer Questions

1. Explain how scope definition influences the validity, efficiency, and ethical defensibility of a job-analysis project.
2. Compare the contributions and limitations of interviews, observation, questionnaires, document review, and system data.
3. Design a governance structure for a job-analysis project in a large, geographically dispersed organization.
4. Explain how communication and change management can reduce employee resistance without making unrealistic promises.
5. Discuss why reliability does not guarantee validity in job analysis, using an organizational example.

Analytical / Application Questions

1. A company samples only top-performing daytime employees to analyze a job performed across three shifts and four sites. Diagnose the threats to representativeness and propose a revised sampling plan.
2. Interviewees report that a safety-critical task is rare, while system records confirm its low frequency. Explain how the analyst should decide whether to include the task in the job description and selection process.
3. An AI tool produces a concise competency model from employee interviews but cannot identify the sources for several competencies. Decide whether the model should be adopted, revised, or rejected, and justify your governance requirements.

Multiple Choice Questions with Answers

Question 1

What should normally be established before selecting job-analysis methods?

A. The final compensation grade

B. The decision purpose and scope

C. The preferred software platform

D. The individual performance ratings of participants

Correct Answer: B. The decision purpose and scope

Question 2

Which statement best distinguishes a job from a position?

A. A job is always performed by one employee, whereas a position is performed by many

B. A position is an individual instance of work, whereas a job is a broader pattern of substantially similar duties

C. A job concerns pay, whereas a position concerns training

D. There is no meaningful distinction between the two

Correct Answer: B. A position is an individual instance of work, whereas a job is a broader pattern of substantially similar duties

Question 3

Which person is most appropriately considered an SME for job analysis?

A. A senior executive with no exposure to the work

B. A current worker with detailed, recent knowledge of the job

C. A software vendor selected to automate the job

D. A randomly chosen customer with no interaction with the job

Correct Answer: B. A current worker with detailed, recent knowledge of the job

Question 4

Why should rare safety-critical tasks not be excluded solely because they have low frequency?

A. Frequency is never relevant in job analysis

B. Rare tasks may have serious consequences if performed incorrectly

C. Rare tasks are always the most enjoyable tasks

D. Safety-critical tasks require no evidence

Correct Answer: B. Rare tasks may have serious consequences if performed incorrectly

Question 5

What is the primary purpose of triangulation?

A. To ensure every stakeholder agrees with the manager

B. To compare evidence from multiple sources or methods

C. To replace interviews with automated data

D. To reduce the number of documented limitations

Correct Answer: B. To compare evidence from multiple sources or methods

Question 6

Which governance role is primarily responsible for methodological and technical quality?

A. Lead analyst

B. Executive sponsor

C. Customer representative

D. Payroll administrator

Correct Answer: A. Lead analyst

Question 7

Which practice best supports psychological safety during job analysis?

A. Linking all interview responses directly to performance ratings

B. Explaining data use and providing a protected channel for concerns

C. Allowing only managers to review the draft findings

D. Promising that no organizational changes can ever result

Correct Answer: B. Explaining data use and providing a protected channel for concerns

Question 8

What does traceability require?

A. That all findings be based only on quantitative data

B. That conclusions can be linked to evidence and decision records

C. That every employee produce identical descriptions of work

D. That the project avoid recording disagreements

Correct Answer: B. That conclusions can be linked to evidence and decision records

Question 9

Why is human oversight important when AI is used to analyze job information?

A. AI systems cannot produce any useful text

B. AI may reproduce bias, lose context, or generate unsupported conclusions

C. Human reviewers are legally prohibited from examining AI outputs

D. AI automatically guarantees fair selection criteria

Correct Answer: B. AI may reproduce bias, lose context, or generate unsupported conclusions

Question 10

Which item is an appropriate example of change control?

A. Adding a new job family to the project without documenting the effect

B. Recording a requested scope change, its risks, resources, and approval

C. Deleting contradictory evidence from the project file

D. Allowing the most senior stakeholder to alter findings informally

Correct Answer: B. Recording a requested scope change, its risks, resources, and approval