There's a fear running through every tech organization I've worked in. Someone raises their hand in a leadership meeting and says, "What if we invest in training our engineers and then they leave?"
Everyone nods. As if this is a serious risk requiring careful management.
I've heard this fear dressed up in different ways:
- "Train someone who then leaves? Money wasted."
- "They should come in ready to contribute."
- "We don't want to be a training ground for our competitors."
It's a reasonable fear on the surface. Training costs money and time. If someone leaves right after, you've lost both.
But here's the question none of those people in the meeting room ever ask: what happens if you don't train your people and they stay?
The Fear Is Backwards
The logic making "training = flight risk" feel true goes like this: skilled people have more options. Train someone, they become more skilled, they have more options, so they're more likely to leave.
It's not wrong. But it's incomplete.
The fuller picture: people who feel they're growing are happier, more engaged, and more loyal. People who feel they're stagnating look for exits.
LinkedIn's 2019 Workforce Learning Report found 94% of employees would have stayed at a previous company longer if offered more development opportunities. Not a few more months. Longer... as in, they left specifically because development wasn't there.
It's not a one-off finding. The Work Institute's Retention Report confirms lack of career development has been the number one reason employees quit for over a decade. Not pay. Not bad managers. Career development.
Let it sink in: not pay. Not bad managers. Career development, for ten years straight.
You're worried training will make them leave. The data says not training them is what's making them leave.
What Tech Companies Do (And Why It Isn't Working)
Gallup research from 2024 found less than half of US employees participated in any training for their current job last year. Any training. Not a structured programme. Not a conference. Any.
This is happening while the pace of change in software engineering is the fastest it's ever been. AI is reshuffling skills. Platforms are fragmenting. Every team I speak to is trying to do more with fewer people.
And yet: less than half of engineers got any training last year.
The most common excuse? Time. 89% of CHROs cite "time away from responsibilities" as the main obstacle to development. 41% of employees name it themselves.
We're so focused on shipping this sprint we never invest in the people who need to ship next year's. The technical debt is visible in your backlog. The people debt is invisible right up until someone hands in their notice.
This is the bug compounding silently.
The Cost You're Not Calculating
When a trained person leaves, you see the cost clearly: recruitment fees, onboarding time, lost productivity while the role sits open, ramp-up time for the replacement. You count it. It's painful and visible.
When an untrained person stays, you don't count any of those costs. But they're still there, distributed across the team in ways harder to measure:
- Slower delivery because skills aren't where they need to be
- More bugs from gaps in engineering practice
- Technical debt from decisions made without sufficient knowledge
- Drag on stronger engineers who spend time correcting or compensating
- Knowledge trapped in a team with no shared language for the problems they're solving
And then there's the cost you've missed entirely: the trained people who left because the undertrained people around them made the work frustrating.
Good engineers leave organizations where the floor is too low. They don't want to spend their days carrying colleagues who were never given a chance to grow. They don't want to clean up decisions made by people who didn't know better. They want to work somewhere the team is strong.
Who sets the floor? You do, by deciding whether to invest in people or not.
The "Training Ground" Objection
"We don't want to be a training ground for our competitors."
I've sat in rooms where this was said with genuine conviction, as if the alternative... the team staying exactly where they are, developing nothing, contributing nothing new, falling behind on every new platform and practice... was somehow preferable.
The fear: you train someone who then takes those skills to a competitor.
Here's the thing: your competitor has the same fear. So they're also not training their people. And the engineers who leave you for them will find a stagnant shop there too, and keep moving.
The organizations winning on engineering talent build a reputation as a place where you grow. They attract engineers who want to develop. They keep them longer because the growth is real. When people do eventually leave... and everyone eventually leaves... they leave as advocates, speaking well of you in the market and sending good people your way.
The "training ground" objection treats talent as zero-sum. It isn't.
What Good Training Looks Like in Tech
I'm not talking about compliance tick-box exercises. Not a mandatory security awareness module. Not a one-hour "lunch and learn" about a framework you'll use once.
The investment moving people and organizations forward looks more like:
Conference attendance with knowledge transfer. You go, you come back, you teach. Not a reward for high performers. A standard practice, built into how work gets done.
Internal tech talks. Engineers present what they're working on, what they've learned, what went wrong and why. This distributes knowledge across the team without formal curriculum or budget.
Structured pairing and mentorship. Not random. Intentional. A junior engineer paired with a senior one on a real project, with time set aside to debrief and reflect.
Learning time with teeth. A book allowance nobody uses is not a learning investment. A dedicated block each month to work on something new, with no deliverables attached, is.
Cross-team rotation. Letting engineers spend time in different parts of the system teaches them things no formal training covers. It also builds resilience when someone does leave, because knowledge isn't siloed.
None of this requires a large training budget. Most of it costs far less than a single unplanned resignation and the months needed to get a replacement up to speed.
The Choice You're Making
When you decide not to invest in your people's development, you don't avoid a risk. You trade one risk for another.
You trade "trained person might leave" for "undertrained team underperforms, and your best people leave because of it."
Gallup found having a supervisor perceived as blocking growth is the strongest predictor of employee turnover intent. Not pay. Not culture. Not workload. Whether your manager invests in your growth.
If you're leading an engineering team and you're not making real time for development... not a quarterly training day, not a Udemy subscription nobody logs into, but real investment in how your people grow... they're already looking. They're responding to recruiters. They're updating their profiles.
60% of employees report never having received any workplace training. Half of them will leave in the next year to go somewhere they believe will develop them. And you'll spend far more replacing them than it would have cost to keep them growing.
The question isn't whether training them is worth the risk.
The question is what you're building: a team growing with your organisation, or a conveyor belt sending your best people to somewhere willing to invest in what you wouldn't.
Which is it?
