Latest / The Marketing Career Podcast with Fexingo: Marketing Jobs, Skills, and Career Growth / How Marketers Use a Career Skills Sprint
Transcript
- Lucas: So Luna, you remember that brand manager we talked about a few weeks ago, the one who was stuck in that campaign analysis role and wanted to move into marketing analytics? Luna: Yeah, the one who kept saying she didn't know where to start. She'd done a skills audit, found the gap, but then... nothing. Lucas: Exactly. And that's such a common trap. You audit, you find the gap, but then the gap feels too big, so you don't take the first step. So today I want to talk about a different approach: the career skills sprint. Luna: Career skills sprint. I love that name. What's the core idea? Lucas: It's a focused, time-boxed effort to close one specific skill gap. Think of it like a sprint in agile software development: a short, intense push toward a defined goal, usually two to six weeks. You pick one skill, you commit a set number of hours per week, and you finish with a tangible deliverable that proves you've learned something. Luna: So instead of saying 'I need to learn data analytics' you say 'I'm going to learn SQL to query our campaign database, and I'll build a dashboard to show my team.' That's a sprint. Lucas: Precisely. And the key is that it's not just about learning, it's about producing something. The deliverable forces you to apply the skill in a real context. And that's what makes it different from a skills audit, which is more about assessment. A sprint is about action. Luna: And a sprint has a clear finish line, which helps with motivation. I've started so many online courses that I never finished because there was no real deadline. A sprint creates a mini-deadline. Lucas: That's the beauty of it. It's a low-risk way to test-drive a skill. You're not committing to a full career change. You're just saying, 'For the next month, I'm going to spend three evenings a week on this, and I'll have something to show for it.' Luna: So how does one actually choose the right sprint? Because I could see someone getting paralyzed by the option. Lucas: The best sprint goals come from a genuine need in your current role or a clear next step you want to take. For our brand manager, she wanted to move into analytics, and she knew the team was drowning in Excel reports. So her sprint was: learn SQL basics, and then build a dashboard that automates one of those reports. Luna: That's a great example because it's tied to real work. It's not like 'learn Python' in a vacuum. It's 'learn SQL to solve this specific problem.' And that makes it easier to stay motivated. Lucas: Right. And the deliverable is something she can show in an interview or a performance review. It's not just 'I completed a course.' It's 'I built a dashboard that saves the team ten hours a week.' That's a tangible career asset. Luna: And that's a key point. The sprint is not just about the skill itself, but about the proof of application. That's what gets you noticed. Lucas: Exactly. So let's get into the mechanics. How do you structure a sprint? First, pick a single skill that's narrow enough to make progress in a few weeks. 'Learn marketing analytics' is too broad. 'Learn how to build a basic cohort analysis in Excel' is better. Second, set a time budget. Be realistic. Maybe two hours a day, three days a week, for four weeks. That's about twenty-four hours total. That's enough to get meaningful. Luna: And what about the plan? Do you need a detailed syllabus or can you just go? Lucas: You need a loose plan. Not a rigid day-by-day, but a week-by-week outline. Week one: basics, tutorials, small exercises. Week two: apply to a sample dataset. Week three: build your real-world deliverable. Week four: polish it, write a short summary of what you did and what you learned. That summary is gold for interviews. Luna: And how do you keep momentum? Because week three is always the hardest. That's where I usually start to fade. Lucas: A few tricks. First, tell someone about your sprint. A colleague, a mentor, a friend. Accountability is powerful. Second, schedule your sprint hours like meetings. Block them in your calendar. Third, celebrate small wins. Finish week one? Do something nice. It sounds simple, but it works. Luna: And what if you realize halfway through that this skill isn't for you? That's a valuable outcome too, right? You just saved yourself from a full career pivot. Lucas: Absolutely. A sprint is a low-cost experiment. If you discover that you hate SQL, that's information. It's not failure. You can cross that off your list and move on to something else. That's a win in itself. Luna: That's a great reframing. And it's so much better than the paralysis of not knowing what to do. You learn something about the skill and about yourself. Lucas: And that learning compounds. Do two or three sprints a year, and in a few years you've built a radically different skill set. It's like the compound interest of career development. Luna: I love that. So for someone listening who wants to try this, what's the first action? Should they email a friend? Write a goal? What's the immediate next step? Lucas: First, pick one skill that's directly relevant to a job you'd love to have in a year. Write it down. Then, set a six-week calendar block, and commit to a weekly time budget. And finally, tell one person. That's it. You've launched your sprint. Luna: And that's actionable right now. I'm actually thinking about a sprint for myself. Maybe I'll finally learn how to use a proper web analytics tool beyond the basics. Lucas: That's a perfect sprint. And it's something you could build a real dashboard for. By the way, this kind of practical, career-building conversation is exactly why we do this show. And if these episodes have sparked a sprint for you, or even just a new idea, you can support the show and help keep it ad-free at buy me a coffee dot com slash fexingo. Every little bit helps us keep diving into topics like this. Luna: Yeah, and it's a simple way to say thanks if the show's been useful. But back to sprints—one thing I want to make sure we cover is how a sprint can help with a career transition, not just a skill upgrade. Lucas: Right. A sprint is a great way to test-drive a new field before you commit. Say you're a content marketer who thinks you might want to move into product marketing. You could do a sprint on product messaging and positioning, and then write a one-page positioning statement for a hypothetical product. That gives you a portfolio piece and a feel for the work. Luna: And it's a lot less risky than quitting your job to 'find yourself.' You can do a sprint while you're still employed. That's the beauty of it. Lucas: Exactly. And the sprint output gives you something to talk about in informational interviews. Instead of saying 'I'm interested in product marketing,' you can say 'I spent six weeks learning how to write a positioning statement, and I built this example. Could you give me feedback?' That's a much stronger conversation starter. Luna: That's a pro move. It shows initiative and follows through. So what are some common pitfalls to avoid? Lucas: The biggest pitfall is trying to do too much. If your sprint goal is still too broad, you'll get overwhelmed and quit. So narrow it. Another pitfall is not scheduling the time. If it's not in your calendar, it won't happen. And a third is picking a skill that's not relevant to your career direction. You might learn something cool, but if it doesn't move you forward, what's the point? Luna: And I'd add: don't pick a skill you're not at least a little curious about. Passion helps. You're going to spend twenty hours on it, so it should be something that sparks some interest. Lucas: Great point. Curiosity fuels persistence. And if you're not curious, it's going to be a slog. So do a quick gut check: does this skill excite me a little? If not, find another angle. Luna: So to wrap up, the career skills sprint is a structured, time-boxed way to close a skill gap and build a deliverable that advances your career. It's low risk, high leverage, and it can be done while you're working full-time. Lucas: And the key takeaways: pick one narrow skill, commit to a time budget, schedule it, tell someone, and build something you can share. Do that two or three times a year, and you'll be amazed at how much your career changes. So, what's your next sprint going to be?