Quitting and Development

I’ve been thinking a lot about exit interviews lately. Not the dramatic ones. The polite ones.

The ones where a thoughtful, capable employee resigns, thanks everyone for the opportunity, and checks the box that says “lack of development opportunities.”

That phrase shows up so often it almost feels procedural. And every time it does, some version of the same question finds its way to Learning and Development.

“What are we doing about this?”

On the surface, it’s a fair question. If people are leaving because they aren’t developing, the function responsible for development should be involved. But the longer I sit with it, the more I’m convinced we’re collapsing three different ideas into one convenient word, and then holding the wrong system accountable for the result.

Training is not development. Development is not opportunity. And quitting rarely hinges on the first one.

Let’s start with what the research actually says, because this isn’t just philosophical hair-splitting.

Gallup has been measuring employee engagement for decades, and one of the most predictive items in their instrument is some version of “At work, I have opportunities to learn and grow.” That item correlates strongly with engagement and retention. When employees agree with it, they are far more likely to stay. When they don’t, voluntary turnover risk rises. That sounds like a training problem until you look more closely at what drives agreement. Gallup’s analysis consistently links that item to manager quality, meaningful work, increasing responsibility, and visible paths forward. It is not strongly tied to hours spent in formal training. Employees interpret “learn and grow” as forward motion, not course completion.

LinkedIn’s Workforce Learning Reports have shown a similar pattern from a different angle. Organizations that enable internal mobility retain employees longer. Employees who make internal moves within their first few years are significantly more likely to remain with the company than those who stay static. Movement, not modules, predicts retention. The signal employees respond to is whether the organization actually creates and fills roles internally, not whether it offers more content.

Academic research on career plateaus reinforces the same point. When employees perceive themselves as structurally or hierarchically stuck, turnover intent increases, even in organizations that provide training access. The plateau effect is about blocked advancement or stagnant scope. You can train someone endlessly, but if they believe their trajectory is capped, development feels cosmetic.

Psychological contract research adds another layer. When employees believe there is an implicit promise of growth and that promise is not fulfilled, they experience that as a breach. Breaches predict withdrawal behaviors and exit. And again, what constitutes “growth” in those studies is rarely defined as instructional access. It is defined as progression, fairness, sponsorship, and credible opportunity.

So when someone writes “lack of development opportunities” on an exit form, it is worth asking what they actually mean. In my experience, they are not saying, “I needed two more workshops.” They are saying, “I don’t see a believable future here.”

They may mean the roles above them are locked in place. They may mean the organization hires externally for the jobs they aspire to. They may mean their manager is not advocating for them. They may mean the company is flat, stagnant, or politically gated. They may simply mean that the opportunity they want does not and will not exist inside the current structure.

That is not a curriculum issue.

And this is where L&D can get trapped.

Executives see exit data referencing development and understandably turn to the development function. L&D responds in good faith. New leadership programs are launched. Career workshops are designed. Mentoring platforms are expanded. Learning pathways are polished. Communications improve.

Energy is spent. Budgets are justified. Metrics are tracked.

Meanwhile, the constraint may be structural. Headcount growth may be limited. Succession planning may be informal or inconsistent. Internal mobility may be opaque. Managers may be rewarded for retaining top performers rather than exporting them to other teams. The organization may simply not be creating enough new roles to absorb the capability it is building.

In that scenario, L&D is being asked to build readiness for seats that do not exist.

Traditionally, L&D does not control opportunity. Workforce planning does. Succession strategy does. Organizational design does. Executive growth decisions do. We can build capability. We cannot manufacture upward mobility in a static system.

But there is an important exception, and it matters.

In mature organizations, development is not isolated from opportunity. Strategy, workforce planning, succession, and capability building are tightly integrated. Leaders define where the business is going. Workforce planning anticipates what roles will be needed. Succession identifies likely vacancies and future talent requirements. L&D builds against those needs before they become urgent. Internal mobility is transparent and real. Development conversations are explicitly tied to forward-looking roles that are expected to exist.

In that system, development and opportunity are intentionally coupled.

In less mature systems, they drift apart. Strategy happens in one room. Succession planning happens sporadically in another. L&D builds programs based on survey data and industry trends. Employees attend cohorts and complete certifications. Then they look up and realize nothing structurally changed.

That is where quitting and development intersect.

Development without opportunity breeds cynicism. Opportunity without development breeds risk. Maturity is when the two are architected together.

This is not a defensive argument on behalf of L&D. It is a call for alignment. If executives are asking, “What are you doing about people leaving for lack of development?” the more useful question might be, “Are readiness and opportunity designed together in this organization?”

Are we clear on what roles will exist in three years? Are we tracking internal fill rates? Are we promoting from within at meaningful levels? Are managers incentivized to sponsor talent? Are we overbuilding bench for seats that are unlikely to open? Are we underbuilding for seats we know will?

If we do not ask those questions, we will keep responding to a structural signal with another program and wondering why attrition persists.

Employees do not stay because of training volume. The research is fairly consistent on that. They stay because they see motion. They see growth. They see a credible path. They believe the organization will create space for them if they do the work to be ready.

Quitting, in many cases, is not a rejection of development. It is a rational response to stalled trajectory.

If we are serious about transformation, it is not about adding more learning. It is about tighter coupling between strategy, succession, workforce planning, and capability building. It is about having the maturity to distinguish between skill gaps and opportunity gaps, and the courage to address the right one.

Until then, “lack of development” will continue to show up on exit forms. And L&D will continue to be asked to solve a problem it can influence, but does not fully control.