Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How to Use Skill Trees to Guide Your Career Growth
Transcript
- Lucas: So, you know how in video games you have a skill tree — you start with basic moves, then choose a branch, and eventually unlock advanced abilities? I think that's actually a really useful way to think about career skills. Luna: I love that analogy. But most people don't build their career like a game character. They take whatever training their employer offers or whatever course is on sale. Lucas: Right. And that's the problem. A skill tree forces you to be intentional. You have to ask: what's the prerequisite for the thing I want to do next? And what branch do I want to specialize in? Luna: So give me an example. Walk me through how someone actually builds a skill tree. Lucas: Sure. Let's take a marketing generalist who wants to move into product marketing. She might start with foundational skills — market research, basic copywriting, data analysis. That's the trunk. Then she branches: maybe she goes deep on competitive analysis, or on messaging frameworks, or on launch strategy. Each branch has levels — like, you don't start with positioning a billion-dollar product. You start by writing one feature brief. Luna: And the tree makes it visible. You can literally see that you need to master market research before you can do effective competitive analysis. Lucas: Exactly. I talked to a product marketer at a SaaS company — her name's Jenna — and she mapped out her entire career this way. She had a whiteboard with circles and arrows. She said it helped her stop taking random courses and focus on what actually moved her toward her target role. Luna: What did she put on her tree? Like, what were the actual skills? Lucas: She started with three core branches: customer understanding, messaging, and go to market strategy. Under customer understanding, she had sub-skills like user interviews, survey design, persona development. Under messaging, she had value proposition, feature narrative, and competitive positioning. She'd check off each node as she felt confident. Luna: And she was honest about what she hadn't done yet. That's the hard part — most of us overestimate our skills. Lucas: Right. The tree forces a kind of brutal honesty. You can't say 'I know messaging' if you've never written a positioning document from scratch. The node is either unlocked or it's not. Luna: So how do you decide which branch to pursue? I feel like that's where people get paralyzed. Lucas: That's a great question. One approach is to look at the skill trees of roles you admire. If you want to be a product marketing director in five years, look at job descriptions for that role. Identify the skills that come up most often — those are your main branches. Then look at the senior version of each skill. That's your level cap. Luna: And you can also look at what skills are adjacent to your current role. Like, if you're a content writer, you might have a natural branch into SEO strategy or into content distribution. Lucas: Exactly. But here's where the analogy gets really useful: in games, some skills are dead ends. They look cool but they don't unlock anything else. In careers, that's things like mastering a software tool that's being replaced by AI, or getting a certification that nobody in your industry respects. Luna: Oof. So how do you avoid dead-end skills? Lucas: You ask: does this skill open up at least two other skills I care about? If the answer is no, it's probably a leaf node — something you do once and then never build on. That's fine for a hobby, but not for a career investment. Luna: Right. So you want skills that have high branch factor — they connect to multiple future options. Lucas: Exactly. And that's why foundational skills are so powerful. Learning how to learn, persuasive communication, basic data literacy — those unlock almost everything else. They're like the core stats in an RPG that boost every other ability. Luna: Speaking of which — if today's episode helped you think about your own skill tree, and if it was worth the price of a coffee to you, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Lucas: And honestly, listener support is what keeps this podcast ad-free and focused on practical frameworks like this. We really appreciate it. Luna: So back to the tree — you mentioned Jenna used a whiteboard. Is that the best tool, or are there digital ones? Lucas: I think pen and paper or a whiteboard is actually ideal for the first draft. It forces you to think spatially. But there are tools too. Some people use mind-mapping software like Miro or Xmind. I've even seen people build skill trees in spreadsheets, with columns for skill name, prerequisite, level, and next step. Luna: Let's talk about leveling up. How do you know when you've mastered a skill enough to move to the next node? Lucas: That's subjective, but you can use a simple rubric. I like a three-level system: Aware, Proficient, and Expert. Aware means you can talk about it intelligently. Proficient means you can do it with guidance. Expert means you can teach it or do it independently under pressure. Luna: So for a skill like 'running a user interview,' aware might mean you know the difference between open and closed questions. Proficient means you've conducted five interviews and synthesized findings. Expert means you've trained others to do it. Lucas: Exactly. And here's the kicker — you don't need to hit Expert on every node. In fact, most roles only require Proficient on the majority of skills and Expert on two or three. The tree helps you see where you need depth versus where you just need competence. Luna: That's reassuring. I think a lot of people feel like they need to be an expert at everything before they can move up. Lucas: And that's how you get stuck. The skill tree lets you optimize for your target role, not for being a generalist genius. Jenna, the product marketer I mentioned — she never became an expert in data engineering. She became proficient enough to query SQL and pull her own campaign data. That freed her to go deep on messaging. Luna: So what about respecing? In games, you can sometimes reset your skill tree and reallocate points. Can you do that in a career? Lucas: To a degree, yes. Some skills transfer. If you've built deep expertise in B2B content marketing, you can pivot to B2B product marketing because the customer understanding branch is similar. But if you try to jump from B2B content to surgery, you're starting a new tree entirely. Luna: So the key is to keep your tree modular. Don't paint yourself into a corner with hyper-specific skills that don't branch. Lucas: Right. And one way to do that is to check in on your tree every quarter. Set a reminder: 'Review skill tree.' Ask: what new nodes have appeared in my industry? Which of my current nodes are becoming obsolete? Do I need to prune anything? Luna: That's a great habit. I think a lot of people would benefit from literally drawing their skill tree and putting it on their wall. Lucas: I did that. I have a small whiteboard in my office with my current tree. It has three main branches: research, writing, and audience strategy. Each has about five nodes. It helps me decide what to work on next. Luna: What's your next node? Lucas: Under writing, I want to level up from Proficient to Expert in narrative structure. Specifically, long-form narrative. That's a skill that branches into book writing, documentary scripting, and maybe even teaching. It has a high branch factor. Luna: Nice. And it's concrete enough that you can measure progress. You could say, 'I'll write three long-form pieces this quarter and get feedback from an editor.' Lucas: Exactly. And that's the whole point of the skill tree. It turns vague career goals into specific skill nodes with clear prerequisites and level-up criteria. It's a map, not a wish list. Luna: I want to try this. I think I'll start with a simple tree for my own role. Maybe just three branches and five nodes each. Lucas: Start with the trunk. What's the single foundational skill that everything else depends on for you? Luna: For me, it's probably active listening. Because I interview people every day. If I don't hear what they're really saying, nothing else works. Lucas: That's a perfect trunk skill. And from there, you can branch into synthesis, into follow-up questioning, into rapport building. Each of those is a node you can develop. Luna: Alright, I'm convinced. I'm going to map my tree this weekend. Lucas: Do it. And if you want to share it, we'd love to see it. Or at least hear how it goes. Luna: I'll report back. For now, I think we've given listeners a solid framework to start with. Skill trees: they're not just for gamers. Lucas: Not just for gamers. And honestly, if you take one thing from today, I hope it's the question: what's the next node you want to unlock?