Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How to Build a Skills Portfolio Not a Resume
Transcript
- Lucas: So we've talked about how skills expire fast — eighteen months, give or take, for a technical skill in the current environment. Luna: Right, and that episode left me wondering — if the half-life is that short, what's the point of building deep expertise in anything? Lucas: Exactly the question I want to dig into today. Because the answer isn't 'don't specialize.' It's 'change how you think about your skill set entirely.' Instead of a resume, think of a portfolio. Luna: A skills portfolio — like an investment portfolio, diversified? Lucas: Exactly. You don't put all your learning into one stock. You spread across layers. I want to introduce a simple framework: three layers. Foundational, hybrid, and frontier. Luna: Okay, let's start with foundational. Lucas: Foundational skills are things like writing clearly, basic numeracy, critical thinking, negotiation. They don't change much decade to decade. They're the bedrock. The World Economic Forum's Future of Jobs report — which came out last fall, for 2025 to 2030 — lists analytical thinking and resilience as the top two core skills employers will demand. Luna: And those are foundational, not technical. Lucas: Correct. Then you have hybrid skills — combinations that cross disciplines. Data storytelling, for example. That's not pure data science, and it's not pure writing. It's both. Or product management, which mixes business strategy, design thinking, and a bit of engineering empathy. Luna: That's where the value is, I think. Pure specialists get automated. Pure generalists get overlooked. The hybrid is the sweet spot. Lucas: Yes. And then the third layer is frontier — the bleeding edge that's changing right now. Today that's things like building agentic AI workflows, prompt engineering at an advanced level, or quantum-safe cryptography. But frontier has the shortest half-life. Luna: So you invest less time there. Maybe 10 or 15 percent of your learning hours? Lucas: I'd say even less — maybe 10 percent. The key ratio I've heard from career coaches is the '30 percent rule.' Spend 30 percent of your learning time on skills adjacent to your current role, not directly in it. Luna: Adjacent meaning? Give me a concrete example. Lucas: Sure. Say you're a marketing manager. Your core skill is campaign strategy. Adjacent would be basic data analytics — SQL, maybe some Python for automating reports. That's not your job description, but it makes you far more valuable because now you can measure what you're doing. Luna: And that's the hybrid layer — marketing plus data. Lucas: Right. There's a real case I love: a marketer named Sarah at a midsize tech company. Two years ago, she had a typical marketing background — brand management, content calendars. She noticed her team kept relying on the data team for simple queries, and it took days. Luna: So she learned SQL on the side. Lucas: She spent about four hours a week for six months. Not a bootcamp — just consistent, adjacent learning. Within a year, she was running her own analyses, and her boss noticed. She moved into a marketing analytics role with a 30 percent raise. Luna: And the 30 percent rule — 30 percent of learning on adjacent skills. That's actionable. Lucas: It's a heuristic, not a law, but I think it's useful. Because if you only ever learn what your job already requires, you stay flat. If you jump too far into something totally unrelated, you waste effort. Adjacent is the productive tension. Luna: But let me push back a little. The hype around 'learn to code' a few years ago convinced a lot of people to try full career switches into tech. Many failed. Was that because they ignored the adjacency principle? Lucas: I think so. If you're a teacher and you try to become a software engineer, that's a big leap. The adjacency is weak — classroom management doesn't map cleanly to debugging code. But if you're a teacher and you learn instructional design software, that's adjacent. Or if you're a journalist and you learn data visualization, that's adjacent. Luna: So adjacency is about skill overlap, not passion. Lucas: Passion helps with motivation, but the portfolio framework says: find the intersection of what you're good at and what's adjacent to your current work. Over time, you can pivot gradually. A career change doesn't have to be a leap — it can be a series of diagonal moves. Luna: Diagonal moves — I like that. You shift sideways and up at the same time. Lucas: Exactly. And this brings me to a tension I want to flag. The soft skills versus hard skills debate. My view is that both matter, but the portfolio approach challenges the idea that soft skills are 'timeless.' Luna: Oh really? I thought empathy and communication would always be valuable. Lucas: They are — but the expression of them changes. Twenty years ago, 'communication' meant writing a memo or giving a presentation. Today it means writing a clear Slack message, running a remote workshop, or recording a Loom video. The skill adapts, but the context shifts. Luna: So even soft skills need updating. Lucas: Right. And some soft skills become more or less valuable depending on the era. For instance, active listening is always good. But the ability to maintain focus in a distraction-filled environment — that's practically a superpower now. That's a newer soft skill. Luna: And yet you can't put 'focus' on a resume easily. Lucas: Which is exactly the problem. The resume is a chronological list of jobs and degrees. It doesn't show your portfolio. A skills portfolio says: here are my foundational skills, here are my hybrid combinations, here's what I'm exploring on the frontier. It's more honest about what's decaying. Luna: How would someone actually build that portfolio practically? Like, this week? Lucas: Three steps. First, audit your current skills. List your top five. Then categorize them into the three layers. Are you heavy on frontier but light on foundational? That's brittle. Are you all foundational but no hybrid? You're not differentiating. Luna: Step one: audit. Step two? Lucas: Identify one adjacent skill. Something that's about 30 percent away from your core. For most knowledge workers, that might be learning a tool like Tableau or Power BI, or basic SQL, or even how to use AI coding assistants to automate tasks. Luna: And step three? Lucas: Schedule the time. Four hours a week. That's it. Over six months, that's about 100 hours — enough to reach competence in most hybrid skills. And importantly, document your projects. Build a portfolio you can show, not just a list. Luna: I want to test this on a real person. Say a recent grad with a liberal arts degree. What's their portfolio? Lucas: Foundational: writing, critical thinking, research. That's solid. Hybrid: maybe they take a course in digital marketing or UX research. Frontier: they learn to use AI tools for content generation or data analysis. The combination — liberal arts plus digital skills — is actually highly employable. Luna: So the portfolio mindset also reduces anxiety. You don't have to be an expert in everything. Lucas: Exactly. The goal is not to be the best at any single thing. It's to have a resilient mix. And that's the core message: future-proofing isn't about predicting the next hot skill. It's about having a system for continuous learning that's balanced across time horizons. Luna: I keep coming back to the 30 percent rule. It's simple enough to remember. Lucas: And it's backed by data. A 2024 study from the Burning Glass Institute found that workers who acquired adjacent skills had 20 percent higher wage growth over five years than those who didn't. The effect was stronger than getting a new degree. Luna: Wow. So the portfolio approach isn't just theory. Lucas: No, it's empirical. And the reason is that adjacent skills compound. Each one makes the next easier to learn. You build a latticework of competencies that's hard to replicate. Luna: One question though: how do you know if an adjacent skill is the right one? What if you pick something that becomes obsolete quickly? Lucas: That's a risk, but it's mitigated by the portfolio structure. Because you're not betting everything on that one skill. If it fades, you still have your foundational layer. And you can pivot. The key is to avoid skills that are too narrow. For example, learning a specific proprietary software tool might be risky. Learning a concept like 'data literacy' is broader. Luna: So favor concepts over tools. Lucas: Yes. And favor skills that have network effects — the more people who use them, the more valuable they become. Data storytelling, for instance, is more valuable when everyone in your organization works with data. It's a multiplier. Luna: Alright, let's wrap with a concrete checklist for listeners. Lucas: Sure. One: write down your current role's core skill. Two: list the top three adjacent skills you've seen colleagues use that you don't have. Three: pick one to learn for four hours a week for six months. Four: after six months, assess — did it open new opportunities? If yes, go deeper. If not, pick another. Luna: And repeat. Sounds like a lifelong habit. Lucas: It is. The half-life of skills is shrinking, but the half-life of a learning habit is long. Build the habit, and the portfolio takes care of itself. Luna: I'm going to audit my own skills tonight. I think I'm heavy on foundational, light on frontier. Lucas: That's the first step. And if any listener wants a template, we'll put a simple one in the show notes. A one-page skills audit grid. Luna: Perfect. And next episode, I want to talk about how to actually negotiate a raise based on your portfolio, not your tenure. Lucas: That's a great topic. Let's schedule it. Luna: Alright. Thanks Lucas. Lucas: Thanks Luna. Talk to everyone next time.