She joined in September. Fourteen years of experience. A graduate degree from a school the hiring committee mentioned twice during the offer call. Her hiring was announced in the all-hands. The CHRO used the word "thrilled." The slide deck for the board showed three new senior hires under the heading "Building Toward a More Inclusive Leadership Team." Her photograph was on that slide.
By March, she had been excluded from six consecutive strategy sessions. Not intentionally. Nobody sent a calendar invite that said "senior leaders minus her." The exclusions were architectural. The sessions were called by the SVP who scheduled them in a Slack channel she had not been added to. The pre-read documents circulated on a shared drive she had view-only access to, and the link was never sent to her directly. The decisions that shaped her function's priorities for the next two quarters were made in rooms she was not told about. She found out through a peer who thought she already knew.
The Announcement Was the Program.
This is the architecture most organizations build for diversity: a rigorous hiring process, a visible announcement, and then nothing. The rigor ends at the offer letter. What comes after is the existing system, unchanged, populated by one new person who was promised something the system was never redesigned to deliver.
Organizations that are serious about this spend months on sourcing, panel composition, structured interview frameworks, and bias mitigation in evaluation. These are real improvements. They solve the access problem. What they do not solve, and what nobody seems to want to name directly, is the influence problem. Getting the hire in the door is not the same as getting the hire into the actual decision-making infrastructure of the organization. Those are two entirely different challenges. Most organizations have a program for the first one. Almost none have a program for the second.
The influence infrastructure of a large organization is invisible by design. It is not in the org chart. It is in the Slack channels that were created three years ago when the current team was smaller and newer members were never added. It is in the "quick sync" that five people have every Tuesday at 7:45 AM because one of them starts at 8:00 and the others adjusted their schedules to match. It is in the shared drives where the real working documents live, not the sanitized versions that get distributed in formal meetings. It is in the relationships where somebody says "I'll run this by [name] before the meeting" and the name they say is never yours.
Representation Is Not the Same as Access.
This distinction matters more than most organizations are willing to say out loud. Representation means someone who looks like, sounds like, or shares the background of an underrepresented group now has a seat in the formal hierarchy. Access means that seat comes with the information, relationships, and informal channels that make the formal seat meaningful. You can have full representation and zero access. It happens constantly. It is happening right now in organizations that have diversity hiring metrics they are proud of.
The person on the slide is not in the room. Not because anyone decided to exclude her. Because the room predates her, and the habits that determine who is in it were formed before she arrived, and nobody thought to audit those habits when she joined. The Slack channel is old. The Tuesday sync is old. The shared drive permissions were set two years ago. The relationship where someone says "I'll run it by [name]" is years older than her tenure. None of these things were built to exclude her. All of them function to exclude her. The outcome and the intent have no relationship to each other, and organizations consistently use the absence of bad intent as evidence that the problem does not exist.
The org chart gives you the title. The informal architecture decides whether the title means anything.
What the Exit Data Actually Says.
Senior diverse hires leave at a measurably higher rate than their majority-group peers at the same level. This is well-documented and consistently under-discussed. When exit interview data is analyzed for this cohort, the most common stated reason is not workload, not compensation, and not the work itself. It is some version of: "I was not able to have the impact I came here to have." Which sounds like a personal frustration. Which is, in fact, a systems diagnosis.
Impact requires access. Access requires being in the rooms where the real work is done. The real work is done in informal channels, pre-meeting conversations, and the working relationships that were built before the diversity hire arrived. When you strip away the formal structure, what you find is a network of influence that was not designed with her in mind and was not redesigned when she joined. She was given the title. She was not given the network. She was given the job description. She was not given the actual operating system.
The organization is then surprised. The departure goes into the attrition data. Someone observes that diverse senior hires have shorter tenure. Someone else says the pipeline problem is actually the real issue, and we should focus on hiring more people earlier so the senior roles fill naturally over time. The structural failure that caused the departure gets reclassified as a sourcing problem, and the cycle begins again.
What Rebuilding Actually Requires.
An organization that is serious about this does something most are not willing to do: it audits its informal architecture the same way it audits its formal one. Who is in which Slack channel and why. Which recurring meetings have invite lists that have never been updated. Which shared drives have access permissions that reflect the team composition of 2021. Which relationships carry informal decision-making authority, and whether those relationships extend to every senior leader or only to the ones who were already embedded when the current norms were set.
This audit is uncomfortable because it surfaces the gap between the organization's stated values and its operational reality. Most organizations prefer to manage that gap by adding more programs rather than examining the infrastructure. A mentorship pairing. A sponsor assignment. An ERG with an executive champion. These are not useless. They are also not the same as changing the architecture that decides who is in the room. A sponsor who does not have the cultural standing to say "she should be in this meeting" is a sponsor who costs the organization nothing to provide and delivers nothing meaningful in return.
The organizations that close this gap do not start with programs. They start with questions. Who is making decisions that affect this person's function, and is she in the room when those decisions are made? If not, why not, and what specifically would change to fix that? Not which program would address it. Which structural decision. Which calendar. Which channel. Which relationship. Specificity is the only honest response to a structural problem. Everything else is theater that costs less than the problem it is pretending to solve.
SSUNDAR works with organizations that have stopped pretending the hire is the solution. The work is a diagnostic of the influence architecture: who has access to what, where informal authority actually sits, and what the operating system looks like for leaders who joined after the network was formed. The findings are rarely comfortable. They are always more actionable than another inclusion initiative.
The Honest Version of the Slide.
If the board presentation were honest, the slide would not say "Building Toward a More Inclusive Leadership Team." It would say "We hired three people. We have not yet determined whether our informal decision-making infrastructure will include them. We will report back in eighteen months with attrition data that will tell us whether the answer was yes or no."
That slide will never exist. Which is precisely why the problem keeps existing instead.
The diversity hire on the board slide left in April. The photograph stayed on the slide until the next deck was built. Nobody updated it for three months. The CHRO noticed when a board member asked about her at the quarterly review. The answer was that it had not worked out. The real answer was that the organization had built a door and forgotten to rebuild the hallway.
Hiring for inclusion is the beginning of the work. The organizations that treat it as the end are not building inclusive leadership teams. They are building inclusive org charts. The difference shows up in who is actually in the room when the decisions get made. Always has. Always will.