Diversity & Inclusion: From Corporate Checkbox to Genuine Organizational Change

Let's Start With the Part Nobody Wants to Say Out Loud

Here's the thing about Diversity and Inclusion: it has become, in much of the corporate world, one of the most elaborately performed commitments in the history of organizational behavior. Companies run unconscious bias training. They publish diversity reports with carefully curated percentage breakdowns. They post statements on LinkedIn every time a marginalized group is in the news. They hire Chief Diversity Officers and give them impressive titles and almost no actual budget or authority.

And then, somehow, the demographics of the C-suite don't change. The promotion rates don't equalize. The attrition rates among underrepresented employees remain stubbornly, embarrassingly high.

If that pattern makes you uncomfortable, good. It should. Because the gap between what organizations say about diversity and what they actually do about it isn't a communications problem. It's a strategy problem. And strategy problems require a fundamentally different kind of solution.

The Difference Between Diversity, Inclusion, and Equity — and Why It Actually Matters

Before we go any further, let's untangle some terminology, because people use these three words interchangeably and they are not interchangeable.

Diversity is about representation — who is in the room. It is, at its most basic, a demographic fact. You either have a range of people with different backgrounds, identities, and experiences, or you don't.

Inclusion is about whether the people in the room can actually participate meaningfully. You can have a perfectly diverse organization in which every underrepresented employee feels consistently overlooked, talked over, or quietly penalized for being different. That's diversity without inclusion, and it's both morally wrong and strategically counterproductive.

Equity goes one level deeper. It's about whether the structures and systems of the organization are designed in ways that give everyone a genuine opportunity to contribute and succeed, not just the theoretical possibility. Equality says everyone gets the same ladder. Equity says not everyone starts at the same height, so some people need a taller ladder.

Why Most D&I Programs Target the Wrong Variable

Most D&I programs focus on diversity — on getting people through the door. They put enormous effort into recruitment pipelines, university partnerships, and outreach programs targeting underrepresented groups. And yes, representation matters. You cannot have inclusion without people to include.

But the data on what happens after those people walk through the door is where the strategy breaks down. Research published in the Harvard Business Review has consistently found that underrepresented employees in organizations without strong inclusion cultures experience significantly higher rates of burnout, are promoted at lower rates than their majority peers, and leave organizations at rates that ultimately negate whatever gains the recruitment programs achieved.

You are, in effect, filling a leaky bucket and congratulating yourself on the pouring.

The Psychology of Belonging — Why It's Not Soft and Why It Drives Hard Results

One of the most persistent criticisms of D&I work is that it prioritizes "feelings" over performance. This framing deserves to be pushed back on firmly, because it misunderstands what psychological safety and belonging actually do to cognitive performance.

Research by Amy Edmondson at Harvard Business School on psychological safety — the belief that one can speak up, disagree, and take risks without punishment — has shown that teams with high psychological safety significantly outperform teams with low psychological safety on virtually every measurable outcome: creativity, problem-solving, error detection, learning, and innovation.

The key insight is this: when people feel they cannot bring their full selves to work — when they are managing a performance of assimilation, code-switching, or hiding aspects of their identity — they are consuming cognitive resources that could be deployed on the actual work. Belonging isn't a soft goal. It's a performance lever.

What Code-Switching Costs an Organization

Code-switching — the practice of adjusting one's speech, behavior, and presentation to conform to majority cultural norms — is a well-documented phenomenon, particularly among employees from racial, ethnic, and socioeconomic minorities. It is tiring. It is continuous. And it extracts a cognitive and emotional tax that majority employees simply do not pay.

When you build an organizational culture that implicitly demands code-switching for professional advancement, you are not building a meritocracy. You are building a system that rewards conformity to a specific cultural norm and calling it excellence.

What Actually Works — Moving From Theater to Strategy

Let's get into specifics, because this is where the conversation usually stalls at the level of principle rather than advancing to the level of action.

Structural Audits Over Aspirational Statements

The single most impactful thing an organization can do for inclusion is to audit its own structures — not its stated values. Audit the decision-making processes: who gets to give input on major decisions, and whose input actually changes outcomes? Audit the performance management system: what behaviors get rewarded, and are those behaviors genuinely predictive of impact, or are they proxies for cultural fit? Audit the informal networks: who has access to sponsorship, mentorship, and high-visibility projects?

These structural audits are uncomfortable precisely because they reveal that many organizations' procedures — which were designed in a specific cultural moment, by a specific demographic — are not actually neutral. They carry embedded assumptions about what professionalism looks like, how leadership communicates, and what kind of ambition is appropriate.

Sponsorship Versus Mentorship

Here's a distinction that genuinely changes outcomes: mentorship gives underrepresented employees advice. Sponsorship gives them opportunity.

A mentor helps you navigate the organization. A sponsor advocates for you in rooms you're not in — puts your name forward for the stretch assignment, vouches for your readiness for promotion, uses their own credibility to open doors. Research by Sylvia Ann Hewlett found that employees with sponsors are 23 percent more likely to advance and are significantly more satisfied in their careers. Sponsorship, disproportionately, flows along demographic lines — meaning majority employees tend to sponsor employees who look like them.

Breaking this pattern requires intentionality. It requires leaders to actively sponsor employees who do not share their background, which means taking on some personal reputational risk. Organizations that understand this actively design sponsorship programs, pair senior leaders with high-potential employees from underrepresented groups, and hold those leaders accountable for their sponsors' advancement.

Data Transparency and Accountability

You cannot manage what you do not measure, and you cannot improve what you refuse to be transparent about. Companies that make genuine progress on D&I publish data that is granular: not just overall demographic percentages, but hiring rates, promotion rates, attrition rates, and pay equity analyses broken down by level, function, and demographic group. And they tie leadership compensation — bonuses, stock options, performance evaluations — to measurable progress on those metrics.

When inclusion becomes a factor in how leaders get paid, it suddenly becomes a strategic priority rather than a corporate virtue signal. Funny how that works.

The Backlash Problem — and Why It's Part of the Work

No honest article about D&I can skip this section. There is a real and growing cultural backlash against diversity initiatives, and understanding it is essential for designing programs that are durable and effective.

Some of the backlash reflects genuine bad-faith opposition rooted in demographic anxiety — the discomfort of people who benefit from existing systems with any disruption of those systems. This is worth acknowledging without capitulating to.

But some of the backlash reflects legitimate critique of specific D&I practices that have been poorly designed, poorly communicated, or that demonstrably do not work. Mandatory unconscious bias training, for instance, has mixed-to-poor evidence for effectiveness and has in some studies actually increased bias when it creates reactance — a psychological resistance to perceived coercion. Treating employees as representatives of their demographic group rather than as individuals can be its own form of othering.

The organizations that sustain D&I progress over time are those that engage with legitimate critique, iterate on evidence, and build broad ownership for inclusive culture — not just among HR and diversity teams, but across the entire leadership of the organization.

D&I Is Not an HR Project

Perhaps the most important structural shift in how organizations think about D&I is this: it is not an HR project. It never was.

HR can implement programs and measure outcomes. But the culture of inclusion is built — or destroyed — in ten thousand daily interactions: in how a manager responds when a team member challenges their idea, in who gets credit for a project in the debrief meeting, in whose name appears first on a document, in whether a leader speaks up when a colleague is talked over in a meeting.

Those interactions are leadership behaviors. And leadership behaviors are shaped by organizational culture, incentive structures, and the behavior of people at the very top. If the CEO doesn't practice inclusion daily, no number of D&I programs will compensate.

Real D&I strategy is a leadership development strategy, a culture strategy, a decision-making strategy. It requires every function and every leader to own a piece of it — not as an additional task, but as a core dimension of how they do their actual job.

That is hard. It takes longer than a workshop. It is less visible than a Pride Month post on LinkedIn. And it is the only thing that actually works.

LET'S GET CRITICAL

Alright, let's do something that the D&I industry itself is notoriously bad at: honest self-examination. The article you just read makes a strong, well-supported case for moving from performative D&I to structural, accountable D&I. Most of it is right. But let's push on the parts that deserve more scrutiny.

First, let's talk about the business case framing. The article — like most serious D&I writing — anchors its argument in organizational performance. Teams with psychological safety outperform. Diverse companies are more innovative. Inclusion drives retention. All of this is supported by real research. But here's the problem: the moment you make the business case the primary justification for inclusion and equity, you have also implicitly accepted the premise that diversity only matters if it makes the organization more productive.

That is a morally constrained starting point. Some D&I practitioners are deeply uncomfortable with the business case framing, and they have a legitimate point. What happens to the commitment to inclusion in a downturn, when the case for cost-cutting is stronger than the case for any given program? What happens when the data, in a specific organization, doesn't show a clear performance benefit? Does the organization conclude that diversity is therefore not worth pursuing? The business case is tactically useful for getting organizational buy-in. As a foundation for a values commitment, it is fragile.

Second, let's examine the concept of psychological safety more carefully. Amy Edmondson's research is cited widely and correctly. But it's worth noting that psychological safety operates very differently across cultural contexts. In organizational contexts shaped by East Asian management traditions, for instance, the relationship between hierarchy, face-saving, and what constitutes appropriate speech is substantially different from what Edmondson's framework, developed largely in Western corporate contexts, assumes. A D&I program that assumes a universal standard for what psychological safety looks like — one that implicitly centers Western, particularly American, professional norms as the baseline — may actually be exerting its own form of cultural pressure.

This doesn't invalidate psychological safety as a concept. It does suggest that organizations operating globally, or with truly diverse teams, need to think carefully about whose definition of "safety to speak up" they're centering.

Third, let's talk about structural audits and the limits of what they can find. The article advocates for auditing the structures and processes of an organization rather than just its stated values. Good advice. But structural audits have a fundamental limitation: they can only find what they're designed to find. The more insidious forms of exclusion — the pattern of being talked over, the informal social network that excludes certain people from post-meeting conversations, the way a particular manager's feedback consistently uses different language for similar-performing employees of different backgrounds — these are often invisible to a structural audit. They require ethnographic, qualitative, relational investigation that most organizations are not willing to commission because it produces findings that are uncomfortable and hard to act on quickly.

The structure can be perfectly redesigned and the culture can remain exclusionary. Uber in 2017 was a useful case study: impeccable HR processes on paper, and a culture that was by many accounts comprehensively hostile to women and minorities. The audit reveals the architecture. It doesn't tell you what's actually happening inside the building.

Fourth, the article's framing around sponsorship deserves interrogation. The research on sponsorship is compelling, and the intervention is logically sound. But sponsorship programs also carry a risk: when organizations create formal sponsorship pairings, there is a well-documented tendency for the sponsor to project their own professional path, values, and communication style onto the sponsee — in effect, sponsoring the employee's assimilation rather than their authentic advancement. If a senior leader sponsors a junior employee from a different background by helping that employee become more like the senior leader, the program may be inadvertently reinforcing the exact cultural conformity it was designed to disrupt.

Good sponsorship programs are aware of this and build in counterweights — including feedback mechanisms where sponsees can flag this dynamic. Many programs don't do this.

Fifth, and this is perhaps the most politically complicated point: the article briefly acknowledges the backlash against D&I initiatives but doesn't linger on the specific critique of diversity programs that centers their effects on non-minority employees — particularly white and male employees who experience certain D&I initiatives as a signal that their identity is the problem to be solved. This experience, regardless of intent, can generate the reactance the article mentions — but the response to it in much D&I practice is to dismiss this experience rather than engage with it. This is both strategically counterproductive and, arguably, inconsistent with the values of inclusion itself. Inclusion, if it means anything, must include everyone. An inclusive culture is not one that makes one group comfortable by transferring discomfort to another. Building inclusion requires attending to the experience of all employees, including those from majority groups who are navigating a genuine identity disruption — the recognition that their assumed neutrality was actually a form of privilege — and who need support processing that, not dismissal.

The organizations that build durable inclusive cultures tend to be ones that are honest about this complexity rather than ones that simplify it into a single narrative of who needs to change.

FANTASTIC GUEST — FREDERICK DOUGLASS

For Fantastic Guest this edition, we're bringing in someone who understood the gap between stated principle and lived reality with a precision that most modern D&I consultants could learn from. Frederick Douglass — abolitionist, orator, writer, and one of the most formidable intellectual and moral voices of the 19th century — spent his life navigating the collision between the rhetoric of equality and the structural reality of exclusion. He didn't just argue for inclusion. He lived through, and analyzed, the mechanisms by which it is denied. His perspective on the difference between tokenism and genuine transformation, between symbolic gestures and structural change, is worth quite a bit more than his era's distance might suggest.

The Interview

Danny: Frederick, welcome. I have to start by acknowledging the somewhat absurd premise here — I'm interviewing a man who was literally property under the law of his country to discuss the corporate world's diversity strategy, and yet somehow I think you might have the most useful things to say.

Frederick Douglass: The absurdity is not lost on me. Though I would observe that the distance between "we hold these truths to be self-evident" and the reality of 1845 may not be so much larger than the distance between "we are committed to creating an inclusive workplace" and the reality of most organizations in your time. The mechanisms of the gap have grown more sophisticated. The gap itself is familiar.

Danny: That's a sharp opening. Let me ask you directly: looking at what modern organizations call Diversity and Inclusion programs, what do you recognize?

Frederick Douglass: I recognize the performance of virtue in the absence of sacrifice. In my day, there were abolitionists — genuine ones, who risked their livelihoods, their social standing, sometimes their freedom — and there were people who disapproved of slavery in the abstract while taking no action that cost them anything. The latter were far more numerous. They passed resolutions at conventions. They wrote letters. They felt their disapproval very sincerely. And the institution continued unchanged for decades after their sincere disapproval was first registered. What your organizations call performative D&I I would call abstract abolitionism. The sentiment is present. The sacrifice is absent.

Danny: That's a devastating analogy. But let me push back a little — isn't there a risk that comparing corporate D&I failures to slavery cheapens the historical reality of what you experienced?

Frederick Douglass: It is a fair caution, and I hold myself accountable to it. I am not equating the experience of a minority employee being talked over in a board meeting with the experience of a person being bought and sold. The moral weight is entirely different. What I am saying is that the logic of exclusion — the mechanism by which a system simultaneously claims universal values and produces unequal outcomes — operates by similar principles at different scales. Understanding those principles in their sharpest historical form can illuminate their softer expressions. That is not diminishment. That is the proper use of history.

Danny: You wrote, famously, that power concedes nothing without a demand. How does that apply to the modern D&I conversation?

Frederick Douglass: It applies precisely and uncomfortably. What I observed in my time, and what I suspect you observe in yours, is that the people who benefit most from existing hierarchies are never the ones who volunteer to dismantle them. They may gesture toward reform. They may fund a scholarship here and a program there. But they will not redesign the systems that produce their advantage unless they are required to — whether by law, by economic pressure, by the organized resistance of those excluded, or by some combination of all three. The modern D&I literature seems to spend a great deal of time persuading leaders that inclusion is in their strategic interest. I find this exhausting. It is also correct, pragmatically. But let's not pretend that organizations are redesigning their promotion practices because they had a moral awakening. They are doing it because they are watching their competitors attract talent they cannot, because regulators are watching, and because the reputational cost of being seen as exclusionary has risen.

Danny: That's a cynical reading.

Frederick Douglass: It is a realistic one. Which is different. Cynicism gives up. Realism builds leverage.

Danny: Speaking of leverage — you were a self-educated man, someone who taught himself to read in secret, in a society where that was literally a criminal act. What does that experience teach you about the concept of meritocracy, which comes up constantly in conversations about D&I?

Frederick Douglass: It teaches me that meritocracy is a beautiful idea that most societies apply only after the inputs have been made unequal. I had to acquire the same literacy that every white child in my city received as a matter of routine — but I had to do it clandestinely, at risk of severe punishment, using discarded newspapers and the pages of a spelling book. When I had done this, the defenders of the existing order did not say, "Ah, here is a man of talent who should be recognized." They said, "Here is property that can now read, which is a danger and must be contained." Meritocracy, as typically deployed in arguments against D&I, assumes that the measurement of merit is itself neutral. My experience suggests it is not. Who designed the test? For whom was the test designed? What counts as qualification, and who decided that?

Danny: The article we're discussing talks about the concept of sponsorship — senior leaders using their credibility to advocate for people who don't look like them. You had allies of exactly this kind. What made the effective ones different from the performative ones?

Frederick Douglass: The ones who made a material difference put something at risk. William Lloyd Garrison published my name and my story at a time when doing so had real consequences — for him, not just for me. Gerrit Smith gave me land and his personal advocacy when personal advocacy was uncomfortable. The ones who were merely supportive attended lectures and applauded. Applause costs nothing. I had great appreciation for applause and a more particular appreciation for people who put something of substance on the line. Your corporate sponsors who attend the right training sessions and voice their support in the right meetings — I would want to know what they have personally risked on behalf of the people they claim to be sponsoring. If the answer is nothing, I would not call it sponsorship. I would call it sympathy at a comfortable distance.

Danny: That's a high standard.

Frederick Douglass: The standard should be appropriate to the importance of the outcome. If the outcome is merely that an organization looks better in its annual report, perhaps a low standard is fine. If the outcome is actually changing who gets opportunity and who does not, the standard should be proportional.

Danny: Let me ask you something more personal. You spent your life navigating institutions — the abolitionist movement, journalism, politics, diplomacy — that were built by people who were not like you and that were in many ways not designed for you. What did that cost you, and what does that cost look like in a modern organizational context?

Frederick Douglass: It cost a continuous expenditure of energy that my colleagues did not pay. Every room I entered required a calculation — how much of myself to present, which parts of my identity to foreground, which to manage carefully. I was always representing more than myself. Every failure I had was evidence about my kind. Every success I had was an exception that proved nothing general. This is not a historical curiosity. When I listen to what you describe — the concept of code-switching, the cognitive tax of assimilation, the way underrepresented employees carry the weight of representing their entire group — I recognize it immediately. It is the same tax. It has been renamed and documented with data. The data is valuable. But the experience it documents is very old.

Danny: Final question. What would you say to a Chief Diversity Officer sitting in a large corporation today, genuinely committed to the work but navigating a system that resists change?

Frederick Douglass: I would say what I have said on many occasions in many forms: do not wait for the system to invite its own transformation. The invitation will never come. Identify where power actually lies, not where the organizational chart says it lies. Understand what the system's actual incentives are, not what its stated values are. Build alliances with people who have real authority and real skin in the game. Measure what matters and refuse to celebrate what doesn't. And do not confuse visibility with progress. Visibility is what happens when the right photograph appears in the right press release. Progress is what happens when the demographic composition of senior leadership changes, when the pay gap closes, when the attrition rate for underrepresented employees drops. Visibility is cheap. Progress is expensive and therefore real.

And — this is important — maintain your integrity about the difference between the two. The organizations that most need diversity and inclusion work are often the ones most skilled at the performance of it. Your job is to know the difference and to say so, clearly and at some personal cost, when the performance is being mistaken for the work.

Danny: Frederick Douglass, I could do this for another three hours, which I suspect you would find both flattering and exhausting.

Frederick Douglass: Three hours is nothing. I once gave a speech that lasted five. And nobody left.

Danny: I believe it. Thank you.

EDUSTORY — THE RIGHT KIND OF STORY

The Right Kind of Story

The email arrived at 9:47 AM with the subject line: Keynote Opportunity — DEI Summit, March.

Priya read it twice, then a third time, then closed her laptop.

It was from Marcus Hollenbeck, Chief People Officer at Trellis, the fintech company where she'd been Head of Talent Strategy for fourteen months. The email said she had been "selected" to deliver the opening keynote at Trellis's upcoming Diversity, Equity, and Inclusion Summit, a half-day event for employees, partners, and invited press. It said her "authentic voice and lived experience would add tremendous value to the day." It said the theme of her talk should be "the journey" — and that this was a tremendous opportunity for visibility.

She opened it again.

Then she opened a new message to her colleague Dara, who sat three desks away and who Priya had once described, accurately, as "the only person in this company who tells me the truth."

She typed: Did you get the keynote email?

Dara's reply arrived in forty seconds: No. Did you?

Priya: Yes.

Dara: Of course you did.

A pause.

Dara: Are you going to do it?

Priya stared at the question for a moment, then pulled on her headphones and got back to work.

---

They had lunch in the small kitchen on the fourth floor, which smelled of someone's leftover curry and which everyone at Trellis treated as neutral territory — the one space where hierarchy was acknowledged to be temporarily suspended.

"Tell me what's actually bothering you about it," Dara said. She was unwrapping a sandwich with the calm efficiency of someone who ate at her desk most days and considered lunch a logistical event.

"They want me to talk about my journey."

"And?"

"My journey. As if the most interesting thing about me professionally is the series of obstacles I had to navigate because of who I am. As if the relevant contribution I make to this company is being a South Asian woman willing to describe the experience of being a South Asian woman in a corporate environment."

"That's not nothing," Dara said carefully. "That story has value."

"It does. For certain contexts. But I've been here fourteen months and I've restructured the entire mid-level hiring pipeline and cut time-to-hire by thirty percent and I've never once been asked to give a keynote about that." Priya paused. "Marcus has never asked me to give a keynote about anything. The DEI Summit comes up and suddenly I'm the face of visibility."

Dara ate her sandwich.

"You think it's tokenism," she said.

"I think it might be well-intentioned tokenism, which is the kind that's hardest to push back on without sounding ungrateful."

---

The meeting with Marcus was at two, in the glass-walled conference room that everyone called the fishbowl. Marcus Hollenbeck was fifty-three, built like a former athlete who had made peace with the former part, and had a way of listening that looked very attentive and occasionally was.

He had the keynote email pulled up on his iPad.

"I wanted to check in before you responded," he said, which was his way of saying he'd noticed she hadn't responded. "I think this is a real chance to amplify your voice."

"I appreciate that," Priya said. "Can I ask — what specifically were you imagining I'd talk about?"

"Well, your experience. Coming up in the industry, navigating — you know, the challenges, the things you've had to work through."

"The challenges of being a woman of color in finance."

"Exactly." He said it warmly, as if she'd identified the obvious right answer. "Our employees would really benefit from hearing that. And with the press presence, it's good for the company's visibility on these issues."

Priya looked at the fishbowl glass for a moment. Outside, two of the engineering managers were in an animated conversation that involved a lot of whiteboard gesturing.

"Marcus, can I share something honestly?"

"Of course."

"When you say you want my voice for this event — whose benefit are you thinking of? Because the way it's framed, I'm being asked to perform my identity for an audience that includes press. I'm being asked to package my experiences with discrimination into a keynote that helps Trellis look like a company that values inclusion. And I'm wondering whether that's about my development or whether it's about the company's positioning."

The silence that followed was approximately four seconds long, which in a professional conversation is a significant duration.

"That's a fair question," Marcus said finally. "And I want to think about it seriously." He set the iPad down. "What would you want instead?"

---

What she wanted, it turned out, took about twenty minutes to explain and required two more meetings — one with Marcus alone, one with Marcus and the CEO, a meticulous man named David Cheng who had the quality of truly listening that Marcus occasionally approximated.

What she wanted was to talk about the structural changes she had actually made.

She wanted to present data: the pipeline numbers, the demographic breakdown of hires before and after the process changes, the retention delta, the promotion rates by level and demographic, the pay equity audit results she had commissioned and which were, she noted, sitting in a folder on the shared drive that approximately six people had opened.

She wanted the keynote to be about what organizational change looked like when it was operational rather than aspirational. About the three promotion criteria that had been quietly rewritten because they were proxies for cultural fit rather than performance. About the sponsorship pilot she was running with twelve senior leaders and the early indicators she was seeing. About the data that was uncomfortable and the data that was encouraging and the methodology for telling the difference.

"That's more of a strategy presentation than a keynote," Marcus said, in the second meeting.

"Yes," Priya agreed.

"The DEI Summit audience — it's not all senior leadership. There'll be junior employees, interns."

"Junior employees and interns can understand strategy. We consistently underestimate people when we decide they need inspiration rather than information."

David Cheng, who had been quiet for most of this meeting, said: "I'd like to hear the strategy presentation."

Marcus looked at him.

"I've read the pipeline numbers," David said. "I haven't heard them explained in a room out loud. I think I should." He looked at Priya. "Would you be willing to build it as a keynote? I mean the actual data, the actual argument. Make it as accessible as you can, but don't soften what's uncomfortable."

Priya considered this for a moment.

"Yes," she said. "With one condition."

"What's that?"

"The pay equity audit results go in the slide deck. Publicly. Not the summary. The actual numbers."

David was quiet.

"Some of those numbers aren't flattering," Marcus said.

"That's what makes them credible," Priya said. "If we publish only the good data, nobody believes any of it. If we publish what's actually true, including the gaps, people understand we're serious."

---

The keynote ran thirty-one minutes, which was four minutes longer than the slot. Nobody left.

Priya had put the pay equity data on slide seven. Not in the summary format. The actual distribution. The chart was clear and the gaps were visible and there was a moment when the room went quiet in a way that a room full of people working hard to look professionally neutral goes quiet when they are collectively processing something real.

She didn't perform anything. She explained what had been broken, what she had done about it, what the current state was, and what the organization still needed to do. She used the word "inadequate" twice — once about the previous promotion process, once about the current sponsorship ratio at VP level. She put both on slides.

In the Q&A, a junior developer named Kofi, who had been at the company for eight months and who had never spoken in any all-hands event, raised his hand and asked whether the data on promotion rates was going to be published internally on an ongoing basis.

Priya said she was recommending it but it hadn't been decided yet.

Kofi said he thought it should be.

From the second row, David Cheng said: "Agreed."

After the session, in the corridor outside the main hall, Dara found Priya and stood beside her for a moment, watching the crowd thin out.

"That was the right kind of story," Dara said.

"What do you mean?"

"The kind that's actually about what happened. Not about how it felt to be you. About what was wrong, and what got fixed, and what's still broken." She paused. "That's harder to give."

"Yes," Priya said.

"Also harder to use as decoration."

Priya smiled, which was not quite the same as laughing.

They walked back toward the elevators in companionable silence, which is a kind of conversation that takes years of trust to build and which, Priya thought, was also not in any presentation — not the structures you need, not the data you need, not even the courage you need — but which was, nevertheless, not nothing.

Author's Commentary — Notes on "The Right Kind of Story"

Let me start with the title, because it does more work than it might appear to. "The Right Kind of Story" operates on at least three levels simultaneously: it refers to the narrative Priya is asked to deliver (the inspirational personal journey story), the narrative she pushes back against, and the kind of story she actually tells — the operational, data-driven, uncomfortable one. The title also functions as a gentle piece of criticism of a specific pattern in D&I work: the tendency to reach for personal testimony as a substitute for structural accountability. Stories of hardship are moving and important. They are also, sometimes, more comfortable for organizations to engage with than the data about their promotion rates. The story as a whole is, in a way, about the difference between those two things.

Priya is a character I was very deliberate about. She is not a victim. She is not a hero in the conventional sense. She is a professional who is very good at her job and who is navigating a specific kind of institutional pressure: the pressure to be useful to an organization's image rather than to its actual functioning. The tension in the story is not dramatic in the conventional sense — nobody is fired, nobody has a screaming argument, nobody storms out of a room. The conflict is entirely interior and relational, and it plays out through small, precise negotiations about what a keynote should contain.

I made Priya resist performing her identity not because I think personal testimony is without value — it has enormous value — but because the specific use of it in the email she receives (selected for her authentic voice and lived experience; the theme should be "the journey"; good for the company's visibility) contains within it every tell of tokenistic D&I. She is being asked to serve as a vehicle for someone else's narrative about inclusion rather than being invited to bring her actual professional expertise to bear on the actual problem. That distinction is what the story turns on.

Marcus is the character I was most careful with, because the obvious thing would be to make him a villain — cynical, self-serving, deliberately using Priya. And that's too easy, and also not really what most exclusion looks like. Marcus is well-intentioned. He genuinely believes he is offering Priya an opportunity. He is also, genuinely, thinking about what is good for Trellis's positioning at the DEI Summit. Both things are true simultaneously, and it is the combination of them, the unreflective collapsing of "good for Priya" and "good for how we look," that is the problem. The moment when he falls silent for four seconds after her question is the moment his assumptions become visible to him. Whether he would have changed course without David Cheng's intervention is left open.

David Cheng I put in the story specifically because I wanted to show what a leader who actually uses their authority for inclusion looks like. He doesn't do anything dramatic. He says he wants to hear the strategy presentation. He agrees publicly that the promotion data should be published internally. These are small-scale uses of authority. They change what happens. That is, in my reading of the D&I literature, exactly how sponsorship and advocacy work in practice: not through grand gestures, but through specific moments of using credibility and authority to shift what is possible for someone else.

Dara is the relationship in the story that I find the most quietly important. She is Priya's truth-teller, her professional peer with different vantage, and the character who names the story's central argument in the final exchange: "The kind that's actually about what happened. Not about how it felt to be you. About what was wrong, and what got fixed, and what's still broken." I didn't want this to come from Priya herself — it's more honest coming from someone observing Priya from the outside. And the line "Also harder to use as decoration" is the story's thesis statement, delivered as casually as possible.

The moment I'm most attached to is Kofi, the junior developer, raising his hand to ask whether the promotion rate data will be published. It's a small moment. But it does something important: it shows that the transparency Priya is advocating for isn't just about leadership culture. It's about what junior employees can do with information. Kofi, who has never spoken at an all-hands event, asks a pointed, policy-level question because Priya has given him the information to ask it. Inclusion, when it functions, looks like this: people who previously had no basis for constructive engagement now have one.

The story ends in a hallway, in quiet, in a friendship. No triumph. No resolution of everything that still needs to change. The pay equity data is now public, the promotion data will presumably be published, the work is ongoing and difficult. Priya and Dara are walking back toward the elevators. That's it. I wanted the ending to feel exactly as small and as significant as it actually is — which is to say, a few degrees of shift in one organization on one afternoon, meaningful to the people in it and not, by itself, a revolution. Most of D&I looks like this. The work is in the accumulation.

LET'S DISCUSS

You've read the article, engaged with the critical section, listened to Frederick Douglass push back on abstract abolitionism, and followed Priya through the politics of a keynote invitation. That's a lot of thinking sitting there waiting to be activated. And here's the honest truth: the knowledge sticks differently when you say it out loud, argue it with someone, and hear your own assumptions get challenged. So let's do that.

Question 1

The article argues that most D&I programs focus on diversity — getting people through the door — while neglecting inclusion and equity. But some critics argue the opposite: that organizations spend too much time on internal cultural work while underinvesting in the structural economic inequalities that produce the talent pipeline problem in the first place. Which level of the problem should organizations prioritize, and what does it mean to "solve" something at one level while leaving the other untouched? You can anchor this in the Priya story, in the Frederick Douglass interview, or in organizations you know personally.

Question 2

Frederick Douglass says power concedes nothing without a demand, and he's skeptical about whether organizations change due to moral conviction or because external pressures make the cost of not changing higher than the cost of changing. Think about the D&I progress you've seen, in organizations you know or in society generally. What actually moved the needle? Was it values-led change, external pressure, legal mandate, economic incentive, or something else? And does the reason for the change matter if the outcome is the same?

Question 3

Priya pushes back on being asked to perform her identity for the organization's visibility. But the story also shows that her personal credibility — partly rooted in who she is — is part of what makes her keynote effective. Is there a meaningful line between using your identity as a point of authentic connection with an audience and being instrumentalized by an organization for its own positioning? Where is that line, and who gets to draw it?

Question 4

The critical section raises the concern that D&I programs, if designed only around the experiences of underrepresented groups, can alienate majority employees and generate backlash. Some D&I practitioners would argue that centering the comfort of majority employees in an inclusion conversation is itself a form of centering the wrong thing. Others would argue that inclusion that doesn't include everyone isn't inclusion. Think through this tension honestly. What should organizations do, and what does an inclusive culture actually look like for all employees — including those from majority groups who are being asked to change?

Question 5

The article argues that D&I is not an HR project but a leadership development and culture strategy that should be embedded in every function and every leader's daily work. But this raises a practical question: if everyone owns it, does anyone actually own it? What are the specific accountability structures that make diffused ownership productive rather than diffused responsibility with nobody answerable for outcomes? Think about examples from your own experience — in school, at work, in community organizations — where distributed responsibility actually worked, and what made it work.

WHAT NOW? — FRAMEWORK & 7-DAY ACTION PLAN

The Framework

Hold two truths simultaneously as you read this. First: Diversity, Inclusion, and Equity work is genuinely important — for organizational performance, for moral integrity, and for creating the conditions under which the widest range of human capability can contribute. Second: a significant proportion of current D&I practice is ineffective, sometimes counterproductive, and occasionally serves primarily as organizational reputation management rather than genuine systemic change.

The balanced framework for anyone engaging with D&I — whether as a practitioner, a leader, an employee, or a student of the subject — rests on five principles.

One: distinguish representation from inclusion. Diversity metrics (who's in the room) are visible and easy to report. Inclusion metrics (are those people able to contribute meaningfully, are they advancing at equitable rates, are they staying) are harder to measure and more important to track. Prioritize the harder measurements.

Two: follow the incentives. What gets measured gets managed. What gets tied to compensation gets prioritized. Structural change in organizations follows accountability, not values statements. If D&I outcomes are not tied to how leaders are evaluated and compensated, they will remain a secondary priority.

Three: engage with complexity rather than flattening it. The D&I conversation is genuinely complex — it involves competing interests, contested evidence, legitimate disagreement about tactics, and real tensions between different groups' needs. Organizations and individuals who simplify it into a single narrative (all D&I is good versus all D&I is ideologically captured) do damage. The honest, productive position is harder and more useful.

Four: evaluate evidence. Which specific D&I interventions have solid evidence behind them? (Structured interviews, blind resume review, sponsorship programs with accountability.) Which don't? (Many forms of mandatory unconscious bias training, diversity statements without behavioral follow-through.) Use the first and redesign or eliminate the second.

Five: build for the long term, not for the announcement. The most durable D&I progress happens slowly, structurally, and without press releases. It looks like a promotion process redesigned, a pay gap closed, a sponsorship program running in its third year, a senior leadership team that reflects the organization's talent pool. These are less photogenic than a keynote and more real.

7-Day Action Plan

Day 1 — Audit your own language. For one day, notice how often you use the words diversity, inclusion, and equity — and check whether you're using them interchangeably or with actual precision. Note the difference when someone else uses them.

Day 2 — Find the data. If you work in or study an organization, find its published diversity data. If it doesn't publish it, that is itself a data point. If it does, look not just at the headline numbers but at representation by level, function, and pay band.

Day 3 — Read one counterargument. Find a serious, good-faith critique of a specific D&I intervention — mandatory bias training, diversity hiring targets, whatever you're most familiar with. Engage with it seriously before deciding whether it's persuasive.

Day 4 — Map the informal network. In any organization or community you belong to, think about who has access to informal information, mentorship, and opportunity. Is it evenly distributed? What are the patterns?

Day 5 — Practice precision in a conversation. In one conversation about D&I, introduce the distinction between diversity and inclusion, or between proximate and structural causes of inequity. Precise language is a contribution in itself.

Day 6 — Identify one structural change. Identify one process, policy, or practice in an organization you belong to that may produce unequal outcomes not because of intent but because of design. You don't need to fix it today. You need to see it.

Day 7 — Consider your own position in the system. Not with guilt, not with performance, but with honest curiosity: in what contexts do you benefit from existing structures, and in what contexts does the design of the environment work against you? Both are true for almost everyone, to different degrees. Starting from this honestly is where real engagement begins.