Pay Exposure

She knows she's underpaid. Her manager probably does too. The organization has the market data and has deferred the conversation because fixing it is expensive — and when she leaves, the exit interview will say something true and substantively incomplete.

Does your organization have real, current market data on whether specific roles are underpaid, and if so, when did that data last actually change a number on someone's paycheck?

Most organizations carrying this condition have the market data too, or could pull it in an afternoon. The conversation about closing the gap has come up before and gotten deferred, because fixing it costs real money across more than one role, and that's a harder number to approve than the cost of waiting. When the departures come, the exit interviews will say something about a new opportunity, a better fit, a natural next step. Technically true. Substantively incomplete.

The Gap Between Knowing and Acting

This isn't a story about an organization that doesn't realize it has a pay problem. Most organizations carrying this condition know exactly what the data says. The gap isn't information. It's the distance between having the number and being willing to act on it.

That distance gets filled with deferral, and deferral has a specific logic that makes sense in the short term: fixing pay compression or below-market roles across a team or a department is expensive, immediate, and visible on a budget line in a way that the cost of losing people to it is not. Nobody is choosing to lose good people. Each budget cycle, the organization chooses not to spend the money, and the departures that decision produces get absorbed elsewhere, recorded under different causes, never traced back to the deferred conversation that actually caused them.

Why the Exit Data Is Lying to You, Politely

It runs for years without ever showing up as what it is, for a simple reason: the people leaving over pay almost never say so directly, and the organization rarely pushes past the answer it's given.

Naming compensation as the reason for leaving carries real costs for the person leaving. It can read as ungracious, complicate a reference, or simply feel unnecessary when "better opportunity" is just as true and a great deal more comfortable to say out loud. So the exit interview records what's comfortable, the organization files it as career growth or culture fit, and the actual driver, a number that was knowingly left uncorrected, never enters any system the organization uses to understand its own attrition. Nothing here is falsified. The data is filtered through a politeness that happens to serve the organization's ability to avoid the real question.

What the Departures Are Actually Costing

The visible cost is whoever just left and whatever it takes to replace them: recruiting time, onboarding, the productivity gap while the role sits empty or undertrained. That's real, and it's also the smaller half of the cost.

The larger cost is what happens to the people who haven't left yet. Pay information moves through organizations regardless of how confidential anyone intends it to be, and the people staying generally have at least a rough sense of where they stand. Every departure that the org explains as "better opportunity" while everyone privately suspects it was about money reinforces the same lesson for whoever's still there: the gap is real, the organization knows, and waiting for it to get addressed voluntarily hasn't worked for anyone who's tried it yet. That's a recurring tax on the trust of everyone who's currently deciding whether their own market research is worth acting on, not a one-time cost.

How to Tell This Is What's Actually Happening

The organization has the market data, or could get it easily, and hasn't acted on a known gap. This isn't an organization that's confused about its competitiveness. It's one that's decided, by inaction, that the cost of fixing it isn't worth paying yet.

Departures cluster in roles or levels where the gap is most acute, and get attributed to other causes. If you map exits against the pay data and a pattern emerges that the stated reasons don't explain, that correlation is the diagnostic signal.

The conversation about fixing it has come up before and been deferred, not resolved. "We know, we're working on it, it's in next year's budget" said more than once, across more than one cycle, is its own kind of answer.

Why Waiting for a Better Moment Doesn't Work

The logic behind deferral is usually that now isn't the right time: the budget's tight this year, there's a freeze, leadership wants to wait for the next planning cycle. That logic treats the cost of inaction as zero while the conversation waits for better conditions, when the actual cost of inaction is compounding the entire time, just not on a line item anyone's tracking.

Every cycle the gap goes uncorrected, the market keeps moving, the gap doesn't hold steady, and the population of people who've quietly done their own research and reached their own conclusions keeps growing. The comfortable moment never actually arrives, and waiting for it doesn't defer the cost. It just moves the cost somewhere less visible than a budget line, showing up later as departures the organization will then have to explain to itself using reasons that aren't the real one.

What This Requires

The fix isn't complicated to describe, even though it's expensive to execute: close the gap the data already shows, on a real timeline, communicated honestly rather than implied vaguely. What's actually hard about it is the organization being willing to treat the cost as a current expense rather than a future one it keeps hoping to avoid.

Part of what makes this defensible to leadership, when the budget conversation is difficult, is connecting the actual cost of inaction, replacement recruiting, onboarding time, the compounding signal to everyone still watching, against the cost of correction, instead of comparing correction against a baseline of zero. The organization is already paying for this gap. It's just paying in a currency that doesn't show up on the line item where the fix would.

If people are leaving for reasons that sound plausible and don't quite add up, and the pay data already shows a gap that hasn't been closed, the two are very likely connected. The data is already there. Acting on it is the only remaining variable.