The Exit Interview That Told the Founder Nothing New

The engineer had been there since year one. He had built the payments system, mentored half the team, and never once, in four years, missed a deadline he had committed to. His resignation letter was two sentences long and gave no reason.

The founder asked HR to run the exit interview himself instead of delegating it, because he genuinely wanted to understand what had gone wrong. He expected to learn something new.

He read the transcript twice. Nothing in it was new. The engineer described feeling unheard in architecture reviews, described the founder's habit of interrupting with a counter-solution before anyone finished a sentence, described a specific meeting eleven months earlier where he had raised the exact same concern.

The founder remembered that meeting. He had thought it went fine.

What "fine" had actually meant

In the meeting eleven months earlier, the engineer had raised a concern about the founder's habit of cutting off technical discussions with his own opinion before the team had finished reasoning through the problem. The founder had listened, said "noted," and moved the meeting along.

He had genuinely believed the issue was resolved because nobody raised it again. What had actually happened was that the engineer, and the two colleagues sitting near him, had each individually concluded that raising it again would not change anything. The behavior did not stop. The complaints about it did.

This is a pattern worth naming precisely, because it is easy for a leader to mistake for progress. A concern that stops being voiced has not necessarily been resolved. It has often simply been priced by the room's nervous system. The team ran a private calculation about the cost of raising it a second time, weighed against the likelihood of it changing anything, and the number came back negative for every one of them.

How much is one unresolved conflict really costing your company?

What the founder found when he asked further

He asked HR whether other engineers had said anything similar in past interviews. She pulled two more transcripts he had not personally read, both a year old, both describing the same interrupting pattern in almost identical language.

Three people, independently, over two years, had described the exact same reflex, and he had heard about it only once it was too late to act on it in each case. Nobody had been hiding it from him. He simply had not been the one reading it the first two times.

He asked his COO to sit in on his next three architecture reviews and flag, in real time, every instance where he cut off a technical discussion with his own answer before the team finished. She flagged eleven instances in three meetings. He had estimated he would hear it flagged twice.

Doug Noll's new book Empathy Leadership: The Powerful Skill That Drives Winning Results lays out why the same complaint often surfaces three times before a leader finally hears it. See it here.

What changed after the count

Seeing the number eleven did something the exit interview alone had not. It moved the pattern from a story he could rationalize into a count he could not argue with.

He started pausing before offering his own solution in every technical review, using the count as his own internal check. Six months later, his COO ran the same count again. It had dropped to two. The next exit interview from that team read differently, and it arrived a full year later than the one before it.

‍