People Analytics and Evidence-Based ManagementIntroductionPeople management has traditionally relied on managerial experience, informal observation and periodic surveys. These sources remain valuable, but they can be incomplete and vulnerable to bias. People analytics strengthens managerial judgement by using reliable workforce data to identify patterns, test assumptions and evaluate interventions. It does not replace human judgement. Rather, it helps leaders ask better questions, distinguish symptoms from causes and make decisions that can be explained and reviewed. People analytics is the systematic use of workforce data, analytical methods and organisational knowledge to understand people-related issues and improve decisions. Evidence-based management is the broader practice of making managerial decisions through the conscientious, explicit and judicious use of the best available evidence. Such evidence may include organisational data, research findings, professional expertise and the perspectives of employees and other stakeholders. For team leaders, the practical challenge is not simply to produce more data. It is to select meaningful measures, interpret them carefully, protect employee rights and convert findings into responsible action. Learning objectivesBy the end of this chapter, you should be able to: - Explain the purpose, scope and limits of people analytics.
- Interpret practical metrics for productivity, engagement, absenteeism, turnover, skills and team health.
- Distinguish descriptive, diagnostic, predictive and prescriptive analytics.
- Design and interpret a useful people dashboard.
- Avoid common errors in measurement, comparison and causal reasoning.
- Apply evidence responsibly while protecting privacy, fairness and employee voice.
- Use an evidence-based management cycle to support team decisions.
The foundations of people analyticsData, information, evidence and insightThese terms are related but not interchangeable. - Data are recorded observations, such as hours worked, customer cases completed or survey responses.
- Information is organised data presented in a meaningful context.
- Evidence is information judged relevant and credible for a particular decision.
- Insight is an informed interpretation that explains what may be happening and what should be investigated or done.
- Action is the managerial intervention that follows, such as workload redesign, coaching or skills development.
A dashboard may contain accurate information but still provide weak evidence if the measures are poorly defined, incomplete or unrelated to the decision. The evidence-based management cycleA disciplined cycle prevents managers from jumping directly from a metric to a conclusion: - Frame the question. For example: “Why has voluntary turnover increased among experienced service advisers?”
- Specify the decision. Clarify what action might follow from the analysis.
- Gather evidence. Combine workforce records, employee perspectives, research evidence and professional judgement.
- Assess quality. Check definitions, completeness, reliability, comparability and possible bias.
- Analyse patterns. Examine trends, differences between relevant groups and plausible explanations.
- Decide and act. Select a proportionate intervention.
- Evaluate. Define success measures and review whether the intervention produced improvement without harmful side effects.
This cycle treats management as a learning process rather than a one-time reaction to a red indicator. Four levels of analytics| Level | Main question | Typical output | Appropriate use |
|---|
| Descriptive | What happened? | Monthly turnover rate | Establishing the current position | | Diagnostic | Why might it have happened? | Exit themes associated with a team | Generating and testing explanations | | Predictive | What may happen next? | Risk estimate for future vacancies | Planning and prioritisation | | Prescriptive | What could we do? | Options and estimated consequences | Supporting, not automating, decisions |
Predictive results are probabilities, not facts. A model that identifies employees who resemble previous leavers does not prove that those employees will leave, nor does it justify treating them unfairly. Designing useful metricsA metric should have a clear purpose, operational definition, data source, owner, reporting frequency and interpretation rule. Leaders should ask: - What decision will this measure inform?
- Who is included and excluded?
- What is the denominator?
- What time period and comparison are appropriate?
- Could the measure encourage undesirable behaviour?
- What important aspect of performance does it fail to capture?
A leading indicator may signal future conditions, such as workload pressure, training completion or psychological safety. A lagging indicator records an outcome, such as accidents, turnover or missed deadlines. Effective dashboards normally include both. Productivity and performanceProductivity concerns the relationship between outputs and inputs. A general productivity ratio is: Productivity = Output ÷ Input Output and input must be defined consistently. For example, completed and quality-approved cases per paid labour hour is more meaningful than cases per employee if employees work different hours. Productivity is not identical to busyness. A high volume of low-quality work may reduce organisational value. Useful complementary measures include: - output per labour hour;
- first-time quality or error rate;
- cycle time;
- customer or client outcome measures;
- rework and escalation rates;
- achievement of agreed objectives.
A balanced interpretation is essential. If a team’s output rises while error rates and sickness absence also rise, the apparent productivity gain may be unsustainable. EngagementEngagement refers to the quality of an employee’s connection with and willingness to invest effort in work. It is distinct from job satisfaction, which is an evaluative attitude, and organisational commitment, which concerns attachment to the organisation. Engagement surveys commonly use items about purpose, autonomy, support, recognition, growth and intent to remain. A simple favourable percentage can be calculated as: Favourable percentage = (Number of favourable responses ÷ Number of valid responses) × 100 The definition of “favourable” must be stated. It might mean responses of 4 or 5 on a five-point scale, but different organisations may use different rules. Response rate should also be reported: Response rate = (Number of completed responses ÷ Number of invited employees) × 100 A declining response rate can indicate survey fatigue or distrust, and a high score may reflect acquiescence rather than genuine engagement. Survey results should therefore be interpreted with comments, listening sessions and local context. AbsenteeismAbsenteeism measures time away from scheduled work. One common rate is: Absence rate = (Total absence days ÷ Total scheduled workdays) × 100 For example, if a 20-person team is scheduled for 20 days each during a month, scheduled workdays equal 400. If 12 absence days are recorded, the absence rate is 3%. The measure should specify whether it includes authorised leave, parental leave, workplace injury, unpaid leave or only sickness absence. Frequency and duration provide different information. A team may have many short absences or a small number of long-term cases. Managers must never infer misconduct or medical conditions from an absence statistic alone. Turnover and retentionTurnover is the movement of employees out of an organisation or unit. A commonly used period turnover rate is: Turnover rate = (Number of leavers during the period ÷ Average headcount during the period) × 100 Average headcount is often estimated as: Average headcount = (Headcount at beginning of period + Headcount at end of period) ÷ 2 If a unit begins with 80 employees, ends with 84 and has 6 leavers, average headcount is 82 and turnover is approximately 7.3% for the period. This is a descriptive estimate; it is not automatically an annual rate. Annualisation requires an explicit assumption that the observed rate is representative across the year, which may be inappropriate for seasonal work. Separate voluntary from involuntary turnover and examine regretted loss, tenure, role, location and reason for leaving. Exit interviews are subject to recall and self-presentation bias, while non-exit surveys may reveal different themes. Skills and capabilitySkills analytics maps current capability against present and future requirements. A practical skills inventory should record the skill, proficiency definition, evidence of proficiency, currency, business criticality and development need. Self-ratings alone are insufficient; they should be supplemented, where appropriate, by work samples, assessments, certifications, manager observations and peer evidence. A simple gap indicator can be expressed as: Skill gap = Required proficiency − Current proficiency This subtraction is meaningful only when both levels use the same validated scale. A positive gap indicates development need; a zero or negative gap does not guarantee effective performance, because application, motivation and context also matter. Skills dashboards should not reduce people to scores. They should support fair access to learning, succession planning and deployment, while allowing employees to challenge inaccurate records. Team healthTeam health is a multidimensional assessment of how well a team can perform and sustain collaboration. Potential dimensions include: - clarity of goals and roles;
- workload and capacity;
- psychological safety;
- trust and inclusion;
- coordination and information flow;
- learning and adaptability;
- quality and customer outcomes;
- wellbeing and sustainability.
A composite team-health index may be useful for communication, but aggregation can conceal important differences. If five dimensions are scored from 1 to 5 and equally weighted, a simple index is: Index = (Score₁ + Score₂ + Score₃ + Score₄ + Score₅) ÷ 5 Equal weighting is a managerial convention, not a scientific law. It should be justified, reviewed and supplemented with the underlying dimension scores. A team with an average of 3.8 may still have dangerously low psychological safety. Reading a dashboard criticallyA dashboard is a decision-support interface, not a verdict. An effective dashboard normally contains: - a small number of strategically relevant measures;
- definitions and denominators;
- current values and historical trends;
- meaningful benchmarks or targets;
- segmentation that reveals material differences;
- data quality notes and confidence limitations;
- an identified owner and next action.
Comparisons require care. Compare like with like: similar roles, work processes, time periods and staffing conditions. A team handling complex cases should not be judged against a team handling routine cases without adjustment. Small groups may show large percentage changes from very few observations. Suppression or aggregation may be necessary to protect confidentiality. Managers should distinguish correlation from causation. If engagement and productivity rise together, possible explanations include better leadership, increased staffing, seasonal demand or changes in measurement. The data alone do not identify the cause. A useful practice is to triangulate three forms of evidence: - quantitative evidence, such as absence and quality data;
- qualitative evidence, such as interviews, comments and observations;
- external evidence, including credible research and professional standards.
A worked dashboard exampleAn operations team has 50 employees. During one quarter it records 1,500 completed cases, 30,000 scheduled labour hours, 90 absence hours and 4 leavers. Average headcount is 50. The team receives 40 valid engagement responses from 45 invited employees, of which 28 are favourable. Productivity is: 1,500 ÷ 30,000 = 0.05 cases per labour hour Equivalently, the team completes 5 cases per 100 labour hours. The absence rate is: (90 ÷ 30,000) × 100 = 0.3% The turnover rate for the quarter is: (4 ÷ 50) × 100 = 8% The engagement response rate is: (40 ÷ 45) × 100 ≈ 88.9% The favourable engagement percentage is: (28 ÷ 40) × 100 = 70% These figures describe the position but do not explain it. Before concluding that productivity is strong, the manager should examine quality, case complexity and customer outcomes. Before interpreting turnover as a retention failure, the manager should examine whether the four leavers were voluntary, whether they were concentrated in one role and whether the quarter was unusually seasonal. A practical case: Northbridge Service CentreBackgroundNorthbridge Service Centre is an illustrative case. It employs 120 customer-support advisers across four teams. Over two quarters, overall productivity remained stable, but voluntary turnover increased from 5% to 10% per quarter. The dashboard also showed a fall in engagement from 76% to 64% and an increase in short-term absence. ProblemThe senior manager initially proposed a retention bonus for all advisers. However, the people analyst cautioned that the data did not establish pay as the cause. The leadership team framed the question as: “Which conditions are associated with avoidable turnover, and which actions can improve retention without damaging service quality?” AnalysisThe team segmented the data by tenure, shift, supervisor and role, while maintaining privacy safeguards. Voluntary leavers were concentrated among advisers with six to eighteen months’ tenure, especially on late shifts. Exit comments mentioned unpredictable schedules, limited coaching and difficult customer interactions. Quality records showed that late-shift teams had higher escalation rates, partly because specialist support was less available at night. Interviews with current employees broadly supported these findings, but not all employees experienced the problem in the same way. The analysis also identified a data limitation: exit-interview completion was lower among employees who left abruptly, so the reasons were not fully representative. Approach and solutionThe centre introduced a twelve-week pilot in two late-shift teams: - schedules were published earlier and changes were restricted except in emergencies;
- each new adviser received fortnightly coaching;
- an experienced escalation specialist was assigned to late shifts;
- managers held brief monthly listening sessions;
- quality, absence, engagement and turnover indicators were monitored together.
The remaining teams acted as a comparison group, although the pilot was not a fully randomised experiment. Leaders defined success in advance: improved schedule predictability and coaching access, no decline in quality, and a reduction in voluntary departures over subsequent quarters. OutcomeAt the end of twelve weeks, the pilot teams reported higher perceptions of schedule fairness and coaching availability. Quality remained stable and escalation resolution improved. Turnover had not yet changed enough to establish a durable effect, because turnover is a relatively infrequent outcome and longer follow-up was required. The organisation therefore continued the pilot, improved data collection and avoided claiming that the intervention had been conclusively proven. Learning pointsThe case demonstrates that analytics is most useful when it leads to a focused question, combines different evidence sources, tests a proportionate intervention and evaluates unintended consequences. It also shows why a dashboard should not trigger a universal solution before the problem has been understood. Ethical, legal and governance responsibilitiesPeople analytics concerns individuals’ livelihoods, reputations and opportunities. Responsible practice requires: - purpose limitation: collect and use data for a legitimate, specified purpose;
- data minimisation: use only data necessary for that purpose;
- transparency: explain what is collected, why it is used and who can access it;
- accuracy: provide routes for correcting incomplete or misleading records;
- security: restrict access and protect data from unauthorised disclosure;
- fairness: test whether measures or models disadvantage protected or vulnerable groups;
- proportionality: avoid intrusive monitoring when less intrusive evidence is adequate;
- accountability: document definitions, decisions, model assumptions and review processes;
- human oversight: ensure that consequential decisions are not delegated blindly to algorithms.
Applicable privacy, employment, equality and data-protection laws vary by jurisdiction. Managers should consult organisational policies, legal specialists and data-protection officers where necessary. Sensitive data should not be used casually, and small-group reporting may enable re-identification even when names are removed. Algorithmic systems can reproduce historical bias. For example, a promotion model trained on a historically unequal workforce may learn to prefer patterns associated with previous advantage. Before deployment, organisations should test data quality, error rates and disparate impacts, document the model’s purpose and provide meaningful human review and appeal. Surveillance technologies, including keystroke monitoring, location tracking and sentiment analysis, can damage trust and psychological safety. The fact that data can be collected does not establish that it should be collected. Technology and contemporary developmentsCloud-based human-resource systems increasingly integrate recruitment, scheduling, learning, performance and wellbeing information. Natural-language tools can summarise survey comments, classify themes and identify recurring issues. Such tools can save time but may misunderstand context, encode bias or expose confidential information. Human validation, secure processing and clear retention rules are essential. Contemporary practice is moving toward skills-based workforce planning, continuous listening, process mining and more frequent team-level feedback. These developments create opportunities for earlier support, but they also increase the risk of data overload and continuous surveillance. Good leadership therefore requires analytical restraint: use technology where it improves a clearly defined decision, and preserve dialogue where the issue depends on trust, meaning or lived experience. Best-practice principles for managers- Start with a decision, not with a fascination for data.
- Define each metric, denominator, time period and owner.
- Combine outcome measures with quality, wellbeing and employee-voice measures.
- Examine trends and meaningful comparisons rather than isolated values.
- Investigate alternative explanations before acting.
- Segment only when it is useful and ethically safe.
- Treat predictions as probabilities and never as proof.
- Involve employees in interpreting findings and designing responses.
- Establish success criteria before launching an intervention.
- Review both intended results and unintended consequences.
- Keep an audit trail of definitions, assumptions and decisions.
- Protect confidentiality and provide correction and appeal mechanisms.
Chapter SummaryPeople analytics applies workforce data and analytical reasoning to people-management decisions. Evidence-based management combines organisational data with research evidence, professional expertise and employee perspectives. The evidence-based cycle moves from framing a decision, gathering and assessing evidence, analysing patterns, acting and evaluating. Productivity, engagement, absenteeism, turnover, skills and team health are useful but incomplete constructs. Their value depends on precise definitions, appropriate denominators, valid comparisons and contextual interpretation. Dashboards should support questions rather than issue automatic verdicts. Correlation does not establish causation, and predictive analytics indicates probability rather than certainty. Responsible analytics requires transparency, privacy, data quality, fairness, proportionality and human oversight. When managers triangulate quantitative and qualitative evidence, involve employees and evaluate interventions carefully, analytics can improve both organisational performance and the quality of working life. Key TermsPeople analytics: Systematic use of workforce data and analytical methods to support people decisions. Evidence-based management: Use of the best available evidence, professional judgement and stakeholder perspectives in management decisions. Descriptive analytics: Analysis that explains what has happened. Diagnostic analytics: Analysis that investigates why something may have happened. Predictive analytics: Analysis that estimates what may happen in the future. Prescriptive analytics: Analysis that compares possible actions and consequences. Productivity: Relationship between defined outputs and inputs. Engagement: Employees’ psychological connection to and investment in their work. Absenteeism: Time away from scheduled work, measured according to a stated definition. Turnover: Movement of employees out of an organisation or unit. Voluntary turnover: Leaving initiated by the employee. Leading indicator: Measure that may signal future conditions or outcomes. Lagging indicator: Measure that records an outcome after it has occurred. Denominator: The reference quantity used to calculate a rate or proportion. Triangulation: Combining different evidence sources to improve interpretation. Dashboard: Visual decision-support display of selected measures and trends. Psychological safety: Shared belief that people can speak up, question and admit mistakes without interpersonal punishment. Skill gap: Difference between required and current proficiency on a defined scale. Data minimisation: Limiting collection and use to data necessary for a legitimate purpose. Algorithmic bias: Systematic unfairness arising from data, design or use of an algorithm. Review QuestionsShort Answer Questions- Define people analytics and explain how it differs from evidence-based management.
- Distinguish descriptive, diagnostic, predictive and prescriptive analytics.
- Why must a productivity metric include clearly defined output and input measures?
- State two limitations of engagement survey results.
- Explain the difference between voluntary and involuntary turnover.
Long Answer Questions- Explain the evidence-based management cycle and show how it can improve a team decision.
- Discuss how a manager should interpret absenteeism data without making unjustified assumptions about employees.
- Explain the design features of an effective people dashboard.
- Evaluate the advantages and risks of using skills analytics for workforce planning.
- Discuss the ethical and governance responsibilities involved in people analytics.
Analytical / Application Questions- A team’s output increases by 12%, while errors increase by 20% and engagement falls by 8 percentage points. Analyse at least three possible interpretations and recommend further evidence to collect.
- An organisation reports a quarterly turnover rate of 10% in a 30-person unit. Explain why the figure should not be interpreted without examining headcount assumptions, leaver types, tenure and comparison groups.
- Design a twelve-week evidence-based intervention for a team with low psychological safety and rising absence. Specify the evidence to collect, intervention measures, ethical safeguards and evaluation criteria.
Multiple Choice Questions with AnswersQuestion 1Which type of analytics primarily answers the question, “What happened?” A. Descriptive analytics B. Diagnostic analytics C. Predictive analytics D. Prescriptive analytics Correct Answer: A. Descriptive analytics Question 2A team records 12 absence days and 400 scheduled workdays. What is its absence rate? A. 0.3% B. 3% C. 30% D. 33.3% Correct Answer: B. 3% Question 3Which measure is most clearly a leading indicator? A. Last year’s turnover B. Completed exit interviews C. Current access to coaching D. Past accident frequency Correct Answer: C. Current access to coaching Question 4What is the main purpose of defining a denominator when calculating a people metric? A. To remove the need for qualitative evidence B. To provide a consistent reference quantity for comparison C. To guarantee that the metric proves causation D. To increase the number of reported employees Correct Answer: B. To provide a consistent reference quantity for comparison Question 5A team has 80 employees at the start of a period and 84 at the end. Six employees leave. Using average headcount, what is the turnover rate? A. 6.0% B. 7.3% approximately C. 7.5% D. 8.4% approximately Correct Answer: B. 7.3% approximately Question 6Which statement best describes predictive analytics in people management? A. It proves which employee will leave B. It estimates possible future outcomes using available patterns C. It replaces managerial judgement in all decisions D. It describes only historical events Correct Answer: B. It estimates possible future outcomes using available patterns Question 7Why should productivity be interpreted alongside quality measures? A. High output can coexist with errors or rework B. Quality measures always have larger denominators C. Productivity cannot be calculated numerically D. Quality is unrelated to organisational outcomes Correct Answer: A. High output can coexist with errors or rework Question 8Which practice best reflects data minimisation? A. Collecting all technically available employee data B. Keeping data indefinitely in case it becomes useful C. Collecting only data necessary for a legitimate stated purpose D. Sharing individual records with all managers Correct Answer: C. Collecting only data necessary for a legitimate stated purpose Question 9What is triangulation in people analytics? A. Using three identical dashboards B. Combining quantitative, qualitative and external evidence C. Replacing surveys with algorithms D. Comparing only three employees Correct Answer: B. Combining quantitative, qualitative and external evidence Question 10Why is a low psychological-safety score important even when a team’s average health index is high? A. An average always exaggerates every dimension B. Composite scores can conceal a serious weakness in one dimension C. Psychological safety is not related to team functioning D. Health indices cannot contain numerical scores Correct Answer: B. Composite scores can conceal a serious weakness in one dimension
|