The inclusion measurement gap: programs survived, felt impact didn't
Employers spent 18 months making DEI legally defensible. The programs are still standing, but employees report less impact than ever, and most HR dashboards cannot see the difference.
Two years of legal pressure produced a strange outcome. Inclusion programs at most large employers are still running, membership rules have been rewritten, charters have been narrowed, and outside counsel has signed off. What has not survived is the feeling. That is the inclusion measurement gap: the widening distance between what HR can report about its programs and what employees actually experience at work.
What 18 months of redesign actually changed
The redesign cycle is well documented. HR Dive reported in January 2026 that the stated DEI priority for employers this year is making talent programs "scrutiny-proof" - legally reviewable rather than demographically targeted. Amundsen Davis flagged in July that the EEOC's rescission of roughly 50 years of affirmative action guidance triggered another round of program redesign, and Gibson Dunn's DEI Task Force Update in August kept restructuring pressure live. SHRM's June launch of its Center for Inclusion & Diversity, which folded in CEO Action work, was explicitly framed around the realities employers face now.
HR Brew's reporting in February captured the survival mechanism: employee resource groups largely stayed in place, usually by opening membership to all employees and narrowing their charters. That was the rational move. It also quietly changed what those groups do. A group that once served as an advocacy channel for a specific population now often functions as an open-invitation community forum with a lighter mandate. The nameplate is identical. The function is not.
The problem is that most people ops dashboards were built to track the nameplate. Number of ERGs, chapters per region, training completion rate, policy language reviewed. Every one of those numbers can hold steady or improve while the underlying employee experience deteriorates.
Program inventory metrics have changed jobs. Counting ERGs is documentation for legal review, not evidence that anyone feels included.
The data showing employees stopped feeling it
Citing The Conference Board, HR Dive reported in February 2026 that fewer workers report a positive impact from DEI initiatives than in prior years. The more uncomfortable finding in the same research is the perception split: executives rate the impact of these initiatives higher than employees do. Leaders are grading the program. Employees are grading the experience. Those are different exams.
The macro backdrop makes the gap harder to dismiss as a DEI-specific story. Gallup's global engagement update in April put engagement at a five-year low, roughly one in five employees worldwide, with follow-on coverage framing it as a slide back to 2020 levels. Engagement and felt inclusion are not the same construct, but they move together, and both are downstream of the same daily inputs: whether a manager responds, whether advancement looks fair, whether it is safe to speak in a team meeting.
There is a third signal that rarely reaches inclusion dashboards at all. A 2026 Journal of Management review on work and loneliness links coworker incivility and ostracism directly to workplace loneliness. As one of the researchers, Berrin Erdogan, put it in coverage of the review, loneliness is a business issue rather than a personal one. Ostracism is exactly the kind of thing an ERG headcount cannot detect.
Why program inventory is now a compliance artifact
Here is the reframe that matters for people ops. After 18 months of legal review, program inventory metrics have changed jobs. Counting ERGs and logging training completion is now documentation for legal and regulatory purposes. It demonstrates that the organization has consistent, reviewable, non-targeted practices. That is genuinely useful. It is not a culture signal.
Treating it as a culture signal creates a specific failure mode that is easy to spot in a boardroom. The inclusion slide shows green because every program survived the redesign. The engagement slide, two pages later, shows red. Nobody connects them, because the first slide measures existence and the second measures experience. ESG Dive reported in June that SHRM panelists argued top-down leadership commitment is now the deciding variable for inclusion outcomes. Leaders cannot commit to something their reporting does not show them.
Four listening items to replace program-existence metrics
The practical swap is narrow and cheap. Retire program-existence metrics from your culture reporting, keep them in your compliance file, and adopt four survey items that are legally neutral in wording and analyzable in aggregate. First, perceived fairness of advancement: whether employees believe promotion decisions in their part of the business are made on merit and explained. Second, manager responsiveness: whether raising an issue with a direct manager leads to visible follow-through. Third, psychological safety in team meetings: whether disagreeing with the majority view carries a cost. Fourth, connection or loneliness: whether the employee has meaningful working relationships and feels included in day-to-day work.
Each item asks about experience, not identity, which is why this approach holds up post-rescission. You are not setting demographic targets or allocating opportunity by group. You are asking every employee the same question about how work feels, then analyzing results in aggregate by business unit, manager span, tenure and location to find where the experience breaks down. Cut by any dimension your privacy thresholds allow, and let the pattern tell you where to intervene.
Two operating rules keep this from becoming another dormant dashboard. Report the four items at the same cadence and in the same pack as engagement, so nobody can look at inclusion in isolation. And route the results to the manager level, because every one of the four items describes something a manager either does or fails to do in a given week. Fixing that is not a program redesign. It is a management practice problem, which is a far better problem to have.
