
Employee Development Is a Leadership Responsibility, Not an HR Program
Nearly 70% of American employees aren’t being used to their full potential.
That number comes from a recent Coaching at Work report, and it stopped me. Not because it was surprising, but because of what it actually means. Seven out of ten people showing up to work every day with skills, ideas, and capacity that nobody is asking them to use.
This isn’t a workforce problem. It’s a leadership problem.
Over the past few weeks, five different publications landed on the same theme from different angles: organizations that underinvest in developing their people are losing them. The talent drain isn’t mysterious. The people leaving aren’t ungrateful. They’re underleveraged. And when people stop growing somewhere, they start growing somewhere else.
What I’ve noticed across my work with leaders is a consistent blind spot. They track performance metrics, engagement scores, and retention rates. They rarely ask the question that connects all three: Am I actually developing the people I lead?
Key Takeaways
- Nearly 70% of US employees report being underutilized at work, and the root cause traces back to leadership practices, not HR policies
- Organizations that default to hiring for new capabilities instead of developing existing talent create a costly cycle of turnover and lost institutional knowledge
- Mentoring isn’t an add-on to leadership. It’s one of the most direct ways leaders influence retention
- Balancing short-term performance with long-term development isn’t a trade-off. Development is the performance strategy
- Three specific practices can shift the development-retention connection: skill activation conversations, mentoring as a leadership KPI, and development-first delegation
What the Talent Drain Actually Tells You About Your Leadership
When good people leave, most leaders look outward. They blame the market, the competition, the generational shift. A Coaching at Work report on learning investment reframed this in a way that’s hard to ignore: invest in learning or accept the talent drain. That’s it. Those are the two options.
The report found that organizations failing to invest in employee learning aren’t just losing skills. They’re sending a message about what they value. And people hear it.
Think about what retention actually signals. When someone stays, they’re saying: I’m growing here. Someone sees what I can become, not just what I produce today. When they leave, the opposite is usually true. They hit a ceiling that nobody helped them push past.
The leadership development connection is direct. If you lead people and those people are leaving, the question isn’t “How do we improve retention?” It’s “What am I not doing as a leader that would make people want to stay?”
That’s a harder question. It’s also the right one.
I’ve watched leaders get genuinely confused by exit interviews. “They said they wanted more growth opportunities. We have a tuition reimbursement program!” But growth opportunities and tuition reimbursement aren’t the same thing. Growth happens when a leader looks at someone and says, “You’re ready for more than what you’re doing. What do you want to take on?”
Your People Have More to Give Than You Are Asking For
That 70% underutilization figure from Coaching at Work deserves a closer look. It means the majority of your workforce has capacity that’s sitting idle. Not because they’re disengaged by nature, but because nobody has created the conditions for them to contribute fully.
Want a Clear View of Who’s Underleveraged?
Use a consult to spot where task assignment is crowding out skill activation—and what to change before your top people leave.
Underutilization looks different than disengagement, and that’s what makes it dangerous. An underutilized employee might still hit their targets. They show up, do the work, meet expectations. But they’re operating at 60% of what they could bring. The other 40% walks out the door at the end of every day, unused.

Consider a VP of engineering who has a senior developer on the team. That developer has deep expertise in system architecture, but their role is scoped to feature implementation. They’ve mentioned interest in mentoring junior developers. The VP nods, says “maybe next quarter,” and assigns another feature sprint. Six months later, the developer accepts an offer at a company that put them in charge of technical mentoring on day one.
Was the developer disengaged? No. Were they underutilized? Completely.
What I’ve noticed across my work is that leaders default to task assignment over skill activation. They see what needs to be done and match it to who can do it. Rarely do they flip the question: What can this person do that I’m not asking them to do?
That flip is where retention lives.
Mentoring Is Not Extra Credit. It Is the Job
An IT Brief Australia piece framed mentoring as a leadership responsibility, not a leadership bonus. That distinction matters. When mentoring is positioned as something leaders do if they have extra time, it never happens. Nobody has extra time.
But here’s what shifts when you treat mentoring as core to the leadership role: the leaders who actively mentor their people create multiplier effects. They don’t just develop one person. They build a culture where development is expected, where people teach each other, where growth isn’t dependent on a formal program or budget approval.
The most common objection I hear from leaders: “I don’t have time to mentor.” My response is usually a question. What are you spending time on that’s more important than developing the people who execute your strategy?
Mentoring doesn’t require an hour a week on your calendar labeled “mentoring session.” It lives in the five-minute conversation after a presentation where you share what you observed. It’s in the delegation decision where you give someone a stretch assignment instead of handling it yourself. It’s in the question you ask instead of the answer you give.
Leaders who mentor well don’t add it to their job. They do their job through mentoring. Decisions become teaching moments. Feedback becomes developmental, not corrective. Projects become growth opportunities, not just deliverables.
The retention payoff is immediate. People stay where they feel invested in. Not where the snacks are better.
Stop Hiring What You Could Be Building
MIT Sloan Management Review published a piece on “learning by hiring” that highlighted a pattern worth examining. When organizations need new capabilities, the default response is often to hire for them. Need AI expertise? Hire a data scientist. Need change management skills? Hire a consultant. Need better customer insights? Hire a CX specialist.
Each of those hires might be right. But each one also carries a hidden message to existing employees: We’d rather buy capability than build it in you.
The cycle is predictable. Underdeveloped employees notice they’re being passed over for growth. They leave. The organization hires replacements. Those replacements need onboarding, cultural integration, and time to build relationships. Institutional knowledge walks out with the people who left. The net investment is far higher than developing existing talent would have been.
I’m not suggesting you never hire. Sometimes the gap is too wide or the timeline too tight. But when hiring becomes the default response to every capability need, something is broken in the development culture. The leadership question is: before we open a req, have we looked at who’s already here and what they could become with the right investment?
The organizations that get this right don’t just save on hiring costs. They build loyalty. An employee who was developed into a new role is someone who knows, viscerally, that the organization invested in them. That’s not something a signing bonus can replicate.
The Performance-Development Balance Every Leader Gets Wrong
A recurring theme in recent leadership coverage, including a piece from ecommercenews.com.au on building while balancing, is the tension between delivering results now and developing people for later. Most leaders treat this as a trade-off. Development gets sacrificed on the altar of quarterly targets. And when it does, the challenges compound.
But this is a false choice, and it’s one of the most common leadership blind spots I encounter.
Development IS the performance strategy. A leader who develops their team’s skills is building capacity for better performance over time. A leader who only optimizes for today’s output is burning down the asset that produces tomorrow’s results.
The leaders who get the best long-term performance from their teams are the ones who refuse to separate development from daily work.
What does this look like in practice? It looks like a leader who, during a project debrief, doesn’t just celebrate the win but asks: “What did each person learn? What capability did we build? Who is ready for a bigger challenge next time?”
It looks like a leader who assigns projects not only based on who can execute fastest, but who would grow most from the experience. Sometimes that means the project takes slightly longer. It always means the team gets stronger.
It looks like a leader who, when a direct report makes a mistake, asks a coaching question before offering a solution. “What would you do differently?” takes 30 seconds longer than “Here’s what you should have done.” But the first builds judgment. The second builds dependence.
The leaders who burn out their teams aren’t the ones who push hard. They’re the ones who push hard without building anyone up in the process. It’s a pattern that drives executive burnout too.
Three Development Practices That Actually Move Retention
If the diagnosis is clear, the prescription needs to be specific. Here are three practices that move the needle on both development and retention. They don’t require new programs, budgets, or HR initiatives. They require leadership behavior change.
Make These 3 Practices Stick in the Real World
Coaching helps you turn skill activation conversations, mentoring KPIs, and development-first delegation into consistent leadership behavior.
Skill activation conversations. Once a quarter, sit down with each direct report and ask: “What skills do you have that you’re not using here? What do you want to be doing more of?” This goes beyond a performance review. It’s an explicit invitation to bring more of themselves to the work. Track what you learn and follow through. If someone tells you they want more strategic work and nothing changes for six months, you’ve actually made it worse.
Mentoring as a leadership KPI. If mentoring matters, measure it. Not with a form or a compliance check, but with a simple question in your leadership team meetings: “Who on your team is growing, and what are you doing to support that?” When leaders know they’ll be asked this question regularly, development stops being optional.
Development-first delegation. Before you assign work based on who can do it fastest, ask who would grow from doing it. Yes, this requires more patience. Yes, it sometimes means coaching someone through a task you could do in half the time. But every time you delegate for development, you’re building a stronger team and giving someone a reason to stay.
The leaders I work with who retain their best people don’t have a secret. They invest. They notice. They ask. And they create environments where people are used to their full potential, not just 30% of it.
If you’re leading a team right now, here’s the reflection I’d invite you to sit with: When was the last time someone on your team told you about a skill they have that you didn’t know about? If you can’t remember, it might be time to ask.
Fix the Talent Drain at the Leadership Level
In a free consult, map what’s driving underleveraging on your team and identify 1–2 shifts that improve growth, performance, and retention.
Book a Free Consultation →



