<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>People-Analytics on Workforce Data Lab</title><link>https://workforcedatalab.com/tags/people-analytics/</link><description>Recent content in People-Analytics on Workforce Data Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://workforcedatalab.com/tags/people-analytics/index.xml" rel="self" type="application/rss+xml"/><item><title>Absence and PTO Analytics: Skewed Distributions, Calendar Artefacts, and the Burnout-Proxy Problem</title><link>https://workforcedatalab.com/posts/2026-08-04-absence-and-pto-analytics-skewed-distributions-calendar-artefacts-and-/</link><pubDate>Tue, 04 Aug 2026 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2026-08-04-absence-and-pto-analytics-skewed-distributions-calendar-artefacts-and-/</guid><description>&lt;p>Absence data looks like the simplest feed in the HR stack — days off, per person, per month — and is one of the easiest to misread. The distributions are not the shape analysts assume, the calendar contaminates every monthly comparison, and the field&amp;rsquo;s favourite use of the data, as a burnout early-warning signal, is weaker than its reputation. This piece covers all three, with the statistical posture we recommend for each.&lt;/p></description></item><item><title>Workforce Planning Scenarios: Driver-Based Models vs Budget Arithmetic, and the Assumptions Register</title><link>https://workforcedatalab.com/posts/2026-07-14-workforce-planning-scenarios-driver-based-models-vs-budget-arithmetic-/</link><pubDate>Tue, 14 Jul 2026 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2026-07-14-workforce-planning-scenarios-driver-based-models-vs-budget-arithmetic-/</guid><description>&lt;p>Most workforce plans are budget arithmetic wearing a strategy costume: last year&amp;rsquo;s headcount, plus or minus a negotiated percentage, spread across cost centres. That process produces a number. It does not produce a plan, because it contains no model of how headcount relates to anything the business actually does. Driver-based planning is the alternative, and its track record is mixed for an instructive reason — teams build models with dozens of drivers when the variance is carried by five. This piece covers the structural difference, the small driver set that matters, and the publishing discipline that separates a scenario from a guess.&lt;/p></description></item><item><title>GenAI in People Analytics: Where LLMs Help, Where They Fabricate, and a Validation Protocol</title><link>https://workforcedatalab.com/posts/2026-05-19-genai-in-people-analytics-where-llms-help-where-they-fabricate-and-a-v/</link><pubDate>Tue, 19 May 2026 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2026-05-19-genai-in-people-analytics-where-llms-help-where-they-fabricate-and-a-v/</guid><description>&lt;p>Large language models have entered the people-analytics workflow faster than the validation practices around them. Eighteen months of watching teams deploy them has produced a clear pattern: the failures concentrate in specific task types, not in &amp;ldquo;AI usage&amp;rdquo; generally. This piece separates where LLMs genuinely add capability from where they manufacture confident error, and closes with the validation protocol we now consider the floor for AI-assisted people analytics.&lt;/p>
&lt;h2 id="where-llms-genuinely-help">Where LLMs genuinely help&lt;/h2>
&lt;p>The reliable use cases share a structure: the model transforms &lt;em>text into structured, checkable categories&lt;/em>, and a human can verify any given output.&lt;/p></description></item><item><title>Pay Equity Analysis: The Specification Choices That Change the Answer</title><link>https://workforcedatalab.com/posts/2026-04-07-pay-equity-analysis-the-specification-choices-that-change-the-answer/</link><pubDate>Tue, 07 Apr 2026 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2026-04-07-pay-equity-analysis-the-specification-choices-that-change-the-answer/</guid><description>&lt;p>Two competent analysts, given the same payroll extract and asked the same question — &amp;ldquo;is there a pay gap?&amp;rdquo; — can return materially different answers, and both can be defensible. The divergence is rarely in the statistics. It is in three specification choices made before the model is fit: the model form, the control set, and how the adjusted and unadjusted gaps are presented alongside each other. This piece walks through each choice and the reporting risks that follow.&lt;/p></description></item><item><title>Internal Mobility Metrics That Hold Up: Definitions, Denominators, and the Gaming Problem</title><link>https://workforcedatalab.com/posts/2026-02-17-internal-mobility-metrics-that-hold-up-definitions-denominators-and-th/</link><pubDate>Tue, 17 Feb 2026 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2026-02-17-internal-mobility-metrics-that-hold-up-definitions-denominators-and-th/</guid><description>&lt;p>Internal mobility is the metric every organisation wants to report and few organisations define tightly enough to survive an audit. The numbers travel upward — to CHRO decks, board packs, ESG narratives — and each hop strips away a denominator. This piece lays out definitions that hold up for the three core metrics (internal fill rate, time-to-fill for internal moves, and the post-move outcome window), then catalogues the four places teams quietly game them.&lt;/p></description></item><item><title>Skills Data Quality: Inferred vs Attested Skills, and How to Decide with Bad Mirrors</title><link>https://workforcedatalab.com/posts/2025-12-02-skills-data-quality-inferred-vs-attested-skills-and-how-to-decide-with/</link><pubDate>Tue, 02 Dec 2025 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2025-12-02-skills-data-quality-inferred-vs-attested-skills-and-how-to-decide-with/</guid><description>&lt;p>Every skills-based initiative — talent marketplaces, workforce planning, succession analytics — inherits the error structure of whatever produced the skills data. That provenance is almost always one of two processes: inference (resume and ATS parsing, profile extraction) or attestation (self-report, manager endorsement). These two sources fail differently, predictably, and in ways that matter for which decisions each can support. This piece maps the error profiles and proposes a decision-bounding framework for the common situation: no ground truth available.&lt;/p></description></item><item><title>Engagement Survey Methodology: Why the Instrument Moves More Than the Intervention</title><link>https://workforcedatalab.com/posts/2025-09-16-engagement-survey-methodology-why-the-instrument-moves-more-than-the-i/</link><pubDate>Tue, 16 Sep 2025 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2025-09-16-engagement-survey-methodology-why-the-instrument-moves-more-than-the-i/</guid><description>&lt;p>The engagement survey is the most analysed and least scrutinised instrument in people analytics. Organisations invest in interventions to move scores by a few points, then change the questionnaire in the same cycle and attribute the resulting shift to the programme. This piece covers three methodological problems we consider structural rather than incidental — common-method bias, the anonymity-perception effect, and item-wording effects — and closes with survey-design guidance we now treat as baseline.&lt;/p></description></item><item><title>Attrition Risk Models: What a Defensible Model Actually Needs</title><link>https://workforcedatalab.com/posts/2025-06-10-attrition-risk-models-what-a-defensible-model-actually-needs/</link><pubDate>Tue, 10 Jun 2025 09:00:00 +0000</pubDate><guid>https://workforcedatalab.com/posts/2025-06-10-attrition-risk-models-what-a-defensible-model-actually-needs/</guid><description>&lt;p>Most attrition models in production today would not survive a methods review. Not because the algorithms are wrong, but because the surrounding apparatus is missing: the features leak, the probabilities are uncalibrated, and nobody is watching the model after deployment. This piece lays out the four requirements we now treat as the bar for a defensible attrition model — feature families that generalise, calibration alongside discrimination, a disciplined leakage audit, and drift monitoring treated as the actual product.&lt;/p></description></item></channel></rss>