Latest / Career Coaching with Fexingo: Professional Coaches, Career Counselors, and Guidance for Workers / How to Use a 30-Day Career Experiment to Test a New Path
Transcript
- Lucas: So you've been in the same role for four years. It's fine — good pay, decent team, not miserable. But there's this nagging thought: what if I'd be happier — or better — doing something else? You don't want to quit and find out the hard way. Luna: That's the classic career limbo. You're not unhappy enough to leave, but you're not fulfilled enough to stay complacent. Lucas: Right. And the standard advice is 'take a class' or 'network more,' but those don't really simulate what the actual work feels like. So today I want to talk about a more structured approach: the 30-day career experiment. Luna: I love this. Before we dive in — and this ties in, honestly — we should mention that this show stays ad-free because a small group of listeners chips in monthly. If you've ever found yourself using one of our frameworks in a real conversation or decision, you can support us at buy me a coffee dot com slash fexingo. It genuinely helps us keep doing episodes like this. Lucas: And we mean that — no pressure, ever. But it's nice to know the show is listener-funded, not advertiser-driven. So back to the experiment. Luna: Define the experiment. What exactly is a 30-day career experiment? Lucas: It's a time-boxed, low-stakes project where you simulate the core tasks of a target role — ideally for a real stakeholder, even if it's just a friend's startup or a non-profit. The goal isn't to build a business; it's to test whether you actually enjoy the day-to-day reality of that career. Luna: So it's not a side hustle. It's a hypothesis test. Lucas: Exactly. Let me give you a concrete example. I talked to a woman named Priya — she was a marketing manager at Procter & Gamble for six years. She kept noticing she loved building the product spec sheets and user flows more than the ad campaigns. She wondered if product management was her real lane. Luna: But leaving P&G for a PM role at a tech company — that's a big swing. She'd probably take a pay cut. Lucas: She was afraid of exactly that. So she designed a 30-day experiment. She found a local non-profit that needed a volunteer to redesign their donation funnel. She committed to doing the work — user interviews, wireframes, prioritization — every evening and weekend for a month. She treated it as a real product manager gig. Luna: And what happened? Lucas: Two things. First, she confirmed she loved the work — especially the discovery phase, talking to users. Second, she discovered she hated the constant stakeholder negotiation when the board kept overriding her priorities. That was a real friction point she hadn't anticipated. Luna: So the experiment didn't just validate the role — it surfaced the parts she didn't like. That's huge. Lucas: Exactly. She went into interviews later armed with that honesty. She told hiring managers, 'I know I need a team where product decisions are data-driven, not political.' She ended up at a mid-size SaaS company — no pay cut, because she could speak to actual PM experience from the experiment. Luna: I think a lot of people skip the experiment because they think they need a perfect idea or a side business. But the bar is much lower — just a real project for a real user. Lucas: Right. And the 30-day window is key. It's long enough to push past the honeymoon phase — around day ten you hit the slog — but short enough that you don't lose your nerve or your savings. You're not quitting your job. Luna: So how do you actually structure it? Let's say someone listening is a teacher who's curious about instructional design. Lucas: Great example. Step one: define the hypothesis. Not 'I want to be an instructional designer,' but 'I want to test whether I enjoy creating asynchronous learning modules and working with subject matter experts.' That's specific. Luna: Then what? Where do you find the project? Lucas: Step two: find a real stakeholder. A friend who runs a training program, a local community college, a small online course creator. Offer to build one module for free — in exchange for feedback and a testimonial. Most people will say yes. Luna: And step three — measure success. Lucas: Define what 'learning' looks like. Not 'did I get a job offer?' but 'did I enjoy the process? Did I dread the work? What did I learn about the day-to-day?' Priya used a simple journal: each day she rated her energy level on a scale of one to ten while doing the work. By day twenty, she saw a clear pattern. Luna: That's smart. The data doesn't lie. And it helps you avoid the trap of romanticizing a career. Lucas: Exactly. I think the biggest barrier is perfectionism. People think their project has to be impressive enough to put on a resume. No — it just has to be real. Your first wireframe might be ugly. That's fine. You're testing, not impressing. Luna: And if the experiment fails — meaning you realize you don't actually want the role — that's a win too. You saved yourself years of regret. Lucas: Huge win. One of the most expensive career mistakes is switching into a field you've idealized without testing the reality. A 30-day experiment costs you some evenings and maybe a little pride. That's it. Luna: So what's the one thing someone should do right now if they're intrigued? Lucas: Write down one career hypothesis. Just one sentence. 'I want to test whether I enjoy X more than my current Y.' Then identify one person who could use help with that X. Reach out this week. That's the whole start. Luna: And if you do it, let us know how it goes. We love hearing about listeners' experiments. Lucas: We do. And if you want more frameworks like this, you know where to find us — buy me a coffee dot com slash fexingo, or just tune in next week. We'll be talking about how to negotiate a raise using a 'personal board of directors.' That one's a good one. Luna: See you then.