HR & People Analytics

Chapter 1
Foundations of HR & People Analytics

Bachelors Program in Business Analytics
HR & People Analytics   •   Bachelor

Foundations of HR & People Analytics

Introduction

Organizations increasingly compete through the knowledge, skills, relationships, motivation and adaptability of their people. Yet human decisions are often made using incomplete information, intuition or inherited practices. HR and people analytics provide a disciplined way to use workforce data, organizational theory and evidence-based reasoning to improve decisions affecting employees and organizational performance.

People analytics is not simply the production of dashboards. It involves identifying a decision problem, defining relevant concepts, collecting and integrating appropriate data, analyzing patterns, interpreting evidence and taking responsible action. Its purpose is to improve decisions about people and work while respecting human dignity, privacy, fairness and legal rights.

The field has developed from administrative personnel records and routine HR reporting into a multidisciplinary practice drawing on statistics, data science, psychology, economics, sociology, management and information systems. This chapter establishes the conceptual foundation required for later study of workforce metrics, predictive models, experimentation, talent decisions and strategic workforce planning.

Learning Objectives

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

  1. Explain the evolution and scope of HR and people analytics.
  2. Distinguish operational reporting from descriptive, diagnostic, predictive, prescriptive and causal analytics.
  3. Define important terminology used in people analytics.
  4. Relate human capital, organizational behavior and evidence-based management theories to HR decisions.
  5. Evaluate the quality, limitations, ethics and practical usefulness of people data.
  6. Apply an analytical framework to an HR decision problem.

1. The Evolution of Workforce Information

1.1 From personnel administration to strategic HR

Early personnel departments focused mainly on administrative activities: maintaining employee files, processing payroll, recording attendance and ensuring compliance with employment rules. Data existed, but it was usually fragmented, retrospective and designed for transactions rather than analysis.

The human resource management perspective broadened attention to recruitment, training, performance management, compensation, employee relations and workforce planning. The central question became not only “What transaction occurred?” but also “How can people practices support organizational objectives?”

Strategic human resource management further emphasized alignment between workforce capabilities and business strategy. For example, an organization pursuing rapid innovation may require flexible teams, specialist expertise and tolerance for experimentation, whereas a cost-leadership strategy may emphasize process discipline, standardized skills and productivity.

1.2 The rise of HR information systems

Human resource information systems (HRIS) digitized employee records and enabled standardized reporting. Enterprise systems later connected HR data with finance, operations, customer and productivity data. This integration made it possible to examine relationships such as:

  • whether training participation is associated with sales performance;
  • whether staffing levels affect customer waiting time;
  • whether absence patterns create operational bottlenecks; and
  • whether employee turnover is concentrated in particular roles or locations.

Digitization, however, does not automatically create insight. Poorly defined fields, inconsistent job titles, missing data and incompatible systems can produce precise-looking but misleading results.

1.3 From HR metrics to people analytics

HR metrics summarize workforce activity. Examples include headcount, turnover rate, time to fill, absence days and training completion. People analytics goes further by connecting workforce information to decisions and outcomes. It asks why a pattern exists, what may happen next, which interventions are likely to help and how the organization can learn whether an intervention worked.

The terms workforce analytics, talent analytics, people analytics and HR analytics overlap. “People analytics” is often the broadest term because it includes employees, applicants, contingent workers, teams, managers and sometimes customers or other stakeholders when the analysis concerns work and human behavior. Terminology varies across organizations; the important issue is the analytical purpose and quality of reasoning.

2. Scope and Terminology

2.1 Data domains

People analytics may use several categories of data:

Data domainExamplesTypical use
Demographic and employment dataAge band, tenure, job, location, contract typeWorkforce composition and equity analysis
Transactional HR dataHires, promotions, pay changes, leave, exitsOperational monitoring
Capability dataSkills, qualifications, training, experienceWorkforce planning and development
Performance dataGoals, output, quality, ratingsPerformance and productivity analysis
Experience dataSurveys, interviews, feedback, sentimentEngagement and employee experience
Work-pattern dataSchedules, collaboration records, workload indicatorsWork design and capacity analysis
Business outcome dataSales, quality, safety, customer outcomesStrategic impact analysis

Data may be structured, such as a salary field or hire date, or unstructured, such as interview transcripts and open-text comments. It may also be longitudinal, meaning that observations are recorded over time, or cross-sectional, meaning that they are observed at one point in time.

2.2 Unit of analysis

The unit of analysis is the entity about which a conclusion is made. It may be an employee, job application, team, department, location, manager, shift or organization. Confusing units can produce serious errors. A team-level relationship does not necessarily describe every employee within the team. This is one form of the ecological fallacy.

Similarly, the population is the full group of interest, while a sample is a subset used for analysis. A sample should be appropriate for the decision being made. A voluntary engagement survey, for example, may overrepresent employees with particularly positive or negative experiences.

2.3 Variables and measures

A variable is a characteristic that can take different values, such as tenure or absence days. An outcome variable is the result to be explained or predicted, such as voluntary turnover. A predictor or explanatory variable is associated with the outcome, such as workload or promotion opportunity.

A construct is an abstract concept, such as engagement, psychological safety or leadership quality. Constructs require operational definitions and valid measures. A single survey question may be an imperfect indicator of a complex construct. Reliability concerns consistency of measurement; validity concerns whether the measure represents the intended concept.

A metric is a defined quantitative measure. A key performance indicator (KPI) is a metric considered especially important for monitoring objectives. A KPI can still be poorly chosen. Measuring training completion as a KPI may encourage attendance without demonstrating learning or improved performance.

2.4 Association, prediction and causation

An association means that two variables vary together. A predictive model estimates an unknown or future value using available information. Neither association nor prediction by itself proves that changing a variable will cause an outcome to change.

For example, employees who receive more training may have higher performance. This association could reflect training effectiveness, but it could also reflect selection: high-potential employees may be more likely to receive training and already be expected to perform well. Causal reasoning requires a credible counterfactual: what would have happened to the same employees, at the same time, under a different intervention or condition?

3. The Analytics Maturity Continuum

Analytics categories represent different questions rather than rigidly separate technologies. A single project may use several forms of analytics.

3.1 Operational reporting: “What was recorded?”

Operational reporting provides routine information needed to run the organization. Examples include current headcount, open vacancies, payroll exceptions, absence records and compliance completion.

Reports should be timely, accurate and standardized. They usually answer narrowly defined questions and may involve little interpretation. Operational reporting is essential infrastructure, but it does not necessarily explain patterns or recommend action.

3.2 Descriptive analytics: “What happened?”

Descriptive analytics summarizes historical data. Common techniques include counts, percentages, rates, averages, medians, distributions and trend charts.

For a period, a simple turnover rate can be expressed as:

Turnover rate = Number of separations during the period ÷ Average headcount during the period × 100

Here, separations include the exits defined by the organization, and average headcount is commonly estimated as the mean of beginning and ending headcount. The definition must specify whether internal transfers, involuntary exits and temporary workers are included. The formula is meaningful only when the numerator and denominator refer to compatible populations and time periods.

Worked example. A department has 120 employees at the beginning of a quarter and 130 at the end. Eight employees leave during the quarter. Average headcount is (120 + 130) ÷ 2 = 125. Turnover is 8 ÷ 125 × 100 = 6.4%. This is a descriptive rate, not an explanation of why employees left.

3.3 Diagnostic analytics: “Why did it happen?”

Diagnostic analytics investigates possible explanations. Analysts may compare groups, examine trends, segment results, identify anomalies and test relationships. For example, turnover may be compared by tenure band, manager, role, location, pay position or career progression.

A diagnostic finding should be treated as a hypothesis unless the design supports stronger inference. If turnover is higher under one manager, possible explanations include management behavior, difficult work assignments, local labor-market conditions, team composition or differences in employee tenure. A simple comparison does not establish managerial causation.

3.4 Predictive analytics: “What is likely to happen?”

Predictive analytics estimates the probability or expected value of a future or unknown outcome. Examples include forecasting hiring demand, estimating absence risk or identifying applicants likely to complete a recruitment process.

A model may be accurate in a statistical sense but inappropriate for action. A turnover-risk model can identify groups with elevated risk, yet it may not reveal what intervention would help. Predictions can also reproduce historical inequities if past decisions or data reflect discrimination.

Predictive performance should be evaluated on data not used to train the model. Relevant measures depend on the task. For a classification model, analysts may examine accuracy, precision, recall, calibration and false-positive or false-negative rates. These measures should be interpreted in relation to the consequences of errors.

3.5 Prescriptive analytics: “What should we do?”

Prescriptive analytics evaluates possible actions under constraints. It may compare staffing schedules, recommend learning resources, allocate recruitment spending or identify interventions for a workforce segment.

A prescriptive recommendation depends on assumptions about costs, benefits, feasibility and employee response. Optimization cannot compensate for a poorly defined objective. Maximizing short-term productivity, for example, may increase fatigue, errors or turnover if employee well-being is omitted from the decision model.

3.6 Causal analytics: “What effect did an action have?”

Causal analytics estimates the effect of an intervention or exposure. Examples include whether a revised onboarding program improves six-month retention, whether flexible scheduling affects absence, or whether a pay adjustment changes acceptance rates.

A randomized controlled trial, when feasible and ethical, assigns eligible units to treatment and comparison conditions. Randomization helps balance observed and unobserved factors on average. In other settings, analysts may use quasi-experimental approaches such as difference-in-differences, regression discontinuity or matched comparison groups. These methods require careful assumptions and cannot be treated as automatic proof of causation.

A useful distinction is:

Analytical formCore questionTypical outputMain limitation
Operational reportingWhat is recorded now?Standard reportLimited explanation
DescriptiveWhat happened?Summary or trendRetrospective
DiagnosticWhy might it have happened?Segments and hypothesesConfounding
PredictiveWhat may happen?Probability or forecastNot necessarily causal
PrescriptiveWhat action is advisable?RecommendationDepends on assumptions
CausalWhat effect did an action have?Estimated intervention effectRequires credible design
Progression of people analytics questions ReportingWhat is recorded? DescriptiveWhat happened? DiagnosticWhy might it happen? PredictiveWhat may happen? PrescriptiveWhat should we do? CausalWhat effect occurred?
Progression from reporting to causal and prescriptive people analytics
Figure: Progression from reporting to causal and prescriptive people analytics

Figure: Increasingly decision-oriented forms of people analytics. The sequence is not strictly linear; projects may move between forms.

4. Theoretical Foundations for HR Decisions

4.1 Human capital theory

Human capital theory, associated particularly with the work of Gary Becker, treats knowledge, skills, experience and health as resources that can contribute to productive activity. Education and training may increase capability, while experience may improve judgment and efficiency.

For HR decisions, the theory supports investment in selection, development, knowledge retention and succession planning. It also highlights that human capital is not owned in the same way as physical equipment. Employees can leave, skills can become obsolete and value depends on the context in which capabilities are used.

A limitation is that a narrow economic interpretation may treat people merely as productivity inputs. Human value, autonomy, fairness and well-being cannot be reduced to financial return. Human capital analysis should therefore be combined with ethical and organizational perspectives.

4.2 Resource-based and strategic perspectives

The resource-based view argues that resources can support sustained advantage when they are valuable, rare, difficult to imitate and effectively organized. Specialized expertise, collaborative routines, organizational culture and trusted relationships may meet these conditions.

People analytics can help identify strategically important capabilities, capability gaps and risks associated with key-person dependence. It should not assume that employees are interchangeable units. Context, teamwork and organizational systems often determine whether individual capability produces value.

4.3 Organizational behavior theories

Organizational behavior explains how individuals, groups and organizational systems influence work outcomes. Several theories are especially relevant:

  • Motivation theories: Expectancy theory proposes that effort depends partly on expected performance, rewards and the value attached to those rewards. Goal-setting theory emphasizes clear, challenging and accepted goals supported by feedback. Self-determination theory emphasizes autonomy, competence and relatedness.
  • Job characteristics model: Work is more likely to be motivating when it provides skill variety, task identity, task significance, autonomy and feedback.
  • Social exchange theory: Employment relationships involve perceived mutual obligations. Fair treatment, support and recognition can encourage commitment, while perceived breaches may reduce trust.
  • Organizational justice: Employees evaluate distributive justice, procedural justice, interpersonal treatment and informational explanations. Perceived unfairness can affect engagement, performance and turnover.
  • Psychological safety: Teams learn more effectively when members believe they can raise concerns, admit errors and ask questions without interpersonal punishment.

These theories help analysts interpret data. A survey score is not self-explanatory; theory suggests mechanisms that may connect leadership, job design or fairness to outcomes.

4.4 Evidence-based management

Evidence-based management encourages decision makers to integrate four sources of evidence:

  1. the best available scientific research;
  2. organizational data and analytics;
  3. professional expertise and judgment; and
  4. the values, experiences and preferences of affected stakeholders.

This approach rejects both “data alone” and “experience alone.” Organizational data may be highly relevant but internally limited. Academic research may be rigorous but not perfectly transferable. Managers understand operational constraints, while employees can identify effects that administrative data miss.

A practical evidence-based process is:

  1. formulate an answerable management question;
  2. gather relevant internal and external evidence;
  3. assess evidence quality and alternative explanations;
  4. decide with stakeholders and constraints in view;
  5. implement and monitor the decision; and
  6. learn from outcomes and revise the intervention.

5. From Business Question to Analytical Decision

A strong people analytics project begins with a decision, not a fashionable tool. “Build an AI model” is not a sufficiently defined objective. A better question is: “How can we improve early-career retention without disadvantaging particular groups or intruding on privacy?”

A useful project framing sequence is:

  • Decision: What action could change?
  • Outcome: What result matters, and how will it be measured?
  • Population: Which employees, applicants or teams are included?
  • Time horizon: When should the outcome be observed?
  • Mechanism: Why might the proposed intervention work?
  • Evidence design: What information could distinguish competing explanations?
  • Constraints: What legal, ethical, financial and operational limits apply?
  • Evaluation: How will success and unintended effects be assessed?

Worked application: diagnosing early-career turnover

Suppose a retail organization observes that voluntary turnover among employees with less than one year of service is 18%, compared with 10% for employees with longer tenure. The organization is considering a structured onboarding and supervisor-coaching program.

Descriptive stage. Analysts verify definitions, calculate turnover by cohort and check whether the difference is stable across stores and hiring months. They examine the quality of the denominator and distinguish voluntary from involuntary exits.

Diagnostic stage. Analysts investigate scheduling stability, supervisor, commute distance, starting pay, training completion, workload and promotion visibility. They conduct interviews because administrative records may not capture perceived fairness or role expectations.

Theory stage. Job characteristics theory suggests that unclear tasks and limited feedback may reduce motivation. Social exchange theory suggests that an unfulfilled promise about scheduling could damage trust. Human capital theory suggests that early investment may improve capability and attachment, but only if training is relevant and supported.

Predictive stage. A model could estimate which new hires are at elevated risk of leaving. However, the model should not be used to deny opportunities or label individuals. Its safer use may be to identify stores with conditions requiring managerial attention.

Causal stage. If operationally feasible, stores could be assigned to receive the new program at different times, with comparison stores continuing normal practice. Analysts would compare retention over a predefined period while monitoring workload, employee experience and any differences in implementation.

Decision stage. If retention improves but employee workload increases, the program should be redesigned rather than declared successful. The organization should also assess whether benefits differ across demographic groups and whether improved retention reflects better employment quality rather than pressure to remain.

This example illustrates that analytics is a cycle of reasoning, not a single model.

6. Data Quality, Bias and Interpretation

People data are produced by human systems. They are not neutral observations of reality. Missingness may be systematic; performance ratings may vary by manager; job titles may conceal different work; and historical recruitment decisions may reflect unequal access.

Common data-quality dimensions include:

  • Accuracy: Does the value represent the real-world condition?
  • Completeness: Are important observations missing?
  • Consistency: Are definitions and formats comparable across systems?
  • Timeliness: Is the data current enough for the decision?
  • Uniqueness: Are duplicate records controlled?
  • Validity: Does the variable measure the intended construct?

Selection bias occurs when inclusion in the data is related to the outcome or exposure. Measurement bias occurs when a variable is recorded differently across groups. Omitted-variable bias can arise when an important factor affects both a predictor and an outcome. Survivorship bias occurs when analysis includes only those who remain employed.

Correlation should be interpreted cautiously. A correlation coefficient, often written as r, describes the strength and direction of a linear association between two variables, but it does not establish causation. Even a strong correlation may be produced by a third variable, reverse causality or shared time trends.

7. Ethics, Governance and Responsible Use

People analytics concerns identifiable and sometimes sensitive information. Responsible practice requires more than legal compliance.

7.1 Core principles

  • Purpose limitation: Collect and use data for specified legitimate purposes.
  • Data minimization: Use no more information than necessary.
  • Transparency: Explain what is collected, why it is used and who can access it.
  • Fairness: Test for disparate impact and avoid unjustified discrimination.
  • Security: Control access, protect systems and manage retention.
  • Accountability: Assign responsibility for decisions and provide auditability.
  • Human oversight: Do not delegate consequential employment decisions blindly to automated systems.
  • Employee voice: Involve affected people and provide mechanisms for questions or appeal.

Legal requirements differ by jurisdiction and may concern data protection, employment discrimination, employee monitoring, automated decision-making and records retention. Organizations must obtain specialist legal advice for their context. Consent alone may not be sufficient where employees face a power imbalance or where the data use is unexpected.

7.2 Algorithmic fairness

Fairness is not a single technical statistic. Analysts may examine selection rates, error rates, calibration or outcome differences across groups, but these measures can conflict. A model can appear accurate overall while performing poorly for a smaller group.

Removing a protected attribute does not necessarily remove bias because proxy variables, such as location, school or career history, may encode related information. Fairness assessment should include data auditing, stakeholder review, model documentation, subgroup evaluation and monitoring after deployment.

7.3 Surveillance and trust

Digital traces can reveal work patterns, but extensive monitoring may reduce autonomy, increase anxiety and damage trust. The existence of data does not establish a legitimate reason to use it. Analysts should ask whether collection is proportionate, whether employees reasonably expect it and whether the decision could be made with less intrusive information.

8. Technology and Contemporary Developments

Cloud HR platforms, natural-language processing, collaboration analytics and generative AI expand analytical possibilities. Text analysis may summarize themes in employee comments; machine-learning models may identify complex patterns; generative systems may help draft reports or explain metrics.

These tools also create risks: fabricated outputs, confidentiality breaches, opaque reasoning, automation bias, insecure data transfer and overconfident interpretation. Generative AI should not be treated as an independent source of truth. Sensitive employee data should not be entered into an unapproved system, and outputs require human verification.

A practical governance framework includes an inventory of analytical uses, risk classification, documented data provenance, validation standards, access controls, impact assessments, monitoring and a process for contesting decisions. Technology should serve a clearly justified decision process rather than determine the process by default.

9. Professional Practice and Employability

An entry-level people analyst should be able to translate a management problem into measurable questions, work with HRIS and spreadsheet data, communicate uncertainty, create clear visualizations and explain limitations to nontechnical audiences. Technical competence is necessary but insufficient. Credibility also depends on business understanding, research literacy, ethical judgment and relationship skills.

A professional analyst should:

  1. clarify definitions before calculating metrics;
  2. document data sources, assumptions and exclusions;
  3. distinguish facts, interpretations and recommendations;
  4. avoid overstating causal conclusions;
  5. report uncertainty and data limitations;
  6. check results across relevant groups;
  7. protect confidentiality; and
  8. evaluate whether the decision improved outcomes without creating unacceptable harm.

The most valuable analysts are translators between data, theory and action. They can explain not only what a number says, but also what it does not say and what evidence would be needed next.

Chapter Summary

HR and people analytics developed from administrative personnel records and routine HR reporting into a multidisciplinary approach to workforce decisions. Its scope includes employee, applicant, team, organizational and business-outcome data. Important terminology includes units of analysis, variables, constructs, metrics, KPIs, samples, populations, predictors and outcomes.

Operational reporting describes recorded activity. Descriptive analytics summarizes what happened; diagnostic analytics investigates why patterns may have occurred; predictive analytics estimates what may happen; prescriptive analytics evaluates possible actions; and causal analytics estimates the effects of interventions. These categories answer different questions and should not be confused.

Human capital theory explains the value of knowledge and skills, while resource-based perspectives connect capabilities to competitive advantage. Organizational behavior theories help explain motivation, job design, exchange, justice and psychological safety. Evidence-based management integrates research evidence, organizational data, professional judgment and stakeholder values.

Effective people analytics begins with a decision problem and requires valid definitions, appropriate data, careful interpretation and evaluation. Data quality, selection bias, measurement bias and confounding limit conclusions. Ethical practice requires purpose limitation, transparency, fairness, security, accountability and meaningful human oversight. Technology can extend analytical capability, but it does not replace theory, judgment or responsibility.

Key Terms

Human capital: Knowledge, skills, experience, health and other human attributes that can contribute to productive activity.

People analytics: The systematic use of workforce data, analytical methods and organizational knowledge to improve decisions about people and work.

HR analytics: Analysis focused primarily on human resource activities and outcomes.

HRIS: A human resource information system used to store, manage and process workforce information.

Operational reporting: Routine reporting of recorded transactions and current conditions.

Descriptive analytics: Analysis that summarizes historical or current patterns.

Diagnostic analytics: Analysis that investigates possible explanations for observed patterns.

Predictive analytics: Analysis that estimates future or unknown outcomes.

Prescriptive analytics: Analysis that evaluates or recommends actions under stated constraints.

Causal analytics: Analysis designed to estimate the effect of an intervention or exposure.

Unit of analysis: The entity about which an observation or conclusion is made.

Construct: An abstract concept that requires operational measurement.

Metric: A defined quantitative measure.

KPI: A metric considered especially important for monitoring an objective.

Confounding: A situation in which another factor helps explain an observed relationship between variables.

Selection bias: Systematic distortion caused by how observations enter or remain in a dataset.

Human capital theory: A perspective treating knowledge and skills as investments that can produce economic value.

Evidence-based management: Decision-making that integrates research, organizational data, professional judgment and stakeholder values.

Psychological safety: A shared belief that people can speak up, ask questions and discuss errors without interpersonal punishment.

Algorithmic fairness: The evaluation and management of whether automated or statistical decisions produce unjustified disparities.

Review Questions

Short Answer Questions

  1. How does people analytics differ from routine HR reporting?
  2. What is the difference between a population and a sample?
  3. Why does correlation not necessarily establish causation?
  4. Identify two data-quality dimensions relevant to HR analytics.
  5. What four evidence sources are integrated by evidence-based management?

Long Answer Questions

  1. Explain the evolution from personnel administration to strategic people analytics.
  2. Compare descriptive, diagnostic, predictive, prescriptive and causal analytics, giving an HR example of each.
  3. Discuss how human capital theory and the resource-based view can inform workforce planning.
  4. Explain how organizational behavior theories can improve interpretation of employee survey results.
  5. Evaluate the ethical principles that should guide the use of employee data and algorithmic tools.

Analytical / Application Questions

  1. An organization reports higher turnover in one department. Design a sequence of descriptive, diagnostic and causal analyses that could investigate the issue without assuming that the department manager is responsible.
  2. A predictive model identifies employees who are likely to resign. Explain two beneficial uses, two risks and safeguards that should be applied before implementation.
  3. A company introduces supervisor coaching in half of its stores and wants to assess its effect on new-hire retention. Propose an evaluation design, identify a suitable outcome and discuss at least three threats to valid interpretation.

Multiple Choice Questions with Answers

Question 1

Which question is primarily answered by descriptive analytics?

A. What happened to voluntary turnover last quarter?

B. Which intervention will maximize retention?

C. What causal effect did coaching have?

D. Which employee is most likely to resign next month?

Correct Answer: A. What happened to voluntary turnover last quarter?

Question 2

Which statement best distinguishes prediction from causation?

A. Prediction always requires randomization.

B. A predictor associated with an outcome may improve forecasts without causing the outcome.

C. Causal analysis cannot use organizational data.

D. A causal relationship is simply a strong correlation.

Correct Answer: B. A predictor associated with an outcome may improve forecasts without causing the outcome.

Question 3

What is the unit of analysis when an analyst compares absence rates among departments?

A. The individual absence event only

B. The employee's age

C. The department

D. The payroll system

Correct Answer: C. The department

Question 4

Which is an example of prescriptive analytics?

A. Reporting current headcount

B. Summarizing last year's training completion

C. Estimating next year's hiring demand

D. Recommending a staffing schedule subject to budget constraints

Correct Answer: D. Recommending a staffing schedule subject to budget constraints

Question 5

A department begins with 120 employees, ends with 130, and has 8 separations. Using average beginning and ending headcount, what is the turnover rate?

A. 6.4%

B. 6.7%

C. 8.0%

D. 15.4%

Correct Answer: A. 6.4%

Question 6

Which theory emphasizes autonomy, competence and relatedness?

A. Human capital theory

B. Self-determination theory

C. Resource-based theory

D. Expectancy theory

Correct Answer: B. Self-determination theory

Question 7

Which practice best reflects evidence-based management?

A. Following intuition without checking data

B. Using an algorithm without stakeholder input

C. Integrating research, organizational data, expertise and stakeholder values

D. Using only external academic studies

Correct Answer: C. Integrating research, organizational data, expertise and stakeholder values

Question 8

Which situation is an example of selection bias?

A. A report uses a consistent date format.

B. A survey is completed mainly by employees with very positive or very negative views.

C. A dataset contains a clearly defined outcome.

D. A manager documents the data source.

Correct Answer: B. A survey is completed mainly by employees with very positive or very negative views.

Question 9

Why can removing a protected attribute fail to eliminate algorithmic bias?

A. Models cannot use any variables without bias.

B. Protected attributes are never relevant to fairness.

C. Proxy variables may encode information related to the protected attribute.

D. Fairness is guaranteed when data are large.

Correct Answer: C. Proxy variables may encode information related to the protected attribute.

Question 10

Which is the strongest reason to involve employees in people analytics governance?

A. Employees can replace all statistical validation.

B. Employees can identify expectations, harms and contextual information missing from administrative data.

C. Employee involvement makes privacy law irrelevant.

D. Employees guarantee that a model will be accurate.

Correct Answer: B. Employees can identify expectations, harms and contextual information missing from administrative data.

HR & People Analytics
Chapter 1 of 15