Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / When Your Skills Feel Stuck Try This Career Reset
Transcript
- Lucas: So you've been learning a new skill — maybe it's data analysis, maybe public speaking, maybe a coding language — and for the first few months, progress feels real. You can literally feel yourself getting better week over week. Luna: Right, that honeymoon phase where every tutorial unlocks something. Lucas: Exactly. Then, somewhere around month six or eight, the curve flattens. You're still putting in the hours, but the improvement? Barely perceptible. And that's where most people either burn out or quietly quit. Luna: It's such a common story. I've been there with learning Spanish — after the basics, you just plateau. Lucas: That plateau is the subject of today's episode. I want to talk about what's actually happening when your skills feel stuck — and why the fix isn't always 'try harder' or 'take another course.' Luna: So what is it? Because I think listeners know exactly what we're describing. Lucas: Let me anchor this with a specific case. A graphic designer I know — let's call her Priya — joined a mid-size tech startup about 18 months ago. She came in strong, learned the tools fast, and within six months she was shipping production-quality work. Luna: That's the fast part of the curve. Lucas: Right. But then, around month ten, she hit it. The same kind of projects, the same feedback loops, the same tools. She stopped feeling challenged. She started wondering if she was even growing anymore. Luna: And her instinct was probably to learn a new tool — like Figma or Spline — or take an advanced design course. Lucas: That's exactly what she tried. She took a motion design course. It helped for maybe two weeks, then the plateau came right back. The reason is that the plateau isn't about a lack of knowledge — it's about a lack of novel context. Luna: Can you unpack that? 'Novel context' sounds a bit academic. Lucas: Sure. The way we build expertise isn't linear. You get these steep gains when you're first mapping a new domain — your brain is building the framework. But once that framework is solid, improvement requires new input. Not more of the same input — new conditions, new constraints, new problems. Luna: So it's not about the skill itself, it's about the environment you're exercising it in. Lucas: Exactly. Priya's context was 'design for the same product, same team, same velocity.' Her brain had optimized for that. To grow, she needed a different context — even temporarily. So the tactic I want to talk about today is called 'context shifting,' and it's deceptively simple. Luna: What does it look like in practice? Lucas: You deliberately put yourself into a situation where you're bad at something related but not identical. For Priya, that meant she volunteered to lead the design sprint for a completely new product line — one she had zero domain knowledge in. She had to learn the user base, the constraints, the business metrics from scratch. Luna: That sounds uncomfortable. Most people avoid feeling incompetent at work. Lucas: That's exactly the point. The discomfort is the signal that you're in a new context. And when you're forced to solve problems without your usual shortcuts, you build new neural pathways. The old plateau dissolves because you're not operating on autopilot anymore. Luna: I want to push back a bit. That sounds great if your company has a different product line you can jump into. But what if you're in a smaller team, or you're early in your career and you don't have that latitude? Lucas: Fair pushback. And the answer is that context shifting doesn't have to mean changing your job title or project. It can be much smaller. You could, for instance, take a task you normally do in a familiar tool and force yourself to do it in a completely unfamiliar one. Or you could write a tutorial for beginners — teaching forces you to restructure what you know. Luna: So it's about artificially introducing constraints. Lucas: Yes. Another example: a financial analyst I know hit a plateau with Excel modeling. So she spent 30 days building the same models in Python — she barely knew Python. It was painful, she was slow, but by the end, her understanding of the underlying math was way deeper. Luna: That's a great example. So the principle is: when your skill feels stuck, don't look for more information — look for a different environment to apply what you already know. Lucas: That's it. And I think this is especially relevant in mid-2026, because so many of us are working in roles that are more specialized than ever. The risk is you become incredibly efficient at a narrow thing, and that efficiency feels like a dead end. Luna: Because efficiency is the enemy of growth at a certain point. Lucas: Exactly. When you're efficient, you're not learning. You're just executing. And the plateau you feel is your brain telling you, 'I've optimized this path. Give me a new map.' Luna: So practically, for a listener feeling stuck today, what's the first step? Lucas: Identify one skill you feel you've plateaued on. Then ask: what is one context I could shift into that would force me to use this skill differently? It could be a different audience, a different tool, a different time constraint, a different team. The key is that the new context must make you feel a little unsure of yourself. Luna: That's a hard ask. Most of us avoid feeling unsure. Lucas: That's why it works. And look, you don't have to stay in that uncomfortable context forever. Thirty days is enough. You'll either re-engage with the skill in a deeper way, or you'll discover that the skill itself isn't worth the investment — and that's useful information too. Luna: I love that. It's a low-risk experiment. Lucas: And if it's low-risk and it works, that's a pretty high return. Let me give one more concrete example from outside of tech. A friend who's a high school teacher — she was great at classroom management, but she felt like she was on autopilot. So she volunteered to teach a summer program for students with learning differences — completely different pacing, different strategies. Luna: And that shook up her approach. Lucas: Completely. She had to unlearn her usual techniques and build new ones. When she went back to her regular classroom in the fall, she was a better teacher — not because she learned a new theory, but because she had to adapt to a new context. Luna: So context shifting is a way to reset your skill trajectory. I think a lot of listeners will try this — I'm thinking about where I could do it myself. Lucas: Honestly, if today's episode was worth a coffee to you — maybe you're thinking about your own plateau and this gave you a concrete next step — that's the link: buy me a coffee dot com slash fexingo. It's the listener support that keeps this show ad-free and lets us keep drilling into these practical ideas. Luna: Yeah, and it really does make a difference. We hear from folks who say these episodes helped them get unstuck, and that's exactly why we do it. So if you're finding value, that's the place. Lucas: Back to the idea of plateaus — one thing I want to emphasize is that plateaus are not failures. They are signs of mastery at one level. The question is whether you want to stay there or push through to the next level. And context shifting is the lever. Luna: It reframes the stuck feeling as a signal, not a verdict. Lucas: Exactly. So here's a challenge for listeners: this week, identify one skill plateau you're facing. Then pick one context shift — small, uncomfortable, but doable. Commit to 30 days. And then let us know what happens. Luna: I'm going to try it myself with my data visualization skills. I've been using the same tool for years — time to try something else. Lucas: I'd love to hear how it goes. That's it for episode 113. We'll be back next time with another angle on building skills that actually matter for your career. Luna: See you then.