Library/Cases/LIB-023
LIB-023The Exit PatternCase Pattern

The First One Out the Door

When a high performer resigned, the organization called it a personal decision. It was. It was also a pattern — and by the time leadership recognized it as one, four more people had already made the same decision.

She had been there six years. She was not the loudest person in the room, but she was the one other people adjusted their positions to match after she spoke. She ran two of the organization's highest-visibility programs, knew where every important relationship lived, and had trained, informally, at least four of the people who came after her.

When she resigned, the executive director said it was a loss but that he understood. She had been offered something she couldn't turn down. Bigger role, better compensation, room to grow. These things happen.

What he did not do — what nobody did — was ask her what she had been watching for the last eighteen months. What she had tried to raise and how it had landed. What had shifted in her assessment of whether this organization was going somewhere she wanted to go.

The exit interview was thirty minutes. The person who conducted it was her direct supervisor, who was also part of what she was leaving. The notes described her as departing on good terms with positive feelings about her tenure. She was thanked for her contributions and wished well.

Three weeks later, the second resignation arrived.


The second person to leave had been there four years. He was quieter about it than she had been — less of a presence in rooms, more of a presence in the work itself. His departure was attributed to burnout. He had been carrying too much, the organization acknowledged, and hadn't said so clearly enough. They would work on workload distribution. They would be more attentive to signals.

The third departure, two months after that, was a program manager who had joined eighteen months earlier and had never fully found her footing. This one felt more explicable. Not everyone is a fit. Some people need a different environment. The organization noted it, expressed some mild concern about the cluster, and moved into a hiring cycle.

It was in the hiring cycle that the fourth departure was announced — a senior staff member who had been passed over for a role that had just opened, who said simply that the timing felt right to explore other options. Leadership accepted this explanation without examining what it meant that someone with eight years of institutional knowledge had concluded, at the moment a senior role became available, that the timing felt right to leave rather than apply.

The fifth departure came the following month. By this point the organization was alarmed, but the alarm was focused on the wrong question. Leadership was asking how to stop people from leaving. The question they needed to be asking was what all five of these people had seen.


They had all seen the same thing.

Not a single dramatic incident. Not one bad actor or one toxic moment. Something structural — a decision made two years earlier that had reorganized authority in a way that concentrated it narrowly and left a significant portion of the senior staff without meaningful input into the work they were accountable for. The decision had been presented as an efficiency measure. It had functioned, in practice, as a signal about whose judgment the organization trusted and whose it did not.

The people who left were not the people who had been elevated by the reorganization. They were the people who had watched it, updated their assessment of where the organization was going, and eventually concluded that it was not going somewhere they wanted to follow.

None of them said this in their exit interviews. The exit interview was not a safe place to say it — not because anyone had made it explicitly unsafe, but because the person conducting it was embedded in the structure they would have had to criticize, and because they had already decided to leave and saw no reason to spend their final professional capital on a conversation they didn't trust to go anywhere.

The information existed. It simply had no pathway to the people who needed it.


Eighteen months after the first departure, the organization commissioned an engagement survey. The results were concerning. Trust in leadership was low. Clarity of direction was rated poorly. A significant portion of respondents indicated they did not feel their contributions were valued at the level they warranted.

Leadership reviewed the results in a two-hour session and identified three action items. They communicated to staff that they had heard the feedback and were committed to improvement. They hired a consultant to facilitate a team-building retreat.

The retreat was held on a Thursday and Friday at a conference center forty minutes from the office. Attendance was strong. The facilitated sessions produced a shared values document and a set of communication commitments that were posted in the break room the following week. Six weeks later nobody could tell you what was on it.

The sixth departure arrived four weeks after the retreat. This one was someone who had been there nine years.


Exit Pattern does not announce itself as Exit Pattern. It announces itself as a series of individually explainable departures, each one absorbed by the organization through whatever narrative makes it most manageable. Personal opportunity. Burnout. Poor fit. Life changes. The narratives are usually partially true, which is what makes them so effective at preventing the organization from seeing what is actually happening.

What is actually happening is that a specific, unaddressed condition is being scored, independently and privately, by the people most capable of recognizing it. Those people — the ones with enough organizational literacy to identify what the condition means for the future, and enough professional options to act on that assessment — are the ones who leave first. Their departure is not random. It is the output of a rational calculation made by people who saw something clearly and concluded it was not going to change.

The organization that waits for this pattern to become undeniable before addressing it has already paid a compounding price. The talent that leaves first is the talent that was most capable of naming the problem, most likely to have attracted the people who came after them, and most irreplaceable in the specific ways that don't show up in a job description. What remains is not a representative sample of the organization. It is the people who either haven't yet reached the threshold that triggered everyone else's departure, or who have and decided to stay anyway — which is its own signal worth examining.


What it cost to wait

He had the exit interview notes from six departures. He had engagement survey data pointing directly at trust and clarity failures. He had a sequence of losses that spanned eighteen months and touched every level of his senior staff. He had the retreat attendance sheet and the values document and the communication commitments.

What he did not have — what nobody had handed him, because nobody had assembled it — was a single document that laid all six departures side by side and asked what they shared. That document would have taken an afternoon to produce. It would have been uncomfortable to read. It would have named the reorganization within the first page.

Nobody produced it. So he managed each departure as it arrived, and the organization absorbed each one, and the condition that generated all of them ran uninterrupted for eighteen months while everything else was tried.


What a different organization does with the same facts

The facts do not change. The same reorganization. The same concentration of authority. The same structural signal sent to the same people about whose judgment the organization trusts.

What changes is what happens after the first departure.

A different organization has an exit process designed to surface information rather than manage sentiment. The exit interview is not conducted by the departing employee's direct supervisor. It is conducted by someone with no stake in the answer — or better, through a structured written process that creates enough distance for honest response. The questions are not "how was your experience here" but "what did you see that you couldn't change" and "what would have made you stay" and "what should we understand about why you're leaving that we probably don't." The answers are not filed in HR. They are read by someone with pattern recognition responsibility and compared against every other exit in the preceding eighteen months, looking specifically for what they share.

A different organization has leadership that can receive the answer to those questions without immediately converting it into a narrative that protects the existing structure. The reorganization that generated the problem was a decision made by people who are still in the building. Hearing that the decision produced a departure pattern requires those people to hold two things at once: that they made the best call they could at the time, and that the call had costs they didn't anticipate and need to address now. Organizations whose leadership culture cannot hold that simultaneity will convert every exit into an individual story. The pattern will never assemble because nobody is looking at the exits together.

A different organization treats the first high-performer departure as a data point requiring investigation, not a loss requiring explanation. The investigation is not punitive or dramatic. It is a genuine attempt to understand what that person saw and whether others are seeing it too. That conversation — conducted early, before the pattern is established, when one honest exchange can still surface what six exit interviews later will not — is the intervention. Not the retreat. Not the survey. Not the communication commitments posted in the break room. The willingness to ask the hard question before the answer becomes expensive.

The window to do this is the first departure. Every organization has that window. Most organizations spend it writing a job posting.

Seeing this pattern in your organization?

The diagnostic identifies which institutional state is generating the friction — and what to do about it.

Take the Diagnostic →