Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How Skill Friction Reveals Your Real Growth Edges
Transcript
- Lucas: You know that moment when you're working on something and you just hit a wall — not because you're lazy, but because you literally don't have the skill to push through? I want to talk about that today. Luna: Oh, I know exactly what you mean. It's that sinking feeling where you realise you're in over your head. But you're saying that's actually useful? Lucas: Exactly. I think we've been conditioned to treat that friction as a sign we shouldn't be doing this. But in reality, it's the clearest signal you'll get about what you need to learn next. I'm calling it 'skill friction' — the specific, uncomfortable gap between what the task demands and what you currently know. Luna: So it's almost like a diagnostic tool. Instead of randomly picking a course on Coursera, you let the work itself tell you where the holes are. Lucas: Exactly. And there's data to back this up. LinkedIn Learning put out a report in 2025 — actually, I think it was late 2025 — that looked at how professionals choose learning goals. They found that people who identify their skill gaps by reflecting on actual work friction are twice as likely to complete the learning goal compared to people who just browse by topic. Luna: That makes intuitive sense. When you feel the pain of not knowing something, you're way more motivated to learn it. It's not abstract. Lucas: Right. And the flip side is even more interesting. The same report showed that professionals who upskill based on 'trending skills' or 'what looks good on a resume' have a completion rate below 40 percent. The friction-driven learners were above 80 percent. Luna: So it's not just about motivation — it's about relevance. If you're learning something because it's actually blocking your work, you have a real problem to solve. Lucas: Exactly. Let me give you a concrete example. I talked to a friend who's a software developer at a mid-size SaaS company — about 400 employees. She was asked to lead a cross-functional project that involved some product management decisions. She had zero formal PM training. Luna: And she hit the friction wall hard, I'm guessing. Lucas: Hard. She told me the first week she felt completely lost. She didn't know how to write a product requirements doc, she couldn't prioritise features, and she was supposed to present a roadmap to the VP of product. But instead of panicking, she started a friction log. Luna: A friction log — what does that look like? Lucas: Every time she hit something she didn't know how to do, she'd write it down. Just a sentence: 'Couldn't decide which feature to prioritise — don't know how to weigh customer feedback against engineering effort.' That's one entry. By the end of two weeks, she had 17 specific friction points. Luna: And then she prioritised which ones to learn first. Lucas: Yeah, exactly. She grouped them into themes. The biggest cluster — I think it was seven entries — all related to decision-making frameworks. So she spent a weekend learning RICE scoring and weighted short-term priority. Then the next cluster was about stakeholder communication. Luna: So she didn't try to learn 'product management' as a whole. She just learned the pieces that were causing immediate friction. Lucas: That's the whole point. She told me that approach let her ramp up about 30 to 40 percent faster than if she'd taken a full product management certification course, which would have covered a ton of things she didn't need yet. Luna: This is really resonating with me because early in my marketing career, I had a similar experience. I was handed an analytics project — I had to pull together a campaign performance report for the CMO. I knew basic Excel, but nothing about data visualisation or statistical significance. Lucas: And you hit friction. Luna: I hit a wall. I spent three days trying to figure out why two numbers looked different but didn't know about confidence intervals. It was painful. But now I realise that friction was the fastest learning accelerator I've ever had. I learned more about analytics in two weeks than in a semester of classes. Lucas: And you probably remember those lessons because they were tied to a real outcome. That's the key — friction isn't just uncomfortable, it's sticky. When you learn something because you need it to solve a real problem, the neural encoding is completely different. Luna: So how does someone actually start using this? I think our listeners are probably facing friction right now in their jobs. Lucas: The simplest way is to start a friction log for one week. Every time you're blocked, stuck, or frustrated because you don't know something, write it down. Don't judge it, don't try to solve it yet. Just log it. Luna: And at the end of the week, look for patterns. Lucas: Right. You'll probably find that three or four themes cover 80 percent of your friction points. Those are your growth edges. Then pick ONE theme — the one that's causing the most pain or the one that's blocking the most important project — and learn just that. Luna: I love this because it takes the guesswork out of professional development. You don't have to ask 'what skills should I learn?' You just look at what's slowing you down. Lucas: And that's actually more honest. A lot of us have a list of skills we think we 'should' have — but when you look at your actual work, you might find that you don't really need SQL or public speaking right now. You need to learn how to run better meetings or how to debug a specific type of error. Luna: Let's talk about the emotional side for a second. Friction can feel really demoralising, especially when you're early in your career. You start to think 'maybe I'm not cut out for this.' Lucas: That's the biggest trap. The story we tell ourselves is that friction means we're failing. But the most successful people I know see friction as data. It's just information about where the next opportunity to grow is. The discomfort is temporary. Luna: And if today's episode is helping you reframe that uncomfortable feeling into something productive, I think that's really valuable. It's the kind of shift that can change how you approach your entire week. Lucas: Absolutely. And if you're finding this useful, we want to keep making it. The way these episodes stay ad-free is listener support. If you feel like you've gotten a practical takeaway, you can help us keep going at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to say this matters. And it really does help us keep the show focused on concrete tools like this one. Lucas: So back to the friction log — once you've identified your top theme, the next step is to find the smallest possible learning unit. Don't try to master a whole skill. Just learn enough to remove that specific friction point. Luna: Like the developer learning just one decision-making framework instead of all of product management. Lucas: Exactly. And then you apply it immediately. You use that framework on the actual project that was causing the friction. That's the loop: friction, identify, learn, apply. And each time you do it, you get a little more comfortable with the discomfort itself. Luna: So eventually friction becomes a signal you look forward to, not something you avoid. Lucas: I think that's the ultimate career meta-skill. If you can learn to see friction as a roadmap, you'll never be stuck wondering what to learn next. The work itself tells you. Luna: Alright, I'm starting my friction log today. I already have one entry: 'Couldn't explain this concept clearly to a friend' — that's friction as a communicator. Lucas: And now you have a specific growth edge. That's the whole show right there. Luna: Thanks for joining us. Until next time. Lucas: Yeah, see you then.