Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How Skill Stacks Give You Unfair Career Advantage
Transcript
- Lucas: Let me start with a specific person. A graphic designer I know — let's call her Jenna — worked in the marketing department of a mid-sized software company. She was good at her job, but she wasn't the most talented designer in the room. She was maybe in the top 30 percent of her peer group. Luna: Okay. So not a superstar on raw talent alone. Lucas: Exactly. But Jenna did something that changed her career trajectory completely. She learned SQL. Not at a bootcamp — just enough to query the company's customer database. She spent maybe three months, an hour a week, watching YouTube tutorials and practicing. Luna: And that made a difference? Lucas: A huge one. Within a year, she was the only designer in the department who could pull her own data. When the team needed to segment users for an email campaign, she didn't have to wait three days for the analytics team. She just ran the query herself, designed the assets based on the segments, and delivered the whole thing in an afternoon. Her manager noticed. Her manager's manager noticed. She got promoted twice in eighteen months, and by the end of year two, she was making more than the head of design. Luna: So she wasn't the best designer, but she was the only designer who could also talk to the database. That's a genuinely rare combination. Lucas: That's the core of what we're talking about today. It's a concept called skill stacking — and it was popularised maybe a decade ago by Scott Adams, the creator of the Dilbert comic strip. Adams argued that trying to be the best in the world at one thing is a losing strategy for most people. The odds are against you. But being in the top 25 percent at two or three things, and combining them, is both achievable and extremely valuable. Luna: I remember that argument. He said he was a mediocre cartoonist, but he combined that with a sense of humour about office life and a basic understanding of business. And together, those three mediocre skills created Dilbert. Lucas: Precisely. And Jenna's story is the same principle in a modern context. She was a solid designer, added functional data literacy, and suddenly she was a category of one in her organisation. That's pricing power. That's negotiating power. That's career acceleration without having to be a genius. Luna: But I think a lot of people hear 'skill stacking' and assume they need to learn three completely unrelated things from scratch. And that sounds exhausting. Lucas: It does if you frame it that way. But the real insight is that the best stacks are built on skills that naturally complement each other. The second skill should make the first skill more valuable. Data literacy made Jenna's design skills more valuable because she could work faster and with more context. A marketer who learns basic Python can automate reporting. A project manager who learns negotiation theory runs better stakeholder meetings. The stack isn't random — it's strategic. Luna: So the question becomes: what's the highest-leverage second skill for your current role? And I'd argue most people don't ask that question because they're too busy trying to get better at the thing they already do. Lucas: Right. And that's the trap of the '10,000 hours' myth. If you spend all your time trying to go from the 70th percentile to the 95th percentile in one skill, the effort to reward ratio gets worse the higher you climb. The jump from the 70th to the 80th percentile might take two hundred hours of deliberate practice. But the jump from the 90th to the 95th might take a thousand hours. Meanwhile, you could spend those thousand hours reaching the 70th percentile in two or three other skills — and end up with a much more differentiated profile. Luna: That's the math that most career advice misses. The marginal return on depth diminishes. The marginal return on breadth, when it's strategic breadth, stays high for much longer. Lucas: Exactly. And I want to be careful here — I'm not arguing against deep expertise. Some fields genuinely require it. You can't be a 70th-percentile neurosurgeon who also dabbles in graphic design and expect that to help. But for most knowledge-worker roles — marketing, sales, operations, product, even some engineering — the stack model outperforms the specialist model at the career level. Luna: Speaking of which — if today's episode is helping you think about your own skill stack in a new way, I want to mention something briefly. The reason we can dig into this kind of concrete strategy without a sponsorship break or a mid-roll ad is that this show is listener-supported. If you found this useful, and you want to keep episodes like this coming without commercial interruption, you can support us at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. No pressure — just a way to keep the show ad-free for everyone. Lucas: Yeah, and honestly, it's because listeners like you have made that possible that we can spend a full episode on a single practical concept like this. So thank you. And back to the stacks. Luna: So let's talk about how to actually build one. Where do you even start? Lucas: I think there's a simple diagnostic. Look at your current role and ask: what is the one task or decision that consistently slows you down or requires you to hand off to someone else? That handoff is the friction point. And the skill needed to eliminate that handoff is probably your highest-leverage second skill. Luna: So for Jenna, the handoff was 'I need data to do my job, but I have to wait for the analytics team.' Learning SQL removed that handoff. For a lot of people, the handoff might be 'I need budget approval but I can't build a financial model to justify my request.' So the second skill becomes basic finance. Lucas: Exactly. And once you identify that handoff, the learning investment is usually much smaller than you think. You don't need to become a data engineer to write basic SQL. You don't need a CFA to build a simple P&L in Excel. The goal is functional fluency — enough to unblock yourself, not enough to switch careers. Luna: But there's a risk here, right? The risk of becoming a jack of all trades, master of none. How do you avoid that trap? Lucas: You avoid it by being deliberate about which skills you stack. The key constraint is that at least one skill in your stack needs to be strong enough that people hire you for it. If you're mediocre at everything, you're not a stack — you're a generalist with no anchor. So you need a primary skill that gets you in the door. The stack makes you more valuable once you're inside. Luna: So the anchor skill is your identity. 'I am a designer who also does data.' Or 'I am a project manager who also understands UX.' The second skill enhances the first, it doesn't replace it. Lucas: Right. And there's another way to think about this that I've been experimenting with personally. Instead of stacking skills, think about stacking 'knowledge domains.' A skill is something you can do. A knowledge domain is something you understand. For example, understanding the basics of how your company's revenue model works is a knowledge domain. It's not a skill you'd put on your resume, but it allows you to make better decisions and communicate more effectively with executives. Luna: That's a useful reframe. So the stack becomes: a core skill, a complementary skill that removes a friction point, and a knowledge domain that gives you strategic context. That's a three-layer stack. Lucas: Exactly. And that three-layer stack is incredibly hard to replicate. Someone else can learn your core skill. They can even learn your complementary skill. But combining those with a genuine understanding of the business context — that's where you become truly differentiated. It's also why internal candidates often outperform external hires. They already have the knowledge domain, even if their skills are slightly weaker. Luna: Let's talk about a real-world example that isn't Jenna. Give me someone in a different field. Lucas: Sure. I read about a customer support rep at a SaaS company who decided to learn basic product management. Not formally — just reading, asking product managers questions, learning how they prioritise features. Within a year, she was the go-to person for translating customer complaints into product requirements. She eventually moved into a product role without a title change or a pay cut. She just steadily increased her scope until her title caught up. Luna: And the key there is that she didn't leave her job to learn. She used her existing role as a learning lab. That's a much faster path than going back to school. Lucas: It is. And it's less risky. You get paid to learn, and you can test whether you actually like the skill before committing to it. The worst case is you learn something that makes you better at your current job. The best case is you unlock a new career path. Luna: I think the biggest barrier for most people is not knowing what to stack. They don't have a clear picture of what complementary skills exist in their field. Lucas: That's a fair point. So here's a practical exercise. Look at job descriptions for roles one or two levels above yours — not to apply, but to see what skills they list that you don't have. If a pattern emerges — say, every senior role mentions 'data analysis' or 'stakeholder management' — that's your second skill signal. Luna: And if you're early in your career, you might not even have a clear primary skill yet. What do you stack then? Lucas: Then you're better off building a 'T-shaped' profile first. Get competent enough in one area to be employable, then add breadth. The stack only works if you have a foundation to stack on. If you're too early, you risk being a dilettante. Luna: That's actually a nice bridge to something I've been thinking about. The 'T-shaped' model — deep expertise in one area, broad knowledge across many — is fine as a starting point. But I think the stack model is a more honest description of what actually creates career value. Because breadth without a connecting logic is just scattered. The stack implies intentionality. Lucas: I agree. And the stack model also accounts for the fact that the most valuable combinations are often counterintuitive. A lawyer who understands data privacy and also knows how to code — that's a rare stack. An accountant who can build dashboards in Tableau and also explain them in plain English — also rare. The more unexpected the combination, the less competition you face. Luna: So the takeaway for today is: don't try to be the best. Be the only one who combines these specific things. Lucas: Exactly. And the beauty is that you don't need permission or a budget. Jenna learned SQL on YouTube. The customer support rep learned product management by asking questions. The barrier to entry for most complementary skills is lower than you think. The hard part is just deciding to start. Luna: One last question before we wrap. If someone listening today wants to start building a stack this week, what's the one thing they should do? Lucas: Identify one handoff in your job that frustrates you — a task you could do yourself if only you had one more skill. Write it down. Then find one resource — a YouTube channel, a short course, a colleague — and spend thirty minutes on it this week. That's it. The stack builds one small investment at a time. Luna: I like that. Simple, specific, actionable. And if you do that thirty minutes this week, you're already ahead of everyone who's still trying to become the best in the world at one thing. Lucas: That's the whole idea. Thanks for listening, and we'll see you next time.