Episode 140

Inclusion analytics | with Diana File

Stop counting heads. Diana File reveals how to use calendar data, email patterns, and organizational networks to measure real inclusion—and why perfect data is the enemy of progress.
 

Episode Key Takeaways

Representation metrics alone tell you almost nothing. Most organizations stop at headcount—how many women, people of color, or disabled employees work here—but that’s measuring inputs, not outcomes. The real inflection points emerge when you layer in engagement, belonging, and behavioral data to see where exclusion actually happens.
Calendar metadata exposes hidden bias at scale. By analyzing who attends key decision-making meetings, you can track gender, race, and other demographic representation over time without surveying anyone. One vendor dashboard showed male attendance dropping from ~60% to ~45% over a year while female and non-binary attendance rose—a concrete signal of progress that perception surveys alone would miss.
Diana File emphasizes that perfect data is the enemy of good action. Humans change faster than datasets, so organizations should deploy quick, iterative measurement cycles rather than spending a year perfecting baseline data. The cost of inaction—regressing on inclusion while you wait—often exceeds the cost of acting on 70–80% accurate data.
Email response times, project staffing, and PTO approval patterns reveal systemic bias in real time. These workflow metrics sit in your existing systems—Slack, email, calendar, HRIS—waiting to be analyzed. When certain demographic groups consistently get faster email replies or access to high-visibility projects, you’ve found a lever for change.
Organizational network analysis maps who actually influences decisions, not just who’s on the org chart. Tools like Polynode show collaboration patterns across silos and can compare perceived inclusion (how included people feel) against actual inclusion (who’s really in the room). The gap between those two is where unconscious bias lives.

Frequently
Asked
Questions

How do we get employees to disclose LGBTQ+, disability, and veteran status data?
Communication and trust are foundational. Most employees assume data will be misused without clear messaging on protection, storage, and usage. Run self-disclosure campaigns through ERGs and employee advocates, acknowledge past misuse if it happened, and explain what employees gain—better accommodations, relevant programming, inclusive design. Avoid third-party guessing; let employees own their identity.
Begin with engagement survey data segmented by demographic groups—race, gender, sexual orientation, disability status. Layer in turnover, representation by job level, and career development metrics. If you’re ready for passive data, add calendar inclusion (meeting attendance by demographic) and organizational network analysis. Skip the advanced stuff until you’ve mastered these three tiers.
No. Waiting for perfect data is a form of inaction that carries its own cost. Deploy initiatives quickly, measure iteratively, and refine as you learn. Technology now allows rapid data collection and analysis—get in, get out, act, and improve. Humans and organizations change faster than datasets anyway, so continuous iteration beats delayed perfection.
Calendar invitations show who attends high-stakes meetings. Email response times reveal who gets faster replies. Badge or VPN login data shows work patterns and correlates with promotion. PTO and overtime approvals expose discretionary bias. Document collaboration and chat threads show who’s included in knowledge-sharing. These metadata sources are objective, scalable, and already in your systems.
Quantify the cost of disengagement and turnover. Research shows disengaged employees are 8% more likely to leave; calculate that against your workforce size and salary costs. Map inclusion metrics to productivity, retention, and client acquisition. Show how demographic diversity in decision-making meetings correlates with innovation and market reach. Frame DEI as a talent and revenue strategy, not a compliance checkbox.