Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How Skill Leakage Drains Your Career Potential
Transcript
- Lucas: So last week I was catching up with an old colleague — senior software engineer, spent nearly a decade at a well-known fintech company. She made the leap into engineering management about two years ago. Luna: Classic career move. More responsibility, more influence. Lucas: Exactly. And she loves it — loves building teams, loves mentoring. But she told me something that stopped me cold. She said, 'I don't think I could pass a coding interview for my own job right now.' Luna: Wow. That's a gut punch. She's still in the same company, same domain, but the hands-on skill has faded? Lucas: That's exactly it. And her experience is not unusual. There's actually a name for this phenomenon — skill leakage. It's the gradual, often invisible erosion of a capability you once had solid command of, simply because you stopped applying it regularly. Luna: So it's more specific than just 'I forgot some stuff.' It's a structural loss of fluency. Lucas: Right. And the research suggests it happens faster than most people assume. A 2023 meta-analysis in the Journal of Applied Psychology looked at skill decay across dozens of studies and found that after a year of non-use, people retain about sixty to seventy percent of procedural skills — things like programming languages, data analysis workflows, even surgical techniques. Luna: So in two years, my friend might be down to maybe fifty percent fluency? That's a huge drop. Lucas: Possibly. And the tricky part is that declarative knowledge — the facts you can recall — decays slower. So you still know the syntax rules conceptually, but your fingers don't move the same way. You can't produce the code fluidly under time pressure. Luna: That makes sense of a lot of 'impostor syndrome' stories I hear from people who moved into leadership. They feel like frauds, but maybe it's just straightforward skill leakage. Lucas: Exactly. It's not that they never knew the material. It's that the retrieval pathways have gotten rusty. And the scary part is, skill leakage doesn't just affect your confidence. It can affect your career optionality. If you ever need to pivot back to an individual contributor role, or if your company restructures, that rustiness becomes a real liability. Luna: So what can someone do about it? Especially if their current role doesn't let them use that skill day-to-day? Lucas: The most effective strategy I've seen is what I call a 'sharpening project.' A small, low-stakes, recurring practice that keeps the skill active without requiring you to do it forty hours a week. For my friend, she started contributing one pull request per month to an open-source project in her old language. Just a few hours, no deadlines, no performance review attached. Luna: That's smart. Low pressure, but consistent. She's not trying to master a new framework, just maintain what she had. Lucas: Exactly. And the research backs this up. Spaced retrieval practice — pulling the skill back into active use at regular intervals — is one of the most reliable ways to slow decay. Even thirty minutes a week can make a measurable difference over someone who does nothing. Luna: What about people whose skills are more conceptual? Like a marketing strategist who used to do hands-on data analysis but now reviews dashboards instead of building them? Lucas: Same principle applies. The leakage might look different — you lose the ability to spot data quality issues, or you stop remembering the syntax for a particular query language — but the solution is the same. A monthly 'deep dive' where you actually run the analysis yourself, not just review someone else's summary. Luna: So the key is intentional maintenance. You can't just assume your skills will stay sharp because you're in the same industry. Lucas: Right. And this is where I think the conversation about skill stacking — which we've talked about before — misses something. People focus on adding new skills, but they rarely think about preserving the ones they already own. The most valuable skill set you have might be the one you're quietly losing. Luna: That's a sobering thought. Especially for mid-career professionals who've spent years building a rare combination of abilities. Lucas: Exactly. And the irony is, the rarer the skill, the faster it might decay if you don't use it, because you have fewer opportunities to practice it in a work context. A niche programming language, a specialized statistical method, a foreign language for business negotiations — these leak faster than general skills like project management. Luna: So the very thing that makes you unique on the job market is also the most fragile. Lucas: That's the kicker. So if you're in a role that's pulling you away from your core expertise, it's worth asking yourself: Is this skill something I want to preserve? And if so, what's my sharpening project? Luna: I think that's a really practical takeaway. And honestly, if today's episode helped you think through your own skill maintenance — even if it just clarified one thing — that's exactly the kind of value we hope to offer here. Lucas: And if that felt worth a coffee to you, there's a link at our show notes: buy me a coffee dot com slash fexingo. Totally optional, but listener support like that is what keeps this show ad-free and focused on ideas like these. Luna: Yeah, it's a small gesture that makes a big difference to us. And we really appreciate it. Lucas: Anyway — back to skill leakage. One other strategy I want to mention is what I call 'skill bridging.' Instead of going cold turkey on an expertise, you find ways to keep it warm through related activities. For example, a graphic designer who moves into art direction might not do hands-on design anymore, but they could start a weekly sketch practice that keeps their visual instincts sharp. Luna: So it's not exactly the same skill, but it exercises the same cognitive muscles. Lucas: Exactly. And that bridging can sometimes lead to unexpected innovations. You bring a fresher perspective back to the team because you're not just managing — you're still creating. Luna: I also wonder about the social side of skill leakage. If you stop practicing a skill, you also lose your network of people who are actively using it. Lucas: That's a really good point. There's a concept called 'knowledge depreciation' in organizational behavior — your professional network around a skill also decays. The conferences you used to attend, the Slack groups you were active in, the colleagues who would ping you with questions. When that dries up, you lose the ambient learning that kept you current. Luna: So maintaining the skill also means maintaining the community around it. Even just lurking in a forum or attending a meetup once a quarter could slow the leakage. Lucas: Absolutely. And I think the biggest takeaway from all this is that skill leakage is not a sign of failure. It's a natural consequence of career progression. But if you're aware of it, you can manage it. You can decide which skills are worth preserving and which ones you're okay letting go. Luna: Right. Not every skill needs to be sharpened forever. Some you outgrow, and that's fine. But the ones that define your career identity — those deserve a maintenance plan. Lucas: Exactly. So here's a question for our listeners: What's one skill you used to have that you're starting to feel slip away? And is it worth a sharpening project? If you want to share, we're on LinkedIn and Twitter. We'd love to hear what you're doing about it. Luna: That's a great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. See everyone next time.