Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Career Value of a Weekly Learning Hour
Transcript
- Lucas: So I was talking to a product manager at a midsize SaaS company — 400 employees, B2B analytics platform — and she told me about a boundary she set two years ago that completely redirected her career. Luna: I'm guessing it's not 'stop checking Slack after 6 PM.' Lucas: No, but close. She blocked one hour every Thursday morning — no meetings, no email, no Slack — for learning. Just her, a laptop, and a specific skill she wanted to build. She called it her 'learning hour.' Luna: One hour a week? That seems almost laughably small. Like, what can you really learn in an hour a week? Lucas: That's exactly the reaction most people have. But here's the thing — she used that hour for what researchers call 'deliberate practice.' Not passive reading. Not watching a tutorial at 1.5x speed. She would pick one narrow thing — say, writing a Python script to automate a report she normally did by hand — and she'd work through it, fail, debug, repeat. Luna: So she was actually coding during that hour, not just skimming articles. Lucas: Exactly. And over 18 months, that's roughly 78 hours of focused, iterative skill-building. She went from being a product manager who knew a little SQL to someone who could build basic machine learning models. She eventually pivoted internally to a data science role. Luna: Seventy-eight hours — that's less than two work weeks. But it's distributed in a way that actually sticks. I read a study once that said the optimal spacing for skill retention is about 24 hours between practice sessions. A weekly cadence is way better than a once a quarter bootcamp. Lucas: Right. And the 70-20-10 model of learning — you know, 70% from on-the-job experience, 20% from social learning, 10% from formal instruction — that 10% is often the most neglected. Companies pour money into onboarding and then just assume people will pick things up as they go. Luna: But here's my pushback. A product manager at a SaaS company with a supportive boss — that's a pretty privileged scenario. What about someone who works retail, or in a factory, or even in a law firm where every billable hour is tracked? A weekly learning hour feels like a luxury. Lucas: It is harder in those environments. But I'd argue that's exactly where a learning hour has the highest ROI. If you're in a job with limited upward mobility, a small, consistent investment in a portable skill — something like data analysis, or even writing — can be your ticket out. Luna: But how do you even find the hour? When I worked at a big law firm, my day was booked in six-minute increments. There was no 'learning hour.' Lucas: So you hack it. Maybe it's not a full hour at work — maybe it's 45 minutes during lunch, or a 30-minute block before anyone else logs on. The cadence matters more than the duration. And if your employer allows any kind of professional development budget, use it to buy a course that forces you to show up weekly. Luna: I've seen some companies actually institutionalize this. There's a tech company called Buffer that tried a 'learning Friday' — but they found people just used it to catch up on email. So they switched to a 'no-meeting Wednesday morning' specifically for learning. Lucas: That's smart. The key is that it has to be protected. If it's just 'we encourage learning,' it gets eaten by the urgent. One study from the Corporate Executive Board — now part of Gartner — found that companies where managers explicitly protect learning time see 14% higher retention, especially among high performers. Luna: Fourteen percent — that's not nothing. Especially when replacing a high performer can cost 200% of their annual salary. Lucas: Exactly. So the learning hour isn't just a personal career boundary — it's a retention strategy. And I think the reason it works is that it signals to the employee: 'I care about your future, not just your output this quarter.' Luna: But let's be real — most managers won't proactively offer this. So how do you ask for it without sounding like you're trying to slack off? Lucas: Frame it as a win-win. Say, 'I want to spend one hour a week learning so I can for the team. Can we block that time on my calendar?' The more concrete the outcome, the harder it is to say no. And if they still say no, you have your answer about that workplace. Luna: That's a good litmus test. I think a lot of people are afraid to even ask because they assume the answer is no. But the worst they can say is no, and then you know where you stand. Lucas: And if you're self-employed or freelance, you have even more control — but also more temptation to skip it. I've found that scheduling it as a recurring appointment with myself, and even telling a friend or a colleague about what I'm working on, creates enough accountability to actually do it. Luna: Speaking of accountability — and I know this is a little meta — but we talk about boundaries like this every week, and for some listeners, this show itself might be part of their learning hour. And that actually points to something we haven't really mentioned. Lucas: What's that? Luna: The fact that we can keep making this show, ad-free, every single day, is because a small group of listeners chips in through buy me a coffee dot com slash fexingo. It's a really simple thing — no tiers, no perks, just people who find value in what we do and want to keep it going. Lucas: Yeah, and honestly, that support is what lets us spend the time researching and scripting these episodes properly. If we were chasing ad revenue, the topics would probably be very different. So if this show has helped you think through a career boundary or a decision, and you're in a position to throw a few bucks in the virtual tip jar, it truly makes a difference. Luna: And if not, no worries at all. We're glad you're here either way. Lucas: Alright, back to the learning hour. One thing I want to emphasize is the compounding effect. If you invest one hour a week in a skill for a year, you've put in 52 hours. That's basically an entire work week and a half focused on your own growth. No one else is going to do that for you. Luna: And if you do it for three years, that's 156 hours. That's enough to go from beginner to competent in most technical skills. I think people underestimate how fast they can progress with consistent, focused effort. Lucas: Absolutely. And the beauty is, you don't need to know exactly what you want to learn in advance. You can cycle through a few topics. Maybe you spend three months on Python, then three months on presentation skills, then three months on basic accounting. Each one adds a new tool to your belt. Luna: That's a good point. I've done something similar — I spent a year learning Spanish with a weekly tutor. One hour a week, every Wednesday. After a year, I could hold a decent conversation. Not fluent, but functional. And that felt amazing. Lucas: So what's the one thing you'd tell someone who wants to start a learning hour tomorrow? Luna: Pick a skill that you can practice actively. Not just consume. So not 'I'll watch YouTube videos about data science' — but 'I'll work through one chapter of that data science textbook and do the exercises.' Active beats passive every time. Lucas: I'd add: protect the time like it's a meeting with your CEO. Because in a way, it is. It's a meeting with your future self. Luna: That's a good note to end on. So here's the question for listeners: What's the one skill you'd start learning if you had a protected hour every week? And what's stopping you from blocking that time starting this week? Lucas: We'll be back tomorrow with another episode. Until then, keep that hour sacred.